Specialist advisors and industry operators meet these logs from the inside, tuning reschedule rules or untangling call-out codes. That vantage point lets you say whose operation a log describes; it also means what you saw, you saw as someone's adviser, and it stays theirs.
What a scheduling exception records, in plain words
An exception is a written trace of the moment the plan and the day disagreed: a technician outside the promised window, a shift left open after a call-out, a dock appointment pushed because the yard was full. Each one tends to leave the same fields: what was planned, what happened instead, when, a reason code, who approved the change and what was done about it.
| Operation | Typical exceptions | Usually logged in | Whose work it shows |
|---|---|---|---|
| Field and home services | Missed arrival windows, reschedules, jobs that could not be finished | The company's dispatch or field service platform | The company's own crews and dispatchers |
| Contact centers and shift-based teams | Call-outs, shift swaps, schedule overrides, overtime approvals | A workforce management or timekeeping tool | The employer of the people on the roster |
| Freight, warehousing and delivery | Missed dock appointments, late pickups, rebooked delivery slots | Transport or yard software, or a shipper's booking portal | Whoever ran the truck or the dock; the shipper may hold the booking |
| Clinics and appointment services | No-shows, late cancellations, double bookings | Practice or booking software | The provider, with client or patient details in nearly every row |
The reason codes are usually the operating company's own work even when the software is not. Salesforce's Field Service documentation, for example, has companies map each custom appointment status to a standard category, and gives the case of a Customer Absent value that a company may file under Cannot Complete. The vendor supplies the categories. The operator decides what its dispatchers may say about a failed visit, and years of those choices are part of the history.
Worker-side exceptions are employment records before they are anything else. New York City's Fair Workweek guidance for retail employers, as its FAQ describes it, expects covered employers to keep three years of records showing the schedules they issued and the shift trades they allowed, with original versions kept rather than overwritten. Rules like that point at the employer as the record keeper, and mean every row names a worker. The workforce schedule exception map draws the anatomy of one exception day and the main site's media scheduling walkthrough traces a supplier case; this page asks whose records they are.
Five places an exception log lives outside the business it describes
Only the company whose operation produced the exceptions may be able to license them, and it is often not the one holding the log.
- A software vendor's platform. The vendor hosts the tenant. The customer configured it and the customer's people filled it. Hosting is custody, not ownership.
- A staffing firm's desk. Its desk produces records about its placements; the client's site roster is the client's. Placed workers do not count toward the firm's 50 full-time employees, only its own staff do; give both figures and introduce a firm with strong records anyway, as the staffing firm owners page explains.
- An outsourcer working inside a client's system. A contact center that books appointments for a client, in the client's software, types the entries, but the bookings, the customers and usually the system belong to the client.
- A franchisor's required platform. Franchisees create the entries on software the franchisor licenses and mandates. The franchise agreement decides what the franchisor may do with them.
- A shipper's booking portal. A carrier sees its own missed dock appointments there; the shipper sees everyone's.
The operations-owner screening map
Treat one exception record as six layers and ask four questions of each: whose work it records, whose system holds it, whose rules shaped it, and who can describe it without opening anything. A layer points to the operating business when all four answers name the same company.
| Layer | What it holds | Points to the operating business when | Points elsewhere when | Who can describe it |
|---|---|---|---|---|
| 1. Plan | The schedule, route or roster in force | The company built it for its own crews or staff | A client or shipper set the slot and the company only carried it out | The scheduling or dispatch lead |
| 2. Event | Time, exception type, planned against actual | It happened in the company's own operation | It happened at a client site under the client's supervision | The operations manager |
| 3. Reason and note | Reason code and free-text explanation | Codes and notes written by the company's dispatchers or supervisors | Codes imposed by a client contract or a franchisor's standard | Whoever maintains the code list |
| 4. People | Worker IDs, customer or patient names | The workers are the company's employees and the customers are its own | The people are a client's customers or patients | HR or the privacy lead, in categories only |
| 5. Resolution | Rebooking, credit, escalation, penalty | The company decided the fix and paid for it | The client decided, or the credit came from a client contract | The operations or finance lead |
| 6. Attachments | Photos, messages, emails | Taken or written by the company's staff | Sent by clients, customers or suppliers | The system administrator |
Read the finished map by the four layers that carry the history: plan, event, reason and resolution.
- All four point to the company. The CEO may want a conversation; introduce once they say yes.
- They split. Describe only the company's own layers. The rest stays out of the first conversation.
- The plan or reason layer is unknown. Hold until the company itself answers the contract question. You never answer it for them.
Method note. The map applies SourceX's screening profile (client-owned material is usually not a fit, and rights must not breach client confidentiality, employee privacy or third-party contracts), the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), Salesforce's status-category documentation and New York City's Fair Workweek FAQ, all checked 2026-10-27. Layer names are ours. The map does not measure demand, record quality or value; SourceX assesses relevance in review, and no figures on how often scheduling records are accepted have been published.
Three exception logs on the map (Illustrative)
Illustrative. Generic companies, invented facts, no outcome implied.
| Layer | A. Heating and plumbing contractor, 240 people | B. Contact-center outsourcer, 650 seats | C. Home-services franchisor, 130 corporate staff |
|---|---|---|---|
| Plan | Its own dispatch board since 2016 | Its own agent rosters; client booking calendars in client systems | Set by 280 franchisees |
| Event | Its own crews | Call-outs and swaps are its own; booking no-shows are the clients' | Franchisee jobs |
| Reason and note | 41 codes its dispatchers wrote | Its own codes for agents; client codes for bookings | A code list the franchisor requires |
| People | Its technicians; homeowners named in rows | Its agents; clients' patients | Franchisee staff and customers |
| Resolution | Its own credits and callbacks | Split by account | Franchisees decide |
| Route | Ask the CEO | Describe the workforce layer only | Hold until counsel reads the franchise agreement |
A, original work. Ten years of missed windows and reschedules, coded by the contractor's own staff in a tenant it pays for. Homeowner names are personal data inside the company's own history, a matter for its privacy review and its agreement with SourceX. The route is a short note to the CEO.
B, mixed third-party content. Two histories that look alike. The workforce exceptions describe the outsourcer's own employees and rostering decisions; the appointment exceptions describe its clients' customers, in its clients' systems, under its clients' rules. Only the first is a candidate, and "years of scheduling data" without that split misdescribes the second.
C, uncertain ownership. The franchisor runs the platform and wrote the code list, but franchisees, separate businesses, created every entry about their own jobs. Only its own 130 full-time employees count for its size, as the franchise headcount answer sets out. Whether the agreement lets it reuse franchisee records is unknown, and nobody approaches franchisees one by one to get around the question.
Tracing the company owner and where the material came from
- Name the entity whose operation the exceptions describe, by legal name, not by brand. In a franchise or a group, this is where the trail usually forks.
- Ask whose account the system runs under: who pays for the tenant and who administers its users. That establishes custody and nothing more.
- Ask who wrote the code list and when it last changed. A company-written list is evidence of original work; an imposed one points to whoever imposed it.
- Ask what share of rows involve a client's site, customers or patients, as a rough proportion with no names.
- Ask about history with licensing and with SourceX. Records already licensed for AI training are out, because SourceX's process has the supplier confirm that its data never was. Section 3 of the terms adds: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." A company SourceX already knew is a duplicate, and a later introduction is not credited.
- Name the decider. The operations director who owns dispatch or workforce scheduling can explain the log and sponsor the idea internally; the CEO authorizes a licensing discussion.
The fit checks sit beside the trace: 50 or more full-time employees at peak with contractors left out, several years of the company's own records, the rights to license them and a CEO who wants the conversation. 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. SourceX's qualification takes a few questions and no files, and a qualifying company lists at least five systems, so a firm running dispatch, timekeeping and billing separately may hold more history than its operators assume.
Bounded questions for a first conversation, with nothing exported
Eight questions an operator can answer from memory or a settings screen:
- Which exception types does the log record, and from which year?
- Roughly how many exceptions a month, and how has that moved with headcount?
- Which system holds them, under whose account, and who administers it?
- Who wrote the reason codes, and do notes allow free text?
- What share of exceptions involve a client's site, customers or patients?
- Are workers identified by name or by ID, and does HR know the log exists?
- Has any of it been licensed to anyone for AI training?
- Would the CEO want to hear about licensing the company's own records?
Never ask for an export, a sample week, a screenshot of the dispatch board, a login or a client list; anything you already hold from consulting work stays inside that engagement. The note to the CEO can be four sentences: "Your dispatch history since 2016 records missed windows, reschedules and the reasons your team gave. SourceX licenses company-owned operating history like this for AI training and evaluation. Would you want a conversation? Nothing about the log has been shared." Assessing field service records covers what makes a service history useful, and finance exception logs screens a sibling log the same way.
Where the screening map points the wrong way
- Free text crosses layers. A dispatcher's note can quote a client's instruction verbatim, putting client content inside a layer scored as the company's.
- Vendor terms are unread. A platform's terms can say something about data generated in a tenant. That is read in rights review, not guessed by the introducer.
- Clinic logs are personal in every row. Whether any part can be licensed is a privacy question long before it is a referral question.
- Demand is unknown. SourceX checks relevance to current data needs in review, and a strong map can still end in a decline.
- Old tenants lapse. Exceptions in a retired system may be gone. A dated retirement is real urgency; a sales quarter is none. A renewal-timed inventory shows what a platform switch can lose.
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 plan, event, reason and resolution layers all trace to one company and its CEO wants the conversation, register as a partner, check the company once more against who qualifies and read the program terms before your note goes out.