ModelsReads · Sends
Reads every new version of the model and compares it, element by element, with the one before. Sends issues back as BCF, pinned to the elements they affect.
watches the models, drawings, emails and meetings your project runs on, works out what each change means for mechanical, electrical and plumbing, and tells each team in plain words what changed and what it does to their work. Then it drafts the next iteration for review.
Design moves fast, and it should. The cost comes when a change slips past a team and the work gets done twice. Those hours either go on the client’s bill, which makes your price harder to win with, or the firm absorbs them. gets the change to the right people while it is still a small adjustment, and the time and energy that saves is capacity for the next project.
reads the tools your team already works in, and sends what it finds back through the ones they already check.
Reads every new version of the model and compares it, element by element, with the one before. Sends issues back as BCF, pinned to the elements they affect.
Picks up new sheets, markups and specifications from wherever the project is kept.
Finds the decisions that were only ever sent as a message, and emails each team what a change means for them.
Catches the quick question and the answer that settled it, and posts new issues to the channel your team watches.
Pulls what was agreed out of the transcript, so a decision made on a call is not lost.
Every issue arrives as a preliminary review for you to accept, reassign or dismiss. Nothing is issued in your name.
Each item points to the element, the version and the change behind it, so you can check it yourself in seconds.
Each change is logged with who was told and what they decided, dated, for the project file.