Separate preparation from professional judgment

Preparation work has a source, a rule, and a checkable output. A takeoff of a clearly dimensioned wall, a comparison of two supplier quotes on the same specification, or a list of unanswered requests for information all fit that description. Professional judgment begins when the answer depends on interpreting incomplete design, weighing risk, or accepting a commercial position.

Write the split in verbs. The assistant may extract, count, compare, label, reconcile, and route. The estimator may decide, approve, waive, qualify, and release.

When a task needs a verb from the second list, the assistant prepares the evidence and stops at a named review point. This is easier to audit than a general instruction to use good judgment.

Define the task envelope in writing

A task envelope names the inputs, the output, the source of truth, and the stopping condition. For a quantity worksheet, the inputs might be a specific sheet set and a measurement standard, the output a line per assembly, and the stopping condition a missing dimension or an unresolved detail. Include the software and the file locations the assistant may use.

If the estimate lives in a workbook with protected formulas, say which columns are editable and which are read only. The envelope should also name the reviewer who answers questions. An assistant without a named reviewer will either guess or stall, and both outcomes waste the preparation.

List the decisions that stay with the estimator

At minimum, keep scope interpretation, pricing basis, productivity assumptions, risk treatment, qualifications, and bid release with the estimator. Keep any decision that changes the legal or commercial position of the bid, including alternates, allowances, and exclusions. These are not clerical choices, even when they look like a single cell in a spreadsheet.

Also keep personnel and supplier judgments with the accountable lead. An assistant may flag that a quote is late or incomplete, but should not decide that a supplier is acceptable because the price is attractive. The cost estimator role description is a useful public reference for the analytical and consultative work that belongs to the professional role.

Assistant and estimator decision boundary
ActivityAssistant mayEstimator must
Quantity takeoffExtract and count from a current sheetApprove the measurement basis
Quote comparisonNormalize scope and flag gapsAccept the commercial position
Drawing conflictDocument the conflict and route itDecide or request direction
Alternate pricingPrepare the comparisonChoose the recommendation
Bid releaseAssemble the packet indexSign and release the bid
ExceptionRecord the reason and ownerResolve or escalate

Handle ambiguous drawings with a stop rule

Ambiguity is the most common place where a well meaning assistant crosses the line. A missing dimension, a detail that contradicts a note, or a schedule that does not match the plan should trigger a documented question. The assistant may search the drawing set for a related detail, but should not select the most convenient interpretation.

Use a three part stop rule: state what is missing, state what was checked, and state what decision is needed. Route it to the named reviewer with a needed date.

This turns an ambiguity into a reviewable item and gives the estimator a clean place to resume. It also creates a record of how the issue was resolved.

Control external communication

An assistant may send a request for a quote or a clarification if the language is approved and the recipient is on an approved list. The assistant should not negotiate price, promise a delivery date, or confirm a scope interpretation. Those messages can create expectations that bind the company.

Provide templates and a clear escalation path for replies that ask a commercial question. Log every outbound message with the project, the recipient, and the template used. The log helps the estimator see what was asked and prevents duplicate requests that confuse suppliers.

Review a sample and correct the system

Review the assistant's output on a predictable schedule. Sample a high value line, a line with a recent revision, and a line that was previously corrected. Check the source reference, the arithmetic, and the status.

If the same gap appears twice, fix the checklist or the source guidance rather than coaching the person again. Track a small set of signals: rows with complete source references, items waiting on the wrong owner, exceptions by reason, and rework caused by a missed instruction.

These measures show whether the boundary is working. They do not measure how busy the assistant looks, which is a poor proxy for useful preparation.

Scale only after the boundary holds

Start with one workflow and one reviewer. Add a second workflow only when the first has a stable checklist, a reliable stop rule, and a review record that the estimator trusts. Expanding too early hides defects inside volume and makes correction harder.

The onboarding sequence should mirror this discipline: one bounded task, a source map, an exception script, and a review cadence. A narrow role that reliably stops at the right point is more valuable than a broad role that occasionally makes an unauthorized call.

Put the stop rule inside the task brief

A boundary that lives only in a manager's head is not a control. Write the stop rule into the same brief that describes the task. Name the source of truth, the output, the fields the assistant may change, and the exact conditions that require a handoff.

Keep the brief short enough to read before the work starts. Review the brief when the workflow changes. A new drawing set, a new estimating template, or a new approval step can invalidate the old stop rule.

The evidence index gives the assistant a place to record what was checked, which makes the boundary visible in the work itself rather than only in the policy document. A written stop rule also protects the assistant. When a request arrives that falls outside the brief, the answer is not a personal refusal.

It is a documented handoff to the named reviewer. That clarity reduces friction and keeps the professional decision with the person who is accountable for it.

Frequently Asked Questions

Can an assistant update the estimate workbook directly?

Only in fields the estimator has explicitly opened for that task, with version control and a review step. Protected pricing and release fields should stay locked. The assistant should record the source beside every value it enters.

What is the first task to delegate?

A repeating task with a stable source, a visible output, and a named reviewer. Quote normalization and quantity worksheet preparation are common starting points because the evidence can be checked line by line.

How do I know the boundary is too loose?

Look for decisions that appear in the estimate without a reviewer name, clarifications that no one approved, or repeated rework on the same issue. Tighten the stop rule and retrain before adding more volume.

Role designConstruction EstimatingCost Support