Skip to content

Communication & documents

Work stops when a question goes unanswered. Someone on site hits an ambiguity, a client asks whether a fixture can move, a decision made in a meeting needs to be confirmed before material is ordered.

This area is how those exchanges become tracked records with a named owner and a date, instead of a text message someone remembers differently.

An issue is a tracked question or problem on a project. It’s raised, routed to whoever can answer it, answered, and kept on the project’s permanent log.

Issues are typed by what they concern — design, construction, quality, project controls, or a client request — so the log stays readable as it grows and the right person picks up the right question.

An issue carries a response path back to the client. That’s a deliberate widening of an older idea. A request for information, or RFI, was a formal question from the contractor to the architect or owner: one direction, one kind of question. An issue covers that and also the requests that come the other way, from the client to the team. One channel, both directions, one log.

Threaded notes attach to a project or to any record within it — a contract, a quote, an issue. A note sits with the thing it’s about, so the discussion and the decision live in the same place.

Documents attach to the record they belong to rather than to a separate document system. A drawing set attaches to the project, a signed contract to the contract, a photo to the issue it illustrates. There’s no parallel filing structure to keep in sync, and nothing to go searching for in a second place.

Every document carries a flag for whether the client can see it. That flag is set deliberately, one document at a time.

Project updates are posted to the project as the work progresses — a written summary of where things stand, kept with everything else rather than sent out and lost in an inbox.

You see the issues raised on your project and the answers to them, including the ones you raised yourself. You see project updates as they’re posted.

And you see the documents that were marked client-visible. That flag is why the document list you see is a deliberate set rather than everything the team has accumulated — plans, contracts, and selections are shared with you on purpose.