Build a dependency map

Start with milestones, not invented weeks: goal and scope, site information, required documents or reviews, documented selection, coordinated availability, work, and handover. For every milestone, write what unlocks it and who must confirm it.

A dependency may be a household decision, site access, product information, outside review, or an unanswered question. Identifying it prevents an apparent delay from being presented as failure without context.

  • Milestone or decision.
  • Missing fact, document, or review.
  • Person or entity that must answer.
  • Effect on later milestones.

Update the sequence when scope changes

A different selection can affect documents, availability, finishes, equipment, and handover. Ask the person proposing the change to identify which decisions need review; do not assume a desired date remains valid.

Separate a target date from a confirmed date. Record the source and condition for each, and communicate material changes to people who depend on them.

Table: Update the sequence when scope changes
MilestoneWhat unlocks itRecord
ScopeClear decisions and boundariesProposal version
ReviewRequested informationResponse received
SelectionDocumented model or finishData sheet or final list
HandoverResolved items and documentsHandover list

Use the schedule to ask better questions

Ask what depends on the owner, what depends on others, and which uncertainty remains. A responsible answer may not offer a date until enough information exists. Do not request a completion guarantee where reviews or supplies remain pending.

Keep one record

Maintain one shared list of decisions, sources, and changes. It does not guarantee availability, but it makes clear what still needs confirmation before progress.

Frequently asked questions

Is a date in a proposal a guarantee?

Not necessarily. Ask what dependencies, conditions, and supporting document it identifies.

What should I do if a selection changes?

Request review of the milestones and documents that selection may affect.