How to Use: Project Handover Information Schedule & Closeout Log

Principal Contractor Advisory Support

Need a Competent Health & Safety Advisor for Your CDM Project?

Practical CDM support for Principal Contractors — advice, documentation, and structured systems to help you run organised, compliant projects.

If you’re managing the Principal Contractor role alongside running the job, we provide the expert guidance and support that keeps your Construction Phase Plan, RAMS, and site records properly organised and ready when clients or auditors ask to see them.

Experienced construction safety advisors supporting SME Principal Contractors across the UK.

37 Critical document templates for Principal Contractors: User Manual Index

Purpose and outcome

This resource helps you plan, chase, check, and prove all the information and “handover items” needed to finish a job properly. It’s meant for real site use: set expectations early with subcontractors, track progress during the build, and avoid the last-week scramble.

Good completion looks like: every required handover item has an owner and due date, the status has been updated as the job runs, the final documents/items are checked (not just “received”), and the Closeout Log shows what was filed, where, and by who.

Who uses it (clear roles)

Role What they do with this resource
PM / Site supervisor Owns the schedule, sets due dates, runs weekly review, chases owners, confirms what “done” means, and keeps the closeout log up to date.
Leading hands / foremen Feed in what’s coming up (tests, access, deliveries), help confirm practical items are handed over (keys, demos, spares).
Subcontractors / suppliers Provide their documents on time (as-builts, test sheets, certificates, warranties, manuals) and fix anything rejected as incomplete.
Admin / document controller (if you have one) Files documents into the agreed folder structure, keeps versions tidy, and helps compile the client handover pack.
Client rep (at handover) Confirms receipt/acceptance of the handover pack (as per contract) and signs where required.

When to use it (timing in the workflow)

  • Kick-off / early job (best time): set up the schedule and assign owners/due dates to each item. Tell subs up front what you’ll be asking for and when.
  • During the build: update it continuously (minimum weekly). Use it at site meetings to chase items before they become urgent.
  • Commissioning / pre-completion: focus on test results, certificates, approvals, training, and O&M manuals. Push “At risk” items hard.
  • Handover week: verify everything is complete and correctly labelled, then finalise the Closeout Log and issue the handover pack.
  • After handover (defects period): keep the log and folder handy for quick answers if the client queries warranties, serial numbers, test results, or compliance.

Before you start (what you need on hand)

  • Contract / scope documents: what the client expects at completion (handover pack requirements, formats, deadlines).
  • Drawing register / revision info: so “as-built” means the latest and correct set.
  • Subcontract agreements / purchase orders: so you can tie deliverables to each trade (e.g., sparkies provide CCEW/CoC, test sheets, as-builts).
  • Client requirements: digital folder structure, naming conventions, whether they want PDFs, native CAD, editable manuals, etc.
  • Site program / key dates: commissioning dates, inspection dates, practical completion target, handover date.
  • A filing location (set this early): one agreed “source of truth” folder (cloud drive, project server) with a simple structure.

How to complete it (step-by-step)

Step 1 — Set up the project details

  1. Fill in project name, client, site address, job number, and key contacts.
  2. Add the target completion and expected handover date. These dates drive every “Needed by” date in the schedule.

Step 2 — Build your “handover schedule” early (don’t wait)

  1. Go through each section (as-builts, testing/commissioning, certificates, O&M/warranties/training, practical items, extras).
  2. For every line item:
    • Assign a real Owner (company or person). Usually the subcontractor or supplier.
    • Set a Needed by date that is before handover (not the handover day). Give yourself time to check and fix gaps.
    • Agree the Evidence / location format early (e.g., “Upload PDF to \\Projects\Job123\Handover\Certificates”).
    • Set initial Status (often ⛔ Not started).
  3. Use the Extras (project-specific) section for anything unusual:
    • manufacturer special warranties, council conditions, specialist equipment packs, landlord requirements, photos, asset lists, QR codes, etc.

Site tip: If an item has no owner and no date, treat it as “not happening”. Put names and dates in early.

Step 3 — Run a short weekly review (10 minutes is enough)

  1. Bring the schedule to the weekly site meeting (or toolbox if that’s your main forum).
  2. Scan for anything due in the next 2–3 weeks and anything marked ⚠️ At risk.
  3. For each “At risk” item, record:
    • what’s missing,
    • who is chasing it,
    • the new committed date (don’t leave it vague).
  4. Update the status as you go (🟡 In progress → ✅ Received). Keep it simple and current.

Step 4 — Check items properly (don’t just accept a PDF)

When something is “received”, do a quick quality check before you mark it as done:

  • Correct project/site: job number, address, and client name match.
  • Correct dates: test dates, inspection dates, and certificate dates make sense.
  • Signatures and licence numbers: present where required (common gap).
  • Serial numbers / model details: included for plant/equipment and match what was installed.
  • “As-built” really means as-built: marked as as-built, correct revision, and reflects site changes.
  • Completeness: all pages attached, all schedules included, and no “draft” watermarks.

If it’s not right, mark it as “returned for correction” (keep it in your notes) and keep the schedule status as 🟡 or ⚠️ until fixed.

