Construction Submittals: A Log, Follow-Ups and Architect Replies That Stay in Step

A submittal log that has to agree with the drawings, the architect and the schedule

Every submittal on a project moves through the same questions. Does it reference the current drawing revision? Is the product data on file? What did the architect say? Is the trade's required-by date still comfortably ahead, or close enough that the row is escalated to the project manager? The answers become the row's disposition in the submittals log, and the disposition decides who chases what.

The log is a SharePoint list, the drawing set index and product data sit in the project's Box folder, the architect's review statuses are tracked in ClickUp, and the PM's follow-ups are ClickUp items too. A new drawing set or a batch of architect responses changes dozens of rows at once, and a follow-up left open on a row that is no longer escalated sends someone chasing a submittal that was settled last week.

Who works in the room

The project has one submittals room, and its default agent is Myco: ask about any row's disposition and Myco answers. Nova takes anything about a colleague's draft review. Ryan owns the ClickUp follow-ups and the architect threads, and drafts in Gmail as the person it is working for, with access checked on every call. After every re-run, Myco hands the rows that entered or left escalation to Ryan in the same thread, with the reason for each already written.

The weekly review, row by row

The Submittal and RFI Review Policy is in Drive, and its rule order and recording conventions are copied into the room guidelines. Each stage ends with the project manager or a project engineer.

When the drawings, the architect or the deadlines move

A new drawing set touches the mechanical sheets. Myco re-runs the mechanical rows only, because the electrical and finishes rows still reference current sheets and moving them would undo reviews nobody asked to redo. Then the architect's office sends a batch naming ten submittals: four now have product data on file and six come back revise and resubmit. Ryan drafts one reply on the product data thread listing the four cleared numbers and one on the batch thread listing the six rejected, and a project engineer sends both.

A deadline extension for one trade can take rows out of escalation. Each of those rows needs its ClickUp follow-up updated in the same change, or the PM keeps a reminder for a submittal that no longer needs one. Myco proposes the row changes, Ryan proposes the matching follow-up changes beside them, and the project manager approves the pair together.

What the checks catch

• A new drawing set applied to every trade, when only the named trade's rows should be re-run
• A row that left escalation while its ClickUp follow-up stayed open
• A draft review flag set on rows the draft never covered
• A second reply on an architect thread, or the cleared and rejected numbers posted on each other's thread
• A row cleared on the architect's approval while its product data is still missing from Box

What stays with people

• Approving every disposition and follow-up before SharePoint or ClickUp changes
• Sending each reply to the architect's office or a subcontractor, which Ryan prepares as a Gmail draft
• Deciding when an escalated submittal threatens the schedule enough to call the architect
• Signing the weekly close-out per trade

Integrations in this workflow

Kylon is not construction project management software and it does not replace it. It sits across the project team's existing tools and holds the coordination between them.

• Box
• ClickUp
• Gmail
• Google Drive
• SharePoint
• Slack

• SharePoint holds the submittals log, with disposition, follow-up window and draft flag on every row
• Box holds the drawing set index and the product data files
• ClickUp tracks the architect's review statuses, the PM's follow-ups and the close-out items
• Gmail carries replies on architect threads, each one sent by a project engineer
• Google Drive keeps the review policy, drawing set notices and draft log reviews
• Slack is where subcontractors and the field team outside the room ask about status

Where to start

A single project is enough to begin. Connect the SharePoint list that holds its submittals log and point the room at the Box folder with the drawing index. Then put one rule in the room guidelines: a row that leaves escalation updates its ClickUp follow-up in the same change, and the project manager approves both.

“Each re-run touches the trade it names, and the rest of the log stays where it was.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.