Participant pathways, outcomes with evidence, and a file that matches the data import sheet — built for CICs and funded programmes, not for a pitch deck.
A community interest company takes referrals, assesses people, delivers support, and is contracted on outcomes — often employment, training starts, or sustained job outcomes. The funder issues a data import sheet: fixed columns, coded stages, dates that must not invert. Staff have the story in case notes. The sheet wants integers. Every quarter someone copies between them and discovers a participant who was “in work” without an evidence file.
A pathway object: referral → assessment → intervention → outcome. Each stage has owners, dates, and optional evidence (offer letter, wage slip redacted, attendance log). Reports are generated from that model into the funder’s shape. If a required evidence type is missing, the row fails validation instead of shipping a rounded success.
That is what we built for a CIC in Impact Tracker. It is closer to document intelligence than to a CRM theme pack.
We sit with the contract and the last accepted import sheet. Those columns are the schema. Then roles (case worker, manager, auditor), a pathway UI that case workers will actually use, and an export. First funder in 30 days if the pathway is one contract. A second funder with a different sheet is a mapping problem, not a new product — unless they define “outcome” differently, in which case we keep two schemas.
We will tell you what we would validate before a row can export.
→ Book a call