How do you hand a construction project over properly from estimating to site work?

Why is information lost during project handover?

Information is lost when the sender assumes something is known, while the recipient only receives the files. For example, the construction estimator knows a price assumes an empty room. The site manager sees an amount and programme, but is not told that clearing the room is excluded. If the room turns out to be full, the reasoning behind the assumption is missing.

Handover must therefore convey more than documents. Discuss what has been assumed, what has been agreed and what still needs deciding. An estimate line is a financial or technical assumption; it is not automatically a complete construction instruction. An alternative in the quotation may also remain undecided.

Start with the documents on which the instruction is based and compare them with the latest changes. Record differences and ask the recipient to explain what they will do about them. This tests shared understanding. Ticking ‘quotation sent’ only says something about transmission.

A useful handover ends with three outcomes: the recipient understands the assumptions, outstanding items have owners and the information for the next work is accessible. This is practical process advice. Establish which formal confirmations are needed within the project’s agreements and authority.

What information belongs in the handover records?

Handover records contain the assumptions behind the brief, sources for construction and questions still outstanding. Distinguish between confirmed, assumed and still to be decided. Otherwise an unconfirmed choice quietly acquires the same status as an approved instruction.

Keep controlled documents in the agreed source environment. Handover records may contain references; they need not become a second collection of separate copies. Test links using the recipient’s access. A working link on the construction estimator’s computer does not prove the site manager can open the same document on site.

For an incomplete item, use a clear note. For example: ‘Corridor wall finish not yet chosen; construction project coordinator requests confirmation from project manager before ordering.’ This is more useful than ‘colour to follow’, without a person or date.

Who does what: construction estimator, construction project coordinator, project manager and site manager?

The construction estimator hands over the supporting basis. The construction project coordinator translates it into workable preparation. The project manager oversees coordination, decisions and authority. The site manager checks whether the necessary information is usable on site. Adapt the allocation to your own organisation: job titles do not automatically establish all authority.

Who signs off the handover? Designate a sender and recipient and record who may resolve outstanding items or authorise work to proceed. An acknowledgement may state: ‘records received, with these three items still outstanding.’ This need not block preparation of other items. Nor does it grant permission to carry out the undecided item in advance.

In a small construction business, the construction estimator and project manager may be the same person. Still discuss the assumptions explicitly with whoever works on site. Larger organisations more often have separate disciplines and handover stages. Headcount alone does not determine how much procedure is needed; the number of parties, dependencies and project risks also matter. Explore the allocation in roles in a construction project.

How do you capture site surveys and verbal agreements with clients?

During the site survey, record where you are, what you observe and what the client requests. Link photos to the correct room or component. Record relevant dimensions, finishes and limitations with their source. A photo of a wall, for example, does not automatically show whether its finish is included in the quotation.

Make clear in the record whether something is an observation, wish, proposal or confirmed agreement. ‘We might include that’ must not become ‘included’ during handover. Seek confirmation through the agreed project procedure. For an outstanding choice, state who arranges an answer and before which preparatory activity it is needed.

A fictional example: a different wall finish is discussed during the survey. The quotation includes the basic option; substrate repairs are excluded. Hand over the discussed preference, quoted option and exception separately. Do not leave site teams to infer from a photo or isolated note that the different finish has already been ordered.

Record the site survey within the project

The built-in recording function for in-person meetings lets you capture a physical site survey without first starting an online meeting. For supported recorded communication, Wouby AI creates a transcript and summary and automatically turns identified agreements into tasks with people responsible. This means the construction estimator does not have to recall the verbal context from memory weeks later.

If no action date is known, the task is set to today. For a finish still to be chosen, that is an action to obtain clarity, rather than an instruction to apply the finish today. Check dimensions, quantities and conditions; ordinary mobile calls outside Woub are not automatically captured through this route. For scope changes, see the guide to recording additional and omitted works.

How do you prevent a revised drawing going unnoticed?

Alongside a drawing, state which revision and suitability status apply. The newest file may still be under review. It may therefore differ from the drawing approved for construction. A date or a filename saying ‘final’ is insufficient if the agreed approval is missing.

De UK BIM Framework guidance on information management distinguishes between revision and status: the version and the purpose for which the information may be used. This British guidance is used here as a source for the concepts; agree the applicable document arrangements within your own project.

One specific software example is Dalux Box. Its documentation distinguishes design review from publishing documents for construction. Dalux itself also supports comments and follow-up around design documents. The exact functionality depends on setup and permissions.

Woub adds complementary ad-hoc coordination: which change affects which work, who must assess it and what action follows? For documents, Woub offers deep SharePoint integration, OneDrive link sharing and a simple folder structure as an add-on. These routes differ: with SharePoint, the configured document source remains authoritative. See Woub alongside document management. Keep the formal source and approval in the environment agreed for them. A message in Woub does not automatically process revisions there.

Make three checks for a change: can the recipient open the authoritative source, do they understand its effect on their work and do they know what to do with an old download or paper printout? Have the person responsible process this. Sending a notification alone does not prove the team is working to the right instruction.

How do you create checklists and follow-up tasks for site operations?

