This agenda is part of the dispatch platform change guide for field service integrators. The archive context checklist follows up on the answers before the old platform is retired, and the annotated introduction email is what you send if the meeting ends in a yes.
Who sits at the table
Keep it to four or five people, and choose them for what they know about past jobs, not the new rollout.
| Seat | What they know | Blocks |
|---|---|---|
| Owner, CEO or COO | Who owns the service history and whether to discuss licensing | 5 |
| Service operations manager | How diagnoses, callbacks and resolutions are actually recorded | 2, 3, 4 |
| Admin of the old dispatch platform | Field behavior, years of closed work orders, attachments | 1, 2, 3 |
| Integrator lead (usually you) | What the migration will import and what stays behind | 1 |
| Warranty or contracts lead, if there is one | OEM and customer terms that limit reuse | 5 |
The invite needs one sentence of purpose: "Thirty minutes on the closed work order history before the old platform is retired. Descriptions only, nothing pulled." Leave the new platform vendor off the list; their job is the future, and this meeting is about the past.
Agenda sheet: minute by minute
Illustrative. An integrator is moving a fictional 210-person fire protection and sprinkler service company to a new dispatch platform. Its old system holds closed work orders from 2012.
| Minutes | Block | Question to ask | Who answers |
|---|---|---|---|
| 0-4 | Migration scope | Which work orders move: open only, or closed history too, and with notes and attachments? | Integrator lead and admin |
| 4-11 | Diagnosis revisions | Do work orders retain diagnosis revisions and successful repair verification? | Service operations and admin |
| 11-17 | Callbacks and links | When a customer calls back, is the new job linked to the first one and to the asset? | Service operations |
| 17-23 | Proof the fix held | What does the company record as evidence the repair worked? | Service operations |
| 23-30 | Owner and decision | Who owns this history, do contracts limit reuse, and would the company like to hear how licensing works? | Owner and contracts lead |
Ask the admin to keep time. Take notes in four columns: block, answer, who said it, open item with a name.
What a usable answer sounds like
Minutes 0-4: migration scope
Usable: "Open work orders, assets, customers and agreements move. Closed jobs stay in the old system, read-only, until the contract ends." That tells you the history exists and has a lifespan. If the reply is "we'll export everything to a spreadsheet", ask whether notes and attachments go into it; a flat export may keep the header and drop the rest.
Minutes 4-11: diagnosis revisions
Usable, in the sprinkler company's terms: "The tech who found the corroded dry-pipe valve logged it on the first job, and the tech who later traced the real fault to a failing air compressor added a second, dated finding. Both are still there." Weak: "The deficiency field says what was wrong." A single field usually means the last entry wins and the first technician's reading is gone. Product design varies: Microsoft's Field Service documentation, for one, keeps a broad job category apart from the specific incident and lets an admin attach several possible resolutions to that incident. You are not auditing the tool's features, only asking whether the old system kept the first finding once a second one arrived.
Minutes 11-17: callbacks and links
Usable: "A return trip for a dropped alarm panel or a repeat low-air signal is opened from the original job, so it carries the parent number and the building's system ID." Weak: "Dispatch books a new call." Without that parent number, the second trip reads as a fresh service call once it is exported. Ask one follow-up: can a technician reopen the original job instead of starting a new one? Some tools allow it; Microsoft documents a setup in which a booking outcome sends the job back an earlier step for follow-up, with booking status tracked apart from the job's own status. Note which approach the client used, and since when.
Minutes 17-23: proof the fix held
Usable: "After a valve or compressor repair the tech runs a trip test, records the trip time and air pressure on the job, and the next quarterly inspection confirms it." Fire protection companies may have a natural verification point in the scheduled inspection that follows a repair, so ask whether that inspection is linked back to the repair job or stored as a separate visit. Let the company describe its own proof: a logged test, a customer signature, a passed inspection, or simply no return trip within a window it names.
Minutes 23-30: owner and decision
Before the decision, say three things. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. You are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX pays it separately and it never reduces the company's payout. The dispatch project carries on the same whatever the answer.
Answers that end the meeting before minute 30
| What you hear | What it means | Note to record |
|---|---|---|
| "The old system was shut down last year and nothing was kept." | No history remains to describe | Closed |
| "Most of our work is subcontracted, and the subs keep their own records." | The company may not hold or own the diagnoses | Note the arrangement; stop |
| "Our OEM warranty program owns all service data." | Rights likely sit with a third party | Record for counsel; stop |
| "We have about 40 people." | Below the 50 full-time baseline | Closed |
| "We'd rather not." | The owner has declined | Closed; the migration is unaffected |
What the meeting decides
End with one outcome, a name beside it, and a date drawn from the company's own retirement plan where there is one.
| Outcome | Fits when | Next |
|---|---|---|
| Introduce now | Revisions and verification are recorded for several years, the owner is clear and opts in | Send the annotated introduction email |
| Revisit by a date | The archive plan or the old contract's end is still open | Follow up before the documented read-only end |
| Stop | The owner declines, or rights or size rule it out | Record why and close |
For "introduce now", check fit: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. 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. Unknown until SourceX reviews it: whether repeat-visit histories fit current dataset needs, the rights review on OEM and customer terms, de-identification and any offer.
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, with one partner per company. Illustrative only: a $400,000 Actual Supplier Payout would mean a $70,000 default reward; the rewards page has every payment condition.
The field service histories data type describes the record in depth, the HVAC roll-up page shows where such companies cluster, assessing dispatch workflows in transportation covers a neighboring sector, and the portfolio review agenda uses a similar timed format for investors.
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 the meeting closes on "introduce now", register as a partner, confirm the company on who qualifies and read the program terms before the old platform goes read-only.