Use cases · RFI register

Every assumption written down, the right ones sent.

A structural drawing set never answers everything. detumble records each gap as a query - what was taken, why, and what closes it - and helps you choose which become formal RFIs, with the sheet references already attached.

Who it is for

The steps

  1. 01

    Read the set

    Missing dimensions, conflicting levels, unreadable schedules, undefined layers: the reading records each one with the sheet and the place on it.

    Ask in your own words, or type /ingest

  2. 02

    Draft the register

    Queries are grouped, ranked by sensitivity and tender leverage, and drafted in the wording a design house expects.

    Ask in your own words, or type /rfi

  3. 03

    Choose and send

    You decide which queries become formal RFIs. The register keeps the rest as recorded assumptions with the conservative reading applied.

    Ask in your own words, or type /rfi-strategy

What you get

  • Query register with evidence and the closing action for each
  • Formal RFI drafts, numbered and referenced
  • A sensitivity view: which answers move the quantities most

The proof

Conflicts kept as queries
every one
Reference on every query
sheet + place on it
Human decides what is sent
always

Every figure names its scope; none is a promise for every drawing set.

Questions

Do you send the RFIs?
No. The drafts are yours to send; the register records what went out and what came back.
Can I add my own queries?
Yes, in the project chat: the answer is grounded in the run's record and cites it.
How much does it cost?
The register is quoted before it runs, from the size of your drawings, on top of the reading; the pricing page shows credits per building size.