GC project delivery
RFI and submittal software for general contractors
One numbered log for the RFIs you ask and the ones you are asked, submittals dated backwards from when the material has to be on site, and a daily log a superintendent will actually fill in.
The joins are where the money is, and most products cannot make them
Every product in this category has an RFI log and a submittal register. Almost none of them can tell you that submittal 14 is late for the deck pour on the fourteenth, or that an RFI was answered against a sheet that has been revised since, because in those products the RFI log, the drawing register and the schedule are separate modules with no shared key.
What you get
What it does
One RFI log, both directions
A general contractor both asks and is asked. Ball-in-court is derived rather than maintained, and cost impact defaults to unknown rather than none: that null is the unbilled change order somebody eats.
Submittals as a procurement schedule
Required-on-site date minus lead time minus review days is the date it had to ship. That is the number that matters, and it is what the log is built around.
One daily log per day
Typed entries on one screen rather than fifteen separate logs, because it is filled in by somebody standing in the mud. Frozen on submit for everyone; only the office can reopen it.
Drawing register and spec book
A sheet register where a revision is a new row and the current set is derived, sorted in bound-set order so A-1010 files with the plans and not after the elevations.
Answers that went stale
An RFI answered, or a submittal approved, against a sheet that has been revised since. That is a wrong answer sitting in a file somebody is building from.
A lookahead, not a CPM engine
Frozen baselines, a rolling lookahead, and the join that justifies it: which late submittal threatens which task, on which date.
How it works
Start to finish
- 1
Open the project
A project spans many jobs. It never writes a job's status or money: the two answer different questions.
- 2
Run the logs
RFIs and submittals numbered per project, with numbering that cannot collide.
- 3
Let the field file the day
One log, typed entries, frozen when submitted.
- 4
Read the risk
What is late, what it is late for, and which answers went stale when a sheet was reissued.
What this deliberately is not
It is not a CPM scheduler. There is no critical-path calculation, no float propagation, no resource levelling and no Primavera import, and the migration that created the schedule tables says so in its header. What exists is a lookahead with frozen baselines and the joins to the other logs.
Read the restShow less
It is not a drawing viewer either. There is a sheet register and a spec book; there is no tile pipeline and no OCR of callouts. Those are rendering problems, and claiming them would be the easiest thing on this page to get caught overstating.
Per-project permissions can only restrict, never grant. A seat that could not reach a record before can never reach it after: the matrix narrows the access your organisation roles already gave, and an organisation administrator can never be locked out of their own project.
Common questions
- For the delivery layer a mid-sized GC is actually graded on (RFIs, submittals, daily logs, punch, meetings, drawings, documents and a lookahead) it covers the same ground, and it makes joins between those logs that the larger products do not. It is not a CPM scheduler and not a drawing viewer, and we would rather you knew that before a demo than after.
See it on your own jobs.
A 20-minute walkthrough, on your real pipeline. No slide deck, no pressure.