EDGE post-submission commitment: understand the approval risk

An EDGE post-submission commitment may be supportable if the application is later approved, but the company bears the risk while assessment is pending. That distinction matters whenever a supplier asks for a deposit, a project team wants to begin work or management treats submission as if it were approval.

Fix the no-retrospective-work boundary

The official EDGE FAQ says an application is retrospective when the company starts work or makes payment, including a deposit, before submitting the application. Such applications will be rejected. Preserve the BGP submission acknowledgement and exact timestamp before releasing any purchase instruction.

A draft saved in BGP is not a submission. A management decision to apply is not a submission either. Procurement should use the official acknowledgement, not an email from the project owner, as the controlling evidence.

Understand what changes after submission

The same FAQ says a company may proceed with a purchase, payment or deposit after successful application submission and before the outcome. The cost may be supported if the application is subsequently approved, but the company bears the risk if it is not approved.

That is a timing rule, not an assurance of eligibility. The selected activity, vendor, cost, deliverable, applicant and project still need to satisfy the current criteria and eventual Letter of Offer. A supplier should never describe pending support as guaranteed funding.

Prepare a management risk decision

Before committing, show the board or authorised manager the full contract value, deposit, cancellation exposure, cash effect and alternative if support is not awarded. State clearly that the company can complete and pay for the project without grant proceeds.

Record why waiting is or is not commercially practical. Genuine reasons may include a lease deadline, expiring supplier capacity or a regulatory implementation date. An artificial vendor discount should not be accepted without checking whether it changes scope or creates pressure to misstate the timeline.

Keep the vendor instruction precise

The purchase order should identify the applicant, project, scope, milestones and payment terms. Do not backdate it. If a quotation was accepted only after submission, preserve the acceptance evidence and avoid wording that implies work began earlier.

Tell the vendor that grant assessment remains independent. The company, not an adviser or supplier, applies, pays and claims. The EDGE unrelated-vendor declaration guide covers the separate declaration needed when vendor relationships exist.

Reconcile the eventual Letter of Offer

If approved, compare the Letter of Offer with the committed contract line by line. Check supported cost categories, vendor, project dates, deliverables and claim due date. Do not assume the approved amount equals the amount ordered.

If the approval narrows scope, finance should separate supported and unsupported costs. If the application is rejected, account for the project as an ordinary business expenditure and continue only if management still supports the commercial case.

Control changes while assessment is pending

The FAQ limits changes after submission. Other than permitted date changes, a different need generally requires termination and a fresh application. Do not replace a vendor or rewrite the objective quietly while waiting for an outcome.

Keep a dated issue log for price changes, scope questions and project assumptions. Escalate a material change before more money is committed. A transparent decision can be explained; an undocumented change can make the approved file and actual project diverge.

Use a four-date chronology

Record quotation, application submission, contractual commitment and first work or payment as separate dates. Add the approval and Letter of Offer acceptance later. The chronology should be supported by original documents and accounting records.

Link the chronology to the Singapore business support decision guide, the enterprise-support cornerstone. An EDGE post-submission commitment is defensible when submission is proven, commercial risk was authorised and the actual project remains aligned with the approved scope.

Submission creates an opportunity to proceed at the company’s risk, not a right to funding. A short written decision before the first commitment keeps the commercial choice separate from the later grant outcome.

Run a no-support scenario

Prepare a cash-flow view that assumes no grant is awarded. Include the full supplier cost, financing, implementation staff, cancellation terms and any recurring subscription. If the project does not remain commercially sensible, management should wait for the assessment outcome.

Where management proceeds, write the decision in ordinary business language. State what was known, the unsupported amount at risk and the person authorised to commit. Do not use a conditional purchase order if the parties have already agreed that work will begin immediately.

After the outcome, compare the approved scope with the risk decision. This review improves future applications by showing which assumptions were reliable and which costs should not have been committed early.

Keep sales forecasts separate from grant support

Projects are often justified by expected savings, revenue or overseas growth. Preserve the assumptions behind those forecasts, but do not add the possible grant amount to project benefits. Support reduces a qualifying cost if approved; it does not create customer demand or prove that the chosen solution will work.

Set a commercial review after implementation even if the grant is awarded. Compare actual benefits, recurring costs and staff effort with the decision made before commitment. This prevents the grant outcome from becoming the only measure of project success.

Prepare a clean approval handover

Once the Letter of Offer arrives, circulate the accepted scope, dates, cost lines and deliverables to procurement, finance and the project manager. Retire earlier draft budgets so staff do not order against an obsolete version.

Record unsupported lines clearly and decide whether the company still wants them. The project can include ordinary business expenditure, but the claim must never imply that an unapproved item was part of the award.