Auroranexis

Reports package operational outcomes for client conversations. Auroranexis supports reusable templates, draft and published lifecycles, scheduled generation, PDF export, email delivery, and client portal publishing. Every report is linked to a client and can surface health scores, SLA metrics, and related open risks and incidents in a consistent format your agency controls.

Overview

The Reports module spans the full lifecycle: define structure in templates, generate content for a reporting period, review and edit, then publish or export. Reports → Templates holds reusable section layouts your agency standardizes on; Reports → Schedules automates recurring generation where your plan allows.

Report statuses progress from draft through generated to published. Draft reports are internal work in progress. Generated reports have metrics and default narrative populated for the selected period. Published reports are finalized and eligible for portal delivery, PDF export, and email. Archived reports remain for history but are not actively delivered.

The report detail page shows version history, metrics captured at generation time, delivery options, and activity logging. Each report links to exactly one client, which determines portal audience and which operational data feeds into generated sections.

Templates reduce preparation time and enforce consistency across account managers. Schedules help teams meet contractual cadence without manual reminders, though every generated report should still pass human review before publishing to clients.

Purpose

Clients expect periodic visibility into what your agency delivered and what needs attention. Reports standardize that narrative—executive summary, key wins, risks, next actions, and operational metrics—so every account manager presents consistent, defensible information in QBRs and email updates.

Template-driven reporting reduces preparation time and improves quality control. Instead of rebuilding slide decks from scratch, operators start from agency-approved structure, generate period-specific metrics, edit narrative sections, and publish through channels clients already use.

Published reports in the client portal create a durable record of what you communicated externally. That history supports renewal conversations, dispute resolution, and internal audits when questions arise about what the client was told and when.

Core Concepts

Report lifecycle

Report status values

Status	Description
Draft	Work in progress; not visible to clients; may lack generated metrics.
Generated	Content and metrics populated for the reporting period; ready for review.
Published	Finalized; eligible for client portal, PDF export, and email delivery.
Archived	Retained for history; not actively delivered or promoted externally.

Templates and schedules

Template — reusable structure for sections and default content your agency standardizes on.
Schedule — ties a template and client to a recurring generation cadence when your plan includes scheduling.
Reporting period — start and end dates that frame metrics and narrative content for each report.
Sections — typical areas include executive summary, key wins, key risks, next actions, and operational metrics.

Features

Report templates with configurable sections under Reports → Templates.
Create reports linked to a client and reporting period.
Generate draft content including executive summary, wins, risks, and next actions.
Capture health score and SLA score at generation time.
Edit narrative sections after generation while status remains internal.
Publish to client portal with activity logging.
PDF export from the report detail page.
Email delivery with PDF attachment where enabled.
Schedules for automated generation under Reports → Schedules.
Version history for published report iterations.
Archive workflow for superseded reports without deleting history.
Client-linked report lists on client detail pages.
Role-based permissions for create, generate, publish, and archive actions.
Integration with operational modules for metrics and linked risk references.

Step-by-step usage

Open Reports → Templates and create or select a template that matches your delivery format.
From Reports, create a new report and choose the client and reporting period dates.
Save as draft and confirm the linked client and period are correct before generating.
Run Generate to populate metrics and default narrative sections from operational data.
Review and edit executive summary, key wins, key risks, and next actions for accuracy.
Conduct internal peer review while status is draft or generated—never publish prematurely.
Publish when the report is client-ready; confirm activity shows published status.
Verify portal users exist on the client detail page if external portal delivery is required.
Export PDF or send by email from the report detail page as needed for non-portal stakeholders.
Optionally create a schedule under Reports → Schedules for recurring generation on the same template.
After client feedback, archive superseded versions rather than deleting published history.
Reference the published report in your next client meeting and update risks if new issues emerged.

Best Practices

Assign a report reviewer who is not the primary author for strategic accounts. A second pair of eyes catches metric mismatches and client-facing language issues that authors overlook after hours of editing.

Maintain separate templates for executive summaries, monthly operations, and post-incident reviews.
Generate before editing so metrics reflect the correct reporting period boundaries.
Conduct internal review while status is draft or generated—never publish prematurely.
Align report cadence with contract obligations and QBR calendars.
Reference linked risks and incidents when clients expect transparency on open items.
Archive superseded reports rather than deleting history clients may have viewed.
Use consistent template naming so staff select the correct format under time pressure.
Confirm portal users are active before publishing sensitive operational content.
Store PDF exports for accounts without portal access to maintain delivery records.
Review schedule output promptly—automated generation still requires human approval before publish.

Examples

Marketing agency

A marketing agency uses a Monthly Operations template for all retainer clients, generates on the first business day of each month, and publishes after the account director reviews key wins and risks. Portal users at each client access reports without email attachments.

AI automation agency

An automation agency publishes quarterly executive summaries highlighting integration uptime from linked monitoring data and open incidents resolved during the period. They maintain a separate post-incident template for failure reviews shared selectively through PDF export.

MSP

An MSP schedules weekly operational reports for Premium clients using Reports → Schedules, triages generated drafts during Monday standup, and publishes by midday. Standard-tier clients receive monthly reports with SLA compliance sections generated from assigned policies.

Consultancy

A consultancy produces engagement-close reports from a custom template with next actions and lessons learned, publishes to portal users on the client steering committee, and archives reports when follow-on work begins under a new reporting period.

Enterprise deployment

A large agency enforces three approved templates globally, requires admin publish approval on Critical-status clients, and exports PDF batches for legal records. Schedules run per region with local account owners responsible for narrative edits before publish.

Troubleshooting

Common reports module issues

Problem	Cause	Solution
Report not visible in client portal	Not published or no portal users	Confirm status is Published and active portal users exist on the client detail page.
Generate action unavailable	Report not in draft status	Only draft reports can be generated; check current status on the report detail page.
Metrics missing or zero in generated report	No operational data in reporting period	Verify incidents, SLA activity, or health data exists for the client during the selected dates.
PDF export fails	Transient generation error	Retry after a few minutes; contact support if the issue persists across attempts.
Schedule did not run

FAQ

What is the difference between draft and generated?: Draft is an empty or partially edited report. Generated means the platform populated metrics and narrative content for the selected period. Both are internal until published.
Can I edit a published report?: Published reports are finalized for client delivery. Create a new version or archive the report and produce an updated draft if material changes are required.
Do reports require a template?: Templates standardize structure and speed creation. You can work from an existing template or create one under Reports → Templates before generating reports at scale.
Which roles can publish reports?: Publishing requires report lifecycle permissions assigned to your role. Staff may create and generate; owners and admins typically control publish actions.
Are schedules available on all plans?: Scheduled reporting availability depends on your subscription. Review Settings → Usage and Settings → Billing for plan-specific limits.
Do published reports update if client health changes?: No. Metrics reflect values at generation time. Regenerate or create a new report if you need updated figures after significant operational changes.

Need help?

Contact support@auroranexis.com for onboarding support, billing questions, or product guidance. Include your workspace name, the module you are working in, and a brief description of your goal so we can respond efficiently.

Delivery channels

Published reports can be viewed in the client portal by active portal users on the linked client. PDF export supports attachments for email or offline QBR decks. Email delivery with PDF attachment is available where configured in Settings → Email and on the report detail page.

Portal delivery requires published status and at least one active portal user. Internal reviewers should confirm narrative accuracy and metric alignment before publishing because clients may see content immediately.

Metrics at generation

When you run Generate, the platform captures health score, SLA compliance metrics, and related open risks and incidents for the selected client and period. These values reflect point-in-time operational state and do not retroactively change if underlying data shifts later unless you regenerate.