Skip to content

Systems and records

Industrial repair estimate revision data: recording scope changes after teardown

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Record a repair scope change found at inspection as a new, dated revision of the original quote, linked to the coded finding and its as-found evidence, with the approver's role, the authority limit that applied, the channel and time of approval, and whether work began before it. Keep the original quote, keep declined and irregular cases, and close each job with its outcome and final test.

System export

Industrial repair estimate

This page covers industrial repair estimate revision data: recording scope changes after teardown.Illustrative

Key takeaways

  • Never overwrite the original quote; each scope change is a new revision linked to the finding that caused it.
  • Record the approver's authority basis as data, because an approval from the wrong role is a different case.
  • Phone approvals need the date, time, name, number and added work written down at the time, then confirmation.
  • An append-only event timeline keeps the order of finding, revision, approval and work, which snapshots lose.
  • Declined revisions, partial approvals and work started before approval belong in the dataset with their own codes.

How do you represent repair scope changes after an inspection?

Represent each scope change as a new, dated revision of the original quote, linked to the inspection finding that caused it, and record who approved it, under what authority, through which channel, at what time, and whether any work started before that approval. Never overwrite the original quote. The value of the record is the difference between what was quoted before teardown and what was agreed after it, and the evidence that the agreement was valid.

Industrial repair shops for motors, pumps, gearboxes, compressors and hydraulic components live with this pattern every week. Equipment arrives with a stated problem, a technician opens it, and the real condition differs from the request. The commercial decision that follows, revise the scope, get approval, then repair or return, is exactly the reasoning an AI system for quoting, triage or customer communication would need to learn, and it is usually scattered across a service order, an email thread and a phone note.

The specification below joins those pieces into one case packet per job. It works for a single shop and for a group of shops that want comparable records across locations.

Where the change starts: findings recorded at teardown

Every revision should point to a finding, and every finding should be recorded before the revised quote is written. That ordering is what makes the change explainable later.

Standard repair practice already separates the stages. EASA's guidance on maintaining motor efficiency during repair walks through preliminary inspection, dismantling, removal of the old winding, rewinding, reassembly and verification, and recommends recording winding data as found and testing the core before and after rewinding. Those as-found readings are the evidence for any change in scope; a revision that cites no as-found measurement or photo is an opinion.

Consumer auto repair law in California shows how formal the split can be. The Bureau of Automotive Repair's guidance requires a teardown estimate before a portion of a vehicle is disassembled for diagnosis, including the cost to reassemble it, and after teardown an itemized estimate for the needed repairs, with the customer's authorization required before the shop repairs or reassembles. Industrial work is usually governed by contract rather than that statute, but the two-estimate structure is the right data model: a diagnostic scope, a findings record, then a repair scope.

Who was allowed to say yes? Recording approval authority

Record the approver's authority as data: the person, their role, the limit they could approve, and the document that gave them that limit. A signature from someone without authority is a different case from a signature from someone with it, and models trained on the two mixed together learn the wrong lesson.

Federal contracting makes the distinction explicit and is a useful template for commercial customers. The FAR says contracting officers may bind the Government only to the extent of the authority delegated to them. Its Notification of Changes clause says the term contracting officer does not include the officer's representatives, and the FAR treats an agreement made by someone who lacked authority as an unauthorized commitment that only an official who has that authority can later ratify.

In commercial repair the equivalent facts are the purchase order and its line limits, a not-to-exceed amount, a blanket approval for minor findings, and the customer's own approval matrix. Capture them as fields at intake, before teardown, so that the revision step can be checked automatically against them instead of reconstructed months later.

What counts as proof that the customer approved the new scope?

Proof is a record made at the time, naming who approved what, when, by which channel and for exactly which added work. Anything less is a claim.

California's automotive repair statute gives a precise checklist for oral approvals. When consent to exceed an estimate is given by phone, the dealer must note on the work order the date, time, name of the person authorizing the additional repairs and the telephone number called, together with the additional parts and labor and the total additional cost, and confirm it on the invoice or by the customer's acknowledgment. Those fields transfer cleanly to industrial work, where the approval is often a call from a plant maintenance planner.

For contracts on commercial terms, the FAR's commercial products and services clause states that changes to the contract's terms and conditions may be made only by written agreement of the parties. Many private repair agreements carry similar language. When they do, a phone approval is evidence of intent but not the modification itself, and the packet should hold both and say which one governs.

