This template belongs to the emergency work order prioritization guide. Use it after the service operations director has agreed that you may describe the company's dispatch history to SourceX in general terms.
When the brief is ready to write
Write the brief at the end of a conversation, not the start. Three conditions should hold:
- The service operations director, or someone of equal standing, has agreed to sponsor an internal discussion.
- You know the CEO, who can approve a licensing conversation, is willing to read it. The who can say yes decision tree explains the other roles.
- You can fill most fields from what the owners told you. If a field would require logging in to the dispatch platform, ask the owner and write down their answer instead.
A good brief can be forwarded inside the company without edits, and it lets SourceX decide whether a first call is worth everyone's time.
The blank emergency dispatch brief
Copy the table into a document and fill in the right-hand column. Keep each entry under twenty words: a description, a count, a range or a role.
| Field | What to write |
|---|---|
| Company | Full-time employees at peak, contractors excluded; trades covered; client types served |
| Business task | The dispatch decision in one line, such as upgrading a routine job that turns out to be safety critical |
| Priority levels | How many levels and their target times, described, not attached |
| Systems | Each system by category and start year: dispatch platform, service desk, scheduling board, technician app, response-time tracker |
| Years of history | Earliest usable year per system, and any break at a past migration |
| Volume | Rough work orders per year and the share whose priority moved up or down, with whose estimate it is |
| Change history | Whether priority changes are audited with user and time, and since when |
| Record owner | The role that runs or knows each system |
| Records event | Any dated change confirmed by the company: dispatch contract end, read-only date, retention setting |
| Open question | The one thing nobody could answer yet |
| Authorized contact | The CEO, who can approve a licensing discussion, plus the sponsor as working contact |
There is no field for record content. Partners never ask for or handle raw client records.
Notes on the harder fields
Priority levels. Describe the levels the company uses today and whether they changed. A platform may allow many more grades than the company uses; Dynamics 365 Field Service priorities, for example, carry a level of importance from 1 to 10 and a priority value from 1 to 100. Write what the company actually uses, not what the platform allows.
Change history. This is the field SourceX reads first. A current priority shows where a job ended; the change log shows the judgment. Change logging may have started years after go-live, or never, so "logged since 2021" and "never logged" are both honest answers. Ask the administrator, and write what they say.
Volume. An attributed estimate is fine ("about 4% of jobs, by the dispatch lead"). Never count records yourself.
Records event. Write only dated events the company confirmed in writing. If the dispatch contract ends next year, that is real urgency. If nothing is scheduled, say so; the preservation timeline explains what to inventory if a change is planned.
SLA coverage. If the company measures response times, note where. Work order SLAs in Dynamics 365 track arrival and resolution with warning and failure times; other platforms or spreadsheets do it differently. One line is enough.
Completed example: a supermarket maintenance contractor (Illustrative)
Fictional company, invented for this page; not a real case or a completed deal. A 510-person facilities maintenance contractor services supermarket chains across three regions. Store staff report problems through a portal and by phone.
| Field | Completed entry (Illustrative) |
|---|---|
| Company | 510 full-time at peak, contractors excluded; refrigeration, plumbing and building services; supermarket clients |
| Business task | Reclassifying jobs when new facts make a routine job safety critical, and downgrading false emergencies |
| Priority levels | Three levels; P1 means on site within four hours |
| Systems | Dispatch platform since 2019, service desk since 2016, technician app since 2019, response clocks in the dispatch platform |
| Years of history | About six years of work orders; service desk calls from 2016; earlier dispatch history in a retired system |
| Volume | Roughly 90,000 work orders a year, about 3% re-prioritized, by the dispatch lead's estimate |
| Change history | Priority changes audited with user and time since 2021 |
| Record owner | Service operations director for dispatch; service desk manager for calls; field operations manager for the app |
| Records event | Dispatch vendor contract ends on a date the company confirmed in writing |
| Open question | Whether the reason for a priority change was kept as a field, a note or not at all before 2021 |
| Authorized contact | CEO; service operations director as working contact |
Read it as SourceX would. The full chain exists from 2021, work orders go back further, audit coverage is named, and the records event is dated by the company. Nothing in the brief identifies a store, a technician or a caller.
What the brief cannot answer
The brief settles which records exist, where they sit, who owns them and who can authorize a licensing discussion. It does not settle whether they can be licensed: client contracts may limit site and incident information, and field staff identities need de-identification. What stays unknown until SourceX reviews it: SourceX's current data needs, the rights review result, preparation effort and any offer.
The company needs 50+ full-time employees at peak (contractors excluded), 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 90% 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, with one partner per company.
Send the brief under a short covering note modeled on the warm introduction brief, or draft one with the client opportunity brief generator. Consultants who scoped dispatch automation may already hold most of these answers from an AI use case prioritization exercise or an AI dispatching project.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
When the service operations director and the authorized contact have read and approved the completed brief, register as a partner, confirm the company on who qualifies and read the program terms before you send it.