Home / Blog

The HRD Corp Policy Tracker Template: A Spreadsheet-and-Owner System for Logging Every Circular Change

· By Ayda Editorial

The HRD Corp Policy Tracker Template: A Spreadsheet-and-Owner System for Logging Every Circular Change

Why the policy tracker is the least glamorous file you will ever build

A trainer I know runs a two-day technical programme for in-house groups of eight. The fee was set in mid-2025 against the rates current at that time. When the January 2026 Approved Cost Matrix booklet landed, the group rate on that course no longer matched the ceiling HRD Corp would honour — and nothing in his filing cabinet flagged it. The claim went in on the old assumption. According to public commentary on the 2026 ACM revision, claims submitted with 2025 or earlier rates are adjusted downward without notification. No rejection letter lands in your inbox. The money simply does not arrive.

That is the failure mode a policy tracker prevents. Not ignorance of a circular. Ignorance of which of your files was built on which version of the rules.

For a certified HRDC trainer, this matters twice over: you may deliver under your own provider entity, and you may deliver under someone else's. In both cases the claim pack will be assembled from documents you touched. If you cannot answer "which guideline was this outline priced against?" in under a minute, you are one revision away from an absorbed shortfall.

Below is the template I would build, the columns it needs, who owns each one, and a version-control method that keeps every programme file tied to a dated rule set. The 2026 revision cycle — covered in more detail in HRD Corp policy changes in 2026 and what they mean for training providers — is a good stress test to build against.

The design principle: one row per rule, not one row per file

Two colleagues comparing a course outline's rule version against a file on screen in a Kuala Lumpur training office Every file carries the rule set it was built on — visible in the header, not buried in a notes column.

The instinct is to build a tracker around programmes. Programme 1, Programme 2, Programme 3, each with a "notes" column. That structure fails because a single revision — say a change to e-learning rate ceilings — will touch several programmes at once, and a programme-centric sheet forces you to hunt through rows to find everything affected.

Build it the other way round. One row per rule or rate item. Then a second sheet mapping rules to programme files. That two-sheet structure is the whole discipline, and it is the part most trainers skip.

Sheet 1: the circular log

Each row is a discrete, citable item from an official HRD Corp source. Suggested columns, in order:

  • Ref ID — your own identifier, e.g. ACM26-07. Never invent an official circular number; the Ref ID is internal.
  • Source document and issue date — the exact publication, e.g. "January 2026 ACM Booklet". Record what the document says it is, not what you assume.
  • Category — course fee ceiling, other claimable cost, eligibility, scheme process, levy, e-learning, certification programme.
  • Rule in plain English — one sentence, no jargon. Example: "Technical external trainer in-house fee capped at RM6,000/day/group." Another real constraint worth logging separately: in-house groups of 2 to 35–40 pax, and the specific rule that claims for in-house groups under 5 pax use (Max Fee ÷ 5) × actual pax rather than the full group rate.
  • Previous position — what the rule was before. This column is what makes the log a change register rather than a snapshot.
  • Effective date — when the new position applies.
  • Affected documents — a controlled list: course outline, quotation template, claim pack, invoice wording, brochure, proposal boilerplate.
  • Owner — a named human, not a department.
  • Status — logged / documents reviewed / documents updated / verified.
  • Verified on official portal (date) — the date you last confirmed the item yourself on HRD Corp's own channels, and by whom.

That last column is non-negotiable. Third-party summaries, including this article, are starting points. Any rate, ceiling, form name or process step gets confirmed on the official portal before it drives a quotation.

Sheet 2: the file-to-rule map

Each row is a programme file, with columns for programme name, file version, and the Ref ID(s) from Sheet 1 it was built against. Add a "last checked against current rules" date and a validator name. This is the sheet that answers the question in ten seconds.

The version-control method: three rules, no software required

A tracker without a versioning convention is just a diary. Three rules do the work.

Rule one: files carry their rule version. Put the Ref ID set at the top of every course outline and quotation template — visible, in the document header. Built on: ACM26-07, ACM26-11. When a trainer opens a file to reuse it for a new client, the first thing they see is which rule set it assumed.

Rule two: superseded files are retired, not edited. When a rule changes, copy the file to a new version, update the header, and mark the old one "superseded — do not reuse" in the filename. Editing in place destroys the audit trail you may need if a claim query arrives. If you want a structured way to handle the query side of that, the eTRiS query response playbook for HRD Corp grant queries covers triage and logging.

Rule three: a monthly 30-minute review. One person on the calendar, once a month, opens the official HRD Corp channels, checks for new or revised material against Sheet 1, and logs anything new. If nothing changed, log the check anyway. An empty row with a date is evidence of diligence.

Before and after: what this looks like in a real provider

