Corporate Training RFP in Indonesia: Template, Evaluation Criteria & How to Write It (Complete Guide for HR, L&D, Procurement)

Short answer: A healthy corporate-training RFP is a 14-section document built from a Training Needs Analysis (TNA) summary, defines measurable learning objectives, mandates a uniform response format (module-to-objective map, named facilitator profiles, Kirkpatrick evaluation plan, itemized budget), and states weighted evaluation criteria upfront. For BUMN/government procurement the RFP takes the form of a Kerangka Acuan Kerja (KAK) and is subject to Presidential Reg. 16/2018 jo. 12/2021 and LKPP Reg. No. 12/2021 (amended by No. 4/2024), with the dominant path being Electronic Catalog Version 6 (Head of LKPP Circular No. 9/2024, mandatory since 1 January 2025).

Most "training RFP template" articles give a table of contents without the logic behind it — section headings that look complete on paper but produce proposals that come back in wildly different shapes and quality. This guide closes that gap: the document-family map (RFI/RFQ/RFP/KAK), 14 mandatory sections with the reason for each, 9 weighted evaluation criteria, a response format that forces apples-to-apples, Q&A mechanics, a healthy timeline, the differences between private, BUMN, and LKPP paths, and audit-grade documentation.

Intended readers: HR / HC / L&D / SDM, Procurement, and Finance teams that author or approve training RFPs/KAKs — in private companies, BUMN/BUMD, government agencies, institutions, associations, and non-profits.

Quick navigation

1. Document-family map: RFI vs RFQ vs RFP vs KAK
2. Four decisions before writing the RFP
3. Fourteen mandatory sections of a training RFP
4. Response format that enables apples-to-apples
5. Nine evaluation criteria & typical weights
6. Separating technical and commercial evaluation
7. Technical questions to include
8. Healthy timeline & Q&A mechanics
9. Budget: open or closed?
10. Private vs BUMN vs LKPP RFPs
11. Sample sessions & finalist presentations
12. Ten red flags in an RFP response
13. Audit-grade documentation
14. RFP-release checklist
15. Common mistakes & how to avoid them
16. FAQ
17. Next step

Document-family map: RFI vs RFQ vs RFP vs KAK

Four documents are routinely confused yet answer different questions. Pick the right one or you answer the wrong question and waste a cycle.

Document	Question it answers	When to use	Vendor output
RFI (Request for Information)	"Who is capable, with what?"	Need still vague; mapping the market	Capability profile, general approach, references
RFQ (Request for Quotation)	"What price for this fixed scope?"	Spec is complete and uniform	Price + terms
RFP (Request for Proposal)	"How will you close this need?"	Scope defined, approach still being explored	Narrative proposal that can be scored
KAK / TOR (Kerangka Acuan Kerja)	Equivalent to RFP + audit basis for state/BUMN procurement	Government/BUMN procurement	Technical & price offer per guidelines

For TNA-based corporate training, the RFP/KAK is the main document: the need is already clear (TNA output), but approach, methodology, and execution are exactly what gets scored. RFI helps as a first step when the market is unmapped. RFQ rarely fits training because nothing is ever truly "standard spec" — customization is the core of the value.

Rule of thumb: RFI screens the market. RFP/KAK selects approach and team. RFQ orders something already identical.

Four decisions before writing the RFP

A strong RFP is written after four decisions are locked. Without them, the document is a table of contents without logic.

1. Business objective & TNA complete. Which competency gap must close, for which role/participants, for what outcome (e.g. lower first-line-manager turnover, raise sales conversion, accelerate digital-tool adoption). See the TNA guide for methods and templates.
2. Format & operational constraints. In-house/public/blended, online/onsite, participants per batch, location, execution window. See in-house vs public for the decision frame.
3. Indicative budget & disclosure mode. Internal budget ceiling exists; decide whether to disclose it in the RFP (see "Budget" below).
4. Evaluation criteria & evaluators. Who are the 3–5 evaluators (HR/L&D, owning-unit leader, Procurement, Finance, Legal/IT if sensitive data), the criteria and weights, and the technical pass threshold.

