Milestone documentation
- Deliverables and submissions
- Reports and supporting files
- Connected to the milestone
Platform · Evidence & Verification
Build evidence into execution - not into a reporting scramble.
Impact reporting becomes more credible when the reported result stays connected to the underlying execution record. CSRise connects milestones, documentation, approvals, and outcomes into a traceable program record.
Canonical verification record demonstrating cryptographic provenance and dual-authorization compliance.
The evidence chain
One traceable line from capital to reported impact.
- 01Capital allocated
- 02Implementation partner
- 03Milestone
- 04Evidence
- 05Beneficiary / activity record
- 06Review / verification
- 07Reported impact
If a reported outcome is challenged, the claim can be traced back to the underlying record.
A structured evidence trail
Connect supporting records
to the relevant milestone.
Instead of storing evidence in disconnected folders, chats, emails, and reports, CSRise keeps supporting records attached to the program and milestone they substantiate.
Beneficiary & activity records
- Field activity
- Beneficiary information, where applicable
- Location and date context
Review & sign-off
- Structured evidence review
- Comments and decisions
- Approval status, where supported
Retrieval & traceability
- Retrieve evidence when a result is questioned
- Trace reporting back to records
- One connected program record
What the record statuses mean
Four statuses. Four distinct meanings.
Submitted
Evidence has been uploaded or provided against a milestone or activity. No review has taken place yet.
Reviewed
An authorized reviewer has examined the record. This does not yet mean the record has been formally approved.
Approved
The relevant internal approval has been recorded against the milestone, activity, or disbursement request.
Verified
Defined verification steps have been completed according to the applicable CSRise workflow for that record type.
These are operational statuses, not independent assurance opinions. Read the full methodology
Separate roles
The person who reviews it
does not pay for it.
Review, approval and payment are different responsibilities, held by different people - and the platform enforces that for each payment, not just by job title.
Reviewer & approver
- A reviewer compares evidence with the milestone acceptance criteria and may request clarification.
- A designated approver gives the final milestone approval, within delegated authority.
- A reviewer cannot authorize payment for a milestone they reviewed.
Payment kept separate
- Evidence approval never triggers payment.
- Payment is authorized separately - by one approver, or two independent approvers above a configured threshold.
- Finance records the bank transfer reference and receipt; a different finance user confirms reconciliation.
Versioned evidence
- Submissions, acceptance criteria and review decisions are versioned.
- Approved evidence cannot be silently replaced.
- Earlier versions stay accessible.
Internal review is a workflow status, not independent verification or an assurance opinion. Product design for the controlled pilot.
Connected modules
Explore the rest of the platform.
Start a conversation
Follow the evidence from capital to reported impact.
See how milestones, documentation, review, and outcomes connect within one accountability record.