Scope and controlled drawings
Work limits, specifications, current drawings, drawing revisions, approved details, interfaces, exclusions, and the latest authorised information used on site.
Project records · Civil works
Good handover begins before the work is finished.
Agree what must be recorded, who prepares it, who reviews it, and when it is due. That creates a clearer evidence trail from the first drawing to the final inspection.
Build one connected project record
A folder full of files is not automatically a useful handover pack. Each record needs a clear subject, date, location, revision or status, and a link to the work or decision it supports.
Instructions and changes
Dated site instructions, requests for information, agreed decisions, deviations, affected quantities, revised details, responsibility, and approval status.
Measurements and quantities
Location-based measurements, sketches, levels, calculation references, joint checks where required, supporting photographs, dates, and the related work item.
Inspection and quality evidence
Inspection requests, material information, test results, acceptance status, non-conformance records, corrective actions, reinspection, and closure evidence.
Progress and concealed work
Dated photographs with location and direction, work-stage notes, reinforcement or services before covering, weather or access constraints, and relevant site events.
Completion and as-built information
Final arrangement, approved changes, outstanding items, snag closure, applicable certificates, asset or maintenance information, keys or access items, and handover acknowledgement.
Do not create records after the fact from memory. Agree the required format and review points early, then capture evidence when the work, measurement, inspection, or decision occurs.
Record at the right moment
Some evidence cannot be recreated later.
-
Before work starts
Confirm the current scope, approved information, site condition, benchmarks, responsibilities, inspection points, required forms, file naming, and where the controlled record will be kept.
-
As work progresses
Record instructions, changes, measurements, site conditions, deliveries, tests, inspections, photographs, constraints, and corrective actions while they remain traceable.
-
Before work is covered
Inspect and record foundations, reinforcement, buried pipelines, drainage, waterproofing, embedded items, and other work that will become inaccessible.
-
Before completion is accepted
Reconcile drawings and changes, review test and inspection status, identify snags, close agreed actions, compile final information, and record who received the handover pack.
Why the evidence trail matters
Public-works documents show the practical distinction between recording quantities, recording quality checks, updating as-built information, and certifying completion. Private projects should define their own proportionate requirements in the contract and project brief.
Himachal Pradesh PWD
Measurements support quantities
The HPPWD General Conditions describe measurement records for work with financial value and checking or test-checking those records.
Review the official HPPWD conditionsHimachal Pradesh PWD
Quality records support corrective action
HPPWD explains that quality-control registers record tests and non-conformance reports, with corrective actions followed through the quality process.
Review HPPWD quality-control guidanceCPWD Works Manual
Completion has defined records
The CPWD Works Manual separately addresses measurements, completion certificates, occupancy requirements, and as-built drawings.
Review the official CPWD Works ManualThese public references illustrate record categories. They do not make a private project subject to the same procedures and do not replace its contract, drawings, specifications, professional advice, or authority requirements.
Give every required record an owner
Before mobilisation, use a simple responsibility schedule to prevent documents being assumed, duplicated, or discovered missing at closeout.
| Question | What to define | Why it matters |
|---|---|---|
| What is required? | Record name, purpose, scope, format, and contract or drawing reference | Prevents vague or unnecessary submissions |
| Who prepares it? | Named role responsible for capture, compilation, and correction | Avoids assuming another party owns the task |
| Who reviews it? | Named reviewer, required checks, response, and acceptance status | Separates submission from acceptance |
| When is it due? | Before start, before covering, at inspection, periodically, or at completion | Keeps evidence available when it can still be verified |
| Where is it controlled? | File location, naming, revision, distribution, and superseded-record method | Helps the site team use current information |
| Who receives the final copy? | Recipient, file type, number of sets, handover date, and acknowledgement | Creates a clear closeout record |
Handover pack review
Check completeness before final issue
Use only the items that apply to the agreed scope and contract.
Scope and status
- Completed work matches the agreed limits
- Current drawings and revisions are identified
- Changes and instructions are traceable
- Outstanding exclusions are stated clearly
- Required approvals or certificates are listed
Evidence and quality
- Measurements relate to locations and work items
- Inspection and test status is clear
- Non-conformances and corrective actions are closed
- Concealed work has appropriate records
- Progress photographs have dates and context
Final information
- As-built information reflects agreed changes
- Snags have an owner and closure status
- Applicable asset or maintenance information is included
- File names and revisions are consistent
- Superseded information is clearly separated
Final issue
- Required format and number of copies are complete
- Open items and limitations are recorded
- Review or acceptance status is documented
- Recipient and issue date are recorded
- Handover acknowledgement is retained
Define the records with the scope
When sharing a project enquiry, include any documentation, testing, inspection, as-built, and handover requirements already known. Items that are undecided can be identified for discussion.
Discuss the project- Project type, location, drawings, and specification
- Measurement and quantity-record requirements
- Inspection, testing, and witness points
- Change, photograph, and concealed-work records
- As-built, snagging, and final handover requirements
The applicable documents depend on the project, contract, professional team, and authority requirements.