Construction Job handover checklist and work pack template

Identify the Job and current arrangement

Enter the Job, Customer, site reference and work address. A customer may have several properties or pieces of work, so a name alone can leave the team opening the wrong record. Identify the areas this attendance concerns.

Record the actual date, time and relevant timezone, with its confirmation status. Use an unambiguous date and familiar 24-hour time where appropriate. A possible window discussed during quoting should not appear as a confirmed attendance.

Name the assigned people and operational responsibilities that actually apply. If assignment is still open, preserve that question and its owner rather than assume an available person knows they are attending.

Keep the work-pack reference or version connected to the scheduling record. A later change should leave the current arrangement identifiable, not introduce another private instruction that competes with the team’s existing plan.

Carry the agreed scope

Select the accepted scope and relevant specification references. Use the version that governs the work, rather than a convenient early estimate or another offer still being discussed. The team needs to know what result they are expected to provide.

Include accepted adjustments through the relevant agreement context. A customer request for another finish can be part of the history without already being the specification to deliver. Identify the actual review or response still needed.

Keep exclusions and boundaries visible where they affect the operational work. Someone attending a fitting-only package should understand which supply or making-good task belongs elsewhere. A short Job title rarely explains that boundary by itself.

Resolve contradictory documents before handing them over. An old drawing and a current scope note can both look authoritative. Establish which information applies and retain the earlier version as history without letting it stand as the current instruction.

Choose work and access contacts

The template separates the work contact from the access contact. A coordinator may answer scope questions while another person meets the team. Record the purpose of each selection rather than assume one phone number handles every task.

Confirm the actual access arrangement relevant to this attendance. The team should know who is expected to meet them or how the reviewed route works. Keep unconfirmed details in the readiness matrix until the appropriate person supplies the answer.

Do not infer commercial approval authority from access information. A person able to open the property may not decide a revised price or specification. Route those questions through the relevant Customer arrangement.

Review the contact position when it changes. A new default elsewhere in the business does not explain whether an existing Job’s selected arrangement remains correct. Check the work-specific choice before somebody leaves for site.

Use the readiness matrix

List the inputs required for the work, their actual position or evidence, the person confirming them and any open action. Materials, access, preceding work and customer decisions can require different owners and review points.

The worked example prepares an alcove joinery package with an available scope reference but a raised finish choice and supply question still under review. Those rows do not claim that the team can proceed from an unconfirmed specification.

Use a confirmation with its basis rather than a general "ready" label. A product selection, delivery expectation and item actually available are different facts. The matrix gives them a place without turning one into the others.

Choose a next responsibility for each open row. That may be obtaining information, arranging access or a competent assessment. An internal review time guides the action; it is not automatically a promise about arrival, delivery or completion.

Select the records needed

The contents checklist prompts current scope, applicable drawings, contacts, supply boundaries, relevant project safety references and known open questions. Select what the recipient needs for their actual role and work.

Keep private office notes, internal costs and unrelated customer records separate unless an appropriate deliberate selection is required. The pack is a working handover, not a copy of everything associated with the Customer.

Check that the selected information is obtainable by the relevant people. A file reference in a document is little help if the person cannot open it or does not know where the current version is kept. Resolve that route before relying on the handover.

Use relevant technical and safety arrangements through the actual project process. The template can reference them and identify a briefing responsibility; it does not manufacture a safe method or substitute for competent review.

Define the outcome to return

Tell the team what information should be recorded after attendance. The outcome fields cover completed work and area, unresolved information, evidence, person reviewing and next responsibility. Choose the detail appropriate to the actual task.

Distinguish work performed from a review still needed. A field note may report a fitting action while another person assesses the result against the specification. Keep those contributions clear instead of declaring the whole Job complete from one activity entry.

If something changes on site, retain the actual observation or request and route it appropriately. A discovery does not itself agree a charge, and a customer conversation about another item is not automatically permission to alter the baseline.

Keep a proposed return arrangement distinct from one confirmed through scheduling and contact review. The office needs the next question and owner so the team does not leave an unfinished note that somebody else must interpret.

Check the pack before attendance

If the team uses a printed or downloaded copy, establish how a revised instruction reaches them. The current record in the office does not automatically update a copy already in a van. Identify the pack version and the actual change when communicating, and check the revised arrangement with the person relying on it.

Read the completed pack as the person receiving it. Can they identify the work, correct scope and version, current arrangement, operational contact and outstanding dependency? Resolve a confusing reference before the person needs to use it.

Use the example to inspect field relationships and remove it from the issued handover. A proposed date or changed selection in the learning pages should never become an actual instruction merely because the file was forwarded in full.

After a confirmed change, update the appropriate record and communicate the revised selection. Do not rely on a separate message to repair a work pack that still contains contradictory information.

Prepare one selective work pack

Choose one upcoming Job and complete the blank worksheet from actual current records. Select the relevant attachments, review the readiness rows and define the outcome needed from the team.

Ask whether someone unfamiliar with the earlier conversation could use the pack without guessing. The useful handover provides enough operational context to act while keeping unresolved and private information in their appropriate places.