Rubric and publication
The assessment rubric defines the criteria and scoring guidance used by the Evaluator workspace. The workflow configuration determines how the intake progresses. Review these settings together before creating a new rulebook version.
Open the Innovation Rules workspace.
1. Review the assessment rubric
- Open Innovation Rules → Assessment rubric.
- Check the live total displayed beside the rubric heading.
- Review each criterion card in sequence.
- Edit Criterion to state the assessment dimension.
- Edit Evaluation guidance to explain what evidence the evaluator should consider.
- Set the Weight for the criterion as a percentage.
- Select Add rubric criterion when a genuinely distinct assessment dimension is needed.
- Remove a criterion only after checking the effect on the scoring model.
The starter rubric contains six proposed dimensions:
| Proposed criterion | Starter weight |
|---|---|
| Problem significance and beneficiary need | 15% |
| Innovation value and differentiation | 20% |
| Technical and implementation feasibility | 15% |
| Market demand and commercial viability | 20% |
| Promoter and management capability | 10% |
| Economic contribution and sustainability | 20% |
| Total | 100% |
These weights are a prototype starting point, not an approved CEDA scorecard. CEDA must review the dimensions, definitions and weights before operational assessment.
2. Maintain the score descriptors
The Score descriptors panel uses a five-point scale. Each point has an editable Label and Descriptor.
| Score | Starter label | What the descriptor communicates |
|---|---|---|
| 1 | Weak | Major gaps or absent/unconvincing evidence |
| 2 | Limited | Some merit, but material weaknesses remain |
| 3 | Adequate | A reasonable approach with identifiable gaps |
| 4 | Strong | Well-supported, with only minor weaknesses |
| 5 | Exceptional | Compelling evidence and a clearly differentiated case |
Use the descriptor to make the difference between score levels clear. Avoid vague wording that would allow two evaluators to interpret the same score in materially different ways.
3. Validate the scoring model
The preview checks that:
- at least two criteria are configured;
- the criterion weights total exactly 100%;
- every criterion has a non-empty title;
- every criterion has evaluation guidance; and
- every criterion has a positive weight.
The live total changes as weights are edited. A total other than 100% is displayed as invalid and prevents publication. The Publish rules buttons remain disabled while any rulebook validation issue exists, not only rubric issues.
4. Save a draft
- Review each of the seven rulebook tabs.
- Check the rubric total and all visible validation messages.
- Select Save draft in the page header.
- Confirm the success notice.
- Review Rulebook activity for the local draft-save event.
The workspace automatically saves draft state in the current browser. Save draft adds an activity event; it does not publish a rulebook version.
5. Resolve all publication checks
Publication validates the configuration across the entire rulebook, including:
- programme name and purpose;
- at least one supported applicant type;
- at least one funding pathway, with a name, description and conditions note;
- pathway links to eligibility and evidence items that still exist;
- at least two rubric criteria with complete descriptions and weights totalling 100%;
- at least one active workflow role, with a name and responsibilities;
- all ten reserved Operations workflow stage identifiers;
- at least three workflow stages; and
- a named owner role for every stage, with each owner active.
The validation panel lists the issues. Use the relevant tab to correct each issue, then review the panel again.
6. Publish a preview version
- Confirm that no Rulebook checks before publish panel remains.
- Select Publish rules in the header or Publish rulebook in the bottom action bar.
- Read the confirmation notice shown by the workspace.
- Check the version panel for the new published version number and timestamp.
- Review Rulebook activity for the publication event.
- Confirm whether the version panel says Draft matches published or Draft changes pending.
Publishing creates a new local preview version based on the current draft. The previous published version is retained in browser-local history, with the preview keeping up to 12 previous versions. The activity list is also local preview history.
7. Understand version pinning in Evaluator
When Operations creates an evaluator assignment, the assignment process reads the currently published rubric and copies its version, criteria and score descriptors into the assignment.
This means:
- evaluator assignments created after publication can use the new rubric snapshot;
- existing assignments retain the rubric snapshot already attached to them;
- changing a rubric later does not silently change the scoring guidance for work already assigned; and
- Adjudication can read the rubric version retained with the submitted evaluation.
The rubric snapshot is a same-browser prototype integration. It is not central rulebook storage or a production audit control.
8. Understand what publication does not do
Publishing this rulebook does not:
- approve CEDA policy or certify a product's terms;
- publish or replace the Applicant funding-enquiry form;
- approve, reject or award an applicant's funding request;
- issue a legal decision, offer or funding agreement;
- turn workflow-role descriptions into access permissions; or
- create an immutable, centrally controlled policy audit.
Formal CEDA approval, controlled policy release, server-side storage, permission enforcement and durable audit records remain separate production requirements.