Skip to main content

Capture and publish a user guide

CEDA guides use real screenshots from the current application. The recommended capture tool is Mimik, an open-source browser workflow recorder. It records actions as numbered steps with annotated screenshots and can export an editable guide or shareable document.

Open Mimik's official website · View the MIT-licensed source code

1. Prepare the browser​

  1. Install the Mimik extension for Chrome, Edge or Firefox from its official website.
  2. Open the CEDA preview in the same browser.
  3. Use the browser's normal window size. A desktop viewport around 1440 pixels wide gives enough room to show the sidebar and primary workspace.
  4. Confirm that the page says Preview environment.
  5. Make sure the page is using synthetic records only.

2. Record one task at a time​

  1. Open Mimik and start a new guide.
  2. Give the guide a task-focused name, such as Review an application in CEDA Operations.
  3. Start recording.
  4. Perform the task slowly, allowing each screen to settle before the next click.
  5. Pause recording before navigating to unrelated screens or entering any information that should not appear in a guide.
  6. Stop recording when the task is complete.

Record separate guides for separate tasks. Do not combine every Operations feature into one extremely long recording.

3. Review every screenshot​

Before exporting:

  • Read every generated step description and correct it where needed.
  • Crop and annotate screenshots so the intended control is obvious.
  • Remove accidental clicks, unrelated menus and duplicated steps.
  • Inspect every image at full size. Do not assume automatic redaction caught everything.
  • Check the address bar and visible page content for email addresses, phone numbers, invitation tokens, personal information or confidential material.
  • Delete any step that contains information that should not be published.
Smart blur is not a substitute for synthetic data

Mimik's Smart blur is a capture-time aid. It does not retroactively mask screenshots already captured, and it does not cover every possible source of text such as iframes or text drawn inside images. Use synthetic data and manually inspect every screenshot before publishing.

4. Export the source and publication formats​

FormatUse
Mimik source fileKeep an editable source copy that can be imported into another Mimik installation
MarkdownBring the steps and image references into this documentation website
HTMLReview or share a self-contained guide
PDF or DOCXDistribute a printable or editable user manual

Keep the editable source file with the documentation working materials. The published website should contain only screenshots and instructions that have been reviewed and approved for sharing.

5. Add screenshots to this documentation site​

  1. Export the Mimik source file and Markdown guide.
  2. Review the exported guide and image assets.
  3. Place approved screenshot files under apps/ceda-docs/static/img/workspace-name/.
  4. Reference them from the relevant Markdown page using a path such as /img/operations/operations-overview.png.
  5. Keep the images in the same order as the written steps.
  6. Build and preview the documentation site before merging or publishing.

6. Capture a multi-tab workspace​

A workspace overview screenshot is not a substitute for screenshots of the controls described in each task guide. Capture one genuine screen for each distinct tab or task state. Do not duplicate the overview image, crop it differently and rename it, or use a mock-up in place of an application capture.

For the Innovation Rules workspace, use this capture sequence:

CaptureNavigate to / showSuggested file
Workspace overviewHeader, version panel and all seven configuration tabsinnovation-rules/innovation-rules-overview.png (already present)
Intake profileProgramme name, purpose, applicant-type selection and CEDA reference cardsinnovation-rules/intake-profile.png
Roles & responsibilitiesRole cards with active status, information scope, assigned-stage indicator and responsibilitiesinnovation-rules/roles-responsibilities.png
Funding pathwaysA pathway card with source, approval-status selector and the three linked selection groupsinnovation-rules/funding-pathways.png
Eligibility rulesRule cards showing enabled state, scope, rule name and explanationinnovation-rules/eligibility-rules.png
Evidence requirementsEvidence cards showing requirement title, purpose and applicabilityinnovation-rules/evidence-requirements.png
Assessment rubricCriterion cards, percentage weights, live total and score descriptorsinnovation-rules/assessment-rubric.png
Workflow stagesOrdered stages, role owner, applicant visibility and exit-reason controlsinnovation-rules/workflow-stages.png
Validation state (optional)A safe synthetic invalid state with the validation panel visibleinnovation-rules/validation-before-publish.png
Published state (optional)New local version number, timestamp and Rulebook activityinnovation-rules/rulebook-published-preview.png

