Docs

Queries / RFI

Structured RFI workflow with AI-drafted questions and source-anchored responses traceable to documents.

Collaboration

← Back to all docs

Overview

The Queries / RFI module is your formal channel for unresolved questions — to a client, a vendor, or another discipline. Each RFI has a number, a subject, a status, an owner, a due date, and a thread of questions and answers.

The AI helps in two ways. First, it can draft an RFI from a comment thread or a document mark-up — turning informal observations into a properly worded query. Second, when an answer comes back, it can suggest the citation in your project documents that the answer should be filed against.

RFIs that close can spawn Tasks automatically when the answer requires action.

When to use it

  • Any question to a client or vendor that needs a paper trail.
  • Inter-discipline coordination where two teams disagree on a specification.
  • When a comment thread has gone on long enough that it needs formalising.

How it works

1. Raise an RFI

From scratch, from a comment, or from a section of a report you marked up. The AI proposes the wording; you edit and submit.

2. Route to a respondent

Set the recipient and a due date. They are notified and can respond in-app or by replying to the email — replies are captured back into the RFI.

3. Anchor the answer

When the answer arrives, link it to the affected document, register row or section. The link is what makes the RFI useful three months later.

4. Close

Closing an RFI optionally creates follow-up tasks and updates statuses on the linked artefact.

Tips

  • One question per RFI. Bundling kills traceability.
  • Always anchor the answer to the document it affects. An unanchored RFI is barely better than an email.
  • Use RFIs sparingly with internal teams; for true blockers only. Otherwise comments are lighter.

Want to see this in your project?

We'll walk you through Queries / RFI on a real engagement of yours — 30 minutes, no slideware.