BOQ (Bill of Quantities)
The itemised list of everything being delivered — description, unit, quantity, cost rate and client rate. Quantity × client rate is the client value; the gap to your cost is your margin. In Pakka, BOQ items link to milestones and carry a QC-verified completion status.
Milestone
A whole phase of work on a project (e.g. “False Ceiling — Phase 1: Grid Work”). Each has predefined tasks and often a QC checklist, and moves from not-started → in-progress → QC-pending → completed, with a QC-failed → rework loop.
Variation (VO)
Any change to agreed scope — an addition, deduction, rate change or quantity change. In Pakka a variation is an approval; once granted, the BOQ updates itself and affected vendor contracts and payment schedules are flagged for review.
Scope sheet
A vendor-facing package generated from the BOQ for one trade — descriptions, units, quantities and specs, but never your rates or margins. Sent to a few vendors for quoting.
RFQ (Request for Quotation)
Sending scope sheets to vendors, collecting their quotes, comparing them side by side, and accepting one — which auto-creates the contract and payment schedule.
Snag
A defect found on site or at QC (a chipped tile, uneven paint). Critical and major snags from a QC failure automatically become rework tasks, and all snags must be cleared before handover.
QC gate
Quality control as a hard checkpoint: a milestone can’t complete until its checklist passes, including cross-trade prerequisites. A QC pass is what makes a vendor payment eligible and a BOQ item “verified.”
Tranche
One slice of a vendor’s payment schedule — advance, per-milestone, or retention. It moves pending → eligible (on QC pass) → requested → approved → released, and release needs a payment reference and a different approver (maker/checker).
Retention / DLP
Money held back from a vendor until the Defect Liability Period ends — the window after handover during which they must fix defects free. Pakka auto-releases it once the DLP passes with zero open snags and a settled bill.
PO (Purchase Order)
A numbered document committing to buy specific materials from a vendor at agreed rates. Created from RFQs or material requests, approved on the rail, and reconciled against the BOQ.
GRN (Goods Receipt Note)
The record that material physically arrived — which PO lines, and quantities received, damaged or short. Captured from WhatsApp at the gate, feeding site stock and the 3-way match.
3-way match
Before paying a vendor’s bill, the PO (what was ordered), the GRN (what arrived) and the bill (what’s charged) must agree. Mismatches are flagged.
GFC (Good For Construction)
The final approved drawing you’re allowed to build from. Pakka can gate a milestone on an approved GFC so no one builds off a draft.
Recce
The initial site-measurement survey. Recce dimensions are compared against GFC drawings and the deltas are flagged.
Selection
A client decision point with visual options (“pick one of these three tiles”). The client picks in their portal; the pick becomes a decision and locks the BOQ spec. Overdue selections are schedule risk.
Measurement book
The actual site quantities recorded per BOQ line — captured at QC pass or manually, and countersigned by the vendor. It’s what a certified final bill is computed from, instead of an argument from memory.
Pre-start condition report
A record of every room’s existing condition — photographed before you mobilise and acknowledged by the client — so a “it was already like that” dispute at handover is unwinnable against you.
Owner’s Cockpit
The owner’s single morning read of the whole firm: a pulse, a 30-day cash view, what needs attention today, project health, and people & vendor scorecards, with the money bands admin-only.
Truth layer
The three never-collapsed levels of “done”: Reported (the engineer says it’s done) → Verified (QC passed) → Eligible (payment can release). Money only ever follows Verified, never Reported.
Walk. Talk. Done.
Pakka’s promise: one voice note, photo or video from site drives the whole lifecycle — it starts the matching milestone, creates the tasks, links the work, notifies the team, and makes payment eligible. No forms.