MILLWRIGHTQC
← Back to Millwright QC
Last updated 12 August 2026
A technical description for anyone who has to satisfy themselves the records will hold up — QA managers, reliability engineers, and the person who signs the turnover package.
There are 42 record sections — equipment register, foundations and grout, anchor bolts, soft foot, shims, precision level, shaft alignment, thermal growth, couplings, runout, belt drives, bearings, clearances, teardown, balancing, lubrication, vibration, run-in, bolt torque, and the QA and compliance sections around them.
They are not 42 separate systems. Every section stores its rows in the same underlying structure: one table, keyed by which section the row belongs to, with the fields held as structured data alongside it. A soft foot reading and a bolt torque record are the same shape to the database and differ only in which fields they carry.
That is why the table, the add and edit form, the CSV export, the search and the job book all behave identically in every section — there is one implementation, not 42. It is also why adding a section is a configuration change rather than a schema migration, and why a section you do not use costs you nothing but an unused tab.
The practical consequence. Anything true of one section is true of all of them. If bolt torque records export to CSV, so do alignment records. If you can search equipment tags, you can search shim thicknesses. There is no section with a worse implementation because it was added later.
Every record hangs off an equipment tag. The tag is the join: it is what lets the alignment sheet, the vibration baseline, the bolt torque record and the grout report for P-1201A be pulled together into one story.
Records in the installation, alignment, mechanical and commissioning sections also carry a drawing reference, pointing at a row in the Drawings section. An alignment sheet that cannot say which general arrangement or foundation drawing it was worked from sends the reader off to find out, which is the cost this product exists to remove.
Two habits break this quietly, and neither produces an error:
P-1201A, P1201A and 1201-A are legible to a human and match nothing. On a job with two hundred records, that judgement has to be made two hundred times.It checks for gaps that would fail a turnover review, not for whether your numbers are good. It has no opinion on whether an alignment passed; it has an opinion on whether the record can be trusted:
It does not certify anything. It does not approve work, verify that a reading is correct, or reconcile counts. If the register shows four machines and there are three alignment records, the audit tells you a record is missing — it cannot tell you whether the fourth machine was aligned and unrecorded, or never aligned.
The audit reports coverage per section. A zero is not automatically a problem: plenty of jobs have no gearboxes, no belt drives, or no balancing. A zero means no records here, and only you know whether that is correct.
What matters is that a zero is visible and explicable. Nine machines with soft foot records and one without reads as a machine somebody had trouble with, whether or not that is true, and it is better to find that before the client does.
One click compiles every section into a cover-paged, indexed document on true letter pages. 39 of the 42 sections appear in it. Contracts and subcontracts do not, because commercial paper does not belong in a technical turnover package, and neither do crew timesheets — the crew's own hours are not the client's business.
The order is the order a reviewer reads in: register first, then calibration and qualifications, then the work in the sequence it was done, then QA, then the punch list. Sections with no records print as a section with no records rather than being silently dropped, so the reader can tell the difference between “nothing to report” and “nothing recorded”.
Point it at a scanned alignment printout, a calibration certificate or a vibration report and the fields fill in for you to check. You confirm every value before it saves.
It never judges whether a document passes. It reads what is on the page and puts it in the right boxes; whether the reading is acceptable is a question for a person with a specification in front of them.
Access is enforced by the database, not by the interface. Hiding a button changes nothing about what a request can retrieve, so every rule lives in row-level security policies that apply to every query regardless of where it came from.
Your records remain readable and exportable for a retention window after cancellation. The database refuses writes during that period, so nothing changes underneath you, but you can still open the job book, export CSVs and take a full snapshot.
That is deliberate: a turnover package can be needed years later for a warranty claim, and holding somebody's own quality records hostage is not a business model worth having.
One record model across 42 sections, joined by the equipment tag. An audit that checks whether records can be trusted rather than whether work was good. A job book that compiles 39 of those sections into something a client can accept. And a database that enforces who sees what, so the answer does not depend on which screen you are looking at.
How Millwright QC works — millwrightqc.com/how-it-works