Skip to main content

Applications and assessment

This guide explains how a funding enquiry form becomes a versioned application response, how documents are attached to a response, and how evaluator assignments and panel decisions use those version references.

Preview data model

The workflows in this guide describe the current browser-based preview implementation. Form definitions, application responses, evaluator assignments, evaluator submissions, conflict records and adjudication outcomes are stored in browser-local preview state. This guide does not imply a live central application database or a production workflow API.

1. Funding enquiry form configuration and publication​

The form studio defines sections, questions and document requirements. Field types include short and long text, number, date, email, select, radio, checkbox, multi-checkbox and repeatable table. A conditional rule can show a field or document requirement when another field has a configured value.

The form definition is persisted in localStorage under ceda-form-studio-demo:v1 in the preview. Publishing stores a numbered version containing the sections, document requirements, data schema and UI schema. Submitted applications can therefore point to a particular published form version rather than silently following later edits to the draft.

2. Application response and version relationship​

An application response is not simply a mutable set of answers. The preview model retains numbered response versions and a published form snapshot. Each assignment identifies the competition, application, application response version and form version being reviewed.

This is essential for reproducibility: when an applicant resubmits a response or a later form version is published, an existing evaluator task must still resolve to the exact material that was assigned.

3. Applicant document storage lifecycle​

The local document store opens the IndexedDB database ceda-local-document-preview, database version 1, and object store application-documents. It stores an attachment record containing an ID, application ID, requirement ID, file name, content type, byte size, upload timestamp and Blob.

Important limits

  • The Blob remains in the browser's storage for the current site origin and browser profile.
  • It is not uploaded to a CEDA-controlled private object store.
  • Clearing site data or changing browser/device can make the file unavailable.
  • A production implementation must add server-side ownership checks, private object storage, file inspection, retention controls and auditable download endpoints.

4. Exact-version evaluator assignment​

The evaluator assignment component reads the submitted applicant records, assignment list, evaluator submissions and conflict records from localStorage. It only assigns a submitted application response when the selected version can be matched to the available published form snapshot.

The assignment pins the application ID, response version, form version, competition, evaluator, due date and rubric snapshot/version. The component checks for an existing active duplicate and uses prior assignment history to avoid silently treating a completed review as a new active assignment.

5. Conflict declaration and evaluation submission​

The evaluator workspace is designed around an assigned response and rubric snapshot rather than a free-floating application. A completed submission is tied back to the assignment. The funding-delivery builder later checks that each active assignment has a submitted result whose application, competition, response version, form version, evaluator, non-conflict status and rubric version match the assignment.

This preview workflow is useful for testing version and completeness rules. It is not a substitute for an independently hosted evaluation service or protected server-side access to confidential assessment records.

6. Adjudication and selection gate​

The panel decision is a distinct stage from authorised funding approval. In the current funding case builder, a case is only surfaced when its assignments and submissions satisfy the exact version and rubric checks, the decision outcome is Selected, and a workflow record is consistent with the selected decision state.

A Selected panel outcome is not an approval to release funds. The funding workspace requires a separate approval authority, reference, date, amount and rationale before the offer and implementation steps are treated as authorised.

7. Version-matching checklist​

Before a new evaluation or adjudication feature is accepted, verify that:

  1. The application belongs to the selected funding programme.
  2. The response version exists and points to the expected published form version.
  3. The evaluator assignment pins the same response and form versions.
  4. The rubric version or snapshot is retained with the assignment.
  5. The submitted evaluation matches its assignment and includes the expected conflict status.
  6. The panel outcome points to the same application response and form version.
  7. Funding delivery is not opened from a merely submitted application or a panel selection that has not passed the consistency checks.
  • apps/web/components/ceda/CedaFormStudio.tsx
  • apps/web/components/ceda/CedaApplicantWorkspace.tsx
  • apps/web/components/ceda/CedaDocumentRegister.tsx
  • apps/web/components/ceda/CedaEvaluationAssignments.tsx
  • apps/web/components/ceda/CedaEvaluatorWorkspace.tsx
  • apps/web/components/ceda/CedaAdjudicationWorkspace.tsx
  • apps/web/lib/ceda/evaluation-types.ts
  • apps/web/lib/ceda/innovation-rules.ts
  • apps/web/lib/ceda/local-document-store.ts