Project information · EPC and engineering firms

Rev D governs. Half the site built to C.

Revisions, RFIs, submittals, change orders and transmittals in one record. Your engineers still sign off.

Got a project bottleneck that costs you $1M or more, and you want it solved?

Which revision governs?

Today the answer comes from memory. It should come from the record.

  • RFI
  • Submittal
  • Change

Every decision keeps its owner.

Tap a stage.

Requirements

Rules
Every requirement gets one ID and one governing source.
AI
Extracts requirements from specs and contracts, with citations.
People
Interpret conflicting requirements.

Bids

Rules
Build the compliance matrix from the requirement record.
AI
Drafts compliance answers with citations, for review.
People
Decide bid or no-bid, risk and price.

Revisions

Rules
Register each revision and mark the one that governs.
AI
Compares revisions, highlights what changed and flags what it is unsure of.
People
Judge the engineering impact.

RFIs & submittals

Rules
Link every RFI and submittal to the revision it was asked against.
AI
Finds answers that relied on a superseded revision.
People
Give the technical answer; accept submittals.

Change

Rules
Open a change record when scope moves, before the work does.
AI
Spots scope changes in meeting minutes, emails and RFIs.
People
Decide the cost, schedule and scope impact.

Approvals

Rules
Record who approved what, on which version.
AI
Assembles the approval pack with its sources.
People
Approve.

Handover

Rules
Check the handover package against the governing record.
AI
Flags records that differ from what was built.
People
Accept the handover package.

Start with revision comparison on your hardest documents.

Uncertain differences go to an engineer, not into the record.

Five stages. You decide at every gate.

  1. Diagnose

    Map the process, owners, systems and today’s performance.

  2. Redesign

    Define the target process and who decides what: rules, AI or people.

  3. Prove

    Test one hard case, including what fails.

  4. Integrate

    Connect systems with monitoring, limits and rollback.

  5. Operate

    Train people, release by scope, review results against the baseline.

For corporates and large organizations

$1M+

We solve project bottlenecks worth $1M or more. Not for small businesses.

Drawings and client data stay inside agreed permissions, tested before production. Security & data

Questions buyers ask

Is this a search bot?

No. Search finds documents; the program connects them to decisions. Every requirement, revision, RFI, submittal and change order gets one governing record, a named decision-maker and the transmittal that sent it.

Do you replace our CDE?

No by default. We work around the systems you already use, such as your CDE or document management. Replacement only comes up if the evidence supports it.

Who signs off?

The authorized people, always. Rules route and check; AI retrieves, compares and flags uncertainty. It does not approve a design change, a submittal or a variation.

How do you handle confidential drawings?

Permissions and data boundaries are designed in diagnosis and tested in the pilot, before anything touches production. Details are agreed in writing per engagement.

Is the pilot the whole offer?

No. The pilot proves one hard stage, such as comparing superseded and governing revisions, inside a funded program. The program covers the whole flow, from requirements to the turnover package.

Program detail

How results are measured

Every program is measured against your own project baseline: time spent finding the governing revision, RFI cycle time, reopened RFIs, rework and claims exposure, set against cost over a horizon you choose. Andy de Wit leads the work; how the team is staffed is on the about page.

What fits

There is no price on this site. Scope and investment are set after the call, against the size of the problem, and agreed in a written statement of work. We take on bottlenecks worth $1M or more in cash, capacity or risk, with an executive owner on your side. That is a fit criterion, not a promised saving. A one-off tool is a weak fit.

Bring one project bottleneck.

30 minutes with our team.