These four decide the voice of the RFP. If you are uncertain on any of them, hold the release — a weak RFP attracts weak proposals, and the cycle is wasted.

Fourteen mandatory sections of a training RFP

#	Section	Purpose	What goes wrong if dropped
1	Background & business objective	Context and why this matters	Vendor sells a generic package
2	TNA summary & competency gap	Evidence of a training problem	Approach is untargeted
3	Participant profile & count	Starting level, role, language, batches	Content level misses
4	Scope, outcomes & measurable learning objectives	Outcome contract	Hard to score / measure
5	Format, venue & duration	Realistic operational shape	Budget drifts
6	Technical questions (capability)	Evidence on approach, facilitator, evaluation, customization	Unverified claims
7	Proposal format & mandatory attachments	Apples-to-apples	Apples-oranges-mangoes
8	Evaluation criteria & weights	Decision transparency	Decision is unauditable
9	Process schedule	Cycle discipline	Healthy vendors decline; weak ones stay
10	Legal & tax requirements	NPWP/PKP, LPK where relevant, PPh 23 readiness	Billing rejected at finance
11	Participant data protection (PDP Law)	Controller-Processor, NDA, retention	Risk on you as Data Controller
12	Commercial terms	Payment, warranties, scope-change, force majeure	Execution disputes
13	Q&A & clarification procedure	Information symmetry	Unfairness claims
14	Point of contact & submission method	Operational	Lost or late proposals

Each section is mandatory because it closes one path a healthy vendor can drift down — or a weak vendor can hide behind. An RFP that drops any one moves cost to the execution phase (scope disputes, tax surprises, failed audit).

Note for Section 4 (Measurable learning objectives)

Distinguish learning objectives from topic titles. Weak: "negotiation training". Strong: "able to run a diagnostic conversation that surfaces three hidden customer needs, propose a BATNA, and write a one-page deal summary." The strong form can be scored in a sample session, measured in Kirkpatrick L2–L3, and used by vendors to design the right module. The weak form has every vendor sending the same materials with no objective way to choose.

Note for Section 10 (Tax)

Must be stated: PKP status, ability to issue tax invoices (code 01 for private, 02 for government agency, 03 for designated BUMN collector), NPWP, and willingness to be withheld at PPh 23 (2% if NPWP-registered, 4% if not — SE-35/PJ/2010). See the PO/VAT/tax-invoice guide for the full mechanism.

Response format that enables apples-to-apples

Without a uniform structure, the panel compares a 60-page narrative against a 12-page table and the decision falls to document aesthetics. Mandate this response format:

• Executive summary (1 page) — needs understanding, core approach, lead facilitator, commercial value, three key commitments.
• Capability table — columns: RFP question, answer (Yes/No/Partial), evidence (reference proposal page X).
• Module-to-learning-objective map — table: module, measurable learning objective, method (simulation/case/practice), duration, assessment.
• Facilitator profile per named person — fixed template: name, photo, relevant hours, certifications, prior clients reachable as references, sample session (video/notes), anti-substitution clause.
• Kirkpatrick evaluation plan per level — instrument per level (form, assessment, observation, KPI), who collects, when, final report format. See the Kirkpatrick 4-level deep guide.
• Structured budget — standard rows: facilitator fee, content development & customization, assessment & instruments, logistics (venue/F&B/accommodation), program management, tax row (VAT incl./excl., PPh 23 position). See the budget guide.
• Legal attachments — deed of establishment, NPWP/PKP, LPK license where relevant, ISO 29993 if any, willingness to sign NDA + data-processing agreement.

Rule of thumb: Specifying the response format is 30% of the RFP work. It turns comparison from subjective to evidenced.

Nine evaluation criteria & typical weights

The weights below are a starting point for a typical behavior/leadership program. Tune them: certification programs raise legality weight; BUMN/government procurement raises tax/procurement weight; sensitive-data programs raise data-security weight.

Criterion	Weight	What is scored
Fit with TNA & business goal	20%	Diagnostic vs brochure-copy; module→objective map
Facilitator quality & transparency	15%	Per-named CVs, sample session, anti-substitution clause
Methodology & measurement plan	15%	Instructional design (ADDIE/SAM), Kirkpatrick L1–L4
Customization capability	12%	Sample module adapted to your context
Verifiable track record	10%	Contactable references from similar clients
Legality & quality standards	8%	LPK, BNSP/LSP, ISO 29993 as needed
Tax & procurement compliance	8%	NPWP/PKP, sample tax invoice, SPSE/INAPROC readiness
Data security & protection	7%	PDP Law: NDA, processing agreement, 3×24-hour incident reporting
Pre/post support & value for money	5%	30–90-day reinforcement plan; transparent budget
Total	100%

Scoring 1–5: 5 = strong and specific evidence; 3 = adequate but generic; 1 = unverified claims. Set a technical pass threshold (e.g. weighted score ≥ 3.5) before opening price.

For the mathematical deep dive (AHP/TOPSIS, fuzzy scoring, worked numerical example), see the vendor scoring rubric guide.

Separating technical and commercial evaluation

Sound international practice (and the default in Indonesian government procurement under Quality-and-Cost-Based Selection, QCBS): open the technical envelope first, score to a pass threshold, then open the price envelope. Reason: if price is opened together, the panel (consciously or not) lets price hijack the technical evaluation — the cheapest vendor seems "good enough".

Common patterns:

• Quality-Based Selection (QBS) — pick best technical without price consideration (fits very specialized consulting).
• Quality- and Cost-Based Selection (QCBS) — technical weight 60–80%, price 20–40%; default for corporate training & government procurement.
• Least-Cost Selection (LCS) — among all who pass the technical threshold, pick the cheapest (fits commodity training).
• Fixed-Budget Selection (FBS) — budget is locked; pick highest technical quality within the ceiling (fits when the ceiling is hard-coded by RKAP/DIPA).

For TNA-based corporate training, QCBS with technical 70% and price 30% is the healthy default: it values approach without ignoring price reasonableness.

Technical questions to include

Ask specifically. Generic questions ("describe your approach") produce template answers. Good questions compel evidence.

Understanding & diagnosis

• What is your hypothesis about the root competency gap among our participants, based on the attached TNA?
• If you would run an additional TNA, what method, what duration, and how does it shape the proposal?

Methodology & design

• Which instructional-design framework do you use (ADDIE/SAM/Backward Design) and why is it right here?
• How do you balance 70-20-10 (experience/social/formal) in this program?
• Show one module already adapted to our industry/role as a sample.

Facilitator

• Attach CVs for the 3 named facilitators who will teach — relevant experience, certifications, sample session (video/link/notes).
• How do you handle facilitator changes? (Anti-substitution clause in the contract.)

Evaluation & measurement

• Kirkpatrick plan per level: L1 (reaction instrument), L2 (competency assessment), L3 (30/60/90-day behavior observation + required drivers), L4 (targeted business KPIs).
• For large programs: Phillips ROI Level 5 plan — the isolation method you propose (control group / trend line / participant estimation) and how benefits are monetized. See the Phillips ROI guide.
• Final-report format and a sample prior report (anonymized).

Commercial & operational

• Structured budget with tax rows (VAT incl./excl., PPh 23 position).
• Payment terms, quality warranty (e.g. free re-run if reaction score below threshold), scope-change clause.
• Procurement-document readiness (NPWP, PKP, SPSE/INAPROC profile where relevant, domicile certificate).

Legal & data

• Willingness to sign an NDA and a participant-data processing agreement per PDP Law No. 27/2022.
• Data-security standards (storage, access, retention, 3×24-hour incident-handling procedure).

Healthy timeline & Q&A mechanics

Stage	Healthy duration	Note
Prep & RFP release	3–5 days	Internal four-decision check complete
Q&A window	3–5 working days	Written questions, simultaneous answers to all
Proposal drafting	10–14 working days	Enough for substantive diagnosis beyond a template copy
Technical evaluation	5 working days	3–5 evaluators, individual scoring then calibration
Finalist presentation / sample session	1 week	2–3 finalists × 60–120 minutes
Price-envelope opening	1 day	Only after technical threshold passed
Negotiation & contract	5–10 working days	Lock facilitator, price, clauses
Total	3–6 weeks	Government/BUMN can be 8–12 weeks

