RFI & Change Orders
Capture every field question and tie every change to cost and schedule.
RFIs route to the right reviewer, responses are logged, and change orders link to the cost and schedule impact they cause.
- warn
RFI 042 — Beam clash at grid C4
Architect · open 2d · SLA 3d
- ok
RFI 041 — Conduit routing level 2
Electrical engineer · responded
- info
RFI 039 — Door hardware spec 3.B
Owner · responded · CO drafted
What it does
Field crews submit RFIs from a phone with photos and drawing references. Reviewers respond inside the project. Approved RFIs that drive change roll forward into a change order with the cost delta and schedule shift recorded.
- RFI capture from the field with photos and drawing markups
- Routing by reviewer with response-time tracking
- Change orders linked to RFIs, costs, and schedule impact
- Approval history preserved with timestamps and authors
- Searchable record for disputes, claims, and closeout
Built for the field
A foreman finds a conflict and submits an RFI in 90 seconds — drawing reference, photo, location, question. The architect sees it on their dashboard, not buried in inbox 47.
- Photo + drawing markup on the RFI itself
- Push notifications when a response lands
- Visible response-time SLAs so reviewers stay accountable
- Linked threads when an RFI begets a change
Key capabilities
Everything rfi & change orders needs to actually replace your current workflow.
RFI routing
Route by trade, reviewer, or project role with backup reviewers.
Response tracking
See how long each RFI has been open and who owes a response.
Cost impact
Attach a cost delta to a change order with approval workflow.
Schedule impact
Record days added or saved to the project schedule.
Approval chain
Owner, architect, GC, and sub approvals recorded with timestamps.
Audit trail
Immutable history makes claims and disputes far easier to defend.
How teams use it
A real workflow — from the field to closeout.
- Step 1 · Submit
Field captures the question
Foreman pins a location on the drawing, snaps a photo, and submits an RFI in under two minutes.
- Step 2 · Route
Architect responds
Reviewer gets a notification, opens the RFI, and posts the answer — SLA clock stops automatically.
- Step 3 · Change
Convert to change order
If the answer drives scope, PM converts to a change order with cost and schedule delta attached.
Why it matters
The business outcome — not the feature list.
RFI response time drops because reviewers see the queue and the SLA.
Every change has a who-decided-what trail tied to the originating RFI.
Cost and schedule impact get recorded as they happen, not reconstructed later.
Run rfi & change orders on LionCommand.
One operational command center for owners, PMs, supers, foremen, vendors, and field crews.