A gap is a question, never an assumption.
Projects stall on questions, not code. So every question is tracked, routed and timed.
Questions and decisions
From the work to the right person, and back.
Nothing is started until the questions it depends on are answered. The work that can move, moves.
Raised
An agent hits a gap, logs the question with what it blocks and when it's due, and takes the next Ready task.
Checked
The Chief of Staff checks the question and reads it back. A change of direction goes to the Build Foreman first.
Sent
The question is emailed to the Building Code Owner for that area. If they're away or it comes due, it goes to their backup.
Answered
They answer by a signed link. No account is needed.
Weighed
The impact is written on the decision card and the Live Board. If the answer changes a build spec, the Build Architect updates it and the Build Foreman and Chief Architect approve.
Released
The decision is logged, the waiting work wakes, and the people kept informed get a short brief.
Every question is timed twice.
- Wait
- Business hours from sent to answered.
- Delay
- Business hours the question alone held up the critical path.
- Decline
- A declined answer comes with a resolution: revise, hold or re-plan.
- Discuss more
- A conversation with the Chief of Staff. The card stays open until it's decided.
Decisions are the work. In-Haus makes them visible, timed and owned.
A scoping call is where Vet begins.