CTC Committee Meeting Agenda Template Singapore

The Company Training Committee gets formed. The kick-off meeting happens. Minutes are filed. Then, in most companies, the committee never meets substantively again until claim time — when nobody can find the records of decisions that should have been made along the way.

The CTC committee meeting is the single most under-leveraged piece of the entire CTC framework. Used well, it is the governance body that makes the claim trail bulletproof, surfaces problems early, and gives the NTUC / Worker Representative real ownership of the worker outcome. Used badly, it is a checkbox at formation that signs the same minute template every quarter.

I learned this running the committee for my own company — Freemansland Consultancy is unionised, so we went through the full cycle ourselves — and then advising on 30+ other CTC projects. This is the agenda template I wish I'd had at the start: the one that turns the committee from a checkbox into a working governance body.

---

TL;DR — the 60-second version

• The CTC committee should meet at minimum quarterly during the project — monthly during high-activity phases
• Each meeting has 5 standing agenda items, plus 1-2 project-specific items
• The minutes from each meeting are part of the audit trail — they protect the claim
• The NTUC / Worker Representative is a co-author of the meeting outputs, not a rubber-stamp signatory
• Most rejected or trimmed CTC claims trace back to decisions that should have been made — and minuted — in committee meetings

---

Why this matters more than it sounds

The CTC framework places the Company Training Committee at the centre of the transformation. The committee is not a formality. It is the body that:

• Reviews progress against the committed worker outcomes
• Approves any variation to the transformation plan
• Documents the wage progression and role progression evidence
• Signs off on training programmes and consultant engagements
• Maintains the audit trail that supports claim submissions

When e2i reviews a claim, the question is not just "did the project happen" — it's "did the committee govern the project the way the LOA requires." A claim with strong committee minutes lands cleanly. A claim with weak or missing committee records gets queried.

The committee meeting is where the governance happens. Skip the meetings and the claims become harder, not easier.

---

The 5 standing agenda items

The committee meeting agenda should be predictable across every meeting — so the minutes are consistent across the project lifecycle and the audit trail is uniform.

Standing item 1 — Worker outcome progress (15 min)

The first standing item is always the worker outcome. Specifically: how is the committed wage progression tracking against the LOA commitment?

What the committee reviews:

• Current wages for the impacted staff at the start of the project
• Wages today (or at the most recent measurement point)
• The committed progression target from the LOA
• Whether the trajectory is on track to meet the target by the project completion date

If wages are tracking ahead, document it — that's claim-strengthening evidence. If wages are off-track, the committee should discuss why and what changes if needed.

The minute entry: "Reviewed worker outcome progress against LOA commitment. Current wage level: [X]. Committed end-of-project: [Y]. On-track / off-track: [status]. Adjustments required: [if any]."

Standing item 2 — Cost line review (15 min)

The 4 supportable cost lines — equipment, software, consultancy, training — should each be reviewed quarterly:

• What was spent in the period
• What's planned for the next period
• Whether spend is tracking to the LOA's eligible-cost breakdown
• Any variances that need attention

This is where you catch cost categorisation drift before it becomes a claim problem. → See LoA negotiation for why categorisation matters.

The minute entry: "Reviewed spend across 4 cost lines: equipment [X], software [Y], consultancy [Z], training [W]. Variances vs LOA: [if any]. Next period planned spend: [breakdown]."

Standing item 3 — Training delivery review (10 min)

What training has been delivered, what training is upcoming, attendance records, and any modifications to the training plan.

The questions:

• Are the planned training programmes being delivered on schedule?
• Are the impacted staff actually attending?
• Are completion rates on track?
• Any training that needs to be added, removed, or adjusted?

Training records are some of the most heavily audited evidence at claim time. Catching attendance gaps in the committee meeting (when they can still be fixed) is much better than discovering them at claim time.

The minute entry: "Training delivery status: [list programmes, dates, attendees, completion]. Issues raised: [if any]. Approved modifications: [if any]."

Standing item 4 — Vendor and consultant performance (10 min)

For projects with appointed consultants and grant-funded vendors, periodic performance review is part of governance. Topics:

• Are deliverables landing on schedule?
• Are invoices structured correctly for claim purposes?
• Any scope variations being proposed?
• Any concerns raised by the impacted staff about the new tools or workflows?

