Participant pathways from referral to employment, outcomes recorded with evidence, reports a funder can import without a cleanup week.
A community interest company ran a funded employability programme. Case notes lived in one place. The funder’s data import sheet lived in another. Quarter-end meant copy-paste and a row that claimed a job start without an evidence file. We built the pathway as the source of truth. The sheet became an export. More context: funder impact reporting software.
Referral → assessment → intervention → employment (or another contracted outcome). Each stage has a date, an owner, and a closed reason. You cannot mark employment without an evidence type the contract named. Dates cannot invert. That is boring software. It is the software they needed.
An outcome is a record plus a file (offer letter, redacted wage proof, attendance). The file is stored; the outcome stores a hash and who attached it. Deleting the file re-opens the outcome. Managers see a queue of outcomes that would fail the import sheet.
Export maps pathway fields onto the funder’s columns and codes. Validation runs first. Invalid rows stay in the product. We did not build a dashboard of “lives changed.” We built a sheet that matches last quarter’s accepted file. Same fail-closed habit as document intelligence.