RFIs and tasks

An unanswered RFI is a claim in waiting

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.

Question, who it was raised with, and the date raised
Answer and the date it was given
A reply-by date on each RFI, marked OVERDUE once it passes

Start free for 30 days See the interactive demo

30 days free, no card.

RFIs

Outstanding on this project

QuestionRaisedStatus

Confirm lintel spec over new opening4 AugOpen

Drainage invert level at MH311 AugOpen

Finish to exposed soffit2 AugAnswered

Open on this project2

QScope keeps the question, the answer and both dates on one record, and counts the days it has been open.

The question, the answer, and the date of each

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.

Tasks

Counted where you will see it

A list of open items on a report nobody opens is not a reminder.

Open RFI and open task counts shown in the project sidebar
Tasks carry an owner and a due date
Closed items stay on the record rather than disappearing

Tasks

Open actions

TaskOwnerDue

Measure remeasured drainage runsAdrian22 Aug

Agree star rate for VO-04M. LewisToday

Chase making good certificateAdrian7 Sep

Open tasks3

Tasks work the same way: an owner, a due date and a status, counted in the same place.

Instructions

When the answer is an instruction

An RFI asks a question.

Architect’s instruction, CA instruction, CVI and site instruction
Instructions with a cost effect and no variation, shown in red
Verbal instructions awaiting written confirmation, shown in amber

Instructions

Unconfirmed

No variation

AI-014 · Revised lintel specVariation VO-06

AI-015 · Additional drainageNo variation raised

CVI-003 · Verbal, 8 AugAwaiting confirmation

With a cost effect16 of 21

An instruction that answers an RFI and changes the cost of the works needs a variation against it, or it will not reach the final account.

See it running before you sign up

RFIs and tasks

Send the RFI from the record

Email project sends the RFI with its question, deadline, status and answer to the people it is directed to.

The subject line carries the job reference, the RFI number and its subject.
Only the people the RFI is directed to receive it.
The card says how many people were emailed.

RFIs and tasks

Send the RFI from the record

In the program

Email projectemail

[<numer projektu>] RFI-001: <subject>email

Emailed N recipientsemail

On screen: “Email project”, “[<numer projektu>] RFI-001: <subject>”, “Emailed N recipients”.

RFIs and tasks

A Request for Information you can send

Print RFI produces a Request for Information on your letterhead with the question, the response, the dates and two signature boxes.

The print carries the RFI number, status, who raised it and the date a response is required by.
Question and response are printed in full, with signature boxes for both sides.
Print it or save it as a PDF straight from the browser.

RFIs and tasks

A Request for Information you can send

In the program

Print RFIdocument

Request for Informationdocument

Question / Information Requesteddocument

Responsedocument

Raised bydocument

On screen: “Print RFI”, “Request for Information”, “Question / Information Requested”, “Response”.

Every other function on the RFIs and tasks screen

11 functions the sections above do not cover, each as it works in the program.

Functions 1 to 6

01Choose who an RFI is for, everyone on the project or named people, and only they are emailed.

02Delete an RFI raised by mistake, with a confirmation first.

03A new task is shared with nobody until you choose, and you can open it to all guests, the client side or one subcontractor.

04Attach a photo to a task, and it follows the task's sharing.

05Delete a task, with a confirmation first.

06A task that became a variation carries a link straight to that variation.

Functions 7 to 11

07Tasks pinned on drawings sit in the same list, with location, dates, manpower, cost and a checklist.

08A guest who raises a task chooses whether only you, their own side or everyone on the project can see it.

09Set a reply-by date and an open RFI past that date is marked overdue in red.

10Email a task to the project with its status, priority, assignee, location, due date and cost.

11RFIs answered is one part of the project health score on the dashboard.

Who it is for

One change, four people it touches

You are applying

You price the change and defend it

You price the instruction, submit the variation and defend it when it comes back cut. Instructed work with no variation against it is money you have already spent.

Applying for payment

the same measurement

You are certifying

You value the change and answer for it

You value the variation from the other chair and account for what you cut. The register you keep is the one the final account will be argued from.

Certifying payment

You are doing both

You build the change, paid or not

You absorb the small changes as they come, and the ones nobody wrote down are the ones you end up building for free.

Doing both yourself

You are reporting

You fund the change, priced or blind

You check that scope changes are priced and approved before money moves, because an unpriced variation is risk the facility is carrying blind.

Recommending a drawdown

The client, the architect and the tenderer are not on this list. They are the people you let in on a link: they see the one document you sent them, answer it, and that answer is written into the record. No account, no licence, no charge, on every plan.

FAQs

The questions this page raises most often, answered without a sales pitch at the end.

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. Any guest can raise and answer RFIs, at every access level, and every guest sees all the RFIs on the project.

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.

From the blog

The part nobody teaches you, written down

Three pieces from the same corner of a contract as this page, answered at length and without a sales pitch at the end.

Engineer on a radio watching a crane over concrete frames under construction

Variations10/08/2026

How do you price extra work so the client actually pays for it?

Instruction first, then the valuation ladder your contract sets: contract rates, adjusted rates, a fair price or dayworks. Where each rung applies, and why the smallest variations are the ones that never get paid.

Read now

Worker in a hi-vis vest fitting a new window into a blockwork wall

Variations15/07/2026

Small extras keep eating the job. How do I stop doing them for free?

No single extra under two hundred pounds feels worth the awkward conversation, and thirty of them are a month’s wages. The three-sentence habit that captures small changes without souring the job, and the quote clause that makes the habit expected.

Read now

Hands pointing at drawings with a pen, white hard hat behind

Variations11/06/2026

Loss and expense is not the same as an extension of time

Time and money are separate entitlements with separate tests. Why an extension of time does not carry money with it, what has to be ascertained, and where these claims usually fail.

Read now

All 174 pieces

Keep reading

The three parts this page leans on

Variations Record the instruction, basis of valuation and clause, on JCT, NEC or FIDIC. Approved variations pull straight into a payment certificate. See how it works Programme A commercial view of the programme: works against the contract period, today marked, and any overrun past practical completion stated in weeks. See how it works Audit trail An immutable record of who changed which figure and when, across certificates, variations, retention and access. Exportable to CSV for RICS traceability. See how it works