🏁 Completion Notice Builder
Report completion and request inspection in one document — separate from use approval.
We report that the works below have been completed in accordance with the contract and design documents, and request completion inspection.
| Project | Site address | ||
|---|---|---|---|
| Client | Contractor | ||
| Contract date | Final contract amount |
| Start date | Contract completion | ||
|---|---|---|---|
| Actual completion | Reason for any change |
| Work type | Description | Quantity / spec | Amount |
|---|---|---|---|
| Liability starts | Liability period (per contract) | ||
|---|---|---|---|
| Defects bond | Defect contact |
Completion documents attached: This notice is for the client and supervisor. For permitted buildings the owner must separately apply to the authority for use approval, attaching the supervisor's completion report and as-built documents (Building Act Art. 22(1)); the building may not be used before approval (Art. 22(3)). Copies are usually one for the contract department and one for the supervising department; add a third for the supervisor where one is appointed.
| Submitted on | Contractor | Site manager | Inspector / supervisor |
|---|---|---|---|
| Date: (Sign) | Date: (Sign) | Date: (Sign) | Date: (Sign) |
Paste into ChatGPT or Claude to tailor it to your situation
🖨️ Choose "Save as PDF" in the print dialog to get a PDF file
📄 Opens and edits directly in Word or Hangul (.doc)
✅ All required items are present
You may omit these. We only tell you the risk.
- TitleCompletion notice (with inspection request) · 12/12
- Project overviewProject overview (full) · 12/12
- PeriodPeriod against contract · 12/12
- Completed scopeCompleted scope by work type · 12/12
- Defects liabilityDefects liability (per contract) · 12/12
- DocumentsDocuments + use approval notice · 12/12
- SubmissionSubmission and inspection · 12/12
- LogoCompany logo · 3/12
Drag or use the arrows. ⇥ places a block beside the row above, ⇤ gives it its own row again. ＋− adjust one column; side-by-side items trade width with each other.
Colors stay; only the header, tables and signature layout change
Harbor Mist
Tap a swatch to lock that color
Tone
- Logo
- Title
- Project overview
- Period
- Completed scope
- Defects liability
- Documents
- Submission
What you type stays in this browser. Nothing is sent to a server.
⚠️ This notice is a document between contracting parties. For permitted buildings the owner must apply to the authority for use approval, attaching the supervisor's completion report and as-built documents (Building Act Art. 22(1)); the building may not be used before approval (Art. 22(3)). Defects liability periods vary by work type and contract — check yours.
We build ISO documentation systems and Daou Office approval forms to order
ISO documents structured the way audits expect, and groupware approval forms shaped around how your company actually works.
- ISO 9001, 14001 and 45001 documentation — manual, procedures, work instructions and record forms as one coherent set.
- Custom Daou Office approval forms — approval routes, required fields and acceptance criteria filled in, not empty templates.
- No off-the-shelf template pack. Each document is reworked around your industry and your processes.
We do not represent you at certification audits and do not guarantee certification. Our scope ends at building the documents and the system.
What this tool does
A completion notice is how a contractor reports that the works are finished and asks for completion inspection. Like the commencement notice it is a contractual document with no prescribed form, and it is separate from use approval. Article 22(1) of the Building Act requires the building owner, in order to use a completed building, to apply to the permitting authority for use approval with the supervisor's completion report and the as-built documents attached, and Article 22(3) provides that the building may not be used or allowed to be used before that approval. Filing a completion notice therefore does not let anyone move in. This builder produces the notice — completion date, scope, defects liability and handover documents — and lets you record the distinction from use approval in the document itself.
Who uses this
- Reporting completion and requesting inspection from the client
- Summarising final as-built scope on a project with repeated variations
- Recording exactly which completion documents were handed over, and how many copies
- Making the defects liability period and the contact for defect reports explicit
- Preventing occupancy dates from slipping because completion and use approval were confused
How to use
- 1Use the same project name as the commencement notice so the documents form one chain from start to finish.
- 2Record the contract completion date and the actual completion date separately, and always state the reason if they differ.
- 3List variations in the scope section. If there were none, write that rather than leaving it blank.
- 4Choose the document block that includes the use-approval notice so the owner's separate duty is on the record.
Completion notice versus use approval
The completion notice is a contractual report from contractor to client; use approval is a statutory application from owner to permitting authority. Article 22(1) of the Building Act requires the owner, in order to use a completed building, to apply for use approval attaching the completion report prepared by the construction supervisor, where one was appointed, and the as-built documents and other papers prescribed by ministerial rules. Under Article 22(2) the authority inspects whether the building was constructed in accordance with the permitted or notified design documents and whether those reports and documents were properly prepared, and issues a use approval certificate for buildings that pass. Article 22(3) then provides that the building may not be used before approval, with exceptions where the authority failed to issue the certificate within the prescribed period or where temporary use was approved.
Worked examples
Project with variations
List only the varied work types in the scope table and note in the remarks whether a variation order was executed. Variations not declared here become disputes about scope at final account.
Project that ran long
Record both the contract date and the actual date with the reason and its basis. Where rain days or client-instructed standby caused the delay, submit the daily reports alongside.
Making defects liability explicit
Copy the period from the contract, and record the start date and the contact for defect reports. Where the contract sets different periods by work type, align them with the work types in the scope table.
Frequently asked questions
Can the building be used once the completion notice is filed?
No. The notice is only a contractual report to the client and supervisor. For permitted or notified buildings the owner must apply to the authority and obtain use approval, and under Article 22(3) the building may not be used before that approval. The exceptions are where the authority failed to issue the certificate within the prescribed period, or where temporary use approval was granted.
What is attached to a use approval application?
Article 22(1) requires the completion report prepared by the construction supervisor, where one was appointed, together with the as-built documents and other papers prescribed by ministerial rules. Under Article 22(2) the authority checks that the building matches the permitted design documents and that those reports and documents were properly prepared. The precise list comes from ministerial rules, so confirm it with the authority before applying.
How long is the defects liability period?
It depends on the work type and the contract. This builder deliberately does not assert a period; it asks you to copy the figure from your contract. If the contract is silent, check the governing rules and standard conditions that apply. The start date matters just as much — many contracts run the period from the date the works pass inspection, so record that date.
Do I file the notice and the inspection request separately?
They can be combined. Choosing the title block that includes an inspection request puts both on one page. Some clients use a separate inspection request form, so check the contract and site instructions first.
Which completion documents should be handed over?
It varies, but as-built drawings, a photographic record, test reports, material delivery records, and manuals and warranties for major plant are typical. What matters most is listing what was handed over and in how many copies. Without that list there is no way to check when someone says months later that a particular document never arrived.
The actual date differs from the contract date. How do I record it?
Record both and state why they differ. Giving only the actual date removes the yardstick for delay; giving only the contract date is untrue. If a variation extended the period, say so; if the extension is still under discussion, record that it is.
Cautions
- •Filing this notice is not use approval. The building may not be used before approval (Building Act Art. 22(3)).
- •Defects liability periods vary by work type and contract. This builder does not assert a period — check yours.
- •Variations not declared here become disputes about scope at final account.
- •List the completion documents and copy counts. Most handover disputes come from the absence of that record.
Related tools
Last reviewed: 2026-09-04