use case
Report against agreements from live records.
Reporting obligations are met from the same records the work produced, with figures traceable back to the submissions and files that generated them.
the problem
Reporting is reconstructed, not recorded.
Most reporting is assembled retrospectively from spreadsheets, emails and recollection, then reconciled against the agreement under deadline pressure.
Duplication across funders
The same activity is reported differently to several funders, each in its own format.
Figures are hard to verify
Numbers arrive without a clear path back to source records.
Late reporting has consequences
Delays put current funding and future eligibility at risk.
the process
How it runs in Tsen’awt.
Reporting reads from the record instead of rebuilding it.
Activity captured as it happens
Form submissions and files record delivery during the period, not after.
Reports generated by period
Figures are drawn by programme, department and date range.
Narrative drafted in place
Reporting text is written against the figures it explains.
Approved and submitted
Sign-off is routed, recorded, and the submitted package retained.
what it uses
The parts involved.
This process is built from parts of the platform working together.
Forms
Structuring the delivery data reporting depends on.
Reporting & Compliance
Producing the figures and packages funders require.
Automated Workflows
Routing approval and triggering on deadline.
Activity
Evidencing the approvals and submissions.
outcome
What it changes.
Reporting periods stop being a crisis.
Traceable figures
Every number can be followed back to its source record.
Less duplication
One structured record supports multiple funder formats.
Reliable timing
Reports are ready before the deadline rather than at it.
next step
Bring this into your Nation.
We start with an assessment of how your departments already work, then bring that work into the environment one area at a time.