Reports & Analytics

Reports & Analytics defines a Scale-stage Analyze setup for an insights hub. Its starting recommendation is a fixed monthly pack containing a small set of numbers and one comment per number, while removing reports nobody reads. The workflow covers gathering data, calculating a metric, writing commentary, circulation and recording an action. These are responsibilities in the proposed process, not automated capabilities of the generated template. The register records report type, source modules, owner, audience, frequency, run dates, report link and status so reporting work has a consistent structure.

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 for periodic reporting templates, an insights register or a report set whose readers and actions are unclear. It does not gather source-system data, verify accuracy or calculate KPIs. Scheduled and Running are status labels rather than a built-in scheduler.

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 reports and how often; required numbers, comparisons and narrative; available sources, preparer and effort; existing production, manual work and trust; and whether the outcome is a report set, template or underlying data. 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 Name (text); Report Type (select); Source Modules (text); Owner (text); Audience (text); Frequency (select); Last Run (datetime); Next Run (datetime); Report Link (url); Status (select); Report ID (id).

Report Type starts with Operational, Financial, Management, Compliance, Custom. Frequency starts with Daily, Weekly, Monthly, Quarterly, Half Yearly, Annual. Status starts with Scheduled, Running, Published, Failed.

Last Run and Next Run are datetime fields; Report Link is a URL property in the Notion mapping.

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_reports_analytics_status ON reports_analytics (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.