One board for the permit, the money and the build.
A rebuild after a loss has three tracks that depend on each other, and the City, the insurer, the architect, the engineers and the trades each hold a piece. ITelliBuilder puts all of it on one screen and answers the only questions that matter this week: what can we do now, who are we waiting on, and where is the money.
Every item knows what it is waiting for.
Nothing is a to-do list here. Each item carries who owns it, what blocks it and who is holding it up. The board works out the rest: what is free to start, what is falling behind, and which single thing is holding a chain of others.
Permit
The City's requirements, the engineers' letters, the surveys and the resubmissions. See the one thing the permit is waiting on, and how long it has been waiting.
Money
Approved by the insurer, invoiced, paid, left to claim, and over. Each invoice sits on the budget line it draws from, so a gap is visible before it is a problem.
Build
After the permit: what runs in parallel, and which inspections gate what. Planned weeks against the target so slipping shows up early, not at the end.
The contractor and the owner see the same facts, in different words.
The same data, never two versions of the truth. The contractor gets the full dependency machinery. The owner's side gets plain English on an iPad, with two actions and nothing to configure.
Dependencies, priorities, weeks
- Which items can start now, and the single blocker behind each chain.
- Who is waiting on whom, and for how many days.
- Planned start and duration against the programme, with "behind" worked out for you.
- Every change stamped with who made it and when. Notes are never rewritten, only added to.
Where we are, in plain words
- A journey strip: permit, shell, finishing, done.
- "Waiting on the City for 9 days", not a status code.
- What changed this week, and what happens next.
- Two actions: add a note, and mark something done.
It reads the project mailbox so nothing from the City or the insurer is missed.
On weekday working hours the board checks the project mailbox for mail from the parties it watches, works out which item a message is about, and records it on the board. It only picks up mail that is actually about the project, and it is deliberately limited in what it may change.
- It may add a note, mark something done, attach the message, or raise the priority.
- It may never change a date, a dependency, or lower a priority, and it can never delete.
- Anything it is not sure about becomes a flag: "read this one yourself".
- Every run is logged: what it read, what it changed, and what it skipped as unrelated.
Ask the board a question.
"Who are we waiting on longest?" "What did the District ask for in March?" "How much is left to claim on the drywall line?" The Ask panel answers from the board, the money and the project's documents, and says what it read. It can only read, never write.