Fair Q&A mechanics:

1. Close the question window; collect all in writing.
2. Anonymize and consolidate answers.
3. Send the Q&A file to every participant simultaneously.
4. If anything material changes (scope/schedule/criteria), issue a versioned addendum and extend the deadline.
5. Avoid private communication outside the formal channel. Log every interaction.

Rule of thumb: A too-short schedule filters out healthy vendors (they decline), leaving template copy-pasters. A too-long schedule wastes momentum. Three to six weeks is the sweet spot.

Budget: open or closed?

Approach	Upside	Risk
Open (range disclosed)	Proposals more realistic within ceiling, honest "value per dollar" comparison, shorter negotiation	Vendors may cluster near upper bound
Closed (hidden)	Market reveals true pricing	Bids may land far outside ceiling, long negotiation

Recommendation:

• TNA-based corporate training → open. A range is a constraint. An honest range produces executable proposals and filters out vendors who would oversell.
• Government/BUMN procurement → open (mandatory). The budget ceiling is typically required in the KAK because it ties to DIPA/RKAP. SBM (PMK 32/2025 for FY 2026) caps per-component honorarium/per-diem.
• Open tenders with many bidders → can be closed. When the goal is true price discovery and the bidder count is high enough to neutralize clustering.

Private vs BUMN vs LKPP RFPs

Aspect	Private	BUMN	Government (LKPP)
Legal basis	Private contract	Minister-of-SOE regulation on procurement guidelines	Presidential Reg. 16/2018 jo. 12/2021; LKPP Reg. No. 12/2021 (jo. No. 4/2024)
Document form	Flexible RFP	RFP/KAK per BUMN guideline	Formal KAK
System	Email/internal vendor portal	Relevant BUMN procurement system	SPSE/INAPROC; Electronic Catalog V6 (Head of LKPP Circular No. 9/2024)
Budget source	Company budget	RKAP (ratified by RUPS)	DIPA (RKA-K/L), SBM (PMK 32/2025 for FY 2026)
Common selection method	Internal negotiation & QCBS	Direct procurement / appointment / tender per ceiling	E-purchasing Catalog V6, Direct Procurement (≤IDR 200m), Tender
VAT collector	Vendor (tax-invoice code 01)	Some BUMN as designated collector (code 03)	Agency treasurer (code 02; PMK 59/PMK.03/2022; IDR 2m threshold)
Contract	PO/PKS	SPK/PKS per guideline	SPK/Contract per Presidential Reg.
Typical cycle	3–6 weeks	4–8 weeks	6–12 weeks

For government procurement, the dominant path is now the Electronic Catalog Version 6: a Procurement Officer handles e-purchasing up to IDR 200 million, the PPK handles above IDR 200 million with negotiation/mini-competition. Training vendors must display products/services on the catalog etalase and be verified in INAPROC (the centralized SPSE account).

Per-buyer billing, invoice, and tax mechanics are covered exhaustively in the PO, VAT & tax-invoice guide.

Sample sessions & finalist presentations

For scale programs, the sample session is the strongest filter. Fair rules of play:

• Give 2–3 finalists an identical case: industry context, problem, simple participant profile.
• The sample-session facilitator = the facilitator who will teach. Not a presales lead.
• Duration 30–60 minutes (small program) or 60–120 minutes (academy / large program).
• Real audience: invite 5–8 real future participants alongside the panel. They signal whether the approach resonates.
• Session scoring rubric: ability to open the topic, manage discussion, adapt to the audience, depth of substance, use of case, quality of reflective questions, time execution.
• Post-sample Q&A: panel probes methodology, evaluation, customization, risk, mitigation.

The sample session filters out vendors who are strong on paper and weak in the room — the most frequent failure mode.

Ten red flags in an RFP response

