User guide/Phases & Schedule

Module 05

Phases & Schedule

The seven-phase model, how a phase completes and what gets filed when it does, the read-only phase archive, and the unified schedule.

5.1 · The model

The phase model

Seven phases. Statuses: upcoming, current, closed, skipped.

Pre-Design
Schematic Design
Design Development
Construction Documents
Bidding
Construction
Close-out
closed
current
upcoming

Settings › Phases: rename · merge stages into one custom phase (“Phase I”) · skip upcoming phases (restorable) · reorder · set start and target dates — the first date entered sets the baseline. Mid-stream projects pick a starting phase at creation.

5.2 · Dashboard

The dashboard

1
Phase rail card. Closed dots open the archive; the current phase carries “Complete phase”; the footer shows month X of Y and the budget change recorded at last close.
2
Hero card. Current phase and target, the next critical-path deadline in gold, and a stat stack that switches to construction-administration counts once construction begins.
3
Permit slot during CD and Bidding.

The menu is deliberately stable — Bidding, CA, Financials, and Closeout exist from day one.

5.3 · Completing

Completing a phase

The only way phases advance. The modal files a record of every working document as it stands — “can’t be undone.” Advancing into Bidding asks once which issuance defines the complete set — recorded once, deferrable to the Bid Set. The estimate and files snapshot at close; drawings are assembled as they stood on the close date, from revision history.

Note

Admins can reopen only the latest closed phase — the record is kept, marked superseded.

5.4 · Archive

The phase archive

Click a closed dot for the read-only record: “as it stood on the day it was completed. Nothing here can change.” Sections appear only with content: documents at close, issuances during the phase, decisions, schedule at close (with chips showing days over the original dates), open at advancement (“record, not blame”), studies (Kept / Set aside), QA/QC.

“Download phase record” compiles the set as of the close date.

5.5 · Planning

The schedule

The Planning tab has five subtabs: Schedule, Tasks, Questions, Notes and QA/QC. Each is its own address, so a link to the Questions register lands on the Questions register.

Notes is where things get written down. Three tiers of one thing: Mine is your private scratchpad (not part of the record); Lists are loose team batches — a site walk, a brain dump; Meetings are dated entries in a series (OAC, design team). A meeting carries the series’ open items forward with their numbers, takes a status note on each, and is issued to seal it. A list can become a meeting without retyping. Type a line and press Enter: a plain line is a takeaway, ? makes a question, [] a task, @name sets the court, #S the discipline. Items born in Notes live in Tasks and Questions too — one row, two doors.

The schedule has three views — List / Timeline / Calendar (LODE remembers your choice) — zooming from a week to a year. Three layers share one horizon:

1
Phase bands with deadline diamonds. An undated phase shows an amber pill: “Set this phase’s start and end dates.”
2
Deliverable Gantt bars, colored by discipline.
3
Tasks and questions as pins in a shared lane. The pins are the working layer’s projection onto the schedule; the Tasks and Questions subtabs are its home — a register each, sortable by column, with ball-in-court and due-date filters and a stamp bar for the whole selection.
On trackAt riskOverdueComplete

Ball-in-court shows on rows; critical-path completions route through a confirmation checkpoint. A QA/QC layer sits alongside. Contractor schedule import takes a spreadsheet or PDF — the full schedule remains the contractor’s PDF. Split projects: each delivery package gets its own phase rail plus a Phase › Package filter.

← Module 04 · Sketch PaperModule 06 · Bidding →