RFIs
Outstanding on this project
QuestionRaisedStatus
Confirm lintel spec over new opening4 AugOpen 16 d
Drainage invert level at MH311 AugOpen 9 d
Finish to exposed soffit2 AugAnswered
Open on this project2
The problem is never raising the question. It is noticing three weeks later that nobody replied, by which time the delay has already happened and somebody is going to pay for it.
An RFI is worth exactly as much as the record of when it was asked and when it was answered. Those two dates are what turn a delay into an entitlement, or fail to.
QScope keeps the question, the answer and both dates on one record, and counts the days it has been open.
A list of open items on a report nobody opens is not a reminder. QScope puts the count on the sidebar of the project, next to the tab, so the number in front of you is the number outstanding.
Tasks work the same way: an owner, a due date and a status, counted in the same place.
No. If your main contractor runs RFIs through a dedicated site platform, keep using it. This exists so the commercial record of a question that affected time or cost sits beside the valuations, rather than in a system you lose access to at the end of the job.
Yes, with comment level access. Their entry is recorded against them in the audit trail, so the record of who asked and when survives.
Not automatically. An RFI that turns into an instruction becomes a variation, and you record it as one with its own valuation basis. Keeping them separate is deliberate: a question is not a change until somebody instructs it.
They stay on the record. Closed and open alike, with their dates, exportable with the rest of the project.
Not your whole portfolio. One live job, one certificate. If it does not save you time the first time you use it, walk away and take your data with you.