Dispatch platform change: do work orders keep diagnosis revisions and repair verification?

Short answer

Often they do in the legacy system, and the migration plan decides whether they survive. A repeat visit usually leaves a first diagnosis, a callback, a revised diagnosis, parts used and a closing record showing the fix held. Field service integrators can ask the owner whether that sequence stays attached to the work order and the asset, or whether only final statuses move to the new dispatch platform. If the history survives and the company qualifies, the owner may choose an introduction to SourceX.

Visual briefFull-size diagram
A two-visit timeline for one repair: the first diagnosis, a callback, a revised diagnosis on the second visit and a verified fix, with a marker showing that a current-state migration keeps only the final status.
Illustrative repeat-visit history for one asset. The revisions in the middle are what a status-only migration drops.

Do work orders retain diagnosis revisions and successful repair verification?

Ask it in those words, then listen for where the chain breaks. Three answers are common: the history is intact and linked to the asset; the revisions exist only as free text or attachments; or the old platform overwrote the diagnosis field each visit, so only the last one remains.

What a complete repeat-visit record looks like, in one Illustrative example: a 180-person commercial HVAC service company, one rooftop unit, two visits.

DayEventRecord left behindLost if only final status migrates?
Day 1Customer reports no coolingWork order, problem code, asset IDNo, the work order header moves
Day 1Technician diagnoses a failed capacitor and replaces itFirst diagnosis, part used, labor timeOften, if the diagnosis field is overwritten
Day 4Customer calls back: unit trips againCallback flag or new work order linked to the firstOften, if links between work orders are not mapped
Day 5Second technician finds a refrigerant leakRevised diagnosis, notes, photosOften, if notes and attachments stay behind
Day 5Leak repaired, system recharged, readings loggedResolution and test readingsPartly, readings are rarely mapped
Day 35No further callback within the company's windowVerification by absence of a callbackYes, unless the history is queried later

Platforms model this differently, so treat the table as a set of questions rather than a description of any one product. One documented example: Microsoft's Dynamics 365 Field Service separates the work order type (the general category) from incident types (the specific request), and notes that incident types support reporting such as the number of power failures for an asset category. Administrators can map several resolutions to one incident type, and the system suggests them on work order incidents. Booking statuses are kept separate from the work order system status, which runs from Unscheduled through Completed to Posted, and a booking status can be set to send the work order back to an earlier stage for follow-up. Whether a given client's platform keeps each revision, rather than the latest value, is the thing to check.

Why it is worth asking: a diagnosis that was wrong, then corrected, then verified is a reasoning trail with a known outcome. Records like that are hard to find in public, and they are the kind of operational history SourceX asks about when it reviews a company for AI training and evaluation data. The field service histories page describes the record type in more depth, and how to assess resolution notes explains what makes notes useful.

Why is repeat-visit diagnostic history easy to overlook at a dispatch change?

Because the project is scoped around tomorrow's dispatch, not yesterday's diagnoses. Replacement work centers on scheduling, routing, mobile forms, technician adoption and integrations with billing. Migration teams typically load open work orders, customers, assets, agreements and price lists, then leave closed history in the old system or a flat export.

Three habits make the gap wider. Callbacks are often logged as new work orders with no link to the original job, so the repeat visit looks like an unrelated call once exported. Diagnosis fields on some legacy tools hold one value per work order, and a second technician's finding replaces the first. And the evidence that a fix held, a passed reading or the absence of a callback within the company's window, is rarely a field at all; it exists only if someone can still query the history later.

None of this is anyone's mistake. The record that shows how a diagnosis changed between visits is not needed to dispatch a technician on Monday, so it has no owner on the project plan. An integrator who raises it is often doing the company a favor regardless of what follows.

Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it. Four questions cover the kept question without touching a record:

  1. Revisions or last value? When a second visit changes the diagnosis, does the old platform keep both entries with dates, or overwrite the first?
  2. Linked or loose? Are callbacks and follow-ups linked to the original work order and asset, or created as unrelated orders?
  3. How is a fix verified? What does the company itself record as proof the repair held: a resolution code, a customer sign-off, a test reading, or no callback within a set window?
  4. How much, and whose? Roughly how many years of closed work orders exist, across which service lines, and do customer, OEM or warranty contracts limit how they can be reused?

Record the answers as yes, no or unknown, with ranges rather than exact counts. Do not request exports, screenshots or sample work orders; SourceX handles any review of records directly with the company. If telematics sits beside the dispatch tool, as on the Samsara export page, note it as a linked system and leave its value to the review. The field service work order field guide covers which kinds of companies tend to hold this history in the first place.

How do you disclose the reward and get the owner's permission?

Ask before you mention SourceX, and disclose your interest at the same time. For example: "Separately from the migration, that history may have value to the company. May I mention one option? I should tell you I am a referral partner and may receive a reward if it goes ahead."

If the owner agrees, explain that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company, and that your reward is funded separately and never reduces the company's payout. If the owner declines, the archive question is still on the record before cutover, which is good project practice.

Describe the reward exactly. The default is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, the amount SourceX actually pays the company, with no cap in total. Illustrative only: a $400,000 payout would mean a $70,000 reward. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) sets out.

Who owns service records, and who can authorize a licensing discussion?

The service company normally owns its work order history, but customer agreements, OEM warranty programs and service contracts can restrict reuse, which is for the company's counsel to judge. The person who can open a licensing discussion is usually the owner, CEO or COO, not the dispatch manager running the project.

What you can noteWho confirms itWhat stays unknown until SourceX reviews it
Record types and years of historyService operations or ITWhether the records fit current dataset demand
Whether contracts limit reuseThe company's counselThe rights review outcome
The authorized decision-makerOwner or executive teamAny offer, its terms and timing
Headcount at peakOwner or HRFinal eligibility confirmation

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact; who qualifies has the detail. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. IT and systems integrators can also read the IT consulting firm page, and the partner hub lists other roles.

Go deeper on dispatch platform change records

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When a client's repeat-visit history survives the dispatch change and the owner wants to explore it, register as a partner, check the company against who qualifies, and keep the program terms open while you prepare the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a technician's free-text note enough, or does the diagnosis need its own field?

Either can work. Structured incident or problem codes make revisions easy to count, but notes that describe what was suspected and what was found are often the richer record. What matters is that the first and the revised diagnosis both survive, with dates.

What counts as successful repair verification?

Whatever the company itself records as proof the fix held: a resolution code, a customer sign-off, a passed test reading, or the absence of a callback within a window the company defines. Ask which one they use rather than suggesting one.

Does telematics data from the vans count?

It can add context, such as arrival and on-site times, but on its own it says nothing about diagnosis. Mention it as a linked system in your notes and let SourceX's review decide whether it helps.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/dynamics365/field-service/work-order-r…
  3. learn.microsoft.com/en-us/dynamics365/field-service/incident-typ…
  4. learn.microsoft.com/en-us/dynamics365/field-service/work-order-s…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment