Letter of Offer Checklist: 30 Days to Secure Your Grant

The grant approval is the start, not the finish. — a question every Singapore SME owner exploring letter of offer singapore eventually faces. — a question every Singapore SME owner exploring letter of offer checklist eventually faces.

Across the grant projects I've advised on — and the CTC cycle I ran for my own unionised company — I've watched owners win an EDG Letter of Offer or a CTC Letter of Award and then go quiet for six weeks while they "kick off the project." Six weeks later they start asking what they need to do to claim, and discover that the milestone they were supposed to deliver in week 2 is now late, the vendor contract they thought was a formality has scope drift relative to the LOA, and the documentation trail they need for the first claim doesn't exist.

The first 30 days after a Letter of Offer is the highest-leverage window of the entire grant. It is when you lock in the claim trail that decides whether the funded amount actually reaches your bank account.

This is the operator checklist.

---

TL;DR — the 60-second version

• Days 1–7 — Re-read the LOA carefully. Map every condition. Identify the first claim milestone.
• Days 8–14 — Lock down the vendor contract. Match every scope line in the contract to a scope line in the LOA. No drift.
• Days 15–21 — Set up the documentation system. One folder per claim milestone. Versioned.
• Days 22–30 — Hold the kick-off meeting with the vendor, consultant, and (for CTC) the worker representative. Get the project clock running, formally.

The full structure follows.

---

Days 1–7: Read the Letter of Offer like a contract, because it is one

The LOA (or Letter of Award, for CTC) is the document that governs everything from here. Most owners skim it, file it, and move on. Don't. Your Letter of Offer is the legal instrument that determines whether your claim succeeds or stalls.

What to extract on the first read

1. The funded amount — gross and net, broken down by cost line if the LOA itemises (most do)
2. The funding period — when claims must be made by, and when the project must complete
3. The claim milestones — what evidence triggers each disbursement, and when each is due
4. The KPIs / outcome conditions — what the company must deliver to satisfy claims (especially the worker outcome for CTC, the capability deliverables for EDG, the market-entry deliverables for MRA)
5. Any scope variations the grant officer wrote in — sometimes the LOA narrows or sharpens the original proposal scope. The narrowed version is what governs.

The non-obvious things to look for

• Mismatches between the LOA and your original proposal. If the officer trimmed a deliverable, the trimmed version is now your contract.
• Claim documentation requirements — invoice formats, evidence of payment, proof-of-delivery, worker attendance records (for CTC), MRA-specific receipts.
• The audit clause — what records must be kept and for how long after project close.

Make a one-page summary of all of the above. That summary is your reference document for the rest of the project.

---

Days 8–14: Lock the vendor contract against the LOA, line by line

This is where most claims fail.

Your proposal said one thing. The LOA said a slightly tightened version of it. Your vendor's quote was written before the LOA was issued and doesn't reflect the final scope. Every line of difference is a future claim issue.

The exercise

Open three documents side by side:

1. The LOA scope as written
2. The vendor's existing quote or draft contract
3. Your original proposal

For every deliverable in the LOA:

• Does the vendor contract describe the same scope, in language consistent with the LOA?
• Are the milestones in the vendor contract aligned to the claim milestones in the LOA?
• Are the payment terms structured so the vendor invoice can be evidence for a grant claim?

If there is any divergence, fix the vendor contract before signing. The cost of fixing a vendor contract pre-signing is zero. The cost of fixing it later is a delayed claim.

Two specific patterns to avoid

Pattern 1 — Lump-sum vendor invoices that don't map to claim milestones. A vendor sends a single S$80k invoice when the LOA expects three S$20k–30k milestone disbursements. Your claim officer cannot match the invoice to the milestone. Restructure the vendor invoice schedule before any work starts.

Pattern 2 — Scope items in the vendor contract that aren't in the LOA. "Stretch goal" features the vendor wants to deliver but that aren't grant-funded. If they're in the same invoice as the funded scope, they create claim ambiguity. Separate them into a non-grant-funded change order.

---

Days 15–21: Set up the claim documentation system

You will make multiple claims over the life of the project. Each one needs a clean evidence package. Build the system before you need it.

The minimum folder structure

/Grant-[grant-name]-[project-name]/
  /00-LOA-and-amendments/
  /01-Vendor-contracts/
  /02-Milestone-1/
    /a-deliverable-evidence/
    /b-invoices/
    /c-payment-proof/
    /d-claim-submission/
  /02-Milestone-2/...
  /02-Milestone-3/...
  /99-Audit-trail/

For each milestone folder, the rule is: everything an auditor would need to verify the claim sits in this one folder, dated and versioned. No exceptions, no "I'll find it later."

What goes into the audit trail folder

• All correspondence with the grant officer (a dated PDF export of email threads is fine)
• All formal amendments to the LOA or vendor contract
• Internal sign-offs (CFO approval, board minutes if relevant, CTC committee minutes for CTC projects)
• Periodic status updates if the LOA requires them

Owners who treat the audit trail as something they'll assemble at the end of the project always struggle. Owners who file documents as they happen never do.

---

Days 22–30: The formal kick-off meeting

A formal kick-off meeting locks the project clock. It also creates the first piece of audit trail.

Who should be in the room

• You (or the operating sponsor inside the company)
• The appointed consultant (for EDG; recommended for CTC and MRA)
• The lead vendor delivering the build
• For CTC: the NTUC / Worker Representative who signed the transformation plan
• For larger projects: the CFO or whoever signs claim submissions

The agenda — 60 minutes is enough

