Skip to main content

Funding delivery and portfolio follow-through

The Funding delivery desk continues an application after Adjudication records a Selected panel outcome. It separates that outcome from the later authorised funding approval and provides a synthetic record for offer terms, applicant response, agreement execution, conditions precedent, disbursement tranches and post-funding milestones.

Open the Operations preview.

Browser-local preview only

The Funding delivery desk uses synthetic records stored in this browser. It does not verify delegated authority, issue a legal offer, collect an applicant signature, execute a contract, instruct a payment, send notifications or integrate with CEDA's finance systems. Do not enter real applicant details, approval references, contract information or financial records.

1. Understand the panel-to-funding hand-off​

A panel outcome of Selected is not the same as authorised CEDA funding approval. The Funding delivery desk requires a separate approval record before the offer can be marked as issued.

A case appears only when all the following are true:

  • the application has an active evaluator assignment for the exact response and published form version;
  • every active evaluator assignment for that version has a matching final submission;
  • each submission matches its original assignment, evaluator identity, application, response version and form version;
  • every completed review records No conflict;
  • Adjudication has a decision record whose outcome is Selected; and
  • the shared lifecycle feed still identifies that same response and form version as the selected panel outcome, or an existing Funding delivery record has already progressed into the Offer, Implementation or Monitoring stage.

The desk does not show Not selected, Clarification required or Deferred panel cases as funding-delivery cases.

The current prototype does not enforce a formal minimum number of evaluators or panel quorum. The number of completed reviews shown is the number of active assigned evaluator identities whose submissions match this response version.

2. Open Funding delivery​

  1. Open CEDA Operations.
  2. Select the correct funding programme in the Operations programme filter.
  3. In the top action row, select Funding delivery.
  4. Review the Selected cases queue.
  5. Select the synthetic case by its application reference and response version.
Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-overview.png. Do not substitute a mock-up.

The selected case summary shows the application ID, exact response and form versions, number of independent evaluators and applicant-requested amount, where captured. The applicant's preferred funding route and requested amount are not a final product match or an approved amount.

3. Record the authorised funding approval​

In 01 — Authority check, record the separate authorisation:

FieldWhat to enter
Authorised approving body / delegationThe CEDA body or delegated authority specified in the approved delegation framework
Approval / minute referenceThe reference identifying the approval record
Approval dateDate of the approval
Approved amount (BWP)The amount authorised by the approving authority
Approval conditions / reference noteOptional conditions or a location/reference for the underlying approval record
  1. Verify the approving body and approval reference against the applicable CEDA delegation outside this preview.
  2. Enter the approval reference, date and positive amount.
  3. Select Record authorised approval.
  4. Confirm the summary shows the approval body, reference, date and amount.

The prototype records the information and moves the sample workflow to Offer and conditions. It does not authenticate the person entering it, verify delegated authority, approve a facility or replace the official approval minute.

Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-approval.png. Do not substitute a mock-up.

The approval record is locked after it has been recorded in this preview. Do not overwrite it to represent an amendment; production requires a governed amendment and audit process.

4. Prepare and issue the offer​

Complete 02 — Offer and terms after recording the authorised approval.

  1. Confirm the approved CEDA product or facility.
  2. Enter the offer reference.
  3. Enter the offer amount. It must be positive and no greater than the authorised amount.
  4. Enter the issue date and expiry date. The expiry date must not precede the issue date.
  5. Summarise the approved terms, including the facility and any conditions relevant to the applicant.
  6. Select Mark offer issued in preview.
  7. Review the offer reference, amount and expiry date in the confirmation record.
Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-offer.png. Do not substitute a mock-up.

The offer becomes read-only after it is marked as issued. This action changes only the local preview status. It does not generate a signed offer letter or send a communication to the applicant.

5. Record the applicant's response​

The applicant submits the response from the Funding & portfolio — Your funding progress card in the Applicant workspace. This is the only response-entry point in the current preview.

When the applicant submits a response:

  • the Applicant workspace writes the response into this shared Funding Delivery record;
  • the response date, response type and applicant note appear here;
  • uploaded acceptance or correspondence files appear as downloadable evidence links; and
  • Operations displays the response read-only so an operator cannot replace the applicant's submitted response.

Until a response is received, this section displays Awaiting applicant response and directs the applicant to the Applicant workspace. The Operations preview does not provide a second editable response form and does not send an invitation or notification.

An Accepted response does not unlock contracting immediately. Operations must review the submitted acceptance evidence in this section:

  1. Enter the Evidence reviewer name / role above the workflow steps.
  2. Open each applicant-submitted file.
  3. Enter an Internal review note for the version-linked record.
  4. Enter an Applicant-facing message when a correction or clarification is needed.
  5. Select Accept evidence or Request replacement.

An accepted review unlocks contracting only when the reviewed file set still matches the current applicant evidence. A replacement request leaves contracting blocked and releases the applicant-facing message in the Applicant workspace. The applicant can upload a replacement file set; the previous review and its file snapshot remain in the review history. Declined or Changes requested offer responses do not permit contracting. CEDA must review a change request and decide whether revised terms can be prepared through its approved process.

Review records capture the reviewer name/role, decision, internal note, applicant-facing message, evidence snapshot, timestamp, application response version and published form version. The review history is retained in this browser-local case record; internal notes remain in Operations and are not displayed in the Applicant workspace.

Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-acceptance.png. Do not substitute a mock-up.

The preview records the response but does not receive or authenticate the applicant's letter, email or signature.

6. Record the executed agreement​

Complete 04 — Contracting only after an accepted offer has been recorded.

  1. Enter the agreement type and contract reference.
  2. Enter the CEDA signing date.
  3. Enter the applicant signing date.
  4. Enter the effective date.
  5. Select Record contract executed.
  6. Confirm the agreement appears as executed in the preview.
Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-contract.png. Do not substitute a mock-up.

Both party signing dates and the effective date are required by the demonstration. The action moves the sample application to Funding and implementation. It does not generate an agreement, verify signatures or create a legally executed contract.

7. Record conditions precedent​

Use 05 — Conditions precedent to record the obligations that must be satisfied before disbursement.

  1. Enter each condition and the responsible party or role.
  2. Select Add condition.
  3. Keep the condition as Outstanding until applicant evidence has been checked.
  4. Open the applicant-submitted files in Applicant evidence received.
  5. Enter the reviewer identity and review notes in the evidence-review panel.
  6. Select Accept evidence to record the condition as Satisfied, or Request replacement to keep it Outstanding and ask the applicant for new evidence.
  7. To use the separate waiver route, enter the authorised waiver reference and select Save condition.

A condition cannot be changed to Satisfied through the status selector. Satisfaction is recorded by an accepted, version-linked evidence review. A replacement request preserves the previous file and review event. A waiver still requires an authority reference and does not represent an evidence acceptance.

Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-conditions.png. Do not substitute a mock-up.

Where the approved offer has no conditions precedent, do not leave the list empty as an implicit assumption. Enter the authorised reference confirming that no conditions apply and select Confirm no conditions apply.

Applicants can attach files to outstanding conditions from the Applicant workspace. Those file links appear here under the corresponding condition as Applicant evidence received. Record the review decision in the evidence-review panel. An accepted review sets the condition to Satisfied and records the reviewed file set; a replacement request leaves the condition outstanding and releases the applicant-facing message. The status selector cannot bypass this review action.

Disbursement is blocked while any recorded condition remains outstanding or lacks the required evidence/waiver reference. Once the first payment is recorded, the preview locks the conditions register against later edits; any real amendment must follow the approved CEDA governance and audit process.

8. Schedule and record disbursements​

The 06 — Disbursement control section shows the authorised amount, total planned tranches, amount recorded as paid and remaining authorised balance.

  1. Confirm the agreement is marked executed.
  2. Confirm every recorded condition is satisfied or formally waived, or the authorised no-conditions reference has been recorded.
  3. Enter a positive tranche amount and planned date.
  4. Select Schedule tranche.
  5. For a planned tranche, enter the paid date, payment reference and verifying officer.
  6. Select Record as paid.
  7. Confirm the amount appears in the recorded-paid total.
Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-disbursements.png. Do not substitute a mock-up.

The preview checks that the total planned and paid tranches do not exceed the authorised amount and blocks recording a payment until the agreement and conditions gates are satisfied.

Record as paid is a local register action only. It does not initiate a bank transfer, payment instruction or accounting posting.

9. Set up post-funding monitoring​

After at least one tranche is recorded as paid:

  1. Enter a Milestone / reporting obligation.
  2. Set its due date.
  3. Select Add milestone.
  4. The applicant uploads progress evidence for a pending milestone in the Applicant workspace.
  5. Open the submitted files under the milestone's Applicant evidence received list.
  6. Enter the reviewer identity, internal note and applicant-facing message.
  7. Enter the verified completion date and select Accept evidence to mark the milestone Completed, or select Request replacement to leave it Pending and ask the applicant for another evidence set.
  8. Add the remaining reporting obligations and implementation milestones.
  9. Once at least one milestone exists, select Start post-funding monitoring.
Screenshot capture pending

Capture the actual preview state and add the reviewed image as /img/operations/funding-delivery-monitoring.png. Do not substitute a mock-up.

The Applicant view shows each milestone's due date, status and released applicant-facing review message. Evidence submitted for a pending milestone is listed in Operations under the corresponding item. The Accept evidence action records the reviewer, file snapshot, response/form versions and verified completion date before marking the milestone Completed. Request replacement leaves it Pending and allows the applicant to submit a new evidence set. Uploading a file in the Applicant workspace does not complete the milestone automatically.

Starting monitoring moves the application to Post-funding monitoring in the sample workflow. Completed milestones retain their date and evidence reference in the browser-local record.

10. Understand the workflow stages​

ActionSample workflow stage
Selected panel outcomeFunding decision review
Authorised approval recordedOffer and conditions
Offer issued / response recordedOffer and conditions
Agreement executedFunding and implementation
Disbursement recordedFunding and implementation
Monitoring startedPost-funding monitoring

The workflow feed carries the application ID, response version and form version. It is a synthetic status feed, not a finance ledger or official applicant notice.

Production requirements​

Before production use, CEDA must approve the delegation matrix, approval thresholds, product-specific offer templates, interest/repayment or investment terms, acceptance and amendment rules, contract execution and document custody, conditions-precedent policy, payment authorisations and segregation of duties, finance-system integration, portfolio monitoring, applicant communications and records retention. Approval, contracting, disbursement and monitoring must use authenticated roles, durable evidence, server-side validation and an authoritative audit trail.