Work Completion Certificate Format

What is a Work Completion Certificate?

A work completion certificate is a signed statement from the client, or the person they appointed to certify, that contracted work was finished on a stated date. It is usually what unlocks the final invoice, releases retention and starts the defects liability clock. Without one, a contractor who has done everything asked can still be told the job was never accepted, and has no dated document to put against that claim.

Building and civil contractors, electrical and plumbing subcontractors, interior fit-out firms, annual maintenance vendors, IT implementation partners and consultants all ask for one at the end of a job. Government departments and public sector undertakings issue them routinely, and contractors keep the file because past-performance credentials in a tender pack are usually proved with completion certificates rather than invoices. Freelancers use a lighter version to close a milestone before raising the final bill.

What the certificate legally triggers comes from your contract and from local rules, and they diverge. Standard building forms define practical or substantial completion differently — JCT and NEC in the UK, AIA in the US, FIDIC internationally, AS 4000 in Australia, and the CPWD or state PWD conditions in India. Payment security law bites too: mechanics lien and prompt-payment deadlines vary by US state, and construction adjudication regimes in the UK, Australia and Singapore run on their own clocks. Check the contract clause and the statute that applies to the site.

This certificate says the work was done. It does not say the work complies with building regulations, fire code or electrical standards — those need the relevant statutory inspection and their own certificates. It is not a payment certificate and does not by itself authorise a sum to be paid. It does not end the contractor's liability: warranties and the defects period usually run from it, not to it. And it does not turn an unapproved variation into an approved one.

What to put in a Work Completion Certificate

These are the details this template asks for. Anything left blank is marked in red on the preview so you can see what is still missing.

How to write a Work Completion Certificate

1. Reference the contract, not just the job

   Open with the contract or work order number and its date, the tender or agreement reference, and the site address. Accounts payable will match the certificate to a purchase order before they release anything, and a certificate that names only ‘the office refurbishment’ sits in a tray until somebody works out which of four projects it belongs to. Add the client's own project code if they use one.

2. Describe the scope that was actually completed

   Set out the deliverables against the schedule of work: quantities, areas, counts, locations. For a maintenance contract, name the period covered and the visits performed. If part of the scope was descoped or deferred, say which lines and why. A certificate that describes the whole contract when two thirds was delivered is worse than useless — the client's auditor will find it and the argument starts there.

3. State the completion date, not the issue date

   Write the date the work actually finished, and separately the date the certificate is signed. They are rarely the same, and the earlier one drives the retention clock, the defects liability period and any calculation of liquidated damages for delay. If completion was reached in stages, list each section with its own date rather than collapsing them all into the last one.

4. List variations and their approval status

   Set out approved variation orders by number, date and value, so the certificate and the final account agree. Keep unapproved or disputed claims in a separate line that says they remain open. Silence is dangerous: a certificate that reads as a clean close-out can later be argued to have settled everything, including the claim you were still negotiating.

5. Have an authorised representative sign and stamp

   The signature should be the client's project manager, engineer, architect or contract administrator — whoever the contract names as able to certify. Print their name, role and organisation, add the company stamp where local practice expects one, and date it. Issue copies to both parties. A certificate signed by a site supervisor with no delegated authority proves the supervisor was happy and nothing more.

Common mistakes

• Issuing a certificate that omits the completion date leaves the retention period, the defects liability period and any delay calculation with no start point, and every one of them then becomes negotiable.
• Certifying a payment amount inside a completion certificate blurs it with a payment certificate, and a client who disputes the figure ends up disputing the completion too.
• Leaving out the contract or purchase order number sends the certificate to a finance team that cannot match it, and the final invoice ages quietly in a queue.
• Describing the scope in a single line means nobody can tell later which parts of a multi-phase job the certificate actually covered.
• Signing off with snags unlisted converts every remaining item into a favour rather than an obligation, because the record says the work was complete.

Frequently asked questions

This page explains general practice and is not legal advice. Requirements differ between countries and, in some cases, between states — check what applies where the document will be used.

Related templates

All templates · Operations templates