A calendar can show that seeding is booked for Friday while saying little about whether the ground will be ready. The missing information is often a dependency: a path is unfinished, a utility crew still needs access or nobody has confirmed water coverage. This Calgary Project Workbook turns those relationships into a sequence that can be reviewed. It does not prescribe one construction order for every property. The aim is to identify what must be confirmed before each area is released and who has authority to make that decision.
List work by location before choosing dates
Draw the project as separate areas rather than one whole-yard task. Identify where grading, underground work, hardscape, planting beds and seedbed preparation intersect. A front area may be ready while the back remains a construction route. Give each area a short identifier, then list the work that could disturb it before and after application.
Ask the builder or property lead which activities are genuinely finished and which are only scheduled. Record the source of each answer. A subcontractor's planned completion date is a useful input, but it does not prove that their work has been accepted or that another trade will not return. Include reinstatement after temporary access in the sequence rather than treating it as an unexpected extra.
Write dependencies as observable conditions
Replace “ready by Thursday” with a condition somebody can check: access crossing no longer required, approved bed boundary marked or watering arrangement demonstrated. Keep the expected date beside the condition so scheduling remains possible. This makes it easier to explain a hold without arguing about whether the calendar promise was sincere.
Calgary's City of Calgary — lot grading and positive drainage guidance matters where planting follows grade work. The sequence should identify the applicable confirmation before landscape changes proceed. Do not let the seeding booking become the reason to skip an unresolved drainage review. Similarly, a finished-looking soil surface does not establish that required underground work is complete.
Identify separate technical and commercial releases
An owner may authorize a visit while a designer still needs to review a grade interface. A contractor may confirm equipment access while the property manager has not released the loading court. Record those as separate decisions. One signature should not silently stand in for every role on the site.
| Dependency | Release evidence | Person to confirm |
|---|---|---|
| Underground work complete in the area | Current project status and required records | Responsible utility or construction lead |
| Grade interface resolved | Applicable reviewed information | Responsible designer or project representative |
| Access no longer crosses prepared ground | Accepted route and trade coordination | Site coordinator |
| Early care available | Named caretaker and working arrangement | Owner or maintenance lead |
Use the project's actual roles. The table is a coordination aid, not a delegation of professional authority. If a required reviewer is unavailable, hold the affected decision and identify the next step. Do not fill the missing role with the person who happens to attend the site meeting.
Keep temporary protection in the sequence
A delayed planting release may leave exposed ground that still needs management. Calgary's City of Calgary — erosion and sediment control plan reviews resources explain its construction-review context. Where those requirements apply, the responsible team must retain the appropriate controls and review. A delayed permanent treatment does not mean the interim site can be ignored.
State who checks temporary measures, who can change them and what event prompts another inspection. Do not prescribe a generic erosion-control product from a scheduling worksheet. If runoff, unstable ground or sediment movement presents a concern, obtain the competent assessment required for that site. The sequence should show the responsibility and hold point rather than pretending a later seeding date settles the issue.
Work through a split-release example
Imagine a project with 240 m² at the front and 180 m² at the rear. The front has a confirmed boundary and care arrangement. The rear still carries a route for patio deliveries. One option is to release the front first and hold the rear until the route is no longer required. That option must be reviewed for practical access, additional visits and maintenance implications before it is accepted.
The worksheet would show two histories: front release and application date, then rear readiness review and later release. If the patio work changes the rear soil or boundary, check it again rather than reusing the earlier observation. These illustrative areas do not recommend a phasing method; they show why one site-wide “complete” checkbox can conceal different conditions.
Review the sequence after meaningful changes
At each coordination update, ask what changed in access, soil condition, grade information, weather exposure and care capacity. Keep the earlier sequence so people can understand the reason for a revised date. Separate a requested change from an approved revision and notify the people relying on the old arrangement.
Close each release with a marked area, evidence, decision owner and date. After installation, transfer that area's care record immediately rather than waiting for the whole site to finish. Continue with utility information, grade hold points and watering handover.
Sources and further reading
- City of Calgary — lot grading and positive drainage
- City of Calgary — erosion and sediment control plan reviews
Read each source in its own product, jurisdiction and project context. Local requirements and the actual project documents govern the work.
Bring the chapter into your project
Keep the relevant measurements, documents, observations and unresolved questions together. Your enquiry brief remains editable before you choose to send it.
Prepare your project enquiry ↗