From quotation to survey to production: what changes?

A quotation, a survey and a production instruction describe the same job, but they do not do the same work. The quotation explains the offer. The survey checks the relevant site information and records decisions. The production instruction tells the workshop what has actually been released to make.

Problems begin when one of those records is treated as if it already contains everything needed by the next team. An early price becomes an order. A site conversation becomes a finish change. A production sheet gets printed before the revision is approved.

The answer is not to copy more information between departments. It is to make the purpose and status of each record clear.

Keep the quotation as the commercial starting point The accepted quotation provides a record of what was offered and agreed at that stage. Preserve its item references, revision, scope and supporting information. If dimensions or specifications were provisional, keep that qualification visible.

The next team should be able to see which version the customer accepted. Do not assume that the latest attachment in somebody’s inbox is the accepted one. A more recent draft may still be awaiting a decision.

Use the quotation to prepare the survey: which items need checking, which choices remain open and which parts of the scope might need clarification? It is a starting point for the visit, not a substitute for technical verification.

Let the survey identify the differences The survey should compare the planned work with what can actually be verified on site. Some details will stay the same. Others may need amendment or further investigation.

Record those differences against the affected item. If the proposed opening arrangement cannot proceed as expected, explain the issue and the decision required. Avoid leaving a general note at the end of the job that the workshop has to interpret across several windows.

Distinguish a surveyor’s observation from a proposed solution and from an approved change. Those are three different states. A sensible suggestion made on site is not automatically a customer-approved specification.

Review changes before they become instructions When a survey produces a different specification, assess the effects on price, lead time, ordering and installation. The correct people need to review the change before it reaches manufacture.

For example, a different finish may affect supplier availability as well as the quotation. A different opening arrangement may require technical review, not just an updated picture. Record the decision and the document revision that contains it.

Use a clear hold where a necessary approval is missing. A team should not have to infer whether “awaiting confirmation” means stop, continue with everything else or make an assumption to keep the schedule moving.

Release a defined production version Production needs the approved information required for the actual system and process being used. Make the job reference, item references, revision and release status easy to identify.

A release check should confirm that required technical reviews, supplier information and customer decisions are complete. Who can release work is a business decision; make that responsibility explicit rather than leaving it to whoever prints the pack.

If part of a job can legitimately proceed while another part remains on hold, identify those boundaries. A general “job approved” label can be misleading when one item still has an unresolved issue.

Control what happens after release A late change needs a route back through review. Contact the people affected, establish what has already been ordered or made and decide how to proceed. Do not simply upload a revised file and assume everyone will notice it.

Keep the superseded version for traceability, but make it clear that it is no longer the working instruction. Where printed packs are used, consider how old copies are withdrawn or marked.

The goal is not an elaborate approval ceremony for every small detail. It is a reliable way to prevent an unreviewed change from travelling further than intended.

Use a short handover note A useful handover should answer four questions: what is being handed over, which revision applies, what remains open and who owns the next action? That is often more helpful than a large unstructured export.

A practical release conversation - Does the accepted scope match the work now being released? - Are differences from the quotation recorded and reviewed? - Are the required technical details and approvals complete? - Is the current production revision unmistakable? - Does everyone affected know about holds or late changes?

When those answers are easy to find, the office, surveyor and workshop can work from the same job without pretending that every stage needs exactly the same document.