
Operational works · Sunshine Coast
As-constructed drawings: why they matter for Sunshine Coast subdivision closeout
A practical guide to as-constructed drawings for Sunshine Coast subdivision and operational works, including survey pickup, inspections, changes and plan-sealing risk.
Concept illustration
Project question?
Check the civil constraints before committing to your next step.
Send CivilCity the address, current plans, approval stage and the issue you are trying to resolve. We will help scope the right civil engineering input for the project.
Quick answer
As-constructed drawings record the infrastructure that was actually built on a Sunshine Coast development site. They can show final lot levels, roads, driveways, stormwater pipes and pits, drainage connections, services, retaining interfaces and other works relevant to completion and plan sealing.
The approved civil drawings describe the design, not necessarily the final site. If construction changed a level, alignment, pipe location, pit position or connection, the closeout record needs to show that change clearly and be supported by the required inspections, tests, certificates and approvals. Plan sealing should be treated as a deliverable designed into construction, not paperwork discovered at the end.
Why the distinction matters
A subdivision can look complete while the project file is not. A contractor may adjust a stormwater line around an existing service, change a retaining edge or alter a driveway level. Those changes may be reasonable, but they still need to be assessed, documented and approved where required.
The commercial risk appears when civil works look finished and registration is expected, but the team has to reconstruct what happened months earlier. Missing evidence can mean extra survey, exposure of buried assets, redesign, authority queries or a contractor return visit.
What the closeout record should answer
The exact submission requirements depend on the approval, works and Council's current process. As a practical starting point, the record should show what was installed, where it is, what levels and dimensions apply, and whether the work matches the approved design or an accepted variation.
| Question | Evidence to coordinate | Why it matters |
|---|---|---|
| Where are the assets? | Surveyed alignments, pits, pipes, kerbs and connections | Confirms the infrastructure footprint. |
| What levels were achieved? | Surface, invert, cover, lot and tie-in levels | Confirms drainage, access and falls. |
| What changed? | Marked-up drawings, variation records and approvals | Prevents hidden site changes. |
| Was the work inspected? | Inspection records, tests, photos and certificates | Supports completion and condition responses. |
| Can the project close out? | Coordinated package and outstanding-item register | Connects construction evidence to plan sealing. |
A Sunshine Coast example
Imagine a two-lot subdivision in Buderim with a shared access handle and a new stormwater connection. An existing service forces the contractor to shift a pipe, move a pit and adjust the driveway transition to suit the surveyed road level.
A better process records the change immediately, confirms the revised design response, surveys the installed infrastructure before it is covered, and updates the as-constructed drawing with final levels and connection details.
Practical closeout process
- Read the approval conditions and Council's operational works and plan-sealing requirements before construction.
- Add as-constructed deliverables to the contractor's scope and inspection plan.
- Agree which assets need survey pickup before backfill.
- Record site changes immediately and obtain confirmation where required.
- Collect tests, inspections, photos, certificates and service sign-offs as work progresses.
- Reconcile the final survey against the approved drawings and condition register.
- Resolve outstanding items before requesting completion or plan sealing.
Mistakes that cause closeout delays
The most common mistake is asking for an as-constructed plan after the contractor has demobilised. Other failures include relying on red-line sketches without survey pickup, omitting invert levels, showing design values instead of installed values, failing to record service connections, and treating a construction variation as informal because it looks minor.
The survey, civil plan, engineering certificate, service authority record and plan-sealing application should describe the same completed works. If they disagree, someone must investigate before the file can be closed.
Specify what must be captured before work is covered
The as-constructed scope should be agreed with the engineer, surveyor and contractor before installation. Identify which assets need survey, what attributes must be recorded and which inspections or tests support acceptance. A photograph can help explain a detail but does not replace a surveyed position or level where one is required. Reconcile the collected information with approved changes while the team can still investigate discrepancies on site.
| Decision or stage | Evidence to check | Practical outcome |
|---|---|---|
| Survey pickup | Asset position, levels and required attributes. | Capture information before access is lost. |
| Quality evidence | Inspection, testing and product records. | Support the relevant completion requirements. |
| Change record | Reason, design response and acceptance where required. | Distinguish installed changes from undocumented departures. |
Checklist for your project brief
Use these points to define the next investigation or consultant deliverable.
- Include the record requirements in contractor and survey scopes so neither assumes the other is collecting them.
- Review the closeout file during construction and chase gaps promptly.
- Check that final plans show installed values and reference the correct approval and variations, rather than relabelling the design set.
When CivilCity should be involved
Bring CivilCity in before construction starts if the project has conditioned infrastructure, new drainage, shared access, retaining, frontage works, service relocations or a plan-sealing deadline. Send the approval decision and conditions, approved civil plans, current survey, construction programme and proposed variations.
CivilCity can define closeout requirements, coordinate inspection and survey inputs, review changes against the approved design, update the as-constructed package and identify unresolved items before they become a plan-sealing problem. The goal is a traceable record of what was built.
Common questions
What are as-constructed drawings?
They record what was actually built, including final levels, locations, dimensions and relevant infrastructure details. They are different from approved design drawings, which show what was intended.
When should as-constructed information be collected?
Plan it before construction and collect critical information while assets, connections and levels are visible. Waiting until the site is finished can make buried infrastructure difficult to verify.
Can missing as-constructed drawings delay plan sealing?
Yes. Incomplete records, unresolved variations, missing inspection evidence or uncertainty about constructed infrastructure can delay demonstrating that conditions and closeout requirements have been satisfied.
Who prepares the final record?
The civil engineer coordinates the requirements, while construction records and survey pickup are normally supplied by the contractor's surveyor or another suitably qualified survey professional.
Official sources and further guidance
- Sunshine Coast Council plan sealing
- Council operational work requirements
- Sunshine Coast Planning Scheme 2014
- Queensland Development Assessment
- Unitywater subdivision servicing pathway
Use the current requirements for your property and proposal. Illustrative scenarios describe possible design issues; they are not reported client projects.
Discuss your project
Construction and closeout support
Send the conditions, approved plans and outstanding records to identify the civil closeout tasks.
