UKOM Sp.JP common mistakes
UKOM Sp.JP · Understand the traps and how to avoid them.
Treating the threshold values for direct appointment, direct selection, and limited tender as interchangeable, or quoting a single threshold for all methods regardless of the type of goods, works, or consultancy being procured.
Candidates memorise one headline figure (often the small-value direct-purchase ceiling) and then apply it to every method. In Indonesian procurement rules the method chosen depends on the procurement type, the value band, the object's complexity, and whether the provider is a qualified small business, so a single number cannot cover all cases. This collapses under scenario questions that deliberately vary the object type.
What to do instead
Build a one-page matrix before revising: rows are procurement types (barang, pekerjaan konstruksi, jasa konsultansi, jasa lainnya), columns are value bands, and cells hold the permitted method plus the approval authority. For each cell, note the article or regulation reference. Practise by taking ten past-style scenarios and writing the method and the legal basis for each, then check against the matrix.
Choosing the procurement method first and then writing the specification, budget, and schedule to fit it, instead of letting the object and value determine the method.
Under time pressure, candidates default to the most familiar method (usually tender) or the fastest one (direct appointment) and rationalise it afterwards. The planning domain tests whether the method selection is a downstream consequence of the identified need, the packaging strategy, and the budget ceiling, not an independent choice.
What to do instead
For every planning question, force the sequence: need identification, object classification, packaging, budget ceiling, method, schedule. Write the sequence as a numbered checklist and refuse to answer until each step is written down. When a scenario gives a method, verify it by working backwards to the object and value, and flag any inconsistency explicitly in the answer.
Confusing the roles and authority of the Pejabat Pengadaan, the Pokja Pemilihan, the PPK, and the KPA, and attributing signing, evaluation, or approval authority to the wrong one.
The functions overlap in practice and the titles sound similar. Candidates learn the definitions separately but never map them onto a single procurement timeline, so they misassign who signs the contract, who evaluates bids, and who approves the budget and the winner.
What to do instead
Draw a swimlane diagram with four lanes and plot every procurement milestone across them: budget approval, specification drafting, method determination, bid evaluation, award approval, contract signing, and payment. Annotate each milestone with the responsible role and the delegating role. Redo the diagram from memory weekly until the lanes are stable.
Writing evaluation criteria that are vague or unweighted, such as 'good technical proposal' or 'reasonable price', and then failing to state how ties or non-price factors are resolved.
Candidates confuse the narrative summary of an evaluation with the actual scoring instrument. They also forget that the criteria and weights must be fixed in the tender document before bids are opened, so any criterion invented at evaluation time is invalid.
What to do instead
Memorise the structure of a compliant evaluation instrument: criterion, weight, sub-criterion, scoring scale, and evidence required. Practise drafting a full evaluation table for a mixed technical and price procurement, including the formula for the price score and the tie-break rule. Always state in the answer that criteria are fixed in the tender document and cannot be changed after bid opening.
Treating the bid security, performance security, and retention as one instrument, or omitting the conditions under which each is released or forfeited.
All three are financial guarantees and candidates lump them together as 'the guarantee'. The exam tests the distinct trigger events: bid security against withdrawal or failure to sign, performance security against default during delivery, and retention against defects during the maintenance period.
What to do instead
Make a three-row table: instrument, purpose, typical percentage range, form, trigger for forfeiture or release, and timing of return. Add a note on which party holds each instrument. Then write two short scenarios, one where the bid security is forfeited and one where it must be returned, and check the reasoning against the table.
Drafting contract clauses that state obligations without stating remedies, timelines, or the standard of performance, so the clause cannot be enforced.
Candidates write in the style of a procurement announcement rather than a contract. They describe what the supplier will do but omit the measurable standard, the notice period, the cure period, and the consequence of failure, which is exactly what the drafting domain tests.
What to do instead
For every obligation you write, force four additions: the measurable standard, the deadline or milestone, the notice and cure mechanism, and the remedy or liquidated damages. Practise by taking a one-line obligation such as 'supplier must deliver on time' and rewriting it into a complete enforceable clause with all four elements.
Answering ethics questions by naming the principle (conflict of interest, fairness, transparency) without identifying the concrete disclosure, recusal, or reporting action the scenario requires.
Candidates treat ethics as a vocabulary test and stop at the label. The scenarios are designed so that the correct answer is a specific act: declare the relationship in writing, withdraw from the evaluation, report the offer of a gift, or document the reason for a deviation.
What to do instead
Convert each principle into an action verb list: for conflict of interest, declare, recuse, document; for gifts, refuse, report, record; for confidentiality, seal, log, restrict access. When answering, write the principle in one line and then the action in two lines, and check that the action is something a named official does on a named document.
Treating e-procurement as a parallel process rather than the same process with digital evidence, and so failing to state what must be recorded, timestamped, or retained electronically.
Candidates learn the platform names and the login steps but not the evidentiary consequences. The exam tests whether electronic submission, electronic bidding, and electronic evaluation produce an auditable trail equivalent to paper, including the rules on late submission, withdrawal, and system failure.
What to do instead
For each procurement stage, write the electronic artefact that proves it happened: the published announcement, the download log, the bid submission receipt with timestamp and hash, the evaluation record, the award notice. Then write the procedure for a system outage during bid submission and for a bid withdrawn before the deadline, and confirm both are documented.
Giving generic risk or dispute answers that list categories (technical, financial, legal) without mapping each risk to an owner, a likelihood and impact judgement, and a specific mitigation embedded in the procurement document.
Candidates reproduce textbook risk taxonomies because they are easy to recall, but the scenario asks which clause, which guarantee, or which approval step addresses this risk in this procurement. Without the mapping, the answer cannot be applied.
What to do instead
Use a risk register format in every answer: risk event, cause, consequence, likelihood, impact, owner, mitigation, and the document where the mitigation appears (specification, contract clause, security instrument, audit checkpoint). Practise with three risks, such as supplier default, price escalation, and collusion, and write the full register row for each.
Describing the audit finding or the dispute path in general terms without naming the evidence the auditor will request or the forum and deadline for the challenge.
Candidates know that audits check compliance and that disputes can be protested, but they do not link the finding to the specific document trail or the protest to the specific body and time limit. The exam rewards precision about who reviews what, within which period.
What to do instead
Build two reference cards. The audit card lists, per stage, the document an auditor samples and the common finding. The dispute card lists the challenge type, the forum, the deadline, and the required contents of the submission. Rehearse by writing a one-paragraph audit finding with its evidence list and a one-paragraph protest with its forum and deadline.