Scope of this guide
For asphalt roadway work under a contract-defined specification. The example source is Wingecarribee Shire Council C10, a locally modified AUS-SPEC 1144 worksection. Its clauses and limits are local contract examples; adopt only the source version named by the actual project. This guide does not design pavement, approve mix composition, prescribe universal temperatures/compaction values or perform laboratory testing.
Set up the mix and lot structure before production
C10 distinguishes mix types and courses and requires a Schedule of Job Details and related quality/construction specifications. Its own daily work record, lot diagram, lot register, delivery docket, test records and closure package show why the plan needs both event records and spatial traceability.
For each course, establish project lot boundaries, chainage/lane, thickness and surfacing type from approved documents. Do not infer lot size or testing frequency from a different council or authority specification.
| Input | What to capture in the plan |
|---|---|
| Contract basis | Jurisdiction, adopted C10/AUS-SPEC or authority specification, revision, project amendments and precedence. |
| Pavement schedule | Road/lane, chainage, course, approved mix designation, documented thickness and lot definition. |
| Mix submission | Constituent sources, approved mix revision, required test certificates and any accepted changes. |
| Plant and traffic | Required equipment checks, road occupancy and traffic-control submissions/records under the contract. |
| Inspection and testing | Project-defined notice events, laboratory scope, methods/frequencies, acceptance sources and responsible roles. |
| Closeout | Lot diagram/register, survey and finish records, test results, NCRs and marked-up drawing/as-built obligations. |
Follow each lot from delivery through closeout
The source specification identifies discrete checks before production, at delivery and placement, and after each pavement course. Keep rows tied to specific course and lot so the resulting report can be reconciled.
| Stage | Plan / source mapping | Daily record and evidence |
|---|---|---|
| Readiness | Identify the required mix approval, plant/vehicle checks, work-area release and project notice. | Approved mix/version; plant check reference; road occupancy/traffic record; surface-preparation inspection. |
| Delivery | Define how each truck docket is tied to a time, production batch, material and lot. | Docket ID; date/time; truck identifier; load mass/quantity where recorded; mix designation; destination lot. |
| Placement | Set the documented limits for lift/course, paving sequence and joint plan from project sources. | Road/lane, chainage, lot map, course, start/end, construction joint, interruption or deviation. |
| Compaction and testing | Map each required sample/test to the contract method, lot, criterion and reviewer. | Sample ID; location/course/lot; test request/report; result as reported; review/disposition reference. |
| Surface and survey | Identify required level/thickness/shape/finish evidence and its source. | Survey certificate; inspection record; observations and measured values only when obtained against the cited criterion. |
| Lot closeout | Reconcile all expected records, open nonconformances and design changes. | Updated lot register and diagram; test references; NCR status; authorised closeout certificate/review as contract requires. |
Blank daily asphalt work record fields
Use project forms when specified. The following field groups support a separate, copyable blank daily record structure and do not imply that the checks or tests have occurred.
| Record area | Blank fields |
|---|---|
| Control | Project / contract: ___ Date / shift: ___ Road / lane: ___ Record ID / revision: ___ Contract specification and revision: ___ |
| Lot / course | Lot number and limits: ___ Chainage start/end: ___ Lane/side: ___ Course/lift: ___ Lot diagram revision: ___ |
| Mix and supply | Approved mix designation/revision: ___ Plant/source: ___ Delivery docket IDs: ___ Truck/load details as required: ___ |
| Readiness | Surface-preparation inspection: ___ Plant/traffic/occupancy record: ___ Notice or release reference: ___ Outstanding issue: ___ |
| Placement event | Paving start/finish: ___ Quantity: ___ Joint locations: ___ Weather/work observations if required: ___ Deviation/query: ___ |
| Testing | Sample IDs and locations: ___ Test method/source: ___ Laboratory/report ID: ___ Result transcribed with units: ___ Review/disposition: ___ |
| Finished course | Survey/level/thickness reference: ___ Surface/shape inspection: ___ Defect/NCR reference: ___ Repair/recheck: ___ |
| Closure | Expected vs received documents: ___ Design change/as-built link: ___ Open item owner/status: ___ Project review/closeout reference: ___ |
Use local source values only where adopted
C10 is a council worksection modified from AUS-SPEC 1144, and its printed copy warns that the website holds the current version. It has source-specific criteria, inspection events and annexures; those should not be copied into another road authority’s project by analogy. Locate the actual adopted edition, annexures and schedule before writing numerical criteria or point codes.
If a delivery docket identifies a mix but not the destination course or lot, preserve that missing link as an open traceability issue. Do not infer that the truck served the nearest lot or mark the lot closed based on a summary register alone.
Fictional workflow: reconcile an asphalt lot
Fictional example only. No actual material, value, test, result or acceptance is represented.
- Create a fictional lot for one lane segment and one course using the contract-defined boundaries.
- Map the approved mix revision and each delivery docket to the same lot and placement record.
- Link actual samples and laboratory reports to their locations and retain the report status without paraphrasing a result as acceptance.
- Add the course survey and surface inspection references when completed.
- Reconcile the lot diagram, test register, open NCRs and authorised closure evidence before submitting the package.
Before issuing the plan
- Tie every delivery docket and test to a course, location and contract-defined lot.
- Keep approved mix, actual deliveries, test reports and surface evidence as distinct sources.
- Use the project schedule and adopted clauses for acceptance, frequencies and control points.
- Do not transfer council or TMR criteria to another project without contractual adoption.
Sources and their limits
Public sources explain the planning topics below. Confirm their jurisdiction, contract context and applicable edition; use controlled project documents for the actual requirements.
- Wingecarribee Shire Council Engineering Construction Specification C10 Asphaltic (Roadways)
C10 worksection; clauses 1.2, 1.7–1.8, 2–4; Annexure Asphalt Work Record; Summary of Hold and Witness Points; Maximum Lot Sizes and Minimum Test Frequencies. The document identifies itself as a modified AUS-SPEC 1144 version and says the live website maintains the current version.
Local government construction specification demonstrates an actual asphalt work sequence, daily record, dockets, lot diagrams/register, testing and closeout. Source values and controls apply only if this project document is adopted.
Source reviewed: 2026-10-10
- NSW Government Quality Management Guidelines for Construction
Quality plan, ITP and project record relationships.
Official procurement guidance provides context for project-defined controls and record closeout; not an asphalt acceptance source.
Source reviewed: 2026-10-10