RFI register

Register

Every question you have asked, who owes the answer, when you need it, and what came back — kept against the job.

Answered is not closed

The stage list has both, and the difference is the whole value of keeping the register. An answer that arrived and that nobody has acted on is still open work, and a log that marked it done the moment the email came back would hide the item most likely to cause a problem.

Numbers are yours

This tool generates no RFI number. Numbering on a construction job follows the contract or the project’s own convention, and a number invented here would be one nobody else on the job could look up. What it keeps stable is an internal id you never see, so two RFIs that happen to carry the same typed number are still two rows with two histories.

Where an RFI ends up

An answer that changes the work is a change order — priced, numbered and signed, which is a different document with different consequences. An answer that only decides something belongs in the project decision log, where the reasoning is kept while somebody still remembers it. The shop drawings that come back with it go in the submittal log.

A record of questions and answers. CompliMaint states no contractual response period, computes no entitlement to time or money, and makes no determination that a late answer is a delay event — those come from your contract and whoever administers it. Everything runs on your device.

Questions people ask

Does this number my RFIs for me?
No, deliberately. Construction numbering follows the contract and the project's own convention, and an RFI numbered by a website is an RFI nobody else on the job can find. You type the number — yours, or the one the contract requires — and the register keeps it. The identity of a row is a stable internal id, so two RFIs typed with the same number are still two rows.
Can it work out whether an answer is late?
It shows you what is past the date YOU entered, and stops there. Whether a late answer entitles anybody to time or money depends on the response period in your contract, on notice provisions, and on what actually happened on site — none of which this tool knows. It gives you the dated record that any of those arguments would have to be built from.
Is this tied to a job?
Yes, by the job's stable id. Two jobs never share rows, and renaming a job or a customer moves nothing. A job opens one of two ways: a customer accepts an estimate, or you open one here for work that already exists — a project that was running before you started using CompliMaint, or one sold on a contract that was never an estimate here. The second kind carries no contract amount, because nobody agreed one here. You do not have to invent an estimate to start a register.
What happens to an RFI once it is answered?
Move it to Answered when the response arrives, and Closed when you have acted on it. Those are two different states on purpose: an answered RFI that nobody has done anything with is still open work, and a register that closed them on receipt would hide exactly that.