Running Projects · Session 13
RFIs & Change Orders
RFIs — questions with a paper trail
New RFI: project, subject, the question itself, spec section and drawing reference, priority, and who holds the ball — defaulting to the architect. The detail page routes it: Forward to another reviewer re-points the RFI (architect to structural engineer, or back to the GC) without answering it; Record response answers it and puts the ball back in your court. The whole log exports to PDF for meetings.
Change orders — PCO first, dollars second
Log a maybe as a Potential change order the moment it appears — PCOs get their own numbering and touch no money rollups. When it's real, promote it to draft and it becomes a numbered CO carrying a cost delta and a schedule delta. From there: submitted → under review → approved or rejected, with void available at every step.
Change orders use the same External Review magic link as submittals — the owner or architect can approve or reject from their inbox, no login.
Try it yourself
- Raise an RFI with the architect on the ball, then forward it to an engineer.
- Log a PCO, promote it to a CO with a cost delta, and submit it.
- Send a change order for external approval and follow the link yourself.
Key takeaways
- RFIs route by chain of command — forwarding is a first-class action.
- PCOs track possibilities without touching contract value; promotion makes them real.
- External approval works the same no-login way on COs as on submittals.
Practice this in the live demo
A fully loaded sample company — every module open, no sign-up, nothing you can break.
Open the live demo