MRA change requests: an MRA change request should be filed through BGP before the approved project ends when dates, claim timing, costs or the vendor need.
MRA change requests: An MRA change request should be submitted through the Business Grants Portal before the approved project ends when the company needs to change its qualifying period, claim due date, project costs or consultant or vendor. The request is assessed by Enterprise Singapore. It is not approved merely because the project team records the change internally.
The safest approach is to compare the approved Letter of Offer with the proposed change before signing a revised quotation or allowing new work to begin. A change that looks commercial may alter the supportable scope, evidence or claim deadline.
Start with the accepted Letter of Offer
The current Market Readiness Assistance Grant page says an award sets out the conditions of support, amount, project qualifying period and deliverables. These details form the baseline for project delivery and the later claim.
For this reason, create a one-page award summary after acceptance. Record the overseas market, approved activity, vendor, cost lines, support amount, start and end dates, claim deadline and deliverables. Link every entry to the Letter of Offer or approved proposal. This prevents a project manager from treating the original application as a general budget that can be rearranged freely.
Keep the approved documents read-only and use a separate change register. The register should show the date the issue arose, business reason, affected amount or milestone, decision owner and BGP request status.
Decide whether the change needs Enterprise Singapore approval
Enterprise Singapore lists changes to the project start and end dates, claim due date, project costs and consultant or vendor as reasons for an MRA change request. A new employee contact or an internal reporting date may not alter the approved project, but the company should still update its own records.
In practice, ask three questions. Does the change affect when the supported work occurs? Does it change who performs the supported work or what the company pays? Does it change a deliverable or the evidence needed for the claim? If any answer is yes, check the BGP change route before the company commits.
Do not split one material change into several small variations to avoid review. Enterprise Singapore will assess the project as delivered against the approved terms.
Handle timing extensions before the end date
The current MRA FAQ states that companies with valid reasons may request an extension through BGP before the project end date. The maximum support period is 12 months, and companies generally have no more than three months after project completion to submit the claim, subject to the Letter of Offer.
At the same time, Prepare the extension request as soon as delay becomes likely. Explain the cause, work completed, revised milestones and measures taken to finish. Attach current evidence, such as a revised event date, overseas permit delay, landlord correspondence or vendor schedule. A statement that the team was busy is not a useful explanation.
If a project has barely started or faces a prolonged delay, the FAQ says the company should consider terminating the approved application and submitting a fresh application when ready. Compare that route with an extension before the existing period expires.
Change a vendor without creating a retrospective problem
The treatment depends on project status. Enterprise Singapore says that where payment has not been made and the project has not started, a company seeking a different consultant or vendor should submit a fresh application and cancel the existing approved project. Where work is ongoing, the company should submit a change request under project costs with the new quotation before the project end date.
As a result, do not pay the replacement vendor first and ask for approval later. Keep the old and new quotations, the reason for replacement, termination terms, work already delivered and any duplicated cost. Show clearly which cost belongs to each vendor.
Review conflicts and related-party connections again. A cheaper quotation is not automatically comparable if the scope, market coverage or deliverables changed.
Use a concise change comparison
| Change | Evidence to prepare | Control before action |
|---|---|---|
| Project end date | Delay reason, progress record and revised milestones | Submit before the approved end date |
| Claim due date | Audit and document schedule | Confirm the Letter of Offer deadline |
| Vendor | New quotation, replacement reason and old contract status | Do not make an unapproved commitment |
| Project costs | Old and revised cost table with scope explanation | Do not assume more grant support |
| Deliverable | Original and revised output with commercial reason | Check whether the activity remains supportable |
Do not treat an approved change as extra funding
The MRA FAQ says grant amounts are finalised when the grant is approved and requests for additional funding above the original grant amount will not be considered. A revised project cost may therefore leave more cost for the company to bear.
For example, Update the finance forecast after the BGP outcome. Separate total project cost, supportable cost and approved grant. The company should understand the cash effect before accepting revised supplier terms.
If a cost falls, preserve the revised calculation and claim only the supported amount actually incurred and paid. Approval sets a ceiling and conditions. It does not turn an unspent amount into an entitlement.
Keep the claim file aligned with the final approval
After a change is approved, update the project summary, purchase order, milestone tracker and claim index. Store the BGP request, attachments and outcome with the Letter of Offer. Tell the auditor which version controls the claim.
In addition, During the final review, reconcile the invoices, proof of payment and deliverables to the approved vendor, period and cost lines. Explain any residual difference. Do not ask the auditor to reconstruct the change history from email.
The Singapore business support guide remains the pillar cornerstone. The MRA claim evidence guide covers the final file, while the MRA overseas-cost guide explains inter-billing. The Enterprise Support and Grants hub links the wider library.
A well-controlled change request leaves no uncertainty about the approved version of the project. The delivery team, finance team, auditor and Enterprise Singapore should all be working from the same dates, vendor, cost table and deliverables.