Organize Section 1 study as a phase map: for every project phase, list the documents generated, who issues them, who reviews them, and what approval each review grants. Work routing scenarios for changes, submittals, and delays until you can justify each party's authority from the contract structure itself, not from memorized slogans.
Build a Phase Map Instead of a Topic Checklist
Divide the material into four phases — design, procurement, construction, and closeout — and attach each management document to the phase where it lives. This turns a loose collection of terms into a sequence you can reason through under time pressure.
A phase map works because construction administration terms are only meaningful in context. An addendum belongs to procurement; a change order belongs to construction; a certificate of substantial completion belongs to closeout. When you organize by phase, an unfamiliar term can often be placed by asking what information was being exchanged at that moment in the project.
To build the map, take each document and record three fields: issuer, recipient, and decision it enables. For example, a request for information is issued by the contractor to the landscape architect, and it enables clarification of contract intent. Filling in those three fields for every document you encounter is itself a study activity, and the finished map is your primary review sheet.
- Design phase: owner-architect agreement, deliverable schedules, consultant coordination
- Procurement phase: instructions to bidders, bid forms, addenda, award of contract
- Construction phase: RFIs, submittals, change orders, payment applications, inspections
- Closeout phase: punch lists, substantial completion, warranties, final payment and certification
Contract Roles: Who Decides, Who Recommends, Who Performs
Track two separate agreements: owner to landscape architect, and owner to contractor. The landscape architect typically administers the construction contract as the owner's representative but is not usually a signatory to it.
This separation of contracts drives many Section 1 questions. The landscape architect reviews submittals, interprets the drawings, and recommends payment because the owner-architect agreement delegates those duties. The owner makes the money decisions — accepting changes, releasing retainage, and terminating — while the contractor performs the work and controls its own means and methods.
The practical implication is that most landscape architect actions during construction are reviews and recommendations, not unilateral approvals or promises. When a scenario asks what the landscape architect should do first, the defensible choice usually flows from documenting the condition and routing it to the party with contractual authority, rather than acting beyond the delegated role. Practice classifying each action as decide, recommend, perform, or review, and check that classification against the contract structure above.
Procurement Documents and Contract Documents Are Different Sets
Bid documents exist to produce a price; contract documents define the work. Instructions to bidders generally fall away after award, while drawings, specifications, and properly executed modifications define the built obligation.
Procurement covers the bidding period: invitation, instructions to bidders, bid forms, and the bidding requirements. An addendum issued during bidding revises those documents for all bidders and becomes part of the contract documents when award occurs. A document issued after award is a modification — a change order, construction change directive, or minor change — and follows a different approval path.
A useful self-check is to ask, for any paper on the project, whether a bidder needed it to price the job or a contractor needs it to build it. Bid Tabulation sheets, for instance, help the owner select a bidder but define nothing about the work. Drawing this boundary cleanly prevents the common confusion between revising a bid set before award and modifying a contract after it.
| Attribute | Bar (Gantt) chart | CPM network schedule |
|---|---|---|
| What it shows | Activity start and finish dates on a calendar | Activities plus logical dependencies |
| Critical path | Not directly identified | Longest dependent chain identifies critical activities |
| Float analysis | Not available | Early, late, and total float computable per activity |
| Typical use | Small jobs, owner communication | Larger contracts, delay and impact analysis |
Worked Scenario: Routing a Field Change Without Creating a Claim
A change order is a mutually agreed modification signed by owner and contractor; a construction change directive orders work when agreement is not yet reached. Choosing the wrong instrument confuses whether the change was negotiated.
Scenario: during plaza construction, the contractor uncovers an unrecorded utility that forces relocating a seat wall by eight feet. The contractor submits pricing and asks to proceed immediately. A tempting response is to tell the contractor verbally to move the wall and sort out cost later. That verbal direction blurs whether the owner ever agreed to the cost, inviting a claim.
The better decision is to document the condition, confirm the design intent, and recommend the appropriate modification instrument to the owner. If the owner and contractor agree on cost and time, a change order formalizes it; if the work must proceed before agreement, a construction change directive authorizes the work now with cost settled under the contract afterward. The distinction matters because the instrument chosen determines whether agreement is a precondition or a consequence of the work.
Worked Scenario: A Submittal Review That Exceeded Its Purpose
Submittal review confirms conformance with design intent; it does not approve construction means, methods, or dimensional field verification, which remain the contractor's responsibility. Stamp wording should match that limited purpose.
Scenario: the contractor submits a shop drawing for a custom railing, and the reviewer marks it fully approved, including the anchor layout the contractor sized. Later the anchors fail a pull test, and the contractor points to the approval. The mistake was stamping beyond the review's scope: the reviewer's duty is to check consistency with the contract documents, not to take over engineering the contractor was required to provide.
The better decision is to return the submittal with a review status that states no exceptions taken for conformance with design intent, while expressly noting that field dimensions, means, and methods are the contractor's. The same logic governs RFIs: the contractor asks what the contract documents require, and the response interprets the documents rather than directing construction. Keeping review authority and construction authority separate protects both parties' contractual positions.
Reading Schedules and Pricing Progress: Float, Delay, and Payment
Understand how a bar chart differs from a critical path network, what float represents, and how payment applications progress from schedule of values through retainage to final payment. These are the computational anchors of construction administration.
On a CPM schedule, an activity with zero float cannot slip without delaying completion, so a delay question usually reduces to whether the delayed activity sits on the critical path and who owns the float. A brief scenario: irrigation rough-in is delayed ten days but holds twenty days of float, while a concurrent lighting delay hits a zero-float activity. Completion impact follows the critical-path delay, not the largest number of days.
Payment follows a parallel logic. The contractor's schedule of values breaks the contract price into line items; each application for payment requests the value of work completed, retainage is withheld per the contract as security, and the landscape architect certifies the amount due before the owner pays. Closeout reverses the flow: substantial completion triggers beneficial use and reduced retainage, the punch list defines remaining work, and final payment and certification release the balance once warranties and closeout documents are in hand.
A Document-Flow Drill, Rubric, and Preparation Sequence
Drill by tracing documents end to end, score yourself against a rubric, then run a phased review: map, drill, scenarios, schedule math, and a final full-map check before your testing window.
Exercise: write each document type on a card. Shuffle, then for each card state the phase, issuer, recipient, review or approval granted, and the next document it triggers — for example, RFI leads to a supplemental drawing, which may lead to a change order, which modifies payment and schedule. Expected observation: the first pass is slow and you will hesitate most on modification instruments and closeout documents, which tells you where to re-study. Self-check rubric: score 2 points for correct issuer and recipient, 2 for correct phase and trigger, 1 for a clear one-sentence purpose. Reaching about 4 of 5 per card across the full set is a reasonable learning milestone before moving on — it measures study progress, not a predicted result.
An adaptable sequence: week one, build the phase map from your references; weeks two and three, drill document flow and memorize the modification instruments; week four, work routing scenarios for changes, submittals, and delays, writing your reasoning aloud; week five, practice schedule float reasoning and a payment-application walkthrough; week six, closeout and warranty paperwork; week seven, a timed full-map rebuild from a blank page; week eight, review weak cards and re-drill. Readiness checks: you can rebuild the phase map unaided, state the authority behind each party's actions from contract structure, and explain both scenarios in this guide without notes. For registration windows and administrative details, check CLARB directly at the link below.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.