Workflow 03 · Revision tracking

Every change found,
carried through.

When a customer revises a drawing or BOM, we compare the revisions and bring every changed line forward for review.

Help shape this workflow Try the example ↓

Planned · shaped with our first partners

Illustrative scene: an engineer compares two drawing revisions side by side and marks a change — Every changed line, found

WE READTwo revisions inOld and new BOM exports
WE COMPAREChanges foundAdded, removed, changed lines
WE LINKCarried forwardTo the quote, the order and the job
YOUR ENGINEERYou approveTechnical changes decided by a person

01 / The life of a revision

One new file.
Many places it has to reach.

Select a step to see what has to happen, and where a change gets lost. Each step also shows what it costs you.

01Revision arrivesA new drawing or BOM from the customer.Often with no change list.02Find what changedSomeone compares two versions.By eye, line by line.03Carry into the quoteThe price has to follow the change.Quote and BOM can drift apart.04Tell purchasingOrders must match the new BOM.Wrong parts, early or late.05Tell the shop floorBuild documents follow the revision.Old drawings stay in circulation.06Close the loopEveryone works from one version.Proof that nothing was missed.

STEP 1 OF 6

Revision arrives

WHAT HAPPENS

The customer sends an updated drawing or BOM, sometimes by email, sometimes as a replacement file with the same name.

WHERE IT GOES WRONG

The email says “updated BOM attached”. It does not say what changed.

WHAT IT COSTS YOU

Version tangle. People work from different documents without knowing it.

STEP 2 OF 6

Find what changed

WHAT HAPPENS

An engineer or estimator lines up both versions and looks for added, removed and changed lines.

WHERE IT GOES WRONG

Small edits hide in long lists: a part number, a quantity, a rating.

WHAT IT COSTS YOU

Weekend of comparing. Senior people give up time for a task a machine can start.

STEP 3 OF 6

Carry into the quote

WHAT HAPPENS

Changed lines are repriced and the quote is updated or reissued.

WHERE IT GOES WRONG

A change is spotted in the BOM but never reaches the quote.

WHAT IT COSTS YOU

Missed line. It surfaces at purchasing, build or test, not at review.

STEP 4 OF 6

Tell purchasing

WHAT HAPPENS

Purchasing needs to know which lines to add, drop or change before anything is ordered.

WHERE IT GOES WRONG

The order is built from the previous version because nobody told purchasing.

WHAT IT COSTS YOU

Wrong order. Returns, restocking and a delayed build.

STEP 5 OF 6

Tell the shop floor

WHAT HAPPENS

Wiring lists, layouts and work instructions must reflect the new revision.

WHERE IT GOES WRONG

The shop builds to the old revision, and the error is found at test.

WHAT IT COSTS YOU

Rework. Labour, parts and schedule, spent twice.

STEP 6 OF 6

Close the loop

WHAT HAPPENS

Changes are confirmed, signed off and recorded against the revision.

WHERE IT GOES WRONG

There is no record of what changed, so the next dispute starts from memory.

WHAT IT COSTS YOU

Scope dispute. Margin on the job depends on a conversation that should not be needed.

02 / How it works

Compare once.
Carry it everywhere.

The comparison is the start. The value is in carrying each change forward.

Your data stays yours, under an NDA
You keep your own tools and files
A person approves every result

INTERACTIVE MOCK-UP · SAMPLE DATA

Revision review / Sample project P-104SAMPLE DATA

Two structured BOM exports are loaded and matched line by line.

REF	ITEM	REV A	REV B
TB-01	Terminal block	DEMO-TB-24 × 8	DEMO-TB-24 × 8
PS-01	Power supply	DEMO-PS-A × 1	DEMO-PS-B × 1
CB-01	Circuit breaker	DEMO-CB-01 × 1	DEMO-CB-01 × 1
RL-01	Relay	DEMO-RL-01 × 4	DEMO-RL-01 × 4

Two lines changed. Two lines are unchanged and stay out of the way.

REF	ITEM	WAS	NOW	CHANGE
TB-01	Terminal block	8	12	Quantity changed
PS-01	Power supply	DEMO-PS-A	DEMO-PS-B	Part changed
CB-01, RL-01	Unchanged	—	—	No change

Each change is linked to the quote line, the purchase line and the job it affects.

CHANGE	QUOTE LINE	PURCHASE LINE	JOB
TB-01, 8 to 12	Q-2041, line 7	PO-118, line 3	J-318
PS-01, part changed	Q-2041, line 4	PO-118, line 2	J-318

An illustration with made-up parts and prices. Your own version is set up around your files and rules.

Read both revisions
Two structured BOM exports are loaded and matched line by line.
List every change
Added, removed and changed lines are listed with the old and new values and a reference.
Link to what depends on it
Each change is linked to the quote line, the purchase line and the job it affects.
Your engineer approves
Technical changes are reviewed and approved by a person before anything moves on.

03 / How we work with you

A 4–6 week pilot on your own work.
A subscription only once it is proven.