For each tab capture:

  1. Open the actual Innovation Rules preview and select the tab named in the table.
  2. Wait for the interface to settle, then position the page so the tab heading and the fields being explained are visible together.
  3. Scroll and take more than one capture when a long list cannot fit legibly in one image. Do not shrink the browser until text becomes unreadable.
  4. Use harmless synthetic configuration values only. Do not expose real applicant, staff or confidential programme information.
  5. Capture the current state after selecting the relevant tab, not a reconstructed design or an image of source code.
  6. Review every screenshot at full size and make sure no address-bar tokens, browser profile details, personal information or unrelated overlays are visible.
  7. Save each approved image under apps/ceda-docs/static/img/innovation-rules/.
  8. Embed the image in the task guide at the point where the reader needs it, with alternative text describing the screen and the controls shown.

For the optional validation and publication states, make the change using fictional preview data, capture the state, then restore the valid starting configuration. Do not publish a demonstration rulebook while presenting its settings as approved CEDA policy.

Current capture coverage: the repository contains the Innovation Rules overview image. The tab-specific images in this table are separate captures and should only be marked complete after the actual preview screen has been recorded and reviewed.

7. Capture the Administration workspace​

The Administration overview screenshot is only the starting point. Capture each additional screen state from the current CEDA application and use fictional profile values. Do not create a mock-up to fill a missing screenshot.

For the Administration workspace, use this capture sequence:

CaptureNavigate to / showSuggested file
Workspace overviewHeader, account summary, directory and main sectionsadministration/administration-overview.png (already present)
Add preview accountOpen the form and show identity fields, proposed role, workspace choices and delegated-onboarding controlsadministration/add-preview-account.png
User directory and filtersSearch and role filter, directory columns and local status labelsadministration/user-directory-filters.png
Access editorOpen Manage for a synthetic user and show role, workspace and delegated-onboarding settingsadministration/user-access-editor.png
Onboarding centre — open previewEmpty invitation state and the three centre metrics, with the preview limitation visibleadministration/onboarding-centre-preview.png
Role templatesEight role cards with their responsibility descriptions, scope notes and default workspace pillsadministration/role-templates.png
Workspace access matrixComplete role-to-workspace table with the filled-dot/open-circle legendadministration/workspace-access-matrix.png
Administration activityA harmless preview account creation or role update reflected in the local activity listadministration/administration-activity.png
Central identity sign-in (conditional)Administrator sign-in screen, only when the separately gated identity environment is deliberately enabledadministration/central-admin-sign-in.png
Initial administrator bootstrap (conditional)One-time bootstrap screen in a safe, isolated test environmentadministration/initial-admin-bootstrap.png
Invitation link dialog (conditional)Invitation-purpose dialog with the token completely hidden or redactedadministration/invitation-link-dialog.png
Guided onboarding (conditional)Welcome, access review, workspace orientation and readiness screens, using an isolated synthetic invitationadministration/guided-onboarding.png

For the open-preview captures:

  1. Open the actual Administration preview.
  2. Capture the account form with Add preview account expanded. Use an obviously fictional name and a reserved .invalid email address.
  3. Capture the directory after creating that fictional profile. Use the search and role filter to demonstrate how the directory is narrowed.
  4. Open Manage for that same synthetic profile and capture the access editor.
  5. Scroll to Onboarding centre and capture the empty state. This is the correct open-preview state: adding a preview account does not create an invitation.
  6. Scroll to Role templates & permissions and capture the role cards and the matrix. Use separate images if the table cannot be read at the normal browser width.
  7. Create or edit a harmless synthetic profile, then capture the corresponding entry in Administration activity.
  8. Save approved images under apps/ceda-docs/static/img/administration/ and insert them into the relevant guides.

The central identity screenshots are conditional. Do not switch on central identity enforcement or configure a deployment only to create documentation images. Capture those screens only after an isolated test environment has been approved and configured. Never publish a live invitation token, password, bootstrap secret, session cookie, real email address or personal data. Redact tokens before export; do not rely on automatic blur alone.

Current capture coverage: the repository contains the Administration overview image only. The tab/section captures in this table are separate genuine screenshots and should only be marked complete after each screen has been recorded and reviewed.

8. Capture the Evaluator workspace​

The Evaluator overview image is only the starting point. The assignment queue, version-pinned review, conflict declaration, rubric, draft and final-submission states need their own real captures. Use synthetic application data and preview evaluator identities only.

For the Evaluator workspace, use this capture sequence:

CaptureNavigate to / showSuggested file
Workspace overviewHeader, synthetic-preview notice, evaluator selector, workload cards and assigned review queueevaluator/evaluator-overview.png (already present)
Assigned reviews and filtersSelected preview identity, assignment cards and the All / Needs review / In progress / Submitted filtersevaluator/assigned-reviews-queue.png
Assigned application versionReview header, application/response/form version, proposal summary and read-only submitted answersevaluator/assigned-application-version.png
Supporting documentsVersion-pinned requirement cards, synthetic attachment filename/type/size and download actionevaluator/assigned-supporting-documents.png
No-conflict declarationConflict-of-interest declaration with No conflict selected and the scoring area unlockedevaluator/no-conflict-declaration.png
Conflict escalationSynthetic Potential conflict state showing scoring paused and the declaration selector lockedevaluator/conflict-escalation-locked.png
Criterion scoringPinned rubric label, criterion title/description/weight, score choices and evidence rationaleevaluator/criterion-scoring.png
Overall assessmentRecommendation selector, overall rationale and progress/weighted-score panelevaluator/overall-assessment.png
Validation before submissionSynthetic incomplete evaluation with the Before you submit validation list visibleevaluator/submission-validation.png
Draft in progressQueue card marked In progress after selecting Save draftevaluator/draft-in-progress.png
Final submission confirmationSubmit this evaluation? dialog showing application, version, evaluator and recommendationevaluator/final-submission-confirmation.png
Submitted and lockedQueue status Submitted and Final evaluation locked bannerevaluator/submitted-evaluation-locked.png

For the captures:

  1. Open the actual Evaluator preview in the same browser that contains the synthetic Applicant and Operations preview records.
  2. Select a preview evaluator identity that has a synthetic active assignment.
  3. Capture the queue with its identity selector and filters visible. Use a separate capture when the queue is scrolled.
  4. Open one assignment and capture the version-pinned review header and proposal summary.
  5. Scroll to the read-only answers and supporting-document section. Use only synthetic attachments; inspect filenames and metadata before publishing.
  6. Capture No conflict before scoring. For the conflict image, select Potential conflict using a synthetic assignment and show the locked declaration and paused-scoring message.
  7. Capture one criterion card with a selected score and evidence rationale. Keep the criterion label, percentage weight and score descriptor visible.
  8. Capture the overall recommendation and rationale, including the minimum-character indicator and progress summary.
  9. If capturing validation, leave a harmless synthetic criterion unanswered, show the validation message, and then restore the test assignment before submission.
  10. Select Save draft and capture the queue's In progress state.
  11. Complete all required fields with synthetic text, open the final confirmation dialog and capture its version/evaluator summary. Do not confirm until the confirmation image has been reviewed.
  12. Confirm the synthetic preview submission and capture the locked final state.
  13. Save approved images under apps/ceda-docs/static/img/evaluator/ and embed them in the relevant guide at the step where the user needs to see the control.

A conflict-state demonstration should use an assignment created solely for that purpose. Once Potential conflict or Conflict declared is selected, the declaration is locked; Operations must revoke that assignment and allocate a new one to another evaluator. Do not reuse a conflict-escalated assignment for the no-conflict, scoring or final-submission captures.

The final-submission dialog contains application reference, response version, evaluator identity and recommendation. Use synthetic values and ensure no real applicant data or confidential files are visible. Do not publish real assessment rationale, applicant uploads, access tokens, email addresses or private browser data.

Current capture coverage: the repository contains the Evaluator overview image only. All other images in this table are separate genuine captures and should only be marked complete after each state has been recorded and manually reviewed.

9. Capture the Adjudication workspace​

The Adjudication overview image is only the starting point. Capture the actual panel workflow from a synthetic case that has completed all active evaluator assignments for one exact response and form version. Use at least two different preview evaluator identities to create a meaningful comparison example; this is a demonstration setup, not a formal CEDA minimum or quorum.

