Contract renewal scope reconciliation referral brief: a fill-in template with one completed example

Short answer

A contract renewal scope reconciliation introduction needs one page of metadata: the company's business and full-time headcount, the task in one line, the record classes, the CLM, asset and finance systems with the years each covers, rough counts of contracts and reconciled renewals, who owns the records, who can authorize a licensing discussion, any documented access deadline and the open rights question. Leave out vendor names, prices and contract copies. Fill the template with the commercial operations director, who then forwards it.

Visual briefFull-size diagram
A grid of nine blank brief tiles, company, task, records, systems, years, volume, owner, signer and open question, that fill one by one with Illustrative values for a fictional 900-person logistics company, ending with a no vendor names, no prices seal.
Illustrative: every tile is a count, a year, a system name or a role. No contract, quote or price leaves the company.

This template is part of the contract renewal scope reconciliation guide. It turns one conversation into a handoff a CEO can read in two minutes and decide on.

The blank handoff: nine fields, no contract content

Copy these into an email or document. Each answer is something the commercial operations director can give from memory, a contract system report total or a project plan. Write "unknown" rather than guess.

FieldWhat to writeWhere the answer usually comes from
1. Company and sizeBusiness type, full-time headcount at peakDirector or HR, without contractors
2. Business taskOne line on what renewal reconciliation means hereDirector's own words
3. Record classesDrafts and quotes, asset or consumption histories, approvals, notice letters, invoice checksDirector
4. SystemsPlain-text names of the contract system, asset register, service desk and ERPContract system administrator, IT asset manager
5. Years of historyFirst year per system; where older contracts liveContract system administrator
6. VolumeActive vendor contracts; renewals reconciled per year; how countedContract system report totals
7. Record ownerWho is responsible for each record classDirector
8. Who can authorizeThe CEO, who can approve a licensing discussion, plus counselThe who-can-say-yes tree
9. Deadline and open questionAny documented date when a portal or archive closes; the rights question nobody can answer yetContract end dates, decommission plan

What never goes in: vendor names, contract numbers, prices, quote PDFs, worksheet extracts, employee names, or a guess at what the records might be worth.

Field notes: answering without opening a contract

Systems and years (fields 4 and 5). Ask the contract system administrator from which year renewal records were kept in the system, and whether the approval trail travels with them. In Ironclad, for example, a Dashboard view can be exported with historical data such as approvals, turns and workflow actions, although adding that history limits the output to a spreadsheet. If structured records only start a few years back, the earlier contracts may be scanned PDFs with no dates attached. Write both facts.

Asset side (fields 3 and 4). Ask the IT asset manager whether renewals were run through an asset step. ServiceNow's contract renewal workflow has an asset selection step to add or remove assets and view those carried over; where it was used, the record of what was removed sits beside the renewal itself. Where it was not, the reconciliation probably lives in spreadsheets, which belongs in field 3.

Volume (field 6). Use totals from reports, not rows. Many contract systems can produce a metadata report; Ironclad, for instance, exports record metadata from its Imports or Dashboard tab as a .csv, .json or .xlsx file, so a count of active vendor agreements is a report total rather than a manual tally. The administrator runs it; you only take the number. Say how you counted.

Deadline (field 9). Only write a date a document supports: a vendor contract that ends after this year's review, so its usage portal closes; a retention setting; an asset tool being retired. A guessed date undermines the rest of the brief.

Open question (field 9). State it plainly. For renewal records it is usually how much of the scope history survives without vendor pricing, or whether drafts from before the CLM were kept anywhere.

Completed handoff: a 900-person logistics company (Illustrative)

A fictional company, written for this page. The values show the level of detail, not a real case.

FieldIllustrative entry
1. Company and sizeU.S. freight and warehousing company, about 900 full-time staff at peak
2. Business taskMatching each vendor renewal's proposed scope to what is in use, and removing retired services before the opt-out date
3. Record classesRenewal drafts and quotes, asset and consumption histories, approvals, notice letters, invoice checks
4. SystemsContract system, asset register, service desk, ERP accounts payable
5. Years of historyContract system since 2019, earlier contracts as scanned PDFs; asset register since 2015; service desk since 2017
6. VolumeAbout 180 active vendor contracts; roughly 60 renewals reconciled a year, counted from approval totals in the contract system
7. Record ownerCommercial operations for drafts and approvals; IT asset management for asset histories; finance for invoice checks
8. Who can authorizeCEO, with the CFO and general counsel; commercial operations director sponsors
9. Deadline and open questionTwo vendors leave after this year's review and their usage portals close with the contracts; open question: were pre-2019 superseded drafts kept anywhere?

A three-renewal spot check, done by the director without sharing anything, is worth a line in field 5 if you have it: two of three past reconciliations rebuilt by contract number; the third needed a match on description. That tells SourceX how well the records join. The detailed case of one renewal is on the exception examples page.

Words to keep out of the brief

A handoff that reads like a sales pitch or a data sample works against the company. Before the director forwards it, strike these:

  1. Any vendor name or price. Use categories and counts.
  2. Any estimate of value. Buyer interest is unknown until SourceX reviews the company.
  3. Any claim of rights. "We own all of this" is for counsel to establish, not for the brief to assert.
  4. Any attachment. No worksheets, screenshots, system exports or sample renewals.
  5. Urgency without a document. A portal closure is real; "before it is too late" is not.

After the brief: the reward and what decides it

The CEO decides whether the company applies. If it does, SourceX reviews record classes, vendor terms and qualification. 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 70% of the data is in English. 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.

Rewards are a share of the compensation SourceX actually pays the company you referred (the Actual Supplier Payout), with no cap per referred company, subject to the program terms. SourceX pays rewards separately; they never reduce the company's payout. The reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap. It is paid separately so the company's payout is not reduced; further qualifying transactions first agreed within 12 months of the first Closing pay 15% of their own payout, and the USD 50,000 floor applies once per company, not again on a renewal or amendment. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. Illustrative only: if the company's first qualifying payout were $800,000, the reward would be USD 120,000 (15%, which exceeds USD 50,000 plus 5%); a later qualifying renewal agreed within the Repeat Window would add 15% of its own payout, with no second floor. See how rewards work.

The client opportunity brief generator can turn the nine fields into a forwardable note, and the warm introduction brief shows how to frame it for an owner. For context the CFO may ask about, see contract review workflows, the SaaS spend audit guide and, for advisors in a transaction, the quality of earnings resource.

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 all nine fields are filled and nothing on the strike list remains, register as a partner, confirm the company on who qualifies and read the program terms before the commercial operations director forwards the brief.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the brief name the vendors whose renewals were reconciled?

No. Write categories instead, such as hardware maintenance, SaaS subscriptions or facilities services. Vendor names and prices are covered by confidentiality terms that SourceX's rights review reads later.

How precise do the counts need to be?

A range with its basis is enough, for example about 180 active vendor contracts, counted from the contract system's active list. SourceX needs to know the scale and how it was measured, not an audited figure.

Who should send the brief?

The commercial operations director, to the CEO, who can authorize a licensing discussion. You help write it; the director decides whether to forward it.

Sources

  1. refer.sourcex.si/terms
  2. support.servicenow.com/kb
  3. support.ironcladapp.com/hc/en-us/articles/12286394278423-Export-Work…
  4. support.ironcladapp.com/hc/en-us/articles/32212463361047-Export-Reco…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment