Take the most ordinary gift a growing nonprofit receives: $250 a month, restricted to a shelter programme, from a household that has given for three years. Follow it end to end and the operational surface becomes obvious.
The chain
- Contributor — the household and legal donor, with their recognition preference.
- Campaign or appeal — the source that attributed the gift, including its UTM origin.
- Payment — the transaction with gross, fee and net, plus its retry history.
- Recurring plan — the schedule, next charge date and failure state.
- Pledge — if the monthly gift fulfils a multi-year commitment, the installment it satisfies.
- Payout and deposit — the batch that carried it and the bank line that received it.
- Allocation — the restricted fund balance it increased.
- Fulfilment — the programme spend or delivery that consumed the restriction.
- Evidence and outcome — what was verified, by whom, and what the donor is told.
Where teams lose the thread
Most stacks hold the contributor, the payment and the campaign. The payout, allocation, fulfilment and evidence live in spreadsheets, programme reports and email threads — which is why the answer to 'what did my monthly gift do' takes a week to assemble and is written in general terms.
Honest status
The interactive lifecycle trace on our homepage walks this exact chain against demo data in the product. Impact evidence and fulfilment are built and demonstrable; they are not yet running on a production organisation's programme data.