For the Adjudication centre, use this capture sequence:

CaptureNavigate to / showSuggested file
Workspace overviewHeading, panel workload cards, cases-to-review panel and case filteradjudication/adjudication-overview.png (already present)
Ready panel queueA synthetic case card and the All cases / Awaiting panel / Decision recorded filteradjudication/panel-queue-ready-case.png
Version-pinned case summaryReference, title, organisation, response/form versions, active assignments and submitted review countadjudication/case-version-summary.png
Evaluator comparisonRead-only comparison table showing criterion weights, each evaluator's score and the meanadjudication/evaluator-score-comparison.png
Evaluator evidenceEach overall rationale and an expanded criterion-level rationale sectionadjudication/evaluator-evidence-rationales.png
Panel recommendation and outcomeAdjudicator conflict declaration, recommendation and final outcome selectorsadjudication/panel-recommendation-outcome.png
Conflict pauseSynthetic Potential conflict state with the visible panel-decision pause alertadjudication/panel-conflict-pause.png
Decision rationale and deliberation80-character rationale indicator, internal panel notes and optional dissenting viewadjudication/panel-deliberation-record.png
Applicant feedback gateFeedback text area, approval checkbox and local-only release warningadjudication/applicant-feedback-gate.png
Review session scheduledProposed date/time, optional instructions and Scheduled statusadjudication/review-session-scheduled.png
Review session completedAttendance/completion note meeting the 20-character threshold and Completed statusadjudication/review-session-completed.png
Decision historyRecorded panel event with outcome, recommendation, rationale, amendment reason and date/timeadjudication/decision-history-register.png

For the captures:

  1. Open Applicant Workspace and submit one fictional application using the published sample form.
  2. Open Operations and create assignments for the same exact application response and form version. Use at least two different preview evaluator identities for the demonstration comparison.
  3. In the Evaluator workspace, complete the conflict declaration, all rubric scores, every criterion rationale, recommendation and overall rationale for each assigned evaluator. Confirm each final preview submission.
  4. Open the Adjudication centre in the same browser. Confirm the case appears only after every active assignment for that exact version has a matching final submission.
  5. Capture the queue and version-pinned case summary. Keep application reference, response version, form version and assignment/review counts visible.
  6. Capture the read-only score comparison. Ensure the reviewer identities are synthetic and each score and mean column can be read.
  7. Expand View criterion-level rationales and capture one example with the overall rationale visible. Do not reveal real applicant details or confidential information.
  8. Capture the panel recommendation/outcome controls before saving. Use No conflict only for the normal decision-path capture.
  9. For the conflict image, use a separate synthetic case or a separate test record. Select Potential conflict and capture the visible pause alert. Do not save a decision or switch the value back simply to continue.
  10. Use the normal no-conflict case to complete the rationale, panel notes and (where useful) dissenting view. Capture the minimum rationale counter.
  11. Capture the applicant-feedback area separately. Any sample feedback must be fictional; the approval checkbox is a local preview state and does not publish or send it.
  12. Enter a proposed session date and time, optionally add instructions, select Save session details and capture the Scheduled status. No invitation is sent.
  13. Enter a synthetic attendance/completion note of at least 20 characters and select Mark completed. Capture the Completed status.
  14. Save the first panel decision and capture the first history event. To demonstrate an amendment, update the recommendation/outcome/rationale, provide a reason for amendment and save again; capture the resulting history sequence.
  15. Save approved images under apps/ceda-docs/static/img/adjudication/ and embed them in the relevant guide at the step where the user needs to see the control.

Do not use one case for both the conflict-pause and no-conflict decision screenshots. The preview conflict field blocks decision saving unless No conflict is selected; a potential or declared conflict must be handled through CEDA's approved panel conflict/recusal process, not cleared just to create a screenshot.

The decision-history panel shows limited decision events, not a full versioned snapshot of panel notes, dissent, feedback or session data. Do not caption it as an immutable audit trail. The selected panel outcome is not an official funding approval or applicant communication.

Current capture coverage: the repository contains the Adjudication overview image only. All other images in this table are new genuine captures and should only be marked complete after each state has been recorded and manually reviewed.

