Who Can Generate and Approve Reports
Report generation and approval are restricted to users with the appropriate role:
Field Officers submit the data that feeds reports but don’t access the report generation or approval flow. This separation keeps sensitive programme narratives and funder communications inside the authorized team.
Before You Generate a Report
The Reports button on a project appears only once the project meets two preconditions:- At least one published form exists on the project, and
- That form has approved submissions feeding it.
The Approve/Reject step on submissions is what decides which data reaches the report. Only approved submissions feed the AI. Rejected or pending submissions are excluded automatically.
Generating a Report
1
Open the Reports tab
Navigate to your project from the Projects sidebar and open the Reports tab at the top of the project page.
2
Click Generate Report
Click the Generate Report button. A setup panel slides in from the right.
3
Select a report type
Choose the type that matches your reporting need. Terriqon currently offers four, with more planned.
Project Report
A narrative covering activities, outputs, and outcomes for a single project — useful for internal reviews and project-level funder updates.
Ops Report
An operational view of team activity, submission volume, and data completeness across the project.
Donor Report
A funder-facing narrative covering KPIs, outcomes, and impact — formatted for external distribution.
Portfolio Report
A cross-project roll-up: KPIs and trends aggregated across every project in your organization.
4
Confirm and start generation
Click Generate. The report moves through Queued → Generating → Pending Approval, and the AI typically finishes drafting in about 30–60 seconds. You can navigate away and continue other work — Terriqon runs the generation in the background.
5
Receive the notification
When the draft is ready, you receive both an in-app notification and an email. Click the notification to go directly to the review screen.
Reviewing the Draft
Every AI report is drafted into the same set of sections, so you always know where to look:- Executive Summary — a high-level snapshot of project performance
- Key Findings — data-driven insights from your submissions
- Recommendations — AI-suggested next steps
- KPI status — where each KPI stands against its target
- Statistical tables — aggregates and breakdowns from your submission data
Fields you tagged as Personally Identifiable or Restricted during form design are excluded from the dataset the AI receives, so the draft is built from aggregated, anonymised metrics only. If a report references personal data you didn’t intend to include, the fix is to tag that field on the form before your next report — see Building Forms → Tagging Sensitive Fields.
Editing the Report
Every section of the report narrative is editable inline. Click any paragraph or heading to activate the text editor for that section. Common edits include:- Adding programme context the AI couldn’t infer from submission data alone
- Adjusting tone to match your organization’s voice or a specific funder’s expectations
- Correcting figures if you spot a data anomaly
- Inserting a quote or case study from your field team
Once approved, the report is final. If you need to make changes after approval, generate a new report from the Reports tab rather than trying to modify the approved document.
Approving a Report
When the draft reads accurately:1
Click Approve
Click the Approve button in the top-right of the review screen. The approval is logged in the report’s audit trail with your name, role, and timestamp — creating a defensible chain of custody from field submission to approved funder deliverable.
2
Download or share
The approved report becomes available to download as a PDF or DOCX. Share it directly with your funders or attach it to a grant report.
Rejecting a Report
If the draft is inaccurate, incomplete, or otherwise unsuitable:1
Click Reject
Click the Reject button in the top-right of the review screen.
2
Enter a written reason
A reason is required (up to 255 characters) — a short, clear explanation like “Submission count too low for Q3; collect more data from the northern district before regenerating.” This reason is visible to all Admins and Managers on the project and is recorded permanently in the audit trail.
3
Confirm rejection
Click Confirm Rejection. The report returns to Draft status, ready to be regenerated once you’ve addressed the underlying issue — usually by getting more submissions approved, or by fixing a form field tag.