# Schedule recovery referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/production-schedule-recovery-referral-brief-template
Last updated: 2026-11-04

A company introduction about production schedule recovery needs one page of metadata: company size, the systems that hold shortage alerts, rescheduling decisions and completions, how many years they cover, roughly how many recoveries a year, who owns each system, and the executive who can authorize a licensing discussion. Nothing else. No order data, screenshots, drawings or customer names. Below is a blank template to copy, notes on each field, and one completed Illustrative brief.

This template is part of the [production schedule change log page](/data-types/production-schedule-change-log), which explains why a recovery leaves an alert, a decision and a confirmation. Use this page when you are ready to write the introduction.

## When an MES consultant should fill one in

Write the brief after a conversation, not before. The usual moment is during an MES upgrade, an APS rollout or an ERP consolidation, when you have already heard how the plant handles a constrained machine failing mid-batch and someone has mentioned that the old system's history may not move. Three conditions should hold before you start:

- The plant operations director, or someone with equal standing, has agreed that you may describe their records to SourceX in general terms.
- You know who sits above that person and can approve a licensing discussion: the CEO, or the owner in an owner-run company, sometimes with a parent company's approval.
- You can answer most fields from what you were told. If you would have to log in to a system to find out, ask instead.

The brief replaces a long email thread. The sponsor should be able to forward it internally without editing, and SourceX should be able to decide from it whether a first call is worth everyone's time.

## The blank brief

Copy the table below into a document and fill in the right-hand column. Every entry is a description, a range or a name. Keep each one under twenty words.

| Field | What to write |
|---|---|
| Company size | Full-time employees at peak, contractors excluded, and number of plants |
| Business task | The recovery situation in one line, such as a constrained machine failing mid-batch |
| Records | The record types that exist: shortage alerts or missing part statuses, downtime events, rescheduled operations, confirmations, planner notes |
| Systems | Each system by category and the year it went live (MES, ERP, scheduling tool, maintenance system, email) |
| Years of history | Earliest year with usable records, and any gap from a past migration |
| Record volume | Rough recoveries per month or year, with whose estimate it is |
| Record owner | The person who runs each system or knows where the records are kept |
| Access event | Any dated change: license end, decommission, read-only cutoff |
| Open question | The one thing nobody could answer yet |
| Authorized contact | The executive who can approve a licensing discussion, plus a working contact |

The template has no field for record content, file names or export samples on purpose. Partners never ask for or handle raw client records.

## Notes on each field

**Company size.** The baseline is 50+ full-time employees at peak, contractors excluded. Agency staff on the line do not count. If the plant belongs to a group, write the group's headcount and note that a parent may need to approve.

**Records.** Name what exists, not what you hope exists. The weak link is usually the alert. In SAP, a failed availability check sets a missing part status in the production order header, but the availability log itself is not kept once the user leaves the order; the missing parts overview shows only the last check. So "missing part statuses" and "a full alert history" are different entries.

**Systems.** Use categories and plain text names. Plants often share order and operation keys between MES and ERP, which is the kind of exchange ISA-95 Part 4 defines object models for; the reason for a reschedule rarely travels with those keys and tends to sit in email. Listing email as a system is normal and useful.

**Record volume.** An estimate is fine if you say whose it is ("by the scheduler's estimate"). Do not count records yourself.

**Completions.** If the plant confirms production in SAP, confirmations can be partial or final and carry yield and scrap, so the outcome end of the chain is often well kept. Write that down; it tells SourceX the chain has a checkable result.

**Open question.** Pick one. Two or three makes the brief look uncertain; one shows you listened. Siblings of this page help with the common ones: the [records-across-systems guide](/guides/production-schedule-recovery-records-across-systems) on joins between MES, ERP and email, and [who can license recovery records](/questions/who-can-license-production-schedule-recovery-records) on authority.

## A completed brief (Illustrative)

Fictional plant, invented for this page. A 340-person injection molder with two plants runs a 48-cavity tool on its only 800-ton press sized for a housing part. When the press's hydraulic unit fails mid-batch, the remaining shots move to a smaller press with a slower cycle and a different tool, and another customer's job slips.

| Field | Completed entry (Illustrative) |
|---|---|
| Company size | 340 full-time at peak, contractors excluded; two plants |
| Business task | Recovering a molding lot when the one press sized for the tool fails mid-batch |
| Records | Missing part statuses on assembly orders, press downtime events, rescheduled operations, partial and final confirmations, scheduler email |
| Systems | MES since 2013, ERP since 2010, maintenance system since 2017, scheduler mailbox |
| Years of history | Confirmations from 2010; MES downtime from 2013; maintenance work orders from 2017 |
| Record volume | About 15 mid-batch recoveries a month across both plants, by the scheduler's estimate |
| Record owner | Plant operations director for MES; ERP administrator; maintenance manager |
| Access event | The MES vendor ends support for the current version at the end of next year |
| Open question | Whether shortage alerts were stored before 2019 or only shown on screen |
| Authorized contact | CEO; plant operations director as working contact |

Read it as SourceX would. The chain has all three links for at least six years, the outcome is recorded with yield and scrap, the reason text sits in a mailbox someone owns, and there is a dated access event that is real, not invented urgency. The open question is narrow and answerable.

## Qualification: what the brief can and cannot settle

The brief settles which records exist, which system holds each, who owns them and who can authorize a licensing discussion. It does not settle whether the records are licensable. That depends on customer supply agreements that may cover part data, on any parent-company approval, and on how employee names in approvals and overtime notes are handled. Why that matters is set out in [why data rights matter](/proof/why-data-rights-matter).

What stays unknown until SourceX reviews it: SourceX's current data needs for this record type, the rights review result, the preparation work needed, and any offer. The company also needs 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. The [manufacturing screening worksheet](/resources/a-referral-screening-worksheet-for-manufacturing-businesses) covers these checks before you write the brief.

Attach the brief to a short note from you to the sponsor; the [warm introduction brief](/resources/a-warm-introduction-brief-for-a-business-owner) is a good model for that note. Sign the Channel Partner Agreement before you submit. 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. After that, SourceX works with the company directly and the partner steps back. More plant record types are on the [manufacturing industry page](/industries/manufacturing).

## 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.

If your completed brief shows all three links of the recovery chain and a named authorized contact, [register as a partner](/register), confirm the basics on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you send it.

## Sources

- https://help.sap.com/docs/PRODUCT_ID/34de0103497c4b80a7c7fbf6952ff971/db02b753128eb44ce10000000a174cb4.html
- https://help.sap.com/docs/s4hana-cloud-best-practices/quality-management-in-discrete-and-process-manufacturing-1e1-jp/confirm-production
- https://www.isa.org/products/ansi-isa-95-00-04-2018-enterprise-control-system-i
- https://refer.sourcex.si/terms