The quote revision and authority tracking specification

Use one row per field below. Keys join the service order, inspection, revision and approval records; every timestamp carries a time zone; every free-text field also has a coded companion so cases can be counted.

The quote revision and authority tracking specification
FieldType and ruleTypical sourceWhy it matters
job_id and asset_idStable keys; asset by serial or tag, not descriptionService order in the shop ERPJoins all revisions and repeat visits for the same unit
quote_revisionInteger from 0; never edited after issue; supersedes link to prior revisionQuoting module or estimate filesPreserves the before and after scope
finding_id, finding_code, as_found_evidenceCoded defect, location on the unit, measurement or photo referenceInspection sheet, test reports, photosExplains why the scope changed
scope_deltaAdded, removed or changed line items with labor hours and parts by part numberRevised quote linesShows the change itself, not just the new total
approval_channelSigned form, PO change, email, portal, phoneEmail, CRM call log, PO systemDetermines what proof exists
approver_role and authority_basisRole code plus the PO line, limit or matrix that appliedCustomer PO, approval matrix on fileSeparates authorized from unauthorized approvals
approval_ts and request_tsTimestamps for request sent and approval receivedEmail headers, call log, portalMeasures customer response time and sequence
work_before_approvalBoolean plus the operation started and its timestampShop floor time entriesFlags work done at risk
outcomeRepaired as revised, repaired as original, returned unrepaired, scrapped, replacedShipping and invoice recordsConnects the decision to what actually happened
verificationFinal test results and warranty claim link if anyTest reports, warranty logShows whether the revised scope fixed the unit

One event per change: the revision timeline

Store the history as an append-only list of events, each with a timestamp, an actor role and a reference to the record it touched. Snapshots of the current quote lose the order of events, and the order is the point.

Steps

One event per change: the revision timeline

Defense maintenance contracts show the minimum content of a change request. The DFARS Over and Above Work clause requires a contractor's work request to state the type of discrepancy found, its specific location and the estimated labor hours and material to correct it, and the Government then verifies that the work is required, is not already covered by the basic contract line items, and is an appropriate corrective action before authorizing it. A commercial revision event can carry the same four elements.

  • quote_issued: revision 0 with diagnostic scope and any teardown or evaluation charge terms
  • finding_recorded: coded finding, location and as-found evidence reference
  • revision_issued: new revision number, scope delta and the findings it cites
  • approval_requested: channel, recipient role and the authority basis checked
  • approval_received or approval_declined: approver role, channel and timestamp
  • work_started: operation code and whether it preceded approval
  • authority_exception: approval outside the recorded limit, and its later ratification or rejection
  • outcome_recorded: repaired, returned unrepaired, scrapped or replaced, with final test reference

Worked example (illustrative): a pump sent in for a seal that needed a shaft

This example is illustrative; the shop, customer and figures are invented. A centrifugal process pump arrives at a regional repair shop for a mechanical seal replacement. Revision 0 covers disassembly, a seal kit and reassembly, estimated at 9 labor hours (illustrative). The customer's purchase order allows the plant maintenance planner to approve changes up to an agreed line limit; anything above goes to purchasing.

At teardown the technician records shaft scoring at the seal face and bearing wear, with runout measurements and four photos. Revision 1 adds a new shaft, both bearings and dynamic balancing, raising the estimate to 21 labor hours (illustrative) and pushing the job over the planner's limit. The shop emails the revision to the planner, who calls back the same afternoon and says to proceed.

The packet records two facts the totals alone would hide. The approval came by phone from a role whose limit the revision exceeded, so the event is an authority_exception. Shaft machining began the next morning, before purchasing issued the change to the purchase order two days later, so work_before_approval is true for that operation. The written PO change then ratifies the scope, and the outcome is repaired as revised with a passing vibration test. A model trained on this case learns that the decision was right but the sequence was risky, which is the lesson a quoting assistant should carry.

Declined revisions and approvals from the wrong person

Keep declined and irregular cases in the dataset with their own outcome codes; they are the cases that teach a model where the boundaries are.

A declined revision usually ends in one of three ways: the unit is reassembled unrepaired and returned, the customer approves only part of the revised scope, or the customer chooses replacement. Record which, along with any evaluation or teardown charge terms that applied and the time the unit sat waiting for a decision. Partial approvals need line-level approval flags, not a single yes or no.

