During construction administration, the design work is mostly done and a different kind of work takes over: responding. RFIs arrive from the contractor, submittals need review, and approvals have to be logged and communicated. Handled well, this is routine. Handled in email, it becomes a flood where things get buried, an RFI sits unanswered for a week, and no one can say for certain whether a submittal was approved as noted or rejected. Tracking RFIs, submittals, and approvals without drowning in email is one of the clearest wins a studio can get from a proper system.
The reason email fails at this is not that email is bad. It is that email has no concept of status, ownership, or a due date. A message about an RFI looks exactly like every other message, and once it scrolls off the screen it is effectively gone. This piece lays out a simple way to keep control.
Why RFIs and submittals need real tracking
An RFI is a question that can stall the site if it goes unanswered, so every one carries a clock. A submittal is a decision you owe the contractor, and the decision has consequences for schedule and cost. Both need three things email cannot give them: a clear owner who is responsible for the response, a visible status so you know where each one stands, and a due date so nothing quietly ages past the point where it causes a problem on site.
Give every item an owner and a status
The single change that fixes most of the chaos is treating each RFI and submittal as a tracked item rather than a message. The moment one comes in, it becomes something with an owner and a status, and it stays visible until it is closed. That way nothing depends on someone remembering to circle back, because the open items are all in one place, staring back at you.
- Open: received but not yet started
- In review: someone is actively working the response
- Waiting on consultant: needs a structural, MEP, or civil input to answer
- Responded: answer sent, awaiting confirmation if needed
- Closed: resolved and recorded
Keep the paper trail attached, not scattered
RFIs and submittals generate documents: the contractor's question and attachments, the reviewed shop drawing, your response, the marked-up PDF. When these live as email attachments, reconstructing the history of a single item later means digging through a mailbox and hoping you saved everything. Keeping the documents attached to the tracked item means the full history of every RFI and submittal is in one place, ready when a dispute or a question comes up months later.
The value of a tracking system shows up months later, when someone asks what was decided and you can answer in seconds instead of searching an inbox.
Approvals are decisions worth recording
Client and consultant approvals are the hinges a project turns on: a finish selected, a phase signed off, a submittal accepted as noted. In email, these decisions blur into ordinary conversation and get lost. Treating an approval as an explicit, recorded event, with who approved what and when, protects the studio. It means you are never in the position of assuming a client signed off on something they later say they never saw.
Make the status visible to the whole team
When RFIs and submittals live in one person's inbox, the rest of the team is blind to them. The project architect does not know a critical RFI is still open, the principal cannot see that submittals are backing up. Putting these items on a shared board or list, where anyone can see what is open and what is overdue, turns individual firefighting into something the studio manages together. Overdue items surface on their own instead of exploding at a site meeting.
Close the loop and communicate the outcome
Tracking an RFI is only half the job. The other half is making sure the answer gets back to the people who need it, and that the outcome is recorded against the project. A response that resolves an RFI but never reaches the field, or a submittal decision that no one logs, recreates the exact problem you were trying to avoid. Keep the resolution and the communication attached to the same item, so the record and the message are one thing rather than two.
Keeping it under control with Spreadbox
Spreadbox lets you run RFIs, submittals, and approvals as tracked tasks on a Kanban board rather than as buried email. Each item gets an owner, a visible status, and a due date, and you can attach the relevant PDFs and marked-up drawings directly to it so the full paper trail stays in one place. Team chat channels keep the discussion attached to the work instead of scattering it, and the shared board means the whole studio can see what is open and what is overdue. Spreadie, the built-in AI assistant, can draft a clear response or summarize a thread of back-and-forth into the answer you need to send, so closing the loop takes a moment instead of an afternoon of writing.