The minute entry: "Vendor / consultant performance: [summary]. Deliverables status: [on-track/delayed]. Scope variations proposed: [if any, with approval / rejection]."

Standing item 5 — Claim status and upcoming submissions (10 min)

The status of submitted claims, the readiness of upcoming claims, and any documentation gaps that need to be closed.

The questions:

• What claims have been submitted in the period?
• What's the status of each (approved, queried, paid)?
• What claims are upcoming, and is the evidence ready?
• Any documentation gaps that need to be filled before submission?

The minute entry: "Claim status: [list submitted/pending/paid]. Upcoming claims: [list with target dates]. Documentation gaps: [if any]."

---

The 1-2 project-specific items

In addition to the 5 standing items, each meeting addresses 1-2 project-specific topics. These are the items unique to your transformation:

Examples:

• A specific role redesign that's been more difficult than expected
• A vendor change being proposed mid-project
• A worker outcome variation request being prepared
• A new IDP function being added to the scope mid-project
• A staff turnover event that affects the impacted cohort

The project-specific items are where the committee actually adds judgement. The standing items maintain the audit trail; the project-specific items make decisions.

---

Cadence — how often the committee should meet

The default cadence:

• Monthly for the first 3 months of the project (the high-activity phase when most decisions are being made)
• Quarterly for the steady-state phase
• Additional ad-hoc meetings for major decisions or proposed scope variations
• A formal pre-claim meeting before any major claim submission

The wrong cadence:

• Quarterly from day one (misses early-project decisions)
• Annually (insufficient audit trail)
• Only when something goes wrong (signals reactive governance to auditors)

The right cadence is predictable and documented in writing at project kick-off. e2i and any auditor want to see consistent governance, not ad-hoc meetings clustered around problems.

---

Who attends, and in what role

The committee has two formal members by structure:

1. CTC Senior Management Representative — typically the owner, MD, or COO
2. NTUC / Worker Representative — your union if unionised; U SME (NTUC SME) if not

Additional attendees who should be regulars or invitees:

• The appointed consultant (PMC-certified, ideally) who scoped the project — they own the consultancy line and the workforce-redesign methodology
• The impacted staff manager or supervisor — they own the day-to-day delivery
• The finance lead — they own the cost line tracking and claim submissions
• The lead vendor for relevant agenda items (not every meeting)

The NTUC / Worker Representative role deserves special attention. Treat them as a co-author of the meeting outputs, not a signatory who arrives at the end. A worker rep who has shaped each meeting's decisions will defend those decisions in the e2i review. A worker rep who only signs minutes will not.

---

The minute template

A consistent minute template makes the audit trail much cleaner. Here's the structure I recommend:

COMPANY TRAINING COMMITTEE — MEETING MINUTES

Date: [date]
Meeting #: [number]
Attendees: [list with roles]
Apologies: [if any]

1. WORKER OUTCOME PROGRESS
   Current vs LOA commitment: [data]
   On-track: [yes/no, with explanation if off-track]
   Adjustments: [if any]

2. COST LINE REVIEW
   Equipment: [period spend / cumulative / LOA budget]
   Software: [same]
   Consultancy: [same]
   Training: [same]
   Variances: [explanation if any]

3. TRAINING DELIVERY
   Delivered this period: [list with attendance %]
   Upcoming: [list with dates]
   Issues: [if any]

4. VENDOR & CONSULTANT PERFORMANCE
   Status: [on-track/delayed]
   Scope variations: [list with committee decision]
   Performance issues: [if any]

5. CLAIM STATUS
   Submitted: [list with status]
   Upcoming: [list with target submission dates]
   Documentation gaps: [list]

6. PROJECT-SPECIFIC ITEMS
   [Item 1]: [discussion + decision]
   [Item 2]: [discussion + decision]

7. ACTIONS & OWNERS
   [Action]: [owner] [due date]
   ...

Signatures:
- CTC Senior Management Representative: ___________
- NTUC / Worker Representative: ___________
- Date signed: ___________

Keep the format consistent across meetings. Auditors love consistency. Inconsistent minutes raise more questions than they answer.

---

What the meeting is NOT for

Three things that shouldn't be in the committee meeting:

Not for vendor selection

