Before booking the template visit, confirm what is actually ready
A shared readiness record helps the office and field technician agree on the purpose of the visit.
A shared readiness record helps the office and field technician agree on the purpose of the visit.
A template appointment is more useful when the office and technician share the same understanding of the site. Confirming readiness does not require the scheduler to make technical installation judgments. It requires collecting the right information and referring unresolved conditions to the qualified person responsible.
Define the visit
Record the rooms and surfaces included, the contact who will provide access, the current stage of the project and the decisions still pending. Ask for the relevant site information through the shop’s established process. Have the templator or responsible production person determine whether the visit can achieve its intended purpose.
Confirm how sink, appliance, backsplash and other specifications will be provided. A customer’s general description may be enough for an early discussion but insufficient for production decisions. Identify who will obtain missing model information and when it is expected.
Record exceptions before travel
If the site is not ready for a final template, explain whether the appointment is a preliminary review, needs a revised scope or should be moved. Preserve that decision in the job record so the technician does not discover a different expectation on arrival.
Prodim’s stone-industry resources describe digital templating applications. The scheduling lesson applies around the measuring equipment: clear preparation lets the field technician spend the visit collecting useful job information rather than reconstructing what the office thought had been arranged.
Source & further reading
Product records for this article
- Proliner — sources, check date and demonstration questions
Original editorial planning guidance. The linked manufacturer resource supplies relevant product or training context; it is not an endorsement of this article or a substitute for machine-specific instructions.
Editorial approach & corrections →