Built Logic

See what AI can do

Site question to answered RFI and costed change

We take off your hands: answering site questions from the drawings, drafting and tracking RFIs, reporting late design information and logging changes.

You get: answers from the drawings and spec where they exist, draft RFIs for your project engineer to approve, and design changes assessed and logged.

Get a price for this

Or check first: Are we ready for AI?

The problem

Our site team raises RFIs for answers that are already in the drawings.

How the steps join up

It starts when: the site team has a technical question.

  1. Answer site team questions from the project's own drawings, specification and contract

  2. Check whether a technical question is already answered in the project documents before an RFI is raised

  3. Draft RFIs from site questions and track them to an answer

    Your team checks and decides at this step.

  4. Report late drawings and design information against the schedule

  5. Assess the knock-on effects of a design change on programme, cost, orders and other packages

  6. Capture site instructions and track potential variations

What you end up with: Questions already answered in the documents are answered at once, real RFIs are drafted and tracked, late design information is reported, and design changes are assessed and logged as changes.

Who signs it off: Your project engineer approves RFIs and your project manager approves the impact of any change.

What it needs to work

  • Current drawings and specification in one place

If those aren’t in place yet, you’ll hear that before anything gets built.

Who it’s for

  • Main contractors
  • Specialist subcontractors

What would this cost for your team?

Answer questions about your company and how this work runs today. You see an indicative estimate of the hours back, what that time is worth and the price when you send your details.

Get a price for this

Or check first: Are we ready for AI?