Vendor selection happens in the project scoping phase, not in committee meetings. Once selected, the vendor performance is a review item, but the committee is not the procurement body.

Not for individual performance management

Individual disciplinary or performance issues are HR territory, not CTC committee territory. The committee reviews role-level worker outcomes, not individual cases.

Not for unrelated business decisions

The committee scope is the CTC-funded transformation. Other operational decisions belong in other governance forums.

Keeping the committee focused on its actual scope is what makes the audit trail clean.

---

What happens when the committee identifies a problem

The committee meeting is where problems get surfaced and addressed. The typical patterns:

Pattern 1 — Wage progression is off-track

Options: revise the training intensity, adjust the role redesign, propose an LOA variation to e2i. Whichever path is chosen, it gets minuted and the rationale is documented.

Pattern 2 — Cost line is over-spending

Options: rebalance within the envelope, request an LOA variation if the over-spend is structural, document the variance for the next claim cycle.

Pattern 3 — Training attendance is below plan

Options: change the training format, change the delivery cadence, flag staffing pressure issues. The discussion gets minuted; remedial actions are tracked through to next meeting.

Pattern 4 — Scope variation being proposed

Options: approve, reject, or request the proposer to bring more information. The committee decision is the formal record of the variation — and it should flow into a written variation request to e2i where required.

---

The most expensive committee meeting mistakes

Mistake 1 — Meeting once, never meeting again

The single most common mistake. Forming the committee is treated as the requirement; meeting substantively is treated as optional. Audit trail problem at claim time.

Mistake 2 — Minutes that don't capture decisions

Generic minutes that read like "we discussed progress and everything is on-track" are worse than no minutes — they signal box-ticking. Auditors prefer specific minutes that show real decisions being made.

Mistake 3 — Treating the worker rep as a signatory

The NTUC / Worker Rep should be involved in shaping each meeting's discussion and decisions, not just signing the final minutes. A worker rep who hasn't been part of the conversation cannot defend the project under audit.

Mistake 4 — No project-specific items

Standing items maintain the trail; project-specific items make decisions. A committee meeting that only covers standing items is administering paperwork, not governing the project.

Mistake 5 — Letting consultant absence become a pattern

The PMC-certified consultant who scoped the project should attend most meetings, especially during high-activity phases. Their absence shifts methodology decisions to people without that expertise.

---

A note on rhythm

The committee meeting works best when it's a working session, not a presentation. The minutes are an output, not a script. The decisions get made in conversation, with the NTUC / Worker Rep, the management rep, and the consultant all contributing in real time.

That rhythm is what makes the committee actually function. It also makes the meetings shorter — typically 60-75 minutes when they're working well — because there's nothing to perform, only things to decide.

---

What to do next

1. Schedule the committee meetings now — for the next 12 months, in advance. Don't let them slip into "we'll meet when something happens."
2. Adopt the standing-item template — same structure every meeting, minutes following the same format.
3. Bring the NTUC / Worker Rep into shaping the agenda, not just signing the minutes.
4. Treat the minutes as audit-trail documents — file them in the post-LOA documentation system from day one.

If you've formed a CTC and want a walk-through of how to set the meeting rhythm and template for your specific project, message me. Operator-to-operator, no sales pitch.

---

Related reading

• How to form a Company Training Committee in Singapore — the full CTC formation guide
• How to frame your CTC worker outcome — the wage-increment basis the committee tracks
• The 30-day post-Letter-of-Offer checklist — the broader post-LOA framework
• Reading a Letter of Award — the 5 lines to negotiate — what the committee operationalises
• CCP vs CTC — when reskilling fits one or the other — workforce-side comparison
• /grants/ctc — canonical CTC landing page

— Nick

Frequently Asked Questions

What is ctc committee meeting singapore?

Ctc committee meeting singapore refers to the approach described in this article. Singapore SMEs apply this practically to reduce cost and increase leverage without adding headcount.

Who should consider ctc committee meeting singapore?

Any Singapore SME owner, manager, or operator looking to streamline their business — especially those running PSG, EDG, or NTUC CTC grant-funded projects.

How long does it take to implement?

Most SMEs see meaningful results within 4-8 weeks of a focused implementation. The bottleneck is usually decision-making speed, not technical complexity.