Funding delivery and evidence governance
This guide covers the hand-off from panel selection to authorised funding delivery, the evidence register's source records, review history, retention model and intended production access boundary.
The current Funding Delivery and Funding Evidence Register interfaces operate on browser-local preview records and local document files. Migration 0002 creates a production-oriented D1 metadata and ownership foundation. It explicitly does not store file bytes or provide the object-storage adapter and server endpoints needed for live evidence operations.
1. Selection-to-delivery hand-off
Funding Delivery is intentionally downstream of adjudication. Its case builder reads the application, active evaluator assignments, evaluator submissions, adjudication decision and application workflow record. It filters out cases whose version, form or rubric references do not match, cases with incomplete active reviews, conflicted submissions, and cases without a Selected panel outcome.
The selected panel outcome remains a recommendation/selection gate. The separate approval record captures the CEDA authority, approval reference, date, approved amount and rationale.
2. Funding delivery record structure
The preview funding record contains distinct sections for approval, offer, acceptance, contract, conditions, tranches, milestones and evidence reviews. This separation makes it possible to show where a case is waiting without collapsing every post-selection activity into one generic “approved” status.
A production service should persist each transition with its actor, authority, timestamp, source case version and an auditable reason. It should also prevent browser-submitted workflow values from acting as authoritative approvals.
3. Funding Evidence Register aggregation
The register builds one inventory from four evidence target types:
- applicant-document: attachments required by the published funding enquiry form;
- offer-acceptance: evidence supplied with an applicant's offer response;
- condition: files supplied to satisfy a funding condition;
- milestone: files supplied to support a delivery or monitoring milestone.
Each evidence item retains its competition, application, response version, form version, target type, target ID, target title, attachment metadata and review status. Applicant-document reviews remain owned by the Operations Document register; the central funding evidence inventory provides visibility and metadata rather than silently transferring that review authority.
4. Review and replacement history
A review applies to a specific evidence target and the file set reviewed at that time. When an applicant replaces a file, a prior acceptance must not automatically apply to the new bytes. The register preserves the historical reviewed-file snapshot and evaluates whether the latest review still matches the current attachment set.
The production schema uses append-only review events, links a review event to the exact evidence files and records a file-set SHA-256 value. This makes the audit trail capable of describing which version was reviewed, rather than only showing a mutable current status.
5. Evidence metadata and ownership model
Migration 0002 defines separate entities for applicant organisations, memberships, application ownership, evidence objects, review events, the exact files included in a review, retention events and access-audit events.
The application scope is the authoritative link between an application and an applicant organisation. The migration comment explicitly warns not to derive that ownership from browser-submitted IDs, email addresses or a client-side profile object.
6. Production access policy
The reference policy is deny-by-default. Applicant leads and team members are limited to their verified organisation's applicant-visible evidence. Funding programme administrators are constrained by funding programme scope. Evaluators, eligibility reviewers and adjudicators require their own assignment or panel scopes. Platform administrators receive identity and access administration by default; they do not automatically inherit access to confidential application content.
This policy is implemented as a reference helper in apps/web/lib/ceda/evidence-access-policy.ts. Every production endpoint that lists metadata, views a file, assigns a reviewer, records a decision, changes retention or exports an audit must call an equivalent server-side authorization check. Hiding a UI control is not sufficient.
7. Retention, legal hold and disposition
The D1 evidence metadata schema stores a retention class, optional schedule reference, retention start, optional retain-until date, legal-hold flag and disposition status. A retain-until value requires a retention schedule reference. Disposition cannot be marked complete while a legal hold remains active.
Retention events record who applied a schedule, changed a date, applied or released a legal hold, reviewed disposition, approved disposition or disposed of an evidence record. These events are separate from the evidence review decision: accepting a document does not authorise its deletion.
8. Production storage completion checklist
Before live applicant or funding evidence is accepted, implement and verify all of the following:
- private object storage with encryption and access restricted to server-side service bindings;
- upload endpoint that derives user and organisation scope from the authenticated session;
- file type, size, integrity and malware inspection controls;
- server-side download endpoint with per-request authorization and access audit;
- immutable or versioned object keys; replacement must create a new object rather than overwrite a reviewed file;
- retention schedule resolution, legal-hold enforcement and approved disposition workflow;
- audit export and monitoring for allowed, denied and failed access;
- data residency, retention and hosting approvals from CEDA.
Related implementation files
- apps/web/components/ceda/CedaFundingDeliveryWorkspace.tsx
- apps/web/components/ceda/CedaFundingEvidenceRegister.tsx
- apps/web/lib/ceda/evidence-access-policy.ts
- apps/web/lib/ceda/evaluation-types.ts
- apps/web/migrations/ceda/0002_funding_evidence_register.sql
- apps/web/lib/ceda/local-document-store.ts