1. Read the LOA scope summary out loud (10 min). Yes, out loud. Everyone in the room confirms they're working from the same scope.
2. Walk the milestone schedule and confirm each owner (15 min)
3. Walk the vendor contract milestone schedule and confirm alignment with the LOA (10 min)
4. Walk the documentation requirements per milestone (10 min)
5. Confirm next checkpoint and decision points (10 min)
6. Document everything in a one-page kick-off note signed by all attendees (5 min)

That one-page kick-off note is the cleanest opening artifact for your audit trail.

---

Grant-specific things to add to the checklist

For EDG

• Confirm the consultant fee structure aligns with the LOA's eligible-cost itemisation
• Confirm IDP Stage 2/3 deliverables are explicitly tagged in the vendor contract
• Lock the IP clauses — for EDG-funded custom builds, IP ownership terms must be unambiguous

For PSG

• The vendor must invoice you AFTER the application is approved, not before. Confirm with the vendor.
• Keep the pre-approval vendor reference handy — claims reference it
• Note the 30 Nov 2026 SFEC expiry — if you're stacking PSG + SFEC, plan the training spend timeline accordingly

For CTC

• Confirm the worker outcome basis is documented in the LOA-aligned format (wage progression anchored to national average increment is the strongest)
• Schedule the first quarterly CTC committee meeting in the 30-day window
• Confirm the U SME / NTUC sign-off process for plan amendments — you cannot unilaterally re-scope a CTC plan post-LOA

For MRA

• Confirm the activity-specific scope (one activity per application — promotion, business development, or market set-up — bundling them is a common rejection trigger)
• Lock the market-specific vendor quotes (in-market consultant, legal, translation) before any travel
• Track the S$100k-per-market cap carefully — over-spend doesn't get retrospective top-up

For DTDi

• DTDi is automatic up to S$400k per YA from YA 2027 — no Letter of Offer per se, but the documentation requirement is the same
• Tag every overseas-expansion expense in your accounting system at the point it's incurred, not at year-end
• Coordinate with your tax adviser before the financial year closes

---

The 4 most expensive post-LOA mistakes I see

Mistake 1 — Treating the LOA as paperwork done

The LOA is the contract that decides whether you get paid. Re-read it. Summarise it. Reference it weekly during the project.

Mistake 2 — Vendor scope drift

The vendor delivers something slightly different from what the LOA funds. Claim gets clarified, narrowed, or partially denied. Lock vendor scope to LOA scope on day one.

Mistake 3 — Late documentation

Owners scramble at claim time to assemble evidence that should have been filed when it was generated. The result is delayed claims, claim queries, and sometimes lower-than-expected disbursements.

Mistake 4 — No audit trail for amendments

If anything changes mid-project — vendor swap, scope variation, timeline extension — formalise it in writing with the grant officer. Verbal agreements don't survive audit.

---

When to engage external help

For most projects, the consultant who scoped the application can also help shape the post-LOA process. The PMC-certified consultant who wrote the proposal already knows the LOA's eligible-cost itemisation, the milestone structure, and the documentation requirements — they should help build the 30-day checklist for your specific project.

If you didn't use a consultant for the application and now need post-LOA support, the most valuable help is usually:

• LOA scope review (1–2 hours)
• Vendor contract review against the LOA (2–3 hours)
• Documentation system setup (one workshop)

That's a fixed scope and short engagement. Anyone charging a multi-month retainer for "claim support" is usually selling more than you need.

For context on where this comes from: I hold PMC certification (PMC-10960), I'm a PSG vendor, and I've advised on 200+ PSG, 100+ EDG, 50+ MRA and 30+ CTC projects — plus run the CTC cycle for my own unionised firm. I don't submit or handle claims for a fee; I advise owners on what to lock down so their own claims disburse cleanly. If you want a 30-minute conversation on your specific LOA — where the claim risk sits in the first 30 days — message me. No charge for it.

---

Related reading

• PSG vs EDG vs CTC — which grant should you actually apply for? — the parent decision tree
• MRA vs DTDi — cash subsidy vs tax deduction — the overseas-expansion sequencing piece
• How to scope an EDG proposal that survives the templated rejection — the EDG application companion piece
• How to frame your CTC worker outcome — the CTC application companion piece
• How to form a Company Training Committee in Singapore — the CTC formation walk-through

---

Frequently Asked Questions

What happens if I miss the 30-day window?

You can still execute the checklist after 30 days, but the further you get into the project, the harder it is to fix vendor scope drift or documentation gaps retroactively. Claim officers expect to see vendor contracts and LOA-aligned documentation from the start. Late setup creates audit friction and claim delays.

Can I apply the same documentation system across multiple grants?

Yes. The folder structure adapts across PSG, EDG, CTC, MRA, and DTDi projects. The core principle is the same: one folder per milestone, everything an auditor needs in one place, dated and versioned. Only the LOA scope and claim milestones change per grant type.

If the vendor says they can't invoice by milestone, what do I do?

Escalate immediately. Vendor invoicing that doesn't match LOA milestones is a claim blocker. Either the vendor restructures their invoicing to align with your claim schedule, or you find a vendor who will. This is non-negotiable. If a vendor won't budge on invoice structure, they're signalling they don't understand grant-funded projects.

Do I need a formal kick-off meeting if we're a small team?

Yes. Even a three-person project needs a documented kick-off. It's not about ceremony — it's about creating a one-page record that everyone read the same LOA, agreed on the same scope, and confirmed the same milestones. That artifact is worth its weight during audit. For CTC projects, a formal kick-off is mandatory per the CTC governance rules.

What if the LOA says something that conflicts with my vendor contract?

The LOA wins. The LOA is the governing document for grant eligibility and claim. If your vendor contract says something different, treat it as a scope gap and fix it before work starts. This is why Days 8–14 exist — to catch and resolve these conflicts pre-execution.

---

— Nick