10. Capture the Funding Delivery workspace​

The Funding Delivery desk needs separate captures for approval authority, offer issue, applicant response, agreement execution, conditions precedent, disbursement and monitoring. Capture the actual Operations sub-workspace using a synthetic case that has completed all active evaluator assignments and has a Selected Adjudication outcome. Do not use a generic application-register screenshot to stand in for a funding delivery state.

For the Funding delivery workspace, use this capture sequence:

CaptureNavigate to / showSuggested file
Funding delivery overviewHeader, selected-case queue, preview boundary and summary cardsoperations/funding-delivery-overview.png
Authorised approvalApproving body/delegation, approval reference, date, amount and recorded approval stateoperations/funding-delivery-approval.png
Offer preparationProduct/facility, offer reference, amount, issue/expiry dates and termsoperations/funding-delivery-offer.png
Applicant responseApplicant-submitted response shown read-only in Operations, response date, applicant note and uploaded file linksoperations/funding-delivery-acceptance.png
Acceptance evidence reviewReviewer identity, applicant acceptance file, internal note and Accept evidence / Request replacement actionsoperations/funding-delivery-acceptance-review.png
Conditions evidence reviewApplicant files, condition review decision and accepted / replacement outcomeoperations/funding-delivery-condition-review.png
Milestone evidence reviewApplicant milestone file, reviewer identity, completion date and review decisionoperations/funding-delivery-milestone-review.png
Version-linked review historyReview decision sequence, reviewer, date, internal note, applicant message and response/form version labelsoperations/funding-delivery-review-history.png
Executed agreementAgreement type, contract reference, both party signing dates and effective dateoperations/funding-delivery-contract.png
Conditions precedentCondition owners, Outstanding/Satisfied/Waived state and evidence/waiver referencesoperations/funding-delivery-conditions.png
Disbursement controlApproved amount, planned tranches, paid-date, payment reference and verifieroperations/funding-delivery-disbursements.png
Post-funding monitoringMilestone list, due date, completion date, evidence reference and progress stateoperations/funding-delivery-monitoring.png

For the captures:

  1. Open Applicant Workspace and submit a fictional funding application.
  2. In Operations, create assignments for the exact application response and form version. Complete all active evaluator assignments using distinct preview evaluator identities.
  3. In Adjudication, compare the completed reviews and record a Selected panel outcome with a synthetic rationale.
  4. Return to Operations and select Funding delivery in the top action row. Confirm the case appears in the Selected cases queue.
  5. Capture the overview and exact application/response/form versions. Do not use the applicant's requested amount as the approved amount.
  6. Complete the approval step with synthetic authority text, reference, date and amount, then capture the recorded approval. The authority field must not be presented as proof that delegated authority has been verified.
  7. Complete the offer details and capture the preparation state before selecting Mark offer issued in preview. Use a fictional product, offer reference and terms.
  8. Return to Applicant and submit an Accepted offer response with a harmless synthetic acceptance file. Capture the applicant response and then return to Operations.
  9. Enter the evidence reviewer name / role. Open the applicant acceptance file and record an internal note. Select Accept evidence, then capture the accepted decision and its response/form version. Use a separate synthetic case to capture Request replacement; return to Applicant, upload the requested replacement, and capture the new pending-review state. Reopen Operations and capture the appended version-linked review history.
  10. Enter fictional agreement details and both signing dates. Capture the agreement marked executed, clearly showing its preview status.
  11. Add at least one condition precedent, then return to Applicant and upload synthetic evidence. In Operations, open the file, record the review and accept it or request replacement. Capture both the decision and applicant-facing replacement message if used. If demonstrating a waiver, show its explicit authorised waiver reference. If demonstrating no conditions, show the authorised no-conditions reference.
  12. Schedule a small synthetic tranche. Capture the planned state, then enter a fictional payment reference, paid date and verifier and capture the recorded-paid state. Never use real banking details or payment references.
  13. Add a monitoring milestone with a due date. Return to Applicant and upload a fictional progress report. In Operations, open the file, enter the verified completion date and record Accept evidence or Request replacement. Capture the milestone review history and post-funding monitoring state.
  14. Save approved images under apps/ceda-docs/static/img/operations/ and embed them in the Funding Delivery guide at the corresponding task step.