Approvals from the wrong person need a stop rule. If the authority basis cannot be found in the packet, mark the case unverified rather than guessing, and exclude it from any training subset that teaches approval decisions. If the customer later ratified it, keep both events. When a pattern of approvals outside recorded limits appears, ask the commercial owner whether the limits on file are stale before treating every case as an exception.

Checking the packet against the shop's systems before release

Reconcile each packet with the job costing and invoicing records before anything leaves the shop. The final invoiced scope should match the last approved revision; a mismatch means a missing revision, an unrecorded approval or a billing adjustment, and each needs its own code.

Then reduce what is sensitive. Replace approver names and phone numbers with role codes and stable pseudonymous identifiers, keep the timestamps, and decide whether labor hours, part numbers and price lines can be shared or should be banded. Customer names and site locations rarely add training value and often carry confidentiality obligations in the service agreement.

Stop and ask for specialist review when contract terms for changes are unclear, when government contracts or regulated equipment are involved, or when packets cite safety-critical findings. This page describes data structure, not legal requirements for any particular shop.

Can a repair shop license its quote revision history?

Repair shops with years of service orders, inspection sheets and quote revisions hold a record of expert judgment that is hard to find elsewhere: what was found at teardown, what it changed and who agreed. A shop that wants that history used for AI can work with SourceX, which licenses business data directly from companies and covers qualification, rights review, contracting, data preparation, delivery and payment.

No service order or inspection photo leaves the shop until it has approved the scope and terms and signed the agreement. To see whether its revision history could qualify, a shop answers a brief company assessment, with no files uploaded at that stage.

Which move is right when a teardown finding changes the repair?

It depends on what the finding changes and who may decide, so a repair estimate revision dataset should label the move made when the new evidence arrived, not only the revised total. Six labels cover the conditional, partial and deferred answers shops give, and applying them in a fixed order lets two reviewers reach the same label from the same packet.

The order works as a revision validator. A finding that leaves the needed work unchanged stops at the first rule, however alarming the photo. A decision that is not the estimator's to make, such as a repair to explosion-protected equipment or a fault caused by the installation, is escalated before anyone checks the approval limit, because a purchase-order limit cannot settle it. EASA's guidance on bearing currents in drive-fed motors lists remedies such as filters or reactors between drive and motor (our paraphrase), which sit outside the motor on the bench. Only when the evidence sizes the added work does the authority on file choose between proceeding, offering options and holding.

  • NO_REVISION: the reading is inside the limit or does not affect the requested repair; record it as an observation and repair as quoted.
  • ESCALATE: route the decision to the customer's engineer, the equipment maker or a person qualified to repair hazardous-location equipment before quoting.
  • TEST_BEFORE_QUOTING: name the test that will size the added work and run it before any revised price.
  • PROCEED_WITHIN_LIMIT: a standing approval on file covers this work at this size; do it and send the revision as notice.
  • QUOTE_OPTIONS: acceptable remedies differ in cost, lead time or expected life; quote each and expect a partial or conditional approval.
  • REVISE_AND_HOLD: issue the revision and start no added work until it is approved.

Can an industrial maintenance record standard carry the revision?

It carries the evidence and the outcome, not the price or the revision chain. MIMOSA, which publishes the Common Conceptual Object Model (CCOM), describes it as an information model for exchanging engineering, asset, configuration, operation and condition data for plants and complex facilities (our paraphrase). We read the CCOM 4.1 draft schema and reference data copied into ccom-dotnet, a library in MIMOSA's GitHub organization, at commit 69e22c7 (7 March 2025; both files unchanged since 2022), expanding every inherited element of nine work and evidence types.

The evidence chain is explicit. A recommendation can cite the measurements, events and health assessments behind it; a request for work carries the recommendation; a work order collects requests and links follow-on orders to their parent; completed work records actual times, what was used and removed, and cause and effect events; and an asset's readiness list of 21 values separates serviceable with and without qualification. Approval is thinner: 3 of the 15 reference work statuses (Waiting for Approval, Approved / Accepted, Canceled / Rejected), each able to carry a time and an agent role, and one yes-or-no flag requesting automatic work-order generation. Across all 389 distinct element and attribute names in the schema, the only money word is a remaining-life estimate and every revision name, apart from the file's version attribute, belongs to a manufacturer's product model; no status marks a partial approval or a revised scope.

