01
Evidence LockEvery claim, metric and statutory detail must trace to an approved source. Critical metric conflicts must be resolved or explicitly excluded.
Owner · Documentation Lead
Publication Control
Nothing becomes final
until the evidence is locked.
SCF's Evidence Lock separates drafting from publication. A claim, metric, statutory detail, financial figure, image or story may enter the working report before it is publishable—but it only moves into the approved publication file after source traceability, reconciliation, qualified review and governance approval are complete.
FY 2025–26 Production Control Snapshot
Current readiness is visible, not hidden.
This snapshot reflects the existing annual-report verification and production-control map. It is a control-state view—not a claim that the report is already publication-ready.
69Total mapped report pages
46Need evidence / verification
31Critical-risk pages
12Need approval
4Awaiting financials
NOReady for final PDF
Five Publication Gates
Evidence before design. Approval before release.
02
Governance & FinanceGovernance, related-party disclosures and financial figures require the appropriate CS, CA, auditor and Board review.
Owner · CS / CA / Board
03
Visual AssetsImages and stories require traceable caption, date, location, credit and consent status. Identifiable content with missing/invalid consent is excluded.
Owner · Communications / Safeguarding
04
Design & PreflightText, charts and visual pages are proofread and checked for data consistency across print and digital proofs.
Owner · Design / Documentation
05
Publication ApprovalThe final controlled PDF is released only after the designated institutional authority completes publication approval.
Owner · Board / Authorized Publication Owner
Publication Status Codebook
A working claim and a publishable claim are different things.
| Status | Meaning | Publication rule | Control owner |
|---|---|---|---|
| Draft | Claim entered but not yet checked. | Internal working use only. | Claim owner |
| Pending | Evidence or approval incomplete. | Internal working use only. | Claim owner / reviewer |
| Blocked | Material variance, consent gap or approval failure. | Do not publish. | Evidence Lock Lead |
| Locked | Evidence, reconciliation and approvals complete. | May enter the approved publication file. | Evidence Lock Lead |
Publication rule: the final public file should contain only Locked claims—or explicitly authorised statements whose limitation is clearly disclosed.
Unit Discipline
Contacts, people, referrals and visits are not interchangeable.
| Unit | Definition | Key reporting rule |
|---|---|---|
| Distinct person | One deduplicated beneficiary/patient, normally by UCID where applicable. | Never combine with service contacts or episodes. |
| Service contact | One interaction or attendance. | One person may contribute more than one contact. |
| Referral | One documented referral event. | Referral issued and referral completed remain separate. |
| Visit | One physical, home or hospital visit. | One person may have multiple visits. |
| Treatment / support episode | One surgery, cycle, procedure, counselling or other support episode. | Do not treat as a distinct-patient count. |
Evidence Certification
The final file should be reproducible from its source trail.
Claim IDsEvery published quantitative claim has a traceable claim identifier.
Primary source archiveSource IDs and controlled archive paths are recorded.
Register reconciliationRegister totals reconcile to approved publication values.
Codebook matchUnits, reporting periods and indicator definitions match the approved codebook.
UCID deduplicationCompleted wherever annual distinct people are claimed.
No false annualisationMonthly caseload or service episodes are not multiplied into annual unique-person totals.
Consent controlIdentifiable stories and media have valid, traceable consent and approval links.
Change LogFinal corrections and accepted exceptions are recorded before release.
Known Publication Blockers
Critical issues stay visible until resolved.
| Area | Current control concern | Required before release |
|---|---|---|
| Financial overview | Audited financial statements / ledgers awaited. | CA / auditor verification and Board approval. |
| Cash, subsidy & in-kind | Resource categories must remain separate. | Documented valuation and disclosure basis. |
| Programme-wise resources | Shared-cost allocation requires a documented method. | Approved allocation methodology and source records. |
| Partner / network representation | MoUs, service scope and permission require confirmation. | Approved partner record before public logo/name use where required. |
| Camp/community geography | Spelling, repeats and 54 distinct communities require reconciliation. | Clean master register. |
| Indicator definitions | Different units and historical figures can create apparent conflicts. | Codebook-led reconciliation working papers. |
| Statutory information | Only verified current details should be released. | CS / governance verification. |