The agenda sits under the policy system migration guide, which explains why endorsement-aware decision histories matter. This page is the meeting itself: who to invite, the run sheet and the close.
Invite list and room setup
Four seats cover every block. Fewer than that and a block becomes a follow-up rather than an answer.
| Seat | Why they are needed | Blocks |
|---|---|---|
| Policy admin system lead | Knows how transactions, versions and attachments are stored in the legacy system | 1, 2 |
| Underwriting lead or referral desk manager | Knows where referral notes, rating overrides and worksheets live | 2, 3 |
| Conversion or migration manager | Knows what the design converts, archives or drops, and the switch-off date | 1, 3 |
| Chief underwriting officer, COO or CEO | Can speak to ownership, carrier agreements and authority to discuss licensing | 4, 5 |
Put one line in the invite: "Thirty minutes on what the legacy policy history holds before conversion design is fixed. Description only; no files." Hold the meeting after the conversion scope is agreed but before data mapping starts, while people still remember how the old system was used.
The run sheet: five blocks, timed
Illustrative. A 240-person regional commercial lines carrier is moving off a legacy policy system. The consultant chairs; the conversion manager keeps time.
| Time | Question for the block | Who answers | A good answer sounds like |
|---|---|---|---|
| 0-5 min | What converts as live data, what goes to archive, and when is the legacy system switched off? | Conversion manager | "In-force terms convert. Prior terms go to a read-only archive. Legacy switch-off is planned after the last renewal cycle." |
| 5-12 min | For a mid-term endorsement, can you see why it was issued and who approved it, from inside the version? | Policy admin lead, underwriting lead | "Yes for commercial property since the 2019 upgrade: the referral reason and approver are on the transaction." |
| 12-19 min | Where does the rest of the decision context sit: worksheets, overrides, broker emails? | Underwriting lead | "Rating worksheets are attached by policy and version number; broker emails are in the account mailbox." |
| 19-25 min | Who owns these records, and do carrier, reinsurance or program agreements limit reuse? | Owner | "We own our underwriting files; program business needs the program administrator's view." |
| 25-30 min | Does the company want to hear how licensing of approved records works, and who would lead? | Owner | "Yes. Our chief underwriting officer is the contact." |
What block two is really testing
NAIC consumer guidance says an endorsement becomes part of the legal insurance agreement and can be added at purchase, mid-term or at renewal, and the NAIC glossary describes it as an amendment that takes precedence over the general contract. Each one therefore marks a decision. Systems record the change, not always the reason: in Guidewire PolicyCenter's Cloud API, a policy change is started with an effective date and creates a job of type PolicyChange. Whether the referral note and approver are attached to that job depends on how the company configured and used the system. Ask for a description of the configuration, not a demonstration.
What block three separates
Version documents keep what the policy said; the context keeps why. If worksheets and overrides are attached by policy and version number, the link survives as long as the archive keeps those keys. If they live in shared drives without keys, the history may be unrecoverable even before cutover.
Hearing the answers: signals to note
| What someone says | What it usually means | Note to write |
|---|---|---|
| "We archive every version as a PDF." | Content kept, reasons probably not | "Versions yes, links unknown" and ask who mapped attachments |
| "Referral reasons are a free-text field." | Context exists but unstructured | "Partial, free text, years {range}" |
| "Personal lines are a different system." | Coverage of links varies by line | Record each line separately |
| "Program business belongs to the administrator." | Rights may sit with a third party | Flag for block four, stop for those programs |
| "The legacy system stays readable for seven years." | Less time pressure | Use the documented date, not a guess |
A useful meeting ends with a description such as "commercial property, 2019 onward, linked; personal lines, documents only; owner to confirm program business." That is enough to decide.
Before the owner decides
Say three things plainly before block five.
What SourceX does. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Attending this meeting shares nothing.
Your interest. You are a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes and every payment condition in the terms is met. It is funded separately and never deducted from the company's payout. Illustrative only: if the company were paid USD 400,000 for a qualifying completed handoff, the reward on its first qualifying transaction would be USD 70,000; a USD 40,000 payout sits below the USD 100,000 Minimum Transaction and earns nothing unless SourceX agrees in writing.
Whether the company can qualify. 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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: demand for this record type, the rights review result, the de-identification scope for policyholder data, any offer and any reward. Partners never request policy files, underwriting notes or claim records.
The decision to record at minute 30
| Outcome | When it fits | What follows |
|---|---|---|
| Introduce now | Block two is yes or partial, ownership is clear, the owner opted in | Send the introduction email to the named contact |
| Revisit after conversion design | Answers depend on mapping decisions not yet made | Agree a check-in tied to the documented design sign-off, then use the archive context checklist |
| Stop | The owner declines, or rights sit entirely with carriers or program administrators | Note the reason; the migration continues unchanged |
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, one partner per company; the rewards page explains the payment statuses. The portfolio review agenda and sell-side kickoff agenda show the same time-boxed method in other settings, the association endorsement question covers a different meaning of "endorsement", and the insurance industry page gives sector context.
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 the meeting closed on "introduce now", register as a partner, check the carrier or MGA against who qualifies and read the program terms before sending the introduction.