Do not imply that the preview verifies a delegated authority, sends an offer, collects signatures, executes a legal agreement, makes a payment or notifies an applicant. The status labels are browser-local workflow demonstrations only. Do not publish real approval minutes, contracts, payment records, applicant communications or personal information.

Current capture coverage: the repository does not yet contain genuine Funding Delivery screenshots. All twelve images in this table are separate captures to be recorded from the live preview and manually reviewed before they are embedded in the guide.

11. Capture Applicant funding offers and portfolio follow-up​

The Applicant workspace's funding card appears only after a panel-selected case or Funding Delivery record is available for that applicant's submitted response version. Capture these screens from the live preview using the same browser profile as Operations. Do not use generic status screenshots as substitutes.

For the Applicant funding and portfolio journey, use this capture sequence:

CaptureNavigate to / showSuggested file
Issued offerApplicant funding card showing the exact response/form versions, CEDA product, offer reference, amount, issue date, expiry and termsapplicant/funding-offer-issued.png
Acceptance responseAccept this offer, supporting evidence file picker and Submit acceptance actionapplicant/funding-offer-acceptance.png
Acceptance review outcomeApplicant card showing acceptance evidence accepted by CEDA and the released applicant-facing messageapplicant/funding-offer-evidence-review.png
Replacement acceptanceApplicant replacement request message, replacement file picker and resubmission actionapplicant/funding-offer-replacement.png
Request changesRequest changes, explanatory note, optional evidence and Send change requestapplicant/funding-offer-changes-requested.png
Decline offerDecline this offer, explanation and optional supporting fileapplicant/funding-offer-declined.png
Conditions evidenceOutstanding condition and Add supporting evidence picker; also capture the file after uploadapplicant/funding-conditions-evidence.png
Condition replacementApplicant-facing replacement message and Upload replacement evidence actionapplicant/funding-condition-replacement.png
Funding releasesPlanned and recorded-paid tranche amounts and datesapplicant/funding-releases.png
Milestone evidencePending milestone, due date, upload control and the uploaded filenameapplicant/funding-milestone-evidence.png
Milestone review outcomeApplicant card after CEDA accepts the milestone evidence and records completionapplicant/funding-milestone-review.png

For the captures:

  1. In Applicant Workspace, submit a fictional application and complete the active evaluator assignments for one exact response/form version.
  2. In Adjudication, record a Selected panel outcome for that same version.
  3. In Operations, record a separate synthetic authorised approval and issue a fictional offer with a future response deadline.
  4. Return to Applicant Workspace in the same browser. Confirm the funding card shows the same response and form versions before capturing the issued offer.
  5. Capture the normal acceptance state before selecting a response. Use a synthetic acceptance file with no signature, bank details or real personal data.
  6. Select Accept this offer, attach the harmless file, submit, and capture the saved response and file listing. Use a separate synthetic case or resettable test record for the change-request and decline states; one response cannot be submitted three times for the same issued offer.
  7. In Operations, open the acceptance evidence, enter the reviewer identity and record Accept evidence. Return to Applicant and capture the accepted-evidence outcome. In a separate test case, request replacement, then capture the applicant-facing message and replacement upload state.
  8. For the conditions image, add a synthetic outstanding condition in Operations, then return to Applicant and upload an illustrative evidence file. Capture both the upload control and the uploaded filename.
  9. In Operations, review the attached condition evidence and record Accept evidence or Request replacement. Return to Applicant and capture the resulting status or replacement message.
  10. In Operations, execute the synthetic agreement, confirm all conditions are accepted or formally waived, and schedule/record a sample tranche. Add a post-funding milestone.
  11. Return to Applicant and capture the funding release information and milestone due date. Upload a synthetic progress report and capture its filename.
  12. In Operations, review the milestone evidence and record Accept evidence with a verified completion date. Capture the updated Applicant milestone state. Use a separate test record to capture a milestone replacement request.
  13. Save approved images under apps/ceda-docs/static/img/applicant/ and embed them in the Applicant funding guide where the reader needs to see the control.

Use only fictional files and names. The preview stores funding-evidence files in the same browser's IndexedDB and metadata in browser-local storage; no file is uploaded to CEDA. Do not publish real signed offer letters, contracts, approvals, bank statements, invoices, payment references or confidential funding evidence.

A submitted applicant response is locked in the preview. A change request is a request for CEDA review, not an automatically amended offer. Evidence uploads do not automatically satisfy conditions or complete milestones; Operations must review and record those outcomes.

Current capture coverage: the repository contains the earlier Applicant overview and clarification screenshots, but none of the eleven new funding/portfolio images in this table. Each image must be captured separately from the actual preview and manually checked before publication.

12. Capture the Funding evidence register​

The Funding evidence register aggregates submitted application-form attachments and funding-delivery evidence. Use the same synthetic browser profile for Applicant and Operations so file metadata and local file bytes are available to the register.

For the Funding evidence register, capture these states:

CaptureNavigate to / showSuggested file
Register overviewFunding evidence register header, metrics, current application-form files, funding evidence and preserved historical snapshotsoperations/funding-evidence-register-overview.png
Application-form attachmentsSubmitted form attachments, review status and Open Document register hand-offoperations/funding-evidence-application-documents.png
Reviewer workloadAssigned reviewer cards, unassigned files and a deliberately overdue synthetic itemoperations/funding-evidence-review-queue.png
Inventory filtersSearch/filter controls, evidence type/status and open funding case hand-offoperations/funding-evidence-register-filters.png
Retention metadataRetention class, synthetic schedule reference, retain-until date and legal-hold controloperations/funding-evidence-retention.png
Audit exportCSV and JSON export controls with a filtered evidence inventoryoperations/funding-evidence-audit-export.png

For the captures:

  1. Use a case already selected in Adjudication and issued an offer from Funding Delivery.
  2. In Applicant Workspace, submit a synthetic offer acceptance file and at least one condition-evidence file. Complete the contracting and sample disbursement gates only with synthetic details, then create a milestone and upload a sample progress file.
  3. In Operations, open Funding evidence register from the top action row. Capture the overview with application-form attachments, acceptance, condition and milestone evidence represented.
  4. Select an application-form attachment and capture its source status and Open Document register action. Open it and confirm the existing form-document review controls remain the authority for that evidence type.
  5. Open Assignment & retention metadata for a current funding evidence file. Enter a fictional reviewer label and due date. Use a deliberately past date for one separate test item to demonstrate the overdue card. Capture the reviewer workload queue.
  6. Search for an application reference or file name, filter by evidence type/status/reviewer and capture the filtered results. Select Open funding case and verify that Funding Delivery opens the matching response/form version.
  7. For retention, use an explicitly fictional schedule reference such as DEMO-SCHEDULE-01. Enter a synthetic retain-until date and show the legal-hold checkbox. Do not imply that this is an approved CEDA schedule or retention period.
  8. Capture a date-reached item as Retention date reached · review only. Do not delete or dispose of the file.
  9. Apply a filter and capture the Export CSV and Export JSON controls. Use only synthetic notes and files because the export can include internal reviewer notes.
  10. Save approved images under apps/ceda-docs/static/img/operations/ and embed each image in the Funding evidence register guide at the corresponding step.

Do not publish real applicant names, signed offer letters, identity documents, contracts, bank statements, payment references, reviewer personal data or confidential business evidence.

Current capture coverage: the repository does not yet contain genuine Funding evidence register screenshots. All six images in this table must be captured separately from the actual preview, manually reviewed and then embedded in the guide.

13. Publish​

The CEDA documentation project is built with Docusaurus and deployed to Cloudflare Pages by the repository's CEDA User Guides GitHub Actions workflow.

A commit that changes apps/ceda-docs triggers a new documentation build and deployment. The CEDA portal's Help link opens the Operations guide when the user is in Operations.

14. Privacy and licensing notes​

Mimik is MIT-licensed and runs locally in the browser. Its basic capture, editing and export do not require a Mimik account or cloud upload. Optional AI descriptions and voice features require a provider key and send relevant content to the provider selected by the recorder; leave these optional features off for the CEDA documentation workflow unless they are specifically approved.

The documentation project uses Docusaurus and a local-search theme. The site is statically generated and hosted on Cloudflare Pages.