Before. A four-person provider keeps course outlines and quotations in a shared drive. When the ACM booklet is revised, the founder reads about it, means to update the templates, and gets busy. A quotation goes out for a two-day soft-skills in-house programme to nine participants, priced at the older group rate. The claim is submitted on the older basis. The adjustment happens quietly, weeks later, and the shortfall lands on the provider, not the client. Nobody can say which files were ever reviewed.

After. The same revision is logged as a single row on Sheet 1 with an effective date and an owner. Sheet 2 runs a filter: which programme files cite the superseded Ref ID? Six files. The owner updates the two quotation templates and four outlines over the following week, bumps each to a new version with the new Ref ID in the header, and marks the old versions superseded. The next quotation that goes out carries the current rule set in its header. If a client asks why the price moved, there is a dated, sourced answer.

The difference is not more compliance effort. It is the same effort, pointed at the right object — the rule, not the file.

Who owns which column

A tracker with no owners is a suggestion box. In a small provider, assign by column group rather than by person-count:

  • Rules and source verification — founder or programme director. This is the person who reads the official documents and confirms rates on the portal. Not delegated.
  • Affected-document mapping — operations or admin lead. They know which files exist, which is exactly the knowledge a founder often lacks.
  • File updates and version headers — whoever builds quotations and outlines. For freelance trainers delivering under a provider, this is a handover item; the HRDC trainer to provider handover checklist is a sensible place to record which template version a trainer is expected to use.
  • Monthly review check — one named person, with the check logged even when nothing changed.

If you freelance across several providers, keep your own Sheet 2. You do not control their templates, but you can control whether your outlines and day-rate quotes cite a current rule set — and you can ask the provider which version they are working from. That single question has saved trainers from being the last to know.

Three traps this template exposes

Trap one: claiming both meal and trainee allowances for the same session. Public guidance on the 2026 revision lists this as a common error — only one type is permitted per event. Once it is a row on Sheet 1 with "claim pack" as an affected document, the person assembling the pack sees it.

Trap two: using old rates in new grant applications. The shortfall is not flagged. The rule row plus the file map makes the linkage explicit.

Trap three: assuming the revision only affects fees. Eligibility rules, minimum durations and scheme process steps change too. A log that only tracks MYR ceilings will miss a duration rule or a submission-timing rule — for example, that applications under SBL-KHAS must be submitted by the employer before the training commencement date. Those belong on Sheet 1 under "scheme process" even though they are not money.

Where the tracker ends and your documents begin

A tracker tells you what changed and what it touches. It does not rewrite the documents. The labour is in regenerating quotations, outlines and claim packs against the new rule set — which is precisely the repetitive, error-prone work where a template-driven system earns its place. Ayda generates HRDC-ready quotations, invoices and certificates from templates, so when a rule row is marked "documents updated", the regenerated files carry the new basis rather than a hand-edited guess. If you want to see how that fits alongside your existing files, the Ayda pricing page sets out the options.

One more link in the chain: several of the documents you will be versioning — courseware, outlines, and the rights around them — sit inside contracts with clients and trainers. The courseware ownership clause guide for Malaysian training providers is worth reading before you start bumping versions of material you may not wholly own.

Getting started this week

Build Sheet 1 with ten rows from the current HRD Corp material available to you, confirm each on the official portal, and date it. Build Sheet 2 with every active programme file you can find. Set the monthly review. That is a working tracker — not a perfect one, but the one that means the next revision does not cost you a claim.

If your team would rather have the administrative load handled than hand-built, sign up as a training provider and start with the documents.

Frequently Asked Questions

What is an HRD Corp policy tracker template?

It is a spreadsheet with two sheets: a circular log where each row records one rule or rate item from an official HRD Corp publication, and a file map that records which programme files were built against which rule version. Its purpose is to stop you submitting a claim or quotation built on a superseded guideline.

Do I need a paid tool to run this?

No. A spreadsheet and a filename convention are enough. The discipline that matters is putting the rule version in the document header, retiring superseded files rather than editing them, and running a dated monthly review.

Who should own the tracker in a small training provider?

In a team of under ten, the founder or programme director should own the rule rows and the verification on the official portal, while operations owns the file mapping and updates. Never split verification across several people with no single named owner.

How do I know the rates on my tracker are current?

Only by checking the official HRD Corp channels yourself. Record the date and the person who verified each row. Treat third-party summaries as leads, not sources, for anything that drives a quotation or a claim.

I freelance for several providers. Should I keep my own tracker?

Yes, at least the file map for your own outlines and day-rate quotations, plus a habit of asking each provider which version they are working from. You cannot control their templates, but you can make sure the documents you hand over cite a current rule set.

Does the tracker cover non-financial rule changes?

It should. Log scheme process steps and eligibility and duration rules under their own categories. For SBL-KHAS, for example, applications must be submitted by the employer before the training commencement date — a timing rule that a fee-only log would miss entirely.

← All articles