# Scope change records completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/service-request-to-scope-resolution-completeness-checklist
Last updated: 2026-11-04

A service-request-to-scope-resolution trail breaks at the pilot that never ends on paper. When a free task outlives its agreed window, the request system still calls it a pilot, the time tracker shows hours with no price, and the contract system shows nothing until someone signs an amendment. Seven checks, each scored pass, partial or fail from a conversation with the delivery and finance leads, show whether a firm's PSA, time and contract records are complete enough to discuss.

This scorecard is part of the [service-request-to-scope-resolution records guide](/guides/chain-service-request-to-scope-resolution). The keys it tests are laid out in [the record chain page](/guides/service-request-to-scope-resolution-record-linkage).

## How to score: 2, 1 or 0 for each check

Each check scores 2 for pass, 1 for partial and 0 for fail; seven checks make 14. Pass means the person answering says the condition holds across the whole period they describe. Partial means it holds for some years, some practice areas or some clients, and they can say which. Fail means it does not hold, or nobody knows; write "unknown" next to a zero that comes from not knowing.

The answers are descriptions, not records. "Roughly what share of amendments cite a project number?" is a good question. "Can I see an amendment?" is not. Your notes hold years, rough counts, system names and owners, never client names, rates or timesheet content.

## Seven checks on the scope-change trail

| Check | Ask at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage overlap | "Since when have the PSA, the time tracker and the contract system all been in use?" | Three or more years with all three | Under three years of overlap | One replaced without its history |
| 2. Shared project code | "Do tickets, time entries and contract records share a project or work order number?" | On all three | Tickets and hours only | Hours joined to requests by name or memory |
| 3. Pilot end dates | "Do pilots and free tasks carry an end date the PSA or time tracker enforces?" | End dates set and enforced | Set but not enforced | Non-billable tasks stay open indefinitely |
| 4. Conversion recorded | "When a task changes from pilot to ongoing work, is that change dated anywhere?" | Status or billability change logged with date | Noted in account reviews only | The conversion has no date |
| 5. Locked hours | "After timesheets are approved, can hours move to a billable code, and by whom?" | Locked; edits need an administrator and leave a trace | Locked for recent years only | Freely editable, no history |
| 6. Linked amendments | "Is each amendment filed against its parent agreement, and does it cite the request or project?" | Linked and cites the project | Linked to parent, no project reference | Amendments filed loose |
| 7. Decision outcome | "When free work is caught, is the decision on past hours recorded?" | Write-off or billing decision recorded with reason | Recorded in finance totals, no reason | Not recorded |

Check 2 decides whether the systems join at all. The request-to-hours join is usually strong; the hours-to-contract join is usually where firms score partial.

Check 5 is more concrete than it sounds. Harvest's help center, for example, says an approved timesheet is locked and only an administrator can edit it by withdrawing approval, and approved, invoiced entries must also be marked uninvoiced first. A firm on a tool like that can say with some confidence whether pilot hours were ever reclassified, which is why a locked history scores pass.

Check 6 depends on how the contract system files changes. Ironclad's Contract Families, for instance, links each amendment to one parent contract and keeps original terms viewable. A firm using that kind of feature passes the first half of the check; the second half, citing the project, is a filing habit rather than a feature.

## Checks 3 and 4: the gray zone between free and priced

These two checks carry the accounting edge that makes this chain interesting. U.S. revenue guidance (ASC 606) treats a contract modification as a change in scope or price, or both, that the parties approve, and says approval can be written, oral or implied by customary business practice. It also recognizes that a modification can exist when the parties have approved a change in scope but not yet its price.

A pilot that runs past its end date sits exactly there. If the firm records the end date (check 3) and dates the conversion (check 4), its records show when scope changed in practice, weeks before the price was agreed. If it does neither, the records show hours rising and an amendment appearing, with the decision in between unrecorded. Finance teams care about that gap, which is why records that capture it carry real decisions.

Ask the finance lead one plain question to score both: "When a free task turns into ongoing work, how do you find out, and where is that written down?" Pass if the answer names a status change or a dated review note in the PSA; partial if it names an account review or utilization report; fail if the answer is "when the client renews."

## Illustrative: a 180-person engineering consultancy scores 8 of 14

Illustrative. A fictional 180-person civil engineering consultancy answered the checks in one call with its head of delivery and a follow-up with its finance manager.

| Check | Mark | Points | What they said |
|---|---|---|---|
| 1. Coverage overlap | Pass | 2 | PSA since 2017, time tracker since 2017, contract repository since 2020 |
| 2. Shared project code | Partial | 1 | Project number on tickets and hours; on about half of contracts |
| 3. Pilot end dates | Fail | 0 | Free tasks have no end date field |
| 4. Conversion recorded | Fail | 0 | Not dated anywhere |
| 5. Locked hours | Pass | 2 | Approved time locked; only finance can reopen it |
| 6. Linked amendments | Partial | 1 | Linked to parent agreements since 2020; no project reference |
| 7. Decision outcome | Pass | 2 | Write-offs recorded with a reason code since 2019 |
| Total | 8 of 14 | 8 | Outcomes traceable; the pilot-to-permanent moment is not |

For the sponsor, in one sentence: the firm can show what free work cost and how each case ended, but not when free work became permanent. That is a fair, specific description. Change orders in construction leave a similar trail, described on the [construction change order data page](/data-types/change-order-data-construction), and request-side records are covered under [ITSM ticket history](/data-types/itsm-ticket-history). Firms in the middle of replacing a finance system can pair this scorecard with the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement).

## Who answers, and what the score cannot tell you

The head of delivery answers checks 1 to 4. Finance answers 5 and 7. The commercial lead or whoever signs amendments answers 6. A licensing discussion needs the CEO's authorization, and counsel's reading of client contracts, because those contracts often limit how delivery records can be used.

Confirm the baseline before introducing: 50+ full-time employees at peak (contractors, including subcontracted consultants, excluded), 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. Sign the Channel Partner Agreement first.

The score does not show whether client contracts allow licensing, whether any buyer wants these records, or what the firm would be paid. Those stay unknown until SourceX reviews the firm. If SourceX comes back with a follow-up, [how to understand a request for more information](/guides/how-to-understand-a-request-for-more-information) explains what it usually means. To see what a single export loses, read [the before-and-after page](/guides/service-request-to-scope-resolution-missing-context). Naming Harvest and Ironclad does not imply a SourceX connector. More record locations are under [systems](/systems).

## 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 you advise has scored all seven checks, fails included, and a managing partner or COO will take the call, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you submit.

## Sources

- https://storage.fasb.org/ASU%202014-09_Section%20A.pdf
- https://support.getharvest.com/hc/en-us/articles/4408205049869-Unlocking-approved-time-and-expenses
- https://support.ironcladapp.com/hc/en-us/articles/12402562074775-Contract-Families-Overview
- https://refer.sourcex.si/terms
