Service-request-to-scope-resolution records: a sample metadata packet for PSA, time tracking and CLM

Short answer

A partner can note, without opening a ticket, a timesheet or a contract, which systems hold each step from new client request to delivery effort to agreed scope change (often a PSA, a time tracker and a contract lifecycle management tool), the years and rough volumes each covers, who administers them, and whether a request, its hours and its amendment share a project or work code. The case to flag is a free pilot task that quietly became permanent delivery work.

Visual briefFull-size diagram
A line chart of cumulative non-billable hours on a free pilot task rising from 0 to 156 over 15 weeks, with a band marking the agreed four-week pilot, a band where the work continued unpriced, and a marker at week 16 where an amendment set a fee of $6,000 per month.
Illustrative consulting account. The pilot was agreed for four weeks; the hours kept accruing for eleven more before the scope was priced.

Free pilot to permanent work: a 16-week record

The account below is Illustrative, built for this page. A 240-person data and analytics consultancy runs monthly reporting for a client under a master services agreement and a fixed-fee statement of work. The client asks for something extra.

WeekSystemEventCumulative non-billable hours
1PSAClient request logged: "weekly data-quality check, free for a four-week pilot"0
1 to 4Time tracker6 hours a week logged to a non-billable task, "Pilot: DQ check"24
5PSAPilot end date passes; the ticket is not closed and no follow-up is created24
5 to 12Time trackerCheck becomes routine; 12 hours a week, same non-billable task120
13 to 15Time trackerAccount review flags the task; hours continue while pricing is discussed156
16CLMAmendment to the statement of work signed: weekly check added at $6,000 per month from week 17156

The past 156 hours were written off. The business decision is clear in hindsight: an agreed pilot, an unplanned conversion to permanent work, a review that caught it, and a priced amendment. It is clear only because three systems were read together.

What metadata can a referral partner collect about service-request-to-scope-resolution without reading private content?

Treat it as a ten-question interview with the COO or head of delivery, answered from memory. Write down the answers, not any examples.

  1. Which PSA or ticketing tool holds client requests, since when, and roughly how many requests a year?
  2. Which time tracker holds hours, since when, and roughly how many consultants log time?
  3. Which CLM or contract repository holds agreements and amendments, since when, and roughly how many amendments a year?
  4. Who administers each system?
  5. What code, if any, appears in all three: project number, work order, client code?
  6. Do pilots and free tasks get their own codes and end dates?
  7. After approval, can time be reclassified, and who can do it?
  8. Are amendments linked to their parent agreements, and do they reference the request that caused them?
  9. Does the firm know that free work sometimes becomes permanent, and how does it catch it (account review, utilization report, client renewal)?
  10. Have any of the three systems been replaced, and what history moved across?

The packet those answers produce (Illustrative)

Packet fieldPSA (new request)Time tracker (delivery effort)CLM (agreed scope adjustment)
Object typesRequests, tickets, projects, tasksTime entries, approvals, task codesAgreements, amendments, parent links
Years held2018 to today2018 to today2020 to today; older contracts as PDFs
Rough volumeAbout 3,000 client requests a yearAbout 180 consultants logging weeklyAbout 120 amendments a year
Reference carriedProject numberProject number and task codeClient code; project number in some amendments
OwnerHead of deliveryFinance operationsCommercial lead
UnknownWhether pilots get end datesHow often approved time is reclassifiedShare of amendments that cite a request

Harvest's help pages, for example, describe approved timesheets as locked until an administrator withdraws approval, and Ironclad's describe amendments linked to a parent contract. Those details tell you which questions to ask; they do not imply SourceX connects to either tool.

Unknown until review: confidentiality and data-use terms in client contracts, personal data in time narratives, buyer interest, the offer and any reward. The scope creep adjudication guide covers the related change-order trail, and the contract review workflows page covers the CLM record type.

Introduce someone who can open a licensing discussion: usually the CEO, COO or managing partner. Name the head of delivery and the finance or commercial lead as the people who can answer the interview. The guide to operational knowledge in a professional services firm explains how to raise the topic with partners.

Before introducing, check: 50+ full-time employees at peak (subcontracted consultants 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.

What stays unknown until SourceX reviews it: demand for this record type, the rights review result, how client and personal data would be handled, the offer and any reward. Related: Jira Service Management request history and the systems hub.

Go deeper on service-request-to-scope-resolution records

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 a services firm can answer the ten questions and link its amendments to the requests behind them, register as a partner, check it against who qualifies, and read the program terms before you introduce its COO.

  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

Is unbilled pilot work a red flag for a licensing discussion?

No. It is ordinary in services firms, and a firm that can show how a free task turned into priced scope has a clear decision record. What matters is whether the request, the hours and the amendment can be linked, not whether the firm always billed correctly.

Do client contracts stop a firm from licensing its own delivery records?

Sometimes they limit it. Master services agreements often have confidentiality and data-use clauses. The partner only notes that client contracts exist and who holds them; SourceX's rights review decides what can be licensed.

What if time is tracked inside the PSA rather than a separate tool?

Then two of the three systems are one, which usually makes the request-to-hours join stronger. Note it in the packet; the CLM join remains the one to ask about.

Sources

  1. storage.fasb.org/ASU 2014-09_Section A.pdf
  2. support.getharvest.com/hc/en-us/articles/4408205049869-Unlocking-ap…
  3. support.ironcladapp.com/hc/en-us/articles/12402562074775-Contract-Fa…
  4. refer.sourcex.si/terms

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