Worked example & fields
Illustrative teaching extension of The Window Room. Pending review; not a client record, supplier quote, site survey, or construction-ready document.
| Phase | Output | Owner | Planned start | Planned finish | Depends on | Review milestone | Status |
|---|---|---|---|---|---|---|---|
| Discovery | Agreed brief and information requests | To appoint | Not entered | Not entered | Project information | Confirm objectives and constraints | Planning example |
| Concept | Selected material direction | To appoint | Not entered | Not entered | Brief review | Select Quiet Oak or revise direction | Planning example |
| Coordination | WR-01, WR-02, partial material schedule | To appoint | Not entered | Not entered | Concept selection and verified inputs | Review references and open issues | Planning example |
| Handoff | Indexed issue package | To appoint | Not entered | Not entered | Coordination review | Confirm recipients and outstanding actions | Planning example |
What each field records
- Phase
- Name a phase or work package.
- Output
- State what must exist at the end.
- Owner
- Assign a real person or role when agreed.
- Planned start
- Enter a project-specific date; example intentionally blank.
- Planned finish
- Allow time for review rather than assuming instant approval.
- Depends on
- Name the prerequisite output or decision.
- Review milestone
- Describe the decision that allows progress.
- Status
- Record an actual state, not a guessed completion percentage.
How to use this template
The worked example shows sequence, not a promised duration. Enter dates only after confirming scope, decision availability, and supplier information. Keep dependencies understandable rather than hiding them in an unsupported automatic scheduler. When a prerequisite changes, review affected dates with their owners and preserve the reason for the revision.
- List phase outputs before adding dates.
- Name dependencies and the people responsible for reviews.
- Revise future dates when a prerequisite changes and record the reason.
Respond to a missing decision, not just a late task
The workbook is a dependency planner, not an automatic scheduler. Write what must be available for the next review, then assign dates using your actual scope and participants. A supplied lead time should retain its source and confirmation date in your project records.
If a prerequisite moves, review dependent activities explicitly. Do not shift dates by an arbitrary standard duration or mark the dependency complete to make the plan look on time.
| Dependency | If unresolved | Record the response |
|---|---|---|
| Agreed brief | Concept studies may answer an unconfirmed problem. | Identify the missing decision and its owner before planning the next review. |
| Final F-01 model | Layout, quote, and delivery information may change. | Review affected activities; dates remain to agree in this example. |
| Coordination review | An issue package may contain mixed revisions. | Record outstanding items and whether they prevent the intended handoff. |
Review before use
- Do not copy durations from another project without checking scope.
- A planned review date is not approval.
- Do not let an outdated supplier lead time become an invisible schedule assumption.
Units, source information, and US use
The worked example keeps its original nominal metric dimensions. For a US project, choose and label a primary imperial or metric convention, distinguish item counts from areas, and document any display conversion and rounding. Never relabel metric values as imperial or treat conversion as site verification.
Make it your own
One workbook with Instructions, Blank Template, and Worked Example sheets. Twenty editable rows; duplicate or extend the template for your project.
Free download · No account · No information uploaded to OpenLintel
About this resource
Authored by OpenLintel with AI assistance. Examples are illustrative and have not received independent professional review. Adapt the structure to your practice and verify project-specific information. No legal agreement, regulatory compliance, or construction readiness is represented.
See the information connect
Follow the corresponding chapter of The Window Room: one illustrative brief, one selected direction, and coordinated sample references.
Explore the sample handoffDiscuss your studio’s workflow
If project dates hide unresolved design decisions, use a pilot discovery conversation to examine where those dependencies are lost.
Request a pilot discovery conversation