Client stories
Notes from committees that asked us to sit with the financial schedules before award.
Voices from recent awards
“The contingency doubled once maintenance years were added.”
They caught a contingency that doubled once the maintenance years were added. That single finding changed how we ranked the shortlist for our hospital expansion tender. We still had to argue the technical scores, but at least the money columns stopped moving mid-meeting.
— Procurement lead, private hospital group, Bangkok
“Plain Thai and English, with page references.”
The report arrived in plain Thai and English, with page references we could open in the meeting. It still took two days longer than we hoped for a five-application pack, and one annex felt denser than our board preferred — yet the panel trusted the arithmetic enough to close the session without a second adjournment.
— Facilities director, industrial estate, Chonburi
“We almost awarded on a rounding trail.”
Our municipal works tender had three applications that looked identical until API Layer Path rebuilt the extensions. One supplier’s total relied on rounding that favoured them across forty line items. Mild embarrassment in the room; better than a protest later.
— Evaluation chair, provincial municipality
Extended story: estate utility package
An Eastern Economic Corridor estate asked us to examine six applications for a multi-year utility maintenance package. Technical scoring was nearly complete; finance worried about escalation clauses written differently in each pack.
We recomputed base years, mapped each escalation formula to the invitation’s index rule, and flagged two applications that priced year-four labour as if the index could never rise. The chair used the exceptions list to request clarifications before ranking. Award followed two weeks later with a single clarified schedule attached to the contract file.
If your committee needs a similar reading, request an audit with the tender name and lot count.