A checklist describes the checks or work belonging to the project. A follow-up task describes the specific step someone must take now. Use a standard as a starting point and adapt it to the brief. Do not quietly turn excluded work into a task to be carried out.

Write a task with an action, subject, location where necessary, owner and agreed deadline. Add a source or condition if it determines how the work is carried out. ‘Coordinate corridor wall’ is unclear. ‘Construction project coordinator requests confirmation of the ground-floor corridor wall finish before ordering’ provides a checkable next step.

Keep the distinction between preparation and construction visible. A task to obtain confirmation of a colour is not the task to apply that colour. Completion should relate to a checkable result: the choice has been confirmed under the project agreement and incorporated into the necessary information. Merely sending the question is a different result.

Wouby AI automatically creates tasks from supported recorded conversations and links the right person. Check the identification and correct any wrong assignment. The confirmed default is today when no action date is known; a later agreed deadline may therefore need attention. If the discussion covers several projects, Wouby AI links the specific tasks to the identified projects, while retaining one call report.

A new site manager also sees earlier context

Add the colleague involved to the relevant Woub project chats. New participants see the available chat history within that context by default. The site manager can therefore also read earlier explanations. Discuss exceptions and outstanding decisions as well; a long history does not replace a clear handover.

Invited subcontractors can participate free of charge in the contractor’s paid environment, including accessible tasks and Wouby AI. Use a separate chat for internal pricing considerations. The allocation of roles determines who makes substantive decisions; app permissions determine who can see what.

How do you use estimating software or CUF alongside Woub?

Estimating stays in the software used for that purpose. Woub supports complementary project communication and follow-up. A file can help with handover, provided its content, version and import result are checked.

CUF-XML is an exchange format for estimating data. Ibis describes CUF-XML for essential budget data and TRADXML for complete exchange between Ibis users. Request the right export type; not every XML file contains the same information.

De Woub guide to CUF import names 2Jours, IBIS, WpCalc, TopCalc and Gilde Software. It describes an upload for each project, selection of lines and creation of checklists for scheduling and work descriptions. Options for groups, estimated hours and material units are described. Have the capabilities checked with your export and software version; other packages need separate assessment.

What comes from CUF and what do you add as a project team?

The file route can reduce repeated retyping of supported items. It does not automatically include every assumption, attachment, pricing agreement or later revision. Discussing exceptions therefore remains part of handover.

First test a small, recognisable cost estimate. Compare source and result: which items, units and descriptions were transferred? Are assumptions and exceptions still understandable? This is a proposed check, rather than an import test performed here.

File import does not prove live synchronisation. Agree how later changes are communicated. Before importing again, check how existing, manually changed or completed tasks are handled. Do not simply reimport over an ongoing project. Read more about estimating software and CUF alongside Woub.

Does a small business without ERP lack a detailed cost estimate? Use the same essential agreements, a project template and the recording with actions. Where time and materials are not already tracked properly elsewhere, the construction-focused add-on can support record-keeping. With an existing ERP, retain the administration configured there. A CUF file is one possible route, rather than a prerequisite for good handover. Explore the software landscape by business size.

Which handover errors cause rework?

Rework can arise because site teams receive a wrong assumption, miss a change or cannot use the right source. For an actual incident, investigate where that happened. ‘The handover was poor’ is too general to change the way you work next time.

These are possible error patterns, rather than measured frequencies. A missing tick does not prove who caused an error. Look at the content, access and actual handover. For remedial work, record the actual activities, cause and costs according to your own accounting practices. An identified risk factor is not yet a demonstrable saving.

Use the finding to make handover more focused. Add a useful check or make an existing question more specific. Continually adding another general document can actually make the important exception less visible.

Handover checklist

Use these nine points as a practical starting list and adapt them to the project:

1. Scope confirmed: the recipient knows which work has been instructed and which documents underpin it.

2. Exceptions discussed: excluded work and boundaries are identifiable alongside the relevant items.

3. Sources accessible: drawings and documents have a recognisable revision and suitability status; the recipient can open them.

4. Estimating assumptions explained: relevant quantities, resources, access and working methods are understood or identified as points to check.

5. Sequence and deliveries coordinated: the preparation team knows which confirmations are required before starting or ordering.

6. Risks assessed: known uncertainties have an appropriate next step and person responsible.

7. Contacts and authority known: everyone knows who provides information, confirms choices and may authorise work to proceed.

8. Outstanding items assigned: each item has an owner, required decision date and feedback to those involved.

9. Receipt checked: the recipient can explain the next work and remaining conditions; later changes follow an agreed procedure.

This list does not replace a project-specific contractual procedure, safety plan or quality plan. First trial the handover with your own project: have someone who did not prepare the estimate use the records and note which questions come back.

The published AZ Schilders case describes a related practice: standard project templates with project preparation, work activities and agreements with residents, supplemented by subcontractor-specific details. Gudo explains that checklists and retrievable project information help with handing over projects. This is a customer’s experience of their workflow, rather than a proven CUF integration or fixed saving for other businesses.

Explore Woub’s role for the construction estimator and construction project coordinator, or try Woub free for 14 days. Assess how complementary communication and follow-up fit your existing source files and software.