Funding evidence register, queues and retention
The Operations Funding evidence register brings application-form attachments, offer acceptance files, funding-condition evidence and implementation milestone evidence into one programme-level inventory. It complements the existing Document register, which remains the review workspace for the form-based application documents.
Open Operations and select Funding evidence register in the top action row.
The current register reads submitted Applicant records, Document register review state, Funding Delivery metadata and evidence-register metadata from this browser's local storage. File bytes remain in the same browser profile's IndexedDB. It is not shared CEDA storage, a private object store or an immutable audit service. Reviewer labels are typed preview values, not verified identity accounts. Use synthetic records and files only.
1. Understand the central inventory
The register includes four evidence groups:
| Evidence group | Source and review authority |
|---|---|
| Application-form attachments | Files submitted against published form requirements; review decisions remain in the existing Document register |
| Offer acceptance | Files submitted with the applicant's Accepted offer response; review decisions remain in Funding Delivery |
| Conditions precedent | Files submitted against an Outstanding funding condition; review decisions remain in Funding Delivery |
| Implementation milestones | Files submitted against a Pending post-funding milestone; review decisions remain in Funding Delivery |
Each row shows the application reference and title, applicant organisation where available, response version, published form version, evidence target, file name, content type, size and upload date. For application-form attachments, the status and review note are read from the existing Document register; this inventory does not create a second document-review authority.
The register displays application-form attachments from submitted response versions, as well as active funding evidence and historical file snapshots captured in prior Funding Delivery review events. For application-form attachments, the status and review note are read from the existing Document register. Use Open Document register to review or update those form-based document outcomes. For offer acceptance, conditions and milestones, use Open funding case to reach the version-matched Funding Delivery review panel.
When an applicant submits replacement funding evidence, the previous reviewed file remains visible as a historical snapshot. The new file set becomes current and returns to the Funding Delivery review queue.
Capture the live Funding evidence register with current and historical files visible. Add the reviewed image as /img/operations/funding-evidence-register-overview.png.
2. Read the summary indicators
The six summary cards report:
- Current evidence files — application-form attachments and files currently attached to acceptance, condition or milestone targets.
- Awaiting review — current funding files without a matching accepted/replacement review, plus application-form files without a source Document register review that applies to that uploaded file.
- Overdue reviews — current files awaiting review whose configured review due date has passed.
- Accepted — current files covered by the latest accepted review.
- Replacement requested — current files for which CEDA has asked the applicant to submit a replacement.
- Retention review due — files whose recorded retain-until date has been reached and which are not on legal hold.
A review is not considered overdue unless a due date has been assigned. The prototype does not assume an official CEDA service-level target. A review date entered here is a test value until CEDA approves the production workflow.
3. Use the reviewer workload queue
The workload cards group current pending files by the Assigned reviewer value recorded in the register.
- Open Assignment & retention metadata on an evidence row.
- Enter the assigned reviewer label.
- Enter the review due date.
- Select Save metadata.
- Return to Reviewer workload queue and select the reviewer's card.
- Check the filtered evidence inventory for the pending and overdue items.
Unassigned files appear under Unassigned. The queue counts files, not unique applications. A case may have several files and more than one evidence target.
The typed reviewer label is not linked to an authenticated staff account in the open preview. Production assignments must store the identity-service user ID, enforce role/workspace permissions and write assignment changes to the server audit register.
Capture reviewer workload cards with assigned, unassigned and overdue files. Add the reviewed image as /img/operations/funding-evidence-review-queue.png.
4. Filter and inspect evidence
Use the filters to narrow the inventory by:
- application reference, title, organisation, filename, evidence target or assigned reviewer;
- review status;
- evidence type; and
- reviewer assignment.
Select Download original to retrieve a synthetic file from the current browser's IndexedDB store. For application-form attachments, select Open Document register to use the existing form-document review flow. For acceptance, condition and milestone evidence, select Open funding case to navigate to the exact response/form-version case in Funding Delivery, where the evidence-review panel and version-linked history can be inspected.
The register is an inventory and workload view. Application-form document decisions remain in the Document register; offer acceptance, condition and milestone decisions remain in Funding Delivery. This avoids duplicate review sources while keeping the evidence inventory searchable in one place.
Capture the filtered inventory, original file download action and Open funding case hand-off. Add the reviewed image as /img/operations/funding-evidence-register-filters.png.
5. Record retention metadata
Open Assignment & retention metadata for a file to record:
| Field | Purpose |
|---|---|
| Retention class | Identifies the broad evidence class |
| Approved retention schedule reference | Links the item to a CEDA-approved schedule or clause |
| Retain until | Records the date derived from that approved schedule |
| Legal hold applies | Flags a hold that prevents normal disposition |
| Retention / hold note | Captures the reason or supporting reference |
A retain-until date cannot be saved without a retention schedule reference. The register does not invent a retention period. CEDA must approve the applicable records schedule and legal-hold process before production dates are entered.
When the retain-until date is reached, the item appears as Retention date reached · review only and increments the retention-review indicator, unless a legal hold applies.
The prototype does not delete, archive, purge or dispose of a file when a date is reached. A retention date triggers a review reminder only. Any production disposition must require an authorised decision, documented legal-hold check, durable audit event and an approved deletion/archive operation in private storage.
Capture a file with a schedule reference, retain-until date and legal-hold control. Add the reviewed image as /img/operations/funding-evidence-retention.png.
6. Export a register extract
Use Export CSV for a spreadsheet-friendly register extract. Use Export JSON for a structured evidence and review extract.
The current export follows the active inventory filters and includes file identifiers, application and version references, target, review status, reviewer/date, review notes, assignment, due date, retention metadata and legal-hold flag. Funding evidence rows include the append-only preview review-event sequence and metadata-change history. Application-form rows include the current source Document register review outcome; the original form-document preview does not provide an append-only review-event history.
Exports may contain confidential internal reviewer notes. In production they must be restricted to authorised users, generated server-side, logged as access events and protected according to CEDA's information-handling policy. A browser-generated preview export is not an immutable audit report.
Capture both export controls and the filtered evidence rows before export. Add the reviewed image as /img/operations/funding-evidence-audit-export.png.
7. Understand applicant-specific access boundaries
The production access policy is deny-by-default:
| Role | Intended evidence access |
|---|---|
| Applicant lead / team | Own verified applicant organisation only; applicant status and download of that organisation's submitted evidence |
| Funding programme administrator | Funding programme evidence metadata, authorised downloads, review assignment/decisions, retention metadata and audit export |
| Eligibility reviewer | Assigned eligibility evidence only; no funding-delivery evidence by default |
| Evaluator | Approved appraisal material for assigned application response/form versions only |
| Adjudicator | Authorised panel pack and decision material; no funding-delivery evidence unless separately granted |
| Platform administrator | Identity and workspace administration; no confidential proposal/evidence content by default |
A user's workspace membership alone is not sufficient. Every production request must check the active identity session, role, applicant organisation membership or staff assignment, funding programme scope, application ID, response version, evidence target and requested action.
Applicant ownership must be stored in an authoritative organisation-membership and application-scope record. The server must not trust a browser-provided organisation ID, application ID or evidence object key. Internal notes, access audit and retention controls must never be returned by applicant-facing endpoints.
The codebase now contains a deny-by-default policy reference in apps/web/lib/ceda/evidence-access-policy.ts. It is not wired into the current open preview; it must be enforced by server-side evidence APIs before real applicant or CEDA files are stored.
8. Production storage, audit and migration boundary
The CEDA D1 migration 0002_funding_evidence_register.sql defines the metadata foundation for:
- applicant organisations, verified applicant memberships and application ownership scopes;
- evidence-object metadata and storage object keys;
- application response/form-version references and replacement lineage;
- append-only evidence review events and the exact files included in each reviewed file set;
- reviewer assignment and due dates;
- retention schedule, retain-until and legal-hold fields;
- retention events; and
- evidence metadata/download/export/review access audit events.
This migration does not create a private object-storage bucket or an upload/download API. The current Worker configuration has no CEDA evidence-object bucket binding. A production storage adapter, content hash verification, MIME/extension/size checks, malware scanning, encryption, backup/recovery and authenticated download endpoint remain required.
Before storing real CEDA information, approve hosting and data residency, the applicant identity-to-organisation mapping, staff roles and permissions, retention schedule, legal hold and disposal procedure, audit ownership, incident response and export permissions. Workspace UI gating or a hidden button does not secure an API or a file.
9. Current prototype boundaries
- Register assignment and retention metadata use browser local storage.
- Evidence bytes are available only in the browser profile where the files were submitted.
- Review and file snapshots are browser-local and are not tamper-proof.
- Reviewer labels are not authenticated identities.
- No automatic notification, retention deletion, malware scanning or private CEDA object storage is active.
- The open preview remains open while the prototype is under review; the production access policy shown here is not enabled.