Requirement checks

Compare survey reports, designs and material lists. Give engineers a clear list of discrepancies to review.

Custom development

Rules defined with your engineers and tested against known errors.

What goes in

Site survey reports, bills of quantities, kit rules and ordering units.

What comes out

A list of discrepancies with references to both sources, from missing kit parts to conflicting cable sizes.

Who decides

The engineer reviews each finding and makes the required changes in the source documents.

01 / My approach

Find the mismatch before the roof does.

2 min read

A site survey, design and bill of quantities describe the same job from different angles. Comparing them can expose gaps that a review of one document would miss.

01

Written once, checked late

A small document error can become a missing part at the warehouse or on the roof.

As information moves from survey to design to order, a check at each handoff can catch discrepancies before the next team inherits them.

The typical mistakes are small: a quantity that is too low, a kit with one clamp for two fixing points, a material ordered in packs when units were meant, the wrong cable cross-section. Each one costs more the later it is found.

Illustration

Four points where a bill of quantities error can be found: design, order, warehouse pickup and on the roof; the first three are places a check could run, and the cost of a fix grows at each step

Check the documents before ordering or pickup, while a correction is easier to make.
02

Two different mistakes

“It wasn’t ordered” and “it wasn’t in the bill of quantities” sound alike. They have different causes and different fixes.

If the item is in the bill of quantities but was not ordered, the problem is in purchasing. If it was never added to the bill of quantities, the problem is in the design. A useful check keeps the two apart, so the finding goes to the person who can fix it.

03

Compare the documents with each other

Read the records side by side to find omissions and conflicting details.

In one delivery I examined, a whole electrical subsystem appeared in the bill of quantities, the material list, the circuit lists and the photos, but not in the design. Each document looked fine on its own. Only the comparison showed the gap.

That comparison becomes a repeatable check, with each discrepancy linked to its source.

Illustrative example

Comparison of five documents for one site: the 380V supply appears in the bill of quantities, materials, circuit lists and photos, but not in the TSSR, and is flagged as conflicting for review

Each document looks complete on its own. Side by side, one row disagrees, and goes to a person with both sources attached.
04

Checks that fit your documents

Keep your existing workbooks and add a focused review report.

I define the rules with your engineers: matching materials to survey items, checking kit quantities and verifying ordering units. Each finding references the relevant entries on both sides.

The report can sit beside the workbook or feed a project list, linked by site code and purchase order.

Checks use document labels and structure so the mapping can be maintained as templates change.

05

Evidence for the reviewer

Each finding gives the engineer a specific question to resolve.

The reviewer confirms or dismisses the finding and updates the source documents. The checker leaves the workbooks intact.

Coverage depends on the available documents and agreed rules; engineering review remains part of the process.

02 / Get in touch

What needs to
work better?

Tell me which documents you compare and the errors you want to catch earlier. A few sentences are enough; you don’t need a finished specification.

I’ll reply personally with any questions and a practical next step. If a call would help, we’ll arrange one by email.

Or email me directly:

hello@lukasja.dev

I’ll use your details to respond to this enquiry.