How PlanEsti Replaces the PDF Email Chain for BOQ Client Approvals

The Chain That Nobody Designed

The BOQ is finished. Three weeks of careful measurement, structured sections, clear item descriptions. The QS exports it as a PDF — twelve pages, professionally formatted — and sends it to the client with a short covering note asking for review and approval before the document is issued for tendering.

Three days later, the client replies. Two comments in the body of the email — one asking about the preliminaries allowance, one flagging that a particular finishes item seems high. The QS responds, makes the adjustments, exports a new PDF, and sends it again. The client forwards the new version to their project director for sign-off. The project director replies to the original email — the one with the first PDF attached — and writes 'approved' at the top.

Now there are two PDF versions of the BOQ in the client's email thread. The approval is attached to the first version. The second version — the one with the adjustments — has never been formally approved. The QS issues the tender documents based on the second version. Three months later, during a cost query, the client pulls up the email thread and references figures from the first version. The QS references the second. Both are looking at different numbers and neither is wrong — they are just looking at different documents.

Nobody designed this process. It grew organically from the tools that were available — email and PDF export — and it creates problems that are entirely predictable and entirely avoidable.

Why the PDF Email Chain Creates Risk at Every Stage

The PDF email chain is not a bad process because the people using it are careless. It is a bad process because it has no structure. Every step is manual, every handoff is informal, and the approval — the moment that actually matters commercially — is recorded in a format that is almost impossible to rely on when it needs to be produced as evidence.

The specific risks that accumulate across a typical BOQ review cycle:

•       Version confusion: Multiple PDF versions circulating across different email threads with no clear indicator of which is current — both parties can end up referencing different documents without realising it

•       Scattered feedback: Client comments spread across email replies, phone call notes, and WhatsApp messages — consolidating them into a single coherent revision requires manual effort and risks missing something

•       Unclear approval: An email reply saying 'looks good' or 'approved' is not a robust approval record — which version was approved, which items were reviewed, and who had authority to approve are all ambiguous

•       Third-party forwarding: When the client forwards the BOQ to a director or partner for sign-off, a separate email thread starts that the QS has no visibility of — decisions get made in conversations the QS is not part of

•       Revision cycle repetition: Each round of changes triggers another export, another email, another wait — on complex BOQs with multiple stakeholders, this cycle can repeat five or six times before a clean approval is reached

The cumulative effect of these risks is not just wasted time. It is a situation where, if a dispute arises during the project, neither party can produce a clean, unambiguous record of exactly what was approved, when, and by whom.

What the PlanEsti Client Review Workflow Does Instead

When a QS finishes a BOQ in PlanEsti and is ready for client review, they send an invitation directly from the platform. The client receives an email with a secure link. They click the link and open the BOQ in their browser — no download required, no PDF to open, no email attachment to manage.

What the client sees is the live BOQ — the actual document, not a snapshot of it. Every section, every item description, every quantity and rate. If the QS updates the BOQ after the client has opened it, the client sees the updated version the next time they open the link. There is no second PDF to send, no new email to write, and no risk of the client reviewing an outdated version without knowing it.

The client can raise comments directly against specific BOQ items inside the platform. Not in a reply email — on the line item itself. The QS sees the comment immediately, can respond or make the adjustment, and the client sees the response without any further email exchange. The entire conversation about the BOQ happens inside the document, attached to the items it relates to, in a format that both parties can follow clearly.

When the client is satisfied, they approve the BOQ inside the platform. The approval is recorded with a date and timestamp — not an email reply that could be forwarded, misattributed, or lost in a thread. The record of what was approved, when, and by whom is clear, traceable, and permanently attached to the document.

The Old Way vs PlanEsti — What Changes at Each Stage

What This Means for the QS Beyond the Approval

The approval workflow is the most visible change. But the practical benefit extends beyond getting the client to sign off. It changes the entire commercial dynamic of the review process.

When feedback is attached to specific BOQ items rather than scattered across email threads, the QS can respond to each comment precisely — explaining the basis of a rate, justifying a preliminaries allowance, or adjusting a quantity with a note that the client can see and acknowledge. The review becomes a professional dialogue rather than an email exchange where both parties are working from imperfect information.

When the approval is recorded in the platform rather than in an email inbox, the QS has a clean audit trail from the moment the BOQ was shared to the moment it was approved. Every comment raised, every response given, every revision made, and the final approval — all in one place, attached to the document they relate to. That record protects the QS if a quantity or rate is challenged later in the project. It protects the client too — they can see exactly what they approved and when.

The BOQ that reaches the client for approval is only as reliable as the measurement and preparation behind it. For a detailed guide on producing accurate, well-structured Bills of Quantities under real project pressure, see our article on How to Prepare a BOQ Faster Without Losing Accuracy.