Home / Blog

The Trainer-to-Provider Handover: What Every HRDC Trainer Needs Before Running Under a Provider

· By Ayda Editorial

The Trainer-to-Provider Handover: What Every HRDC Trainer Needs Before Running Under a Provider

Start with the document list, not the contract

A freelance trainer and a registered provider agree a day rate over WhatsApp, the first session runs well, and three months later the claim file is short two participant feedback forms and one acknowledgement letter. The training happened. The evidence did not.

Most handover problems between an HRDC trainer and a training provider are not relationship problems. They are custody problems. Someone assumed the other side was holding the attendance form, the signed acknowledgement, or the proof of payment to the trainer. Under the revamped HRD Corp guidelines, trainers submitting training hours for accreditation by activity through TDMS must attach a minimum of two supporting documents from a defined list — attendance forms for all declared dates, participant feedback forms, an acknowledgement letter from the provider or employer to the trainer on company letterhead, or proof of payment from provider or employer to trainer. Two documents minimum, from a list of specific ones. If both sides quietly assume the other is collecting them, the file arrives incomplete.

So before you negotiate anything else, settle which operating model you are running. There are three, and they behave very differently.

Three handover models, side by side

Admin executive reviewing a responsibility matrix with a trainer to agree document ownership timelines Attach the RACI to the quotation: named owners, named timelines, fewer arguments later.

The question is not "should the provider handle admin?" It is "which layer of admin does each side own, and who is accountable when it fails?" The three models below cover almost every arrangement in practice.

Model A — Provider-run (full admin custody)

The provider owns the entire paperwork chain: joiner list, attendance capture, feedback forms, certificate issuance, and the claim submission. The trainer delivers and signs off the session record. This is the cleanest model for claims because one party holds every document, but it depends on the provider having real admin capacity and a working document system.

Model B — Trainer-admin hybrid

The trainer collects participant attendance and feedback on the day — often because they are physically in the room and the provider's admin team is not — then hands the pack to the provider within an agreed window. The provider still submits the claim and issues certificates.

This model fails predictably when the handover window is vague. "Send it when you can" becomes "sent after the claim deadline".

Model C — Split by document type

One side owns participant-facing evidence (attendance, feedback, evaluation), and the other owns financial and contractual evidence (invoices, proof of payment to the trainer, acknowledgement letters, certificate records). This works when the provider already has a finance workflow but a trainer-led evaluation design — common when the trainer has built a lightweight Kirkpatrick evaluation into the programme.

Model C carries the highest documentation risk because two parties are producing pieces of one file. It needs one accountable owner — the provider — even though the trainer supplies inputs.

Decision table: criteria by handover model

Criteria Model A — Provider-run Model B — Trainer-admin hybrid Model C — Split by document type
Claim file custody One party, end to end Provider, with trainer inputs Two parties producing one file
Time cost to provider Highest admin load, lowest chase time Medium; depends on handover discipline Medium admin, highest reconciliation time
Time cost to trainer Lowest Highest on delivery day Medium
Documentation failure risk Low if the system works Medium High without a checklist
Trainer payment proof Provider holds Trainer must keep own records Provider holds, trainer copies
Scale ceiling High Low to medium Medium
Best fit Multi-programme providers with admin staff Small providers, single-trainer engagements Providers with finance in place but trainer-designed evaluation

The MYR side of the table

Admin cost is not abstract. If a provider pays an admin executive in the RM2,500–RM3,500 monthly band in Malaysia — a common range for junior-to-mid operations roles in the Klang Valley — the per-programme admin burden of a manual Model A handover usually runs into several staff-hours per programme once joiner lists, attendance transcription, feedback collation, certificate preparation and claim paperwork are counted. A line-by-line training provider admin cost breakdown puts real figures on each task and role; use it to price your own model rather than guessing.

On the trainer side, the same hours come straight out of a freelance HRDC trainer's earning capacity. A trainer billing a day rate loses that day's margin to admin if the provider pushes paperwork back. Model B is attractive for the trainer's cash flow but expensive in time.

RACI: who owns each item and when

This is the part that stops arguments later. Copy it into the engagement letter and attach it to the quotation.

Item Owner (A) Responsible (R) Consulted (C) Timeline
Trainer accreditation status and TTT/TTT exemption evidence Provider Provider Trainer Before contract signing
Signed trainer agreement, including non-solicitation terms Provider Provider admin Trainer Before first delivery
Course outline and session plan Trainer Trainer Provider 10 working days before delivery
Participant joiner list and employer confirmation Provider Provider admin Employer 5 working days before delivery
Attendance capture, all declared training dates Provider (A) Trainer collects on day — Day of delivery
Participant feedback forms Provider (A) Trainer distributes and collects — Within 2 working days of final day
Certificate details and issuance Provider Provider admin Trainer Within 5 working days of final day
Proof of payment to trainer Provider Provider finance Trainer keeps copy Per contract terms
Acknowledgement letter on company letterhead Provider Provider admin Trainer Before claim submission
Claim submission and query responses Provider Provider claims owner Trainer Per portal deadlines

Two lines in that table do the heaviest lifting: attendance capture and proof of payment. Those are recurring weak points because the first depends on someone being in the room and the second depends on finance timing rather than training timing. If your sessions include remote participants, attendance evidence gets harder still — the hybrid training setup in Malaysia has to produce records that survive scrutiny, not just a screenshot.

Course duration and trainer accreditation: the pre-handover gate

Before any of the above matters, the programme itself has to be registerable. Under the SBL-Khas scheme, a course must meet all of the following: a minimum total training duration of at least four hours per day excluding lunch, at least one trainer holding a TTT or TTT exemption certificate, and documentary evidence supporting the registration. Note also that under SBL-Khas, HRD Corp pays the course fee directly to the training provider, subject to a 4% service fee effective 1 April 2021, by deducting from the employer's levy account — and the entire amount claimable remains subject to approval of each individual grant application. Nothing about that is automatic, and no provider can promise otherwise. Confirm current requirements on the official HRD Corp portal before registering.

If you are still at the stage of establishing the entity that will hold these documents, the HRD Corp training provider registration guide covers the sequence.

Who should pick what

Pick Model A if you run more than a handful of programmes a month, you have at least one dedicated admin person, and your trainers are geographically spread. You are buying single-point custody, and it is worth the admin headcount.

Pick Model B if you are a small provider with one or two trainers, the programme is a single-day in-person session, and you can name a hard handover window. Write the window into the agreement as a specific number of working days, not a phrase.

Pick Model C if your trainer designs the evaluation and your provider already runs invoicing and payments cleanly. Do not pick it to save effort — it saves provider admin at the cost of reconciliation.

In all three, one rule holds: the provider is accountable for the claim file even when the trainer supplies the evidence. Accountability cannot be delegated to a freelancer who has no portal access.

Three failure patterns to design against

The missing acknowledgement letter. The trainer assumed the provider would draft it. The provider assumed the trainer would. It is a provider document, on provider letterhead — make it a named owner in the RACI.

The unaccredited substitution. A trainer drops out and a replacement without TTT certification covers the session. This breaks the course registration basis and puts the claim at risk. Run a freelance trainer substitution drill before it happens rather than after.

The re-typed evaluation. Attendance and feedback get re-typed from photos, dates get transposed, and consistency between the joiner list, attendance record and certificate list breaks. Where possible, keep one source of truth per participant.

When a query does arrive, the response is a separate discipline — the eTRiS query response playbook sets out how to match each query type to the evidence it needs.

Where the admin layer gets lighter

None of this is hard, but it is repetitive, and repetition at volume is where handover models break. Providers running 30 to 40 programmes a year eventually stop hand-building attendance sheets and certificate details and move to document generation from a single programme record — which is the problem Ayda is built for. It generates HRDC-ready quotations, invoices and certificates from templates, so the joiner list, attendance record and certificate list stay consistent with each other instead of being rebuilt three times. Read about it on Ayda pricing if you are evaluating the admin layer for your own operating model.

One honest caveat: software fixes formatting and consistency, not process ownership. If your RACI table is unclear, a document generator will produce clean documents for an unclear process.

What to put in the engagement letter this week

Five lines, at minimum:

  • The chosen handover model, named, with the RACI table attached.
  • The handover window in working days for attendance and feedback.
  • Which party holds the original attendance forms, and for how long.
  • Who drafts the acknowledgement letter and who signs it.
  • How proof of payment to the trainer will be evidenced, and by when.

Add the trainer's accreditation evidence and current contract terms, and you have the base pack. Providers who want the full joiner-to-first-delivery sequence can follow the onboarding freelance trainer provider framework, and pair it with the non-solicitation clause for trainer agreements if you want client-protection terms settled at the same time.

Get the document custody right once, and every subsequent engagement with that trainer becomes a short email rather than a reconstruction project.

Frequently Asked Questions

What documents must a trainer supply when running under a provider for an HRD Corp programme?

Under the revamped HRD Corp guidelines, trainers submitting training hours for accreditation by activity through TDMS must attach a minimum of two supporting documents from a defined list: attendance forms for all training dates declared, participant feedback forms, an acknowledgement letter from the training provider or employer to the trainer on company letterhead, or proof of payment from the provider or employer to the trainer. Confirm the current list on the official HRD Corp portal.

Who is responsible for the claim file when a freelance trainer delivers the programme?

The training provider. The provider holds the employer relationship and portal access, so it is accountable for the complete claim file even where the trainer collects attendance or feedback on the day. The trainer's role is to supply inputs by an agreed deadline and keep copies of their own payment evidence.

Does a course under SBL-Khas need a minimum duration or a certified trainer?

Yes. To register a course under SBL-Khas, the recorded requirements include a minimum total training duration of at least four hours per day excluding lunch, at least one trainer holding a TTT or TTT exemption certificate, and documentary evidence supporting the registration. Verify the current requirements on the official HRD Corp portal before registering.

How does HRD Corp pay under SBL-Khas?

Under SBL-Khas, HRD Corp pays the course fee directly to the training provider, subject to a 4% service fee effective 1 April 2021, by deducting the amount from the employer's levy account while paying other claimable allowances to the employer. The entire amount claimable remains subject to approval of each individual grant application.

Which handover model suits a small Malaysian training provider?

The trainer-admin hybrid, where the trainer collects attendance and feedback on delivery day and hands over to the provider within a fixed number of working days. It keeps provider admin load low but only works if the handover window is a specific number written into the engagement letter.

← All articles