A revision case is therefore split between two record holders. The shop holds findings, quote revisions, approvals and final tests, but not how a unit it returned unrepaired later ran, why a customer declined, or whether a comeback went elsewhere; the owner holds condition evidence and field outcomes, but not the quote chain. A sector label such as industrial repair settles none of this: check which half the records hold, the rights to each, and whether hazardous-location work is in scope before calling a set suitable.

Method: names were split at capital letters and matched as whole words, ignoring case, against the money, approval and revision word lists in our script (cost, price, quote, estimate and currency among them). Any CCOM entity may carry custom properties, so a price could still travel that way; the count covers what the standard names. The table maps each link to where the rest usually lives.

Can an industrial maintenance record standard carry the revision?
Link a revision case needsWhat the CCOM 4.1 draft namesWhere the missing part usually lives
Finding to evidenceA recommendation cites measurements, events and health assessments (3 link elements)Shop inspection sheets, as-found readings and photos
Evidence to scopeA request for work carries the recommendation; a work order collects requests and stepsRevised quote lines in the shop's quoting system
Price and revision chainNo element for price, cost, quote or currency; revision elements only on manufacturer product modelsQuote revisions, emails and purchase-order changes
Approval3 of 15 work statuses, each able to carry a time and an agent role; 1 automatic-approval flag; none for partial approvalPurchase-order line limits and the customer's approval matrix
Follow-on workParent and child work orders linked by a hierarchyShop job numbers for return and warranty jobs on the same serial
OutcomeCompleted work with cause and effect events; asset readiness from 21 valuesFinal test reports and warranty returns on the same serial

How should a casebook grade the move, and when does the outcome arrive?

Grade the move against its label first and the outcome second, because they arrive at different times: the final test at shipment, the invoice's match to the last approved revision at billing, and the field outcome only when the warranty window on that serial closes, before which a job without a comeback is censored, not a success. EASA's AR100 recommended practice covers record keeping, tests and analysis for rotating machine repair, and EASA's accreditation checklist asks shops to document core tests before burnout and after winding removal (both paraphrased); those before-and-after records are the test outcome's raw material.

The seven cases below are invented, labeled by a script that applies the rule in order, and unreviewed: a motor or pump repair engineer should confirm each label before use, and explosion-protected rows need someone working to IEC 60079-19, the IEC standard for service facilities repairing equipment for explosive atmospheres. Score answers with these checks.

  • Label: matches the adjudicated one, or an alternate recorded before grading.
  • Grounds: cites the finding and its measurement or photo; a right label without evidence fails.
  • Authority: names the standing approval relied on, or says none exists, before any proceed answer.
  • Severity: work above authority, a skipped hazardous-location escalation or unsupported scope fails whatever the outcome, and a good outcome never rescues a wrong move.
How should a casebook grade the move, and when does the outcome arrive?
Teardown finding (invented)Authority on fileExpected labelHard negative it guards againstOutcome known at
Pump in for a seal; wear-ring clearance measured inside the maker's limitNone neededNO_REVISIONAdding wear rings because they look wornFinal run test; the next teardown of the same serial
Gearbox in for an oil leak; one spalled bearingBlanket purchase-order approval for bearings up to a set amountPROCEED_WITHIN_LIMITStopping the job to ask for an approval already givenFinal run test; invoice against the purchase-order line
Motor in for a rewind; core damage of unknown extentNo standing approvalTEST_BEFORE_QUOTINGQuoting core replacement from photosCore test results before and after the rewind
Motor fed by a variable frequency drive; bearing damage the shop reads as electricalBearings within the planner's limitESCALATEReplacing the bearings only, which passes the final test but leaves the cause in placeEnd of the warranty window on the same serial
Explosion-protected motor; damaged flamepath surface on an end bracketWithin the planner's limitESCALATEMachining it as ordinary repair because the limit allows itRepair documentation from the qualified facility at release
Pump shaft scored under the sleeve; a new shaft with a long lead time, or a sleeve repairNo standing approvalQUOTE_OPTIONSChoosing the faster remedy for the customerOption approved, final runout check, then the warranty window
Compressor valve job; cylinder liner scored; one remedyNo standing approvalREVISE_AND_HOLDStarting liner work before the approval arrivesApproval time against the first labor entry; final run test

