Every promise, measured against delivery.
The Ledger records what we promised on every job — price, date and quality — against what we delivered. It steers routing, backs the guarantee, sets shop standing and feeds a monthly public index.
Every figure, defined before we measure it.
These are the numbers the Ledger publishes, and exactly what each one counts.
On-time-in-full rate
Delivered complete, on or before the date on the order when it was accepted.
Median quote-to-price time
Upload to a priced, dated catalog offer. Reported as a median, with the tail.
Jobs shipped
Customer orders delivered against a released packet. Internal test and calibration runs are reported separately.
Shops on the standard
Shops that have passed the qualification job and receive live routed work.
Capacity utilization
Share of declared network capacity used by routed work, and how much of it ran in batches.
What’s recorded on every job
- Quoted
- Price · promised date · estimated setup and runtime per operation
- Actual
- Accept timestamp · setup start and end · cut start and end · probe logs · inspection results · ship date
- Outcomes
- On-time (binary and days delta) · first-pass yield · nonconformances, cause-coded to packet, shop, material, or tooling · reroutes with reason
- Batch
- Batch membership, keys matched, and realized savings against the solo baseline
Every delivered job makes the next one better.
The Ledger is wired into four decisions. Each delivered job sharpens the next route, the next date and the next price.
Routing
Each job goes to the eligible shop best placed to hit its date — scored on qualification, open capacity, capability and standing.
The guarantee
Ship dates are built from delivered history: the runtime estimate, the shop’s record, and a buffer priced from real variance.
Shop standing
Every shop sees its own standing in full, including exactly how it sets routing priority.
A public index
Anonymized aggregates publish monthly as the Domestic Machining Lead Time Index: quoted against delivered lead times, by part class.
Every metric we keep on a shop, the shop can see.
Shops see the inputs, the weights and how routing priority follows from them. Falling standing starts a conversation.
See what routed work looks like- On-time-in-full
- Rolling 90 days. The headline, and the one the router weighs hardest.
- First-pass yield
- Parts accepted without rework or scrap, measured per packet revision as well as per shop, because both halves cause failures.
- Issue rate
- Issues raised per hundred jobs, cause-coded. A high issue rate against a young packet is usually our fault, and the coding says so.
- Responsiveness
- Accept latency and hold-resolution latency. How long a job waits on a human.
- Calendar honesty index
- Declared availability against actual acceptance and throughput. Measured, not moralized: chronic over-declaration simply lowers the router's trust weighting on that shop's calendar. Liquid capacity is only real if calendars are.
Six rules the record is kept under.
Written down before the first result, so every number can be checked against them.
On-time means the original date
A job is on time if it ships complete on or before the date that was on the order when the customer accepted it. Not a revised date, not a re-promised date, not a date adjusted after the fact because the first one was optimistic. A revised date is recorded as a miss against the first one, and both are kept.
The clock tolls for one published list, and nothing else
Customer print or spec changes after release, customer material late or out of certification, payment terms breached, source-inspection delays beyond the stated window, and narrowly defined force majeure. That list is published in full on the guarantee page. Anything not on it is our problem, and it counts against us.
Part class is defined before the data, not after
Index figures are grouped by part class — material family, envelope band, tolerance class, and operation count. The class definitions publish with the first issue and are versioned. Re-cutting the classes after seeing the results is the oldest trick in industry benchmarking, and versioning is how you can check we did not.
Aggregates only, above a published floor
No shop-identifiable data leaves the network without written consent. Index cells publish only above a minimum job count, so that no cell can be reverse-engineered to a single shop or a single customer. That minimum is published with the first issue rather than chosen per issue.
Nothing is excluded for being unflattering
Cancelled jobs, rerouted jobs, scrapped lots, and escapes are in the denominator. The one category we will separate rather than exclude is internal test and calibration work, because counting our own practice runs as delivered jobs would be a lie of arithmetic.
Corrections are published, not quietly patched
If a published figure turns out to be wrong, the correction runs in the next issue with the original left visible and struck. An index nobody can audit is a brochure.
Send us a part
Upload a CAD file. We engineer it once, and every run after — at any shop in the network — is the same part. Catalog parts are priced in minutes; custom work is quoted within two business days.
Run jobs, not quotes
We send American shops programmed, verified jobs. No quoting, no programming, no fees — and you’re paid on delivery.