Skip to main content

Roles and workflow

Innovation Rules defines who owns each funding-process function and how an application moves through the process. These are process definitions, not portal accounts, job appointments or access permissions.

Open the Innovation Rules workspace.

1. Define workflow roles​

  1. Open Innovation Rules → Roles & responsibilities.
  2. Review each role card's name, active status, information scope, responsibilities and workflow-use indicator.
  3. Edit Role / function name to describe the process function.
  4. Select the intended Information scope.
  5. Update Main responsibilities to explain what the function does and which decisions or records it owns.
  6. Keep the function Active while it is assigned to a workflow stage.
  7. Select Add role to introduce another process function when the existing catalogue does not cover a genuine responsibility.

The starter catalogue includes customer advisory/intake, eligibility review, portfolio/business advice, technical appraisal, finance/risk review, independent evaluation, panel secretariat, authorised decision panel, portfolio management, legal/offer coordination, finance operations and programme administration.

2. Understand the information-scope field​

The Information scope selector describes the intended record boundary for the function. Its starter options include:

  • Applicant and intake records
  • Eligibility and supporting evidence
  • Assigned proposal and financial evidence
  • Own evaluation only
  • Full read-only panel pack
  • Decision register and applicant feedback
  • Portfolio and monitoring
  • Rulebook configuration

Use the narrowest description that accurately reflects the function. In particular, independent evaluators should be described as working on their own assigned evaluation, while panel secretariat work may require a read-only panel pack.

Role descriptions are not account permissions

These settings describe process ownership and intended information scope only. They do not restrict navigation, protect records or enforce separation of duties in the open preview. Administration separately models portal accounts and workspace access; production access must be enforced by the identity and server layers.

3. Manage role dependencies​

The role cards show whether a function is Assigned to workflow stage or Not yet assigned.

  • Renaming a role automatically updates workflow stages that refer to its previous name.
  • Removing a role that is assigned to a workflow stage is disabled.
  • Deactivating a role that is still assigned to a stage causes publication validation to fail.
  • Reassign the affected workflow stages to another active function before deactivating or removing a role.

After changing a role name, open Workflow stages and confirm that the stage owner still reflects the intended function.

4. Configure workflow stages​

  1. Select Workflow stages.
  2. Review the numbered sequence from the first stage to the last.
  3. Edit Stage name to provide a clear label.
  4. Edit Stage description to explain what work should be completed at that point.
  5. Select an active Responsible role / function.
  6. Select Applicant can see this status when the stage should appear as an applicant-facing status.
  7. Select Reason required when leaving stage when a reason should be recorded before an application moves on.
  8. Use the up and down arrow controls to change the order.
  9. Select Add workflow stage only when a separate process step is required.

The stage marker reflects the current sequence. Reordering a stage changes its position; it does not change the stage's underlying reserved identifier.

5. Understand the reserved stages​

The Operations preview uses ten reserved stage identifiers:

Reserved process stagePurpose in the starter journey
IntakeReceive the idea and funding enquiry
ScreeningCheck initial fit and completeness
ProposalReview the proposal and supporting evidence
ClarificationRequest missing or clearer applicant information
AppraisalComplete technical and commercial appraisal
FinancialComplete financial and risk assessment
DecisionPrepare and record the authorised decision
OfferManage offer communication and conditions
ImplementationRecord funding implementation milestones
MonitoringTrack post-funding progress and obligations

Their names, descriptions, order, owner roles, applicant visibility and exit-reason settings can be configured. Their reserved identifiers must remain in the rulebook because Operations uses them for application stages, reporting and transitions. The delete control is disabled for these ten reserved stages.

Additional stages can be added, but the rulebook still needs to retain every reserved stage.

6. Understand stage validation​

Before publication, the rulebook checks that:

  • at least three workflow stages exist;
  • every reserved stage identifier remains present;
  • every stage has a name and responsible role; and
  • every stage owner matches an active role in Roles & responsibilities.

The preview also requires at least one active workflow role, and each role must have a name and responsibility. Resolve any validation message before publishing.

7. Understand exit reasons in Operations​

When a stage has Reason required when leaving stage enabled, the Operations preview requires a reason before moving an application out of that stage. The current preview checks for a reason of at least 10 characters and records it with the sample application activity.

This is browser-local prototype behaviour. It is not an approved CEDA transition policy, an immutable audit record or a server-enforced production control.

8. Keep process ownership separate from adjudication​

The role model distinguishes intake and advice, eligibility checks, technical appraisal, financial/risk assessment, independent evaluation, panel administration, decision authority and post-funding portfolio work. Keep these functions separate in the rulebook where the operating model requires different responsibilities or independent review.

Continue with Rubric and publication.