Sources for this section

  • MIMOSA's ccom-dotnet repository at commit 69e22c7 (7 March 2025) holds copies of the CCOM 4.1 draft schema and reference data; in them a recommendation can cite substantiating measurements, events and health assessments, 3 of 15 reference work statuses concern approval, the readiness list has 21 values, and none of the 389 distinct element and attribute names in the whole schema is a price, cost, quote or currency word. Source
  • The CCOM 4.1.0-draft schema (copyright 2019 MIMOSA) defines a recommendation that can cite measurements, events and health assessments, a request for work that carries it, work orders linked to follow-on orders, completed work with cause and effect events, a work status that can carry a time and agent roles, and a single approval element that requests automatic work-order generation. Source
  • MIMOSA describes CCOM as an information model for exchanging asset lifecycle data, covering engineering, asset, configuration, operation and condition data for plants and complex facilities (paraphrase). Source
  • EASA's resource on shaft and bearing currents in motors powered by variable frequency drives lists remedies including insulated bearings, shaft grounding brushes and filters or reactors between the drive and the motor (paraphrase). Source
  • ANSI/EASA AR100-2025 describes record keeping, tests, analysis and general guidelines for the repair of induction, synchronous and direct current rotating electrical apparatus. Source
  • EASA's accreditation checklist (version 4.1, based on AR100-2020) asks that core testing before burnout or an equivalent process, and after winding removal, be documented (paraphrase). Source
  • IEC 60079-19:2025 covers the overhaul, repair and reclamation of equipment for explosive atmospheres and is aimed at service facilities (paraphrase of the publication summary). Source

Frequently asked questions

Should a revised repair quote replace the original estimate in the system?

No. Issue it as a new revision linked to the original and to the inspection findings that caused it. Overwriting the original erases the before-and-after scope, which is the most useful part of the record for analysis, disputes and AI training.

What should a scope change record include after teardown?

At minimum the finding with its location and as-found evidence, the added or removed line items with labor hours and parts, the approver's role and authority basis, the channel and timestamp of approval, whether work began before approval, and the final outcome and test result.

Is a phone approval enough to proceed with added repair work?

It depends on the contract and, for consumer auto repair in states such as California, on statute. Where phone consent is allowed, record the date, time, name, number called and the added work and cost, then confirm it in writing. Where the agreement requires written changes, the call shows intent but is not the modification itself.

How do you handle work that started before the customer approved it?

Flag the operation, its start time and the approval time, and keep the case. If the customer later approved or ratified the scope, record that event too. These cases show where the process is at risk and should not be cleaned out of the dataset.

Can repair estimate revision data be licensed for AI training?

It can be, when the shop has the rights to license it and sensitive details are removed or reduced. Customer names, contacts and confidential terms usually come out, while findings, scope deltas, timing and outcomes carry the value. Each dataset is reviewed for rights, privacy and fit before any agreement.

Sources

  • EASA's good practice guide sets out a repair process of preliminary inspection, dismantling, winding removal, rewinding, reassembly and verification, and recommends recording winding data as found and testing the core before and after rewinding. Source
  • California's Bureau of Automotive Repair requires a teardown estimate, including reassembly cost, before disassembly for diagnosis, and after teardown an itemized estimate and the customer's authorization before repair or reassembly. Source
  • California Business and Professions Code section 9884.9 requires a shop that receives oral consent to exceed an estimate to note the date, time, name of the person authorizing, telephone number called, and the additional parts, labor and total cost. Source
  • FAR 1.602-1 states that contracting officers may bind the Government only to the extent of the authority delegated to them. Source
  • FAR 1.602-3 defines an unauthorized commitment as an agreement not binding solely because the representative lacked authority, and ratification as approval by an official who has that authority. Source
  • FAR 52.243-7 excludes the contracting officer's representatives from the term contracting officer and defines a specifically authorized representative as a person designated by written notice. Source
  • FAR 52.212-4(c) provides that changes in the terms and conditions of the contract may be made only by written agreement of the parties. Source
  • DFARS 252.217-7028 requires work requests to state the type and location of the discrepancy and the estimated labor hours and material, and the Government verifies the work is required and not already covered before authorizing it. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies