Ask it on the floor, close it on the record.
Every question and every approval runs on one record with the clock visible: who holds it, what came back, and which drawing revision it was answered against. Median close across the portfolio is 3.2 days on a 7.0-day contract clock.
What it does
An RFI starts where the problem is. The engineer standing on L9 raises it against the current sheet, drags in the 360 frame that shows the conflict, and names the ball-in-court. The record issues the number, the author, the date stamp and the due date; nothing is typed a second time in the trailer.
Submittals run the same track — register, packages, revisions, and the stamp that comes back. Replies are appended, never overwritten, so six months later the answer still carries the revision it was given against and the frame that raised it.
How it works
- 01
Raise it where it is
Open the RFI against the current sheet from the field app or the office. Level, drawing, revision and the frame that shows the problem attach themselves, and the record issues the number and the date stamp.
- 02
Route with the clock visible
Ball-in-court, distribution and the contractual due date go on at raise. Every day of the 7.0D clock is counted against whoever holds it, with a reminder at 48H remaining and an escalation at the date.
- 03
Close against the drawing
The answer lands on the record, not in an inbox. Closing writes the response, the revision it was answered against and the closing user into a version history nobody can quietly edit.
Spec
- MEDIAN CLOSE
- 3.2D
- CONTRACT CLOCK
- 7.0D · ESCALATED
- OPEN RFIS
- 38 ACROSS 41 TOWERS
- SUBMITTAL REGISTER
- 862 ITEMS
3.2D
Median RFI turnaround across the portfolio