Stakeholder & Investor Reports

Stakeholder & Investor Reports defines a repeatable external-reporting structure. Agree sections once and reuse them for each period while identifying who verified each number. The workflow gathers data, verifies it, drafts sections, obtains approval and sends the report with a version marker. A fixed section list and named verifier address version drift and unsupported numbers. The register retains stakeholder, period, preparer, approver, key metrics, send date, report link and status. The send step describes the business process; an empty register does not distribute a report.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it when investor updates or board packs are rebuilt each period and previous figures or verification responsibilities are inconsistent. It does not produce audited figures, calculate KPIs or provide investor or legal advice. Qualified reviewers must approve material figures and disclosures before distribution.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Ask who reads the report, whether investors or the board and how often; material numbers, narrative and confidential detail; data sources, verifier and approval process; current effort and omissions; and whether a report structure or underlying data is wanted. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Report Title (text); Stakeholder (text); Period (text); Prepared By (text); Approved By (text); Key Metrics (text); Send Date (date); Report Link (url); Status (select); Report ID (id).

Status starts with Draft, Circulated, Reviewed, Published.

Report Link maps to a URL property. The agreed process must retain its number-verification ownership and version marker even though the starter register has no dedicated fields for those details.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE INDEX idx_stakeholder_investor_reports_status ON stakeholder_investor_reports (status);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.