Raffles Consulting Services
Review an EDGE rejected application against the decision, activity, timing and evidence before deciding whether to apply again.
An EDGE rejected application is not a cue to resend the same proposal with more optimistic wording. Enterprise Singapore says a company may apply again after considering the rejection reason, while projects that do not align with EDGE objectives or have already commenced will not be supported. A disciplined review should therefore establish what failed, what can genuinely change and whether a fresh application remains possible.
Preserve the decision record
Save the submitted form, attachments, acknowledgement, correspondence and rejection notice in one dated file. Record the application reference, activity, supplier, project dates, amount and the people who approved the submission. Do not edit the historical package. The review needs the version that the agency actually assessed, not a cleaner reconstruction prepared afterwards.
Copy the stated rejection reason exactly into a private working paper, then separate explicit findings from assumptions. A short notice may identify one decisive problem without listing every weakness. If the wording is unclear, use the official channel identified in the notice or BizSG. Avoid treating an adviser or supplier’s guess as the agency’s position.
Test whether the project had already started
The current official EDGE FAQ says projects that have commenced before application are not supported. Check purchase orders, accepted quotations, deposits, contracts, invoices, delivery records, user provisioning and project work. The first commitment may be earlier than the accounting payment date.
Build a dated commitment timeline and attach the underlying records. If the project started, changing the description or supplier name does not reverse that fact. Management should decide whether to proceed commercially without support rather than presenting the same committed work as a new project.
Recheck the selected EDGE activity
Compare the problem, deliverables, applicant sector and cost items with the current activity page. One application is submitted for each activity, so a proposal that combines several unrelated outcomes may not fit the chosen route. Record the page version and access date because available activities, support limits and required documents can change.
Use the current EDGE directory rather than an old grant summary. If no activity now matches the project, stop. A different title cannot make an unsupported operating cost, routine compliance task or general purchase eligible.
Reconcile the application facts
Check the legal applicant, local ownership, employee count, revenue, group relationships and financial figures against current corporate and accounting records. Trace each declaration to a named source. A typo may be repairable; a change that affects eligibility or the applicable enterprise definition needs a fresh, documented assessment.
Review the supplier name, quotation date, scope, price, payment schedule and project period across every attachment. Look for inconsistent totals, different product bundles and deliverables that appear only in marketing material. The application should describe one coherent project that the company itself understands and manages.
Distinguish weak evidence from a weak project
A useful project can still be poorly evidenced. Rebuild the current-state baseline from company records, define the business problem, name internal owners and show how completion will be measured. Keep calculations and source samples. Unsupported percentages or supplier forecasts are not company evidence.
A weak project has a different problem: unclear need, little operational ownership, benefits that depend entirely on a vendor claim or no credible implementation capacity. Adding documents may not cure it. Compare the proposal with the broader Singapore business support decision guide before spending more time on grant preparation.
Decide what a fresh application would change
List every proposed change beside the evidence supporting it. Legitimate changes can include a corrected activity, clearer scope, a new baseline, realistic outcomes or a genuinely uncommitted future project. Do not invent distinctions to avoid the earlier decision. If the commercial project remains identical, explain why the new package would answer the stated concern.
Confirm that no new commitment has been made while the review was underway. Keep the business decision and grant decision separate. The company may choose to proceed at its own cost, but it should not assume that a later submission will reimburse work already started.
Obtain a second internal review
Ask someone who did not prepare the original application to trace the new statements back to source records. They should test the rejection reason, timing, activity fit, supplier scope, baseline and projected results. Record open questions and resolve them before submission.
The reviewer should also compare the package with the EDGE post-submission commitment guide. A new application must not create pressure to commit before approval. Management remains responsible for cash flow, delivery and the possibility that support is not awarded.
Close the review with a written decision
Choose one of three outcomes: submit a materially improved fresh application, redesign the commercial project first or do not reapply. State the reasons, evidence owners and next permitted action. A written decision prevents the old package from being quietly recycled by another team member.
If a fresh application is prepared, give it a new controlled file and retain the rejected version. After submission, save the new acknowledgement and verify the official status before retrying any uncertain action. The audit trail should show an honest response to the rejection rather than an attempt to erase it.
Keep the next submission independent
If management decides to reapply, create a clean approval record for the future project. Reconfirm supplier independence, commercial need, project timing and budget. Employees who participated in the rejected submission should disclose any new information, while the fresh reviewer should challenge whether proposed changes are real or merely presentational. Keep correspondence professional and factual; a rejection is an administrative decision, not evidence that the company’s commercial objective lacks value.
Set a final pre-submission meeting with the business owner, finance and the authorised submitter. Read the declarations against the evidence pack and confirm that no contract, payment, delivery or project work has begun. Record the exact package approved for filing. This last comparison matters because a revised quotation or late management instruction can reintroduce the timing or scope issue that the root-cause review was meant to resolve.
The useful outcome of an EDGE rejected application review is not a longer form. It is a clear decision about whether a future, uncommitted project now fits the programme and is supported by evidence that management can defend.