Client Acceptance for General Contracting

Read the contract and specification sections that describe substantial completion, final completion, and acceptance. Note any specific conditions, such as “punch list substantially complete,” “all systems operational,” or “as-builts delivered.”

Look back at proposal language, key meeting minutes, and client emails to identify any promises or expectations that go beyond the formal contract. Capture these so they are not forgotten when discussing acceptance.

Create a list of documents that must be in place before acceptance: completion certificates, closeout package, warranties, as-builts, training records, and any regulatory approvals (like certificate of occupancy).

Translate the technical and legal requirements into a short list of plain-language criteria, such as “building safe and ready for intended use,” “no major outstanding defects,” and “client has received closeout documents.”

Sit down with the project manager to check that your criteria list is realistic and matches the way the job has been executed. Adjust wording or scope based on their feedback.

Provide the criteria to the client or their representative and ask them to confirm that this matches what they expect to see before signing acceptance. Make notes of any added conditions and update your list accordingly.

Look at the latest punch list and quality logs to see how many items remain, their severity, and whether any are in highly visible or critical areas. Decide which items must be complete before you invite the client.

Physically walk entries, lobbies, corridors, restrooms, and primary occupied spaces with a critical eye. Check finishes, cleanliness, lighting, and system operation in the same way a client would on their first day using the space.

Check that lighting controls, HVAC, access control, and other visible systems operate correctly in client-facing spaces. Note any issues and get them into a fast-track correction list.

Make sure key documents such as as-built drawings, warranty summaries, and major test reports are at least in a usable near-final state so you can answer client questions about them.

List any remaining issues that might cause the client to hesitate in accepting the project, such as known leaks, recurring equipment alarms, or unfinished specialty work.

Based on your findings, decide with the project manager whether the project is ready to move into formal client acceptance. If not, identify the top items that must be finished first and assign owners and deadlines.

Write a short paragraph describing the project’s original purpose and main components (for example, “new 30,000 SF office build-out with open work areas, conference rooms, and support spaces”). Avoid heavy technical language.

List the most significant change orders in plain language with a brief explanation—what changed, why it changed, and any schedule or cost impacts. You do not need to list every small change, just those the client is likely to remember or ask about.

Note important dates such as project start, major phase completions, substantial completion, and expected final completion. This helps the client see the project timeline at a glance.

Provide a brief statement of the final contract value and whether it aligned with prior expectations and approved changes, without going into full accounting detail in this document.

If there are items intentionally scheduled after acceptance (for example, seasonal planting, planned upgrades), list them clearly so they are not confused with defects or incomplete work.

Put the summary into a clean, easy-to-read format (one to two pages) that can be shared by email and printed. This document will be used during acceptance meetings and walkthroughs to keep everyone aligned.

Decide who needs to attend from each side: client facilities staff, client project representatives, architect, key engineers, and your internal team (project manager, superintendent, closeout lead). List names and contact details.

Decide which areas will be included in the acceptance walkthrough and in what sequence (for example, site and exterior, main interior paths, typical rooms, critical support spaces). Plan a route that is efficient and covers all agreed areas.

Create an agenda that includes introductions, a brief project overview, the walkthrough itself, time for questions, and a closing segment to discuss next steps. Include approximate timing for each section.

Send a short message to the client and architect with a couple of date/time options for the walkthrough. Ask for feedback on which works best and whether anyone else should be invited.

Once a date is agreed, send a calendar invite with the confirmed time, location to meet, expected duration, and agenda. Include directions and any access or security details needed to enter the site.

Before the meeting, share the project summary, acceptance criteria, and any floor plans or maps participants may need. Bring printed copies to the walkthrough for those who prefer paper.

Gather everyone in a central spot and review the agenda, acceptance criteria, and route. Explain that you will walk the space, demonstrate key items, and record any issues for follow-up rather than trying to fix everything on the spot.

Guide the client and design team through the areas in the agreed sequence. Move at a pace that allows questions but keeps the group from getting bogged down in minor details in every room.

Point out important design or functional features, key equipment rooms, and areas where the building may operate differently than a typical space. Briefly explain how major systems (HVAC, lighting control, access) are intended to be used day to day.

Invite the client to point out anything that looks wrong, unfinished, or confusing. Record each concern in a simple log with location and description, even if you think it is already on the punch list or not your responsibility.

If there is disagreement about whether something is “acceptable,” avoid debating in the field. Acknowledge the concern, note it accurately, and let the client know it will be reviewed against the contract and standards after the walk.

At the end of the walkthrough, recap the main positive points and the general categories of issues noted (for example, minor paint touch-ups, a few door adjustments). Explain that a written list of items and next steps will follow.

Gather written notes, floor plan markups, and any quick emails or texts that captured client comments during or immediately after the walkthrough.

Create a log or use your existing punch/issue system to enter each client concern as a separate line. Include fields for location, description, client priority if stated, and your initial assessment of severity.

Review the list and reword vague descriptions into something specific (for example, “paint defect on north wall, Meeting Room 204”). Combine duplicate items that clearly refer to the same issue, keeping one clear description.

For each item, note which trade or internal team will likely be responsible and categorize it (finish, door/hardware, mechanical, electrical, cleaning, documentation, etc.). This helps when you later coordinate corrections.

Identify any items that might be outside the original scope or more about personal preference than defects. Flag these for review with the project manager and possibly the client before committing to fix them.

Share the list with the project manager to confirm descriptions, responsibilities, and which items should be treated as contractual obligations versus goodwill fixes or change requests.

Working with the project manager, categorize items into high, medium, and low priority based on safety, function, visibility, and client emphasis. Identify a realistic timeframe to resolve each group.

For each item in the log, assign a clear owner—subcontractor, internal crew, or documentation lead. Communicate expectations and target completion dates to each responsible party.

Plan when and how corrective work will occur, especially if the client has already occupied the space. Coordinate after-hours work where necessary and ensure workers understand protection and cleanliness expectations.

Once responsible parties report items complete, go to each location or review each document to confirm the issue is resolved to the agreed standard. Do not mark items complete based solely on verbal reports.

Change the status of each verified item to “complete” and note the completion date and who verified it. For any item that cannot be fully resolved, record the reason and agreed alternative outcome.

When most or all issues are closed, write a short summary showing how many items were raised and how many have been resolved. Highlight any remaining minor items and how they will be tracked (often through warranty).

List everything you are handing over: closeout manuals, as-built drawings, warranty summary, keys, access cards, codes, training recordings, and any digital media (USB drives, links).

Arrange physical documents and keys neatly in labeled binders, boxes, or envelopes. Ensure digital files are organized in a clear folder structure and that links or drives are labeled with project information.

Invite client operations and facilities staff to a focused session where you will walk through what is being delivered and how it is organized. Keep this separate from technical training sessions if those already occurred.

Show the client the structure of the digital closeout package and any physical binders. Demonstrate how to find key items like as-builts for a specific floor, warranties for a specific system, or O&M manuals for a given piece of equipment.

Review the warranty and support contact process, including phone numbers, email addresses, and typical response times. Clarify what types of issues are warranty-related versus operational or new work.

Have the client sign a simple receipt or include a section in the acceptance form listing delivered items. Keep a copy in your project records and give them a copy for theirs.

Create a simple one- or two-page form or use the client’s standard form if they have one. It should reference the project name, location, substantial/final completion dates, and any attachments like final issue lists.

Add a section listing any agreed minor items that will be addressed after acceptance, with target dates. Clarify that acceptance is granted with these items outstanding, as long as they are completed according to the agreement.

Meet with the client’s decision-maker and, if needed, their project manager to walk through the acceptance form. Bring your summary of resolved issues and status of any remaining items.

Go through the document with the client, explaining each section in plain language. Answer any questions and adjust wording if both parties agree a clarification is needed and it still aligns with the contract.

Once the client is comfortable, ask for signature from their authorized representative and sign on behalf of your company if required. Make sure dates are filled in and all signature blocks are complete.

Provide a copy to the client and keep a digital copy in the project’s closeout folder. Share the acceptance confirmation with your internal finance, project management, and warranty teams.

Send a summary email or notice to project management, accounting, leadership, and the warranty/service team confirming the acceptance date and attaching the signed acceptance form.

Change the project status in your project management and accounting systems to reflect that it has moved from active construction to closeout/warranty. Update key dates such as acceptance date and warranty start.

Let subcontractors know that the project has been accepted and remind them of their warranty responsibilities. Share any final minor items they are still expected to complete and how those will be tracked.

With the client’s approval, send a brief note to their broader stakeholder group (facilities, operations, department heads) confirming the project is accepted and who to contact for future issues.

As part of the communication, restate warranty contact information and basic response expectations so the client knows exactly how to get help if problems arise.

Save copies of all acceptance-related communications in the project folder. These records help future team members understand when the project was considered accepted and how the transition to warranty was explained.