We agree the scope and the definition of done, and sign the NDA together. We run the pilot on your own data and keep refining it until it meets that definition. Your annual subscription starts only after you sign off the result.

01START · AGREE THE SCOPE
Agreed up front, in writing.
We sign the NDA and agree the scope together: one workflow, the success measures and exactly what done looks like. Only then do any drawings or prices change hands.
02DURING · 4–6 WEEK PILOT
On your own data.
We run the pilot beside your live work, so nothing you rely on changes. A consistent BOM export, known revision pairs and your team’s expected change list.
03END · SIGN-OFF
Refined until it meets the bar.
A short report against the success measures you set. If it falls short, we refine and run it again until it meets the definition of done.
04AFTER · SUBSCRIPTION
Starts at sign-off.
One annual subscription per workflow covers running it, support and improvements. You already know it works on your own data, so this is not an experiment.

How you are protected. The pilot has a bounded scope and success measures agreed before it starts. Concerns about your data, or about how our two teams will work together, are tested against those measures. At the end you decide whether to go on, and the subscription starts only after you sign off.

Why work with us

Why panel shops
work with us.

Your data stays yours. The workflow gets better every year, for you and for everyone we work with.

Your data stays yours

Your drawings, prices and quotes are covered by the NDA and are never shared with other shops. Access, storage and deletion are agreed up front.

You get the best of every shop

What we learn about the work itself, the common gaps and the checks that catch them, goes back into the product. You benefit from it without anyone seeing your data.

It keeps getting better

We keep refining the format, the checks and the results throughout the year. Improvements to your workflow are included in your subscription.

You see it work first

The pilot runs on your own quotes against a definition of done you set. You subscribe once you have signed off the result.

We run it. You decide.

We set it up, run it and support it. Your team reviews and approves everything that reaches a customer.

Built by AI product engineers

AI product engineering is what we do every day, and that craft goes into your workflow: the design, the testing and the support.

04 / The checks behind every revision check

A comparison you can
trust at a glance.

The result is easy to read, easy to challenge and easy to trace.

Line matchingSame part, same place.

3 checks

Lines matched by part number and reference
Renumbered rows recognised as the same line
Unmatched lines listed, never dropped

Changed valuesWhat is different.

4 checks

Quantity differences shown old and new
Part number changes shown old and new
Description and rating changes shown old and new
Unit and pack-size differences listed

Added and removedWhat appeared or disappeared.

3 checks

New lines listed with their reference
Removed lines listed with their reference
Moved lines distinguished from deleted ones

Downstream effectWhere each change lands.

3 checks

Quote lines affected by each change
Purchase lines affected by each change
Jobs and panels affected by each change

Format and structureWhether the files can be trusted.

3 checks

Column mapping confirmed against your export
Blank or merged cells reported
Duplicate rows reported

RecordA trail for the next question.

3 checks

Revision pair and date saved
Decisions recorded per change
Export of the change list on request

Tap a card to see the checks.

What a flag looks like · sample

QTY CHANGED

Contactor line, quantity differs
Old revision shows 4. New revision shows 6. Linked to the quote and to the purchase list.

PART CHANGED

Relay, different part number
Part number differs between revisions. Suitability is an engineering decision.

LINE REMOVED

Terminal block, no longer listed
Present in the previous revision, absent in this one.

What we will not do · boundaries we keep, on purpose

×Validate the electrical design

×Decide whether a substitute part is suitable

×Release changes to purchasing or the shop floor

×Overwrite your BOM or your quote

×Hide a line we could not match

×Replace your engineer’s review

Scope, input, output and boundaries

Input

Two structured BOM exports

Output

Added, removed and changed lines with references

Your review

Your engineer approves technical changes

Pilot

A consistent BOM export, known revision pairs and your team’s expected change list.

What we measure

Change detection against the agreed reference set, false flags and time to complete review.

Boundary

Comparison is not electrical design validation. Part substitutions and suitability remain engineering decisions.

05 / Questions

What buyers ask
before they start.

How does BOM revision comparison work?

We take the old and new BOM and compare them line by line. The result is a clear list of added, removed and changed lines, so your engineer sees every change in one place instead of hunting for it.

Can it catch a changed quantity or part number between drawing revisions?

That is the core job. A changed quantity, part number or description is flagged against the earlier revision. The pilot measures how well it finds changes against a reference set you agree in advance.

What happens after a customer revises the job mid-build?

Every changed line is carried forward for review, so your team can see which quotes, purchase orders and build tasks it touches. Your engineer decides what to do with each change.

Which files do you compare?

We start from the BOM exports you already have, such as spreadsheets. Anything beyond that, such as comparing drawing PDFs, is agreed in the pilot scope. We sign an NDA before any files are shared.

How is revision tracking measured in a pilot?

The pilot measures change detection against the agreed reference set, false flags, and the time your engineer needs to complete the review. You agree the success measures before it starts.

Is BOM revision tracking available yet, and who signs off?

It is planned next and is being shaped with our first partners. Your engineer reviews and approves every change; nothing is acted on without a person’s sign-off.

Next step