This page belongs to the emergency work order prioritization guide. It answers one question for dispatch software consultants: inside a field service company, who can say yes to a conversation about its emergency dispatch history?
Why the person who knows the records is rarely the one who signs
Emergency dispatch records are spread across people as well as systems. The dispatcher who raised a job to P1, the service desk agent who took the escalation call, the technician who made the site safe and the administrator who configured priority codes all touched the records. None of them owns the company's rights in them.
Ownership sits with whoever controls the company's contracts: the dispatch platform agreement, the maintenance contracts with clients and any confidentiality terms around safety incidents. In a company of 50 to a few thousand people, that is the CEO, or the owner in an owner-run company, advised by general counsel or a contracts lead. The service operations director sits between the two groups, which is why the tree starts with them.
The decision tree, question by question
Ask these in order. Each answer either moves you down the tree or tells you to stop.
- Who runs the priority scheme? If your contact is a dispatcher, scheduler or administrator, ask who decides what P1 means and when the rules change. The answer is almost always the service operations director or head of field operations.
- Will that person convene an internal conversation? Ask whether they would sponsor a discussion about the company's emergency dispatch history. If no, stop. A licensing conversation with no internal owner does not move.
- Whose records are they? Separate the company's own records (dispatch rules, priority change history, booking moves, technician notes) from records tied to a client's site or incident. The second group goes to the counsel branch.
- Do any records describe safety incidents? Hazard escalations, injury reports or regulator notifications often carry their own confidentiality or retention terms. These go to counsel and, where relevant, the head of health and safety.
- Who approves new uses of company information? Ask the convener directly. The answer should be the CEO, with counsel advising. In a group or fund-owned roll-up, add the parent's approver.
The introduction is ready when you have a named convener and a named approver. The system map helps the convener describe what exists without anyone pulling records.
Holder, convener or signer: a role table
| Role | What they hold or know | Can they authorize a licensing discussion? |
|---|---|---|
| Dispatcher or scheduler | Individual priority changes and booking moves | No; a witness to the decisions |
| Dispatch system administrator | Export contents, audit settings, retention settings | No; technical access is not authority |
| Service desk manager | Escalation calls and how they are logged | No; describes coverage |
| Head of health and safety | Hazard escalations and incident reports | No, but should know the discussion exists |
| Service operations director | Priority scheme, systems, years of good logging | Rarely alone; the right convener |
| General counsel or contracts lead | Client contract clauses on site and incident data | Advises; the gate for client-tied records |
| CEO | Vendor contracts, client agreements, company commitments | Yes, usually with counsel |
A useful test: if the person's main answer to "can we discuss this?" is "I would have to ask", ask who they would ask.
Branches that need counsel or the client's sign-off
Four kinds of record send the conversation down the side branch:
- Client site and asset details. Store layouts, equipment lists and access notes may be the client's confidential information under the maintenance contract.
- Contracted response targets. SLA records measure performance against what the client was promised. In Dynamics 365 Field Service, for instance, work order SLAs track arrival and resolution with warning and failure times. Those measurements may be described in a client report, so counsel checks whether they can be used beyond it.
- Safety incident records. Hazard reports and follow-up investigations may be subject to their own confidentiality terms.
- Technician and caller identities. Work orders name technicians, carry user IDs and often record locations. Where EU law applies, personal data includes information identifying a person by name, identification number or location data, so the privacy owner joins counsel. That shapes de-identification; it does not end the conversation.
Partners worried about raising this with a client can read whether referring clients hurts the relationship, and the client-owned versus company-owned data map explains the line in more depth.
Two Illustrative contractors, two paths
Both are fictional, built for this page; neither is a real client or a completed deal.
| Step | Contractor A: in-house maintenance for its own stores | Contractor B: services client sites under contract |
|---|---|---|
| First contact | Dispatch system administrator | Service operations director |
| Convener | Head of facilities operations | Service operations director |
| Record origin | Company's own sites and assets | Client sites, client assets, company's own dispatch logs |
| Side branch | Technician identities to the privacy owner | Site details and SLA reports to counsel; safety incidents to health and safety |
| Approver | CEO | CEO with general counsel |
Contractor A has the shorter path because the sites are its own. Contractor B may still offer its own dispatch rules, priority change history and booking moves even if some client site detail stays out. Multi-site contractors assembled through acquisitions, like those in a fire and life safety roll-up, may need the group approver as well.
Where the answer stays unknown until SourceX's rights review
The tree identifies who can authorize a conversation. It does not decide whether the records can be licensed, how much client content must be removed, whether there is SourceX's current data needs or what an offer would be. Why data rights matter explains why that review comes before any promise.
The introduced 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. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company. The referral brief template is where the named approver goes.
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.
Once the service operations director has agreed to convene and to bring in the CEO, who can approve, register as a partner, check the company on who qualifies and read the program terms before making the introduction.