#	Red flag	Risk
1	No TNA summary / needs diagnosis	Vendor sells a brochure
2	Anonymous facilitators or "to be determined"	Bait-and-switch
3	Schedule too fast with no design phase	Quality sacrificed
4	One-line budget or no tax detail	Billing rejected at finance
5	No NPWP / refuses PPh 23	Admin & cost up
6	Evaluation = satisfaction score only	Stops at Kirkpatrick L1
7	Client claims & figures without proof	Track record unverified
8	Refuses NDA / data-processing agreement	PDP Law risk on Controller
9	Price far below market without breakdown	Quality / surprise add-ons
10	Template response not adapted to industry/role	Vendor sells product

Audit-grade documentation

Seven artifacts to keep for every RFP cycle (a future audit will ask):

1. Final RFP document + every addendum with version code & date.
2. Vendor invitation list + initial-screening rationale (track record, capability, document completeness).
3. Every proposal received + receipt timestamp.
4. Q&A summary distributed to every participant.
5. Per-evaluator scoring sheet + consolidated weighted score + calibration notes.
6. Presentation / sample-session minutes + written clarification notes.
7. Decision minutes with selection rationale for winner & runner-up.

For BUMN/government, additional documentation follows the system (SPSE/INAPROC) and internal regulation. Retained at least 5 years per audit cycle.

RFP-release checklist

Before sending the RFP to vendors, every box ticked:

• Business objective & TNA complete; summary attached.
• Format/venue/participants/timeline explicit.
• Budget disclosure decided open/closed (open recommended).
• Evaluation criteria & weights stated; technical pass threshold set.
• All 14 mandatory sections complete.
• Uniform response format required (capability table, facilitator profile, module map, budget).
• Technical questions specific (not generic).
• Realistic timeline (3–6 weeks private; 8–12 weeks BUMN/LKPP).
• Q&A & addendum mechanics written.
• Legal & tax requirements clear (NPWP/PKP, tax-invoice code, PPh 23, NDA, PDP Law).
• Point of contact & submission method clear.
• 3–5 vendors invited (pre-screen via RFI if market unmapped).
• Evaluators (3–5) selected & briefed.
• Scoring sheet ready & internally calibrated.

Common mistakes & how to avoid them

Key takeaways:

• RFP without TNA → table of contents without logic; vendors guess. Start from TNA.
• Inviting 10+ vendors → evaluation fatigue; pre-screen to 3–5 via RFI.
• No uniform response format → apples-oranges-mangoes; mandate the template.
• Opening price before technical threshold → price hijacks; separate envelopes.
• Schedule too short → healthy vendors decline; allow 3–6 weeks.
• Anonymous facilitators allowed → bait-and-switch; require per-named CVs + anti-substitution clause.
• Tax/data left vague → invoices rejected, PDP Law risk. Lock in Sections 10–11.
• No sample session → document bias; test the room for scale programs.
• Thin documentation → audit fails; retain the seven artifacts.

FAQ

What is a training RFP, and how does it differ from RFI, RFQ, and KAK/TOR?

An RFP (Request for Proposal) is a formal document asking vendors to propose an approach, facilitators, methodology, schedule, and price to close a defined training need — answered with a narrative proposal that can be scored against criteria. An RFI (Request for Information) comes earlier: it maps market capability before the need is locked. An RFQ (Request for Quotation) is narrower: it asks for a price on a fixed scope. A KAK/TOR (Kerangka Acuan Kerja / Term of Reference) is the mandatory document in Indonesian government/BUMN procurement that consolidates background, objectives, scope, deliverables, schedule, supplier qualifications, and cost detail — functionally an RFP plus an audit basis for state/BUMN budgets. For healthy corporate training, the RFP/KAK becomes the single document that standardizes how every candidate answers.

How many vendors should be invited to an RFP?

Three to five. Fewer than three limits comparison and makes market-price validation difficult; more than five creates evaluation fatigue, extends the cycle, and reduces review quality per proposal. Pre-screen via RFI or initial qualification (track record, capability, NPWP/PKP, willingness to run a TNA) before sending a full RFP. For government/BUMN procurement, the number of bidders is set by the procurement method (e-purchasing, direct procurement, tender) per Presidential Regulation 16/2018 jo. 12/2021 and LKPP regulations.

What are the mandatory sections of a training RFP?

At least 14 sections: (1) background & business objectives; (2) TNA summary & competency gap; (3) participant profile and count; (4) scope, expected outcomes & measurable learning objectives; (5) format & venue; (6) technical questions (methodology, customization, facilitator, evaluation); (7) proposal format & mandatory attachments; (8) evaluation criteria & weights; (9) process schedule (Q&A, deadline, presentation, announcement); (10) legal & tax requirements (NPWP/PKP, LPK license where relevant, PPh 23 readiness); (11) participant data-protection clauses (PDP Law 27/2022); (12) commercial terms (payment terms, warranties, scope-change); (13) Q&A and clarification procedure; (14) point of contact and submission method. Drop any one and a healthy vendor will guess — guesses become budget surprises at contract.

How do I build a fair proposal-evaluation criteria set?

Define criteria before opening proposals, assign weights totaling 100% by program priority, score 1–5 against evidence, then separate technical and commercial evaluation: score technical first to a pass threshold (e.g. ≥ 3.5), then open price. A healthy nine-criterion default: TNA fit (20%), facilitator quality (15%), methodology & measurement (15%), customization (12%), track record (10%), legality & quality standards (8%), tax & procurement compliance (8%), data security (7%), pre/post support & value for money (5%). For government Quality-and-Cost-Based Selection (QCBS), the technical weight is commonly 60–80% and price 20–40%. Weights must be stated in the RFP so the decision is auditable.

How long should a healthy training RFP process take?

Three to six weeks for a standard program: 1 week to prepare and release the RFP, 1–2 weeks for the proposal window (enough for vendors to diagnose deeply, going well beyond a template copy), 1 week for evaluation and finalist presentation/sample session, 1 week for negotiation and contracting. Multi-module academies or government/BUMN procurement via LKPP take 8–12 weeks due to additional supplier-qualification, technical clarification, formal negotiation, and SPK administration. Schedules that are too short (e.g. three days to answer a serious RFP) filter out healthy vendors — they decline; what remains are template copy-pasters.

Should an RFP disclose the budget?

Two schools. (a) Disclose a range: proposals come in proportionate to budget, comparison becomes a more honest 'value per dollar' assessment, negotiation cycles shorten. (b) Keep budget closed: the market reveals true pricing, with the risk that vendors guess too low or too high. For TNA-based corporate training, (a) is healthier — budget functions as a constraint, with bargaining targets handled separately; an honest range produces more executable proposals. For Indonesian government procurement via LKPP, the budget ceiling is usually mandatory in the KAK because it ties to DIPA/RKAP.

What is a fair Q&A and clarification mechanism?

Give a 3–5 working-day Q&A window after RFP release, collect written questions from all vendors, answer simultaneously, and send replies to every participant so information is symmetric. If anything material changes, issue an addendum with a version code and extend the deadline. Avoid private one-way communications with any single vendor outside written questions — it breaks fairness and, in government/BUMN procurement, risks audit findings. Log all Q&A as a proposal attachment.

How does a training RFP differ for private companies, BUMN, and government agencies?

Private: more flexible format, internal weights, PO/PKS contract directly with the vendor, tax-invoice code 01. BUMN: subject to the Minister-of-SOE regulation on procurement guidelines, RKAP as the budget source, vendor registered on the relevant BUMN procurement system, and some BUMN are designated VAT collectors (tax-invoice code 03). Government agency: subject to Presidential Reg. 16/2018 jo. 12/2021 and LKPP Reg. No. 12/2021 (amended No. 4/2024), procurement document is a formal KAK, the dominant path is e-purchasing via Electronic Catalog V6 (Head of LKPP Circular No. 9/2024, mandatory since 1 January 2025) or tender via SPSE/INAPROC, and the agency treasurer is the VAT collector (code 02; PMK 59/PMK.03/2022). See the PO/VAT/tax-invoice guide for per-buyer detail.

What response format enables apples-to-apples comparison?

Mandate a uniform response format for every vendor: capability table with Yes/No/Partial columns plus evidence, facilitator profile in a fixed template (name, relevant hours, certifications, sample session), module-to-objective map, Kirkpatrick evaluation plan per level with instruments, structured budget (facilitator fee, content development, logistics, tax), and a one-page executive summary. Without uniform structure, the panel compares apples-oranges-mangoes and the decision falls to 'who packaged the slickest deck' instead of who best fits the need.

What are the red flags in a vendor's RFP response?

Ten warning signs: (1) no TNA summary or needs diagnosis — vendor copied a brochure; (2) anonymous facilitators or 'to be determined' — bait-and-switch risk; (3) schedule too fast with no design phase — quality sacrificed to win; (4) one-line budget or no tax detail — billing will break at finance; (5) refusing PPh 23 withholding or no NPWP — your admin and cost rise; (6) evaluation plan is only a satisfaction score — stops at Kirkpatrick L1; (7) client claims and figures without proof — unverifiable; (8) refuses NDA or data-processing agreement — PDP Law risk on you; (9) price far below market with no breakdown — quality sacrificed or hidden add-ons; (10) template response not adapted to your industry/role — vendor sells a packaged product instead of a tailored solution.

Is a presentation or sample session required before deciding?

For scale programs (multi-batch in-house, academies, retainer contracts): yes. Have 2–3 finalists present the approach and run one short module (30–60 minutes) on a case from your context. What you score: how the actual facilitator opens a topic, manages discussion, and adapts to the audience. This filters out vendors who are strong on paper and weak in the room. For small/single-class programs, a 30-minute presentation is enough. The sample session must be run by the facilitator who will actually teach — not a presales lead — as an integrity test against bait-and-switch.

How do I document an RFP decision so it survives audit?

Keep seven artifacts: (1) final RFP document and all addenda with version codes; (2) list of vendors invited and initial-screening rationale; (3) every proposal received with timestamp; (4) consolidated Q&A; (5) per-evaluator scoring sheet plus weighted-score consolidation; (6) presentation/sample-session minutes and clarification notes; (7) decision minutes with winner-selection reasoning. For government/BUMN, additional documentation follows SPSE/INAPROC and internal regulations. A future audit asks 'why was vendor X chosen?' — complete documentation makes the answer one sentence.

Next step

You now have a complete RFP framework: start from a TNA, build the 14 sections, mandate a uniform response format, set 9 weighted criteria, separate technical from commercial, test finalists in a sample session, and document the decision for audit. The sensible next step is to run a short TNA as the RFP foundation — before inviting any vendor.

Neksus works exactly in this lane: every engagement begins with a training needs analysis, is answered with a measurable proposal (Kirkpatrick/Phillips), arrives tax- and procurement-ready (NPWP/PKP, per-buyer tax-invoice code, KAK/SPSE/Catalog V6 readiness), and comes with audit-grade documentation. Discuss your team's need and request an initial TNA via the Neksus contact page — no obligation, the right starting point.

Also see the companion guides:

• How to Choose a Corporate Training Vendor
• Vendor Scoring Rubric (Weights, Scale, Worked Scores)
• Training Needs Analysis (TNA)
• Building a Training Budget (RAB)
• Training PO, VAT & Tax Invoice Procedure
• LKPP E-Catalog & E-Procurement for Training Vendors
• Kirkpatrick 4-Level Deep
• Phillips ROI Level 5
• See the full training catalog →

---

Last updated: 18 May 2026. The frameworks cited (Presidential Reg. 16/2018 jo. Presidential Reg. 12/2021; LKPP Reg. No. 12/2021 jo. No. 4/2024; LKPP Reg. No. 9/2021 on the Online Store & Electronic Catalog; Head of LKPP Circular No. 9/2024 on Electronic Catalog V6 implementation; PMK 59/PMK.03/2022; SE-35/PJ/2010; HPP Law No. 7/2021; PDP Law No. 27/2022; PMK 32/2025 on SBM FY 2026) are attributed to their official sources. Tax and procurement mechanics described are general and confirmed per contract under current regulations — validate with your tax and legal teams. Neksus does not publish client names or success statistics.