Guide
Freeze the Estimate and Book the Floor to It, and Every Job Explains Its Own Margin
The estimate records what you believed at quoting, and the job card records what happened. We keep both, so each difference lands with the person who can act on it.
4-minute read5 November 2026
In Brief
- When the report arrives weeks after dispatch with labour booked to the wrong job, estimator and production manager each explain the gap differently, and the next quote repeats the error.
- We see four actions: freeze the estimate as quoted, book hours at operation level on the day, give each cause of variance an owner, and show the cost while the job is still running.
- Thinqmesh sets up job costing on your own system beside the one you use now, and brings it live within four weeks.
In any plant that builds to order, the estimator and the production manager tend to hold a standing argument. The job was quoted at one number, it appears to have cost another, and each side places the fault with the other. The report that could settle it arrives weeks after dispatch, with labour booked to the wrong job. Our view is that the aim is to explain the gap by cause, so that each difference reaches the person who can act on it.
Two Records Answer Two Different Questions
An estimate records what the business believed when it set the price. A job card records what happened. Many systems let one overwrite the other: a routing is revised to suit the floor, and the standard moves to match. The variance report then looks tidy, and the original belief is lost.
We freeze the estimate as quoted against the job and add each approved change as a dated amendment. Differences then separate into material substitution, yield, setup, rework, outside processes and machine choice. Each has its own owner, so a variance meeting becomes a short list of causes and actions.
Four Actions That Let a Job Explain Its Own Margin
Each action makes the variance more specific, and each is useful in your current system, so the work holds its value while the ERP is built.
Freeze the Estimate Against the Job
A routing revised to suit the floor, or a bill of materials corrected after a substitution, should not overwrite what you believed at quoting.
We hold the estimate as quoted against the job. A customer's drawing revision or another approved change is added as a separate dated amendment with its own reason. The variance report then compares the floor with the original belief, and the business keeps the record of what it assumed.
Get started
- Pick one recent job and find its estimate as it was quoted.
- Check whether anything on that estimate has since been edited.
Book Hours to the Operation, on the Day
Coarser data captured the same day is worth more than fine data reconstructed on Friday.
We book hours to cutting, fabrication, welding, machining and finishing, and capture them at the machine or the bay with a tablet, a scanned job card or a supervisor's entry at the end of each shift. Where capture proves impractical, we change the method, because the design has failed and the operator has not.
Get started
- Look at last week's time sheets and mark which were filled in later.
- Agree the five operations hours will be booked to.
Give Each Cause of Variance an Owner
Yield is an estimating matter, repeated setup is a planning matter and rework is a quality matter.
Material substitution, nesting yield, setup, rework, outside processes and machine choice each separate in the record, and each has an owner. A single total of over or under budget hides all of this. With causes named, the variance meeting becomes a short list of actions.
Get started
- Take one over-budget job and list each cause of the difference.
- Write the name of the owner next to each cause.
Show the Cost While the Job Is Running
A margin problem found on a running job can still be addressed.
The system holds the quote and the cost so far, so a supervisor can ask what a job has cost against its estimate and which other open jobs are running over on labour. The answer arrives while there is time to change the plan for the rest of the job.
Get started
- Choose a job in progress and total its cost so far by hand.
- Note how long that took and who had to be asked.
How Thinqmesh Solves This
We begin on your floor with a quote and a job card, and the first module runs beside the systems you already use, so you can judge it on real work.
- Week 1
Your Real Jobs, in a Working System
We stand up the platform with data representative of your jobs, and walk the floor to find where cost moves without being recorded.
- Week 2
Estimates Frozen, Operations Set
Estimating, routing and approval rules are configured the way you work, and each cause of variance gets a named owner.
- Week 3
Your Job History Moved Across and Checked
We connect the systems you rely on and migrate your records. If your current system cannot export its data, we tell you first, and extraction gets its own date.
- Week 4
Job Costing Running on Live Work
Job costing goes live on your own system. Further modules are agreed one at a time, in writing, and they move faster because the foundation is in place.
You finish with job costing running on your own system, a quote and a cost behind every job, and a clear view of what comes next. The code and the data are yours.
