Funding offers, acceptance and milestones
The Applicant workspace shows applicant-visible funding information after CEDA records a separate authorised approval and marks an offer as issued in the Funding Delivery desk. It also lets the applicant respond to the offer and attach supporting evidence to outstanding funding conditions and implementation milestones.
The Applicant and Operations workspaces use the same browser-local Funding Delivery record and local IndexedDB file store. They are not connected to CEDA's live systems, secure applicant accounts, official offer letters, legal agreements, finance systems or notifications. Use fictional offer details and harmless synthetic files only. Never upload actual signed agreements, banking information, confidential applicant documents or real funding evidence.
1. Understand when the Funding progress card appears
The Funding & portfolio — Your funding progress card appears when:
- Adjudication has recorded a Selected panel outcome for the application response; or
- Operations has created a Funding Delivery record for a response version that exists in the Applicant workspace.
A panel selection is not the same as an authorised funding approval. The card may first display that the panel selected the proposal and that CEDA's separate approval is pending. It does not mean that an offer is guaranteed.
Funding records are linked to the application ID, response version and published form version. If the case relates to an earlier submitted version, the card identifies that exact response and form version.
2. Review an issued funding offer
When Operations records an authorised approval and marks an offer as issued, the Applicant workspace displays the offer details:
- approved CEDA product or facility;
- offer reference;
- offer amount;
- issue date and response deadline; and
- offer terms summary.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-offer-issued.png. Do not use a mock-up or a renamed overview image.
- Open the Applicant workspace.
- Find Funding & portfolio — Your funding progress beside the application status.
- Confirm the application response and published form versions shown on the card.
- Read the product, offer reference and amount.
- Read the full terms summary and check the response deadline.
- Compare the offer with your application and contact CEDA through its approved channel if the details are unclear.
The offer is shown only after it is marked as Issued in the Funding Delivery preview. The prototype does not generate or deliver a signed offer letter. The displayed terms are a browser-local sample record.
3. Accept an offer
To accept an offer in the preview:
- Under Your response, choose Accept this offer.
- Add an optional note for CEDA.
- Under Supporting evidence, select the signed acceptance or another harmless synthetic acceptance file.
- Confirm the selected filename appears.
- Select Submit acceptance.
- Confirm that the card shows Your response: Accepted and the submitted file appears beneath the response.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-offer-acceptance.png. Do not use a mock-up or a renamed overview image.
An acceptance cannot be submitted without at least one supporting evidence file. The preview accepts PDF, Word, Excel, PNG and JPEG files, up to five files of 10 MB each.
After submission, the card shows Acceptance evidence submitted — awaiting CEDA review. Operations reviews the exact file set against this application's response and form versions. When CEDA accepts the evidence, the Applicant card shows Acceptance evidence accepted by CEDA. Only then can Operations proceed to the contract step.
If CEDA selects Request replacement, the Applicant card displays the applicant-facing explanation and an Upload replacement files control. Select the new acceptance file(s) and choose Submit replacement evidence. The original offer response remains recorded; the new files replace the current evidence set for review, while the prior file snapshot and review history remain in the Operations record. After replacement submission, the Applicant card returns to awaiting CEDA review.
The Applicant sees the message intended for them, not the internal reviewer note. The preview does not verify a signature, transmit the acceptance or execute a funding agreement.
4. Request changes to an offer
If the terms need to be reviewed:
- Choose Request changes.
- Explain the terms or information you would like CEDA to review. Enter at least 20 characters.
- Optionally attach supporting material.
- Select Send change request.
- Confirm the Applicant card shows the submitted request.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-offer-changes-requested.png. Do not use a mock-up or a renamed overview image.
The request is saved in the shared browser-local Funding Delivery record. Operations can see the applicant's status, note and supporting files. A change request does not accept the offer and does not permit contracting.
CEDA must review the request and use its approved process to determine whether revised terms can be offered. The preview does not negotiate, amend or reissue an offer automatically. Use CEDA's approved contact route for time-sensitive matters or an offer that is close to expiry.
5. Decline an offer
- Choose Decline this offer.
- Enter at least 20 characters explaining the decision.
- Optionally attach supporting material.
- Select Submit decline.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-offer-declined.png. Do not use a mock-up or a renamed overview image.
The response is recorded for CEDA review. A declined offer cannot proceed to contracting in this preview. The portal does not send a formal decline notice or close an official funding application.
6. Upload evidence for outstanding funding conditions
After an offer or agreement lists conditions precedent, the Applicant workspace displays each condition and its current status.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-conditions-evidence.png. Do not use a mock-up or a renamed overview image.
- Find Conditions to complete.
- Read the condition title and status.
- For an item marked Outstanding, select Add supporting evidence.
- Choose one or more synthetic files that meet the file restrictions.
- Confirm that the filenames appear in the card.
- Repeat for each applicable outstanding condition.
The preview permits up to five files of 10 MB each for a condition. The selected file bytes are stored in the current browser's local IndexedDB store, while file metadata is attached to the version-linked Funding Delivery record.
Uploading evidence does not change the condition status. The Applicant card displays Evidence submitted — awaiting CEDA review while CEDA reviews the current files against the exact response/form version. An accepted review changes the condition to Satisfied. A waiver is recorded separately by CEDA using an authorised waiver reference.
If CEDA requests replacement, the Applicant card displays the replacement message and the upload action changes to Upload replacement evidence. Choose a new file set and submit it. The previous review and file snapshot remain in the Operations history, while the newly uploaded files become the active set for the next review. Internal reviewer notes are not shown to the applicant.
7. Follow funding releases
When Operations schedules funding tranches, the Applicant card displays each amount, planned date and whether it is planned or recorded as paid.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-releases.png. Do not use a mock-up or a renamed overview image.
The Applicant view does not expose internal payment-verification notes or officer details. A Paid status is a local preview record and is not proof of a bank transfer or receipt of funds.
8. Submit milestone evidence and follow implementation
After funding delivery starts, the Applicant workspace displays the implementation milestones and their due dates.
Capture the actual Applicant preview state and add the reviewed image as /img/applicant/funding-milestone-evidence.png. Do not use a mock-up or a renamed overview image.
- Find Implementation milestones.
- Read the milestone title and due date.
- For a milestone marked Pending, select Submit milestone evidence.
- Choose the relevant synthetic progress report, photograph or supporting file.
- Confirm the selected filename appears.
- Check the milestone status again after CEDA reviews the evidence.
The file is stored locally and attached to the same funding case record. The Applicant card shows Evidence submitted — awaiting CEDA review until CEDA accepts the current file set in Operations and records a verified completion date. An accepted review changes the milestone to Completed.
If CEDA requests replacement, the Applicant view displays the applicant-facing message and changes the upload action to Upload replacement evidence. Submit the new files; the earlier file snapshot and review event remain in the Operations history. The milestone stays Pending until the replacement evidence is accepted. Internal reviewer notes are not displayed to the applicant.
9. Download a file you previously submitted
Uploaded response, condition and milestone evidence appears as a file link in the corresponding card. Select the filename to download the stored file from the current browser's local document store.
If the browser's local IndexedDB data has been cleared, or the file is opened in a different browser profile or device, the file may not be available. This is not a production document-storage or recovery service.
10. Understand the information boundary
The Applicant workspace displays the offer terms intended for the applicant, the applicant's own response, condition titles and statuses, tranche dates and amounts, and implementation milestones. It does not display independent evaluator scores, evaluator rationales, confidential panel deliberations, internal approval rationale, payment-verification officer details or internal risk notes.
In production, CEDA must ensure that applicant-specific authentication and server-side authorisation restrict every offer, document, condition and milestone to the correct applicant organisation. The current open preview does not enforce that access boundary.
Production requirements
Production use requires authenticated applicant access, server-side ownership checks, secure private file storage and malware scanning, authorised offer publication, expiry and amendment workflows, legally effective acceptance, contract generation and signature verification, conditions-precedent review and waiver authority, finance-system payment reconciliation, milestone reporting, applicant notifications, retention controls and a durable audit trail.