Step 5 — File it and update the Closeout Log (this is your proof)

  1. As each item is accepted, file it in the agreed location and naming format.
  2. Enter it in the Closeout Log:
    • Date received
    • Checked / accepted by (name)
    • Filed at (folder path or document ref)
    • Notes (e.g., revision, exceptions, or anything agreed with the client)
  3. When the pack is issued to the client, record the version/date.

Step 6 — Finalise handover

  1. Do a final check that every required item is either:
    • ✅ Received and logged, or
    • ❓ Not required (and you’ve confirmed this with the client/contract, not guessed).
  2. Make sure practical completion basics are covered (keys/fobs, access codes, demonstrations, spares, agreed defect process).
  3. Complete sign-off section as required by your job (internal sign-off and client acceptance where applicable).

Review and approval (who signs and what they check)

  • Prepared by (PM/Site supervisor): confirms the schedule and closeout log reflect what was required and what was actually delivered/checked/filed.
  • Internal check (recommended): director/operations manager (or another PM) spot-checks high-risk items:
    • compliance certificates, inspection sign-offs, test results, health & safety file items, and key warranties.
  • Client representative (where used): confirms the handover pack was issued/received (this is not the same as accepting defects are closed—keep that separate if your contract does).

Escalate early if a critical compliance item is missing (e.g., electrical certificates, fire certification, required inspections). Don’t wait until handover week.

Recordkeeping (storage, version control, retention)

  • Single source of truth: keep one project “Handover” folder that everyone uses. Avoid documents living in emails and phones.
  • Folder structure (simple example):
    • 01_As-builts
    • 02_Testing-Commissioning
    • 03_Certificates-Compliance
    • 04_OM-Warranties-Training
    • 05_Practical-Completion
    • 06_Issued-to-Client (versions)
  • File naming: include job number + document type + trade + date/revision (so you can find it fast later).
  • Retention: keep the schedule and closeout log with your project records for at least the same period you keep contracts, warranties, and compliance documents (often several years). If your contract or local rules require longer, follow that.
  • Audit readiness: the Closeout Log should let someone find the exact document quickly without chasing people who have moved on.

How often to review/update

  • Minimum: weekly update during the build (align it with your regular site meeting).
  • Ramp up near completion: twice weekly in the last 2–3 weeks if you have lots of testing/certificates landing.
  • After handover: only update if you re-issue a corrected pack or receive late documents (record them in the log with dates).

Common mistakes (and how to avoid them)

  • Leaving owners blank: assign the subcontractor/supplier by name. If it’s “TBC”, it won’t happen.
  • Due dates set to the handover day: set due dates earlier so you have time to check and correct.
  • Marking items as received without checking: do the quick completeness check (project, dates, signatures, serial numbers, revision).
  • Accepting “draft” or “sample” manuals: require final versions with the actual installed equipment listed.
  • No agreed filing location: decide early where documents go and record it in the Evidence/Location and Closeout Log.
  • Not confirming ‘Not required’: only mark ❓ Not required once it’s confirmed against contract/client expectations.
  • Forgetting practical handover basics: keys, fobs, access codes, demonstrations, and spares often cause last-minute delays—track them like documents.
  • Missing warranty start dates: confirm what triggers warranty (purchase date, installation date, commissioning date, or handover date) and record it.

Worked scenario (quick, realistic example)

You’re running a small commercial fit-out with electrical, hydraulic, and mechanical subs. Practical completion is in 4 weeks.

  1. Early job: you assign “Electrical test results + certificate” to Sparkies Co. needed by two weeks before handover. Same for hydraulic pressure test results and any compliance sign-offs.
  2. Weekly review: at the site meeting you see O&M manuals are still ⛔. You call the suppliers and set a firm delivery date, then update the schedule to 🟡 with a committed date.
  3. Received: Sparkies email test sheets. You check the job address and licence number and realise the certificate has the wrong site. You return it for correction and keep it ⚠️ until the corrected version arrives.
  4. Closeout: once corrected, you file it in the Certificates folder and enter it in the Closeout Log with date received, checker name, and folder path.
  5. Handover: you issue “Handover Pack v1 (date)” to the client and record it in the Closeout Log. Client signs acceptance of the pack, and you keep the signed page with the project records.

Principal Contractor Support

Running a CDM Project as Principal Contractor?

Get the structure, advice, and documentation support you need to manage the role properly.

When you take on the Principal Contractor role, the responsibility for the Construction Phase Plan, site safety records, RAMS, and CDM compliance usually lands on the desk of a busy director or site manager.

CTC South West provides practical advisory support and structured systems that help you keep your documentation organised, your responsibilities clear, and your projects ready for client checks or audits.

Expert CDM support, site-ready documentation, and organised compliance records — all built around how construction projects actually run.

  • Construction Phase Plans structured and ready for client review
  • RAMS and project documentation tailored to your actual work
  • Ongoing competent person support for Principal Contractors

Practical advice from experienced construction safety advisors — supporting SME Principal Contractors across the UK.