# Request to scope change record chain: keys | SourceX

Canonical: https://refer.sourcex.si/guides/service-request-to-scope-resolution-record-linkage
Last updated: 2026-11-04

A services firm connects its service-request-to-scope-resolution records by carrying one project or work order number from the client request, through the task codes and time entries, into the contract record, and by filing each amendment against its parent agreement. The request-to-hours join is usually strong because the PSA and time tracker share project codes. The hours-to-contract join is usually weak, because contracts are filed by client and agreement number while hours are filed by project.

This page lays the chain out record by record. It is part of the [service-request-to-scope-resolution records guide](/guides/chain-service-request-to-scope-resolution), which covers the full metadata packet and the Illustrative account this chain is drawn from.

## Five records and the identifier each one owns

Treat the chain as five records, each owning one identifier and borrowing another from its neighbor. The borrowed identifier is the join.

1. **Request ticket.** Owns a ticket ID; borrows the project number from the engagement it was logged under. One project holds many tickets.
2. **Task code.** Owns a task code; borrows the project number. Whether it also borrows the ticket ID, recording which request caused it, is a habit that varies by firm and by delivery lead.
3. **Time entry.** Owns an entry ID and an approval status; borrows the project number and task code. One task collects many entries across many consultants.
4. **Statement of work.** Owns an agreement number; borrows a client code, and only sometimes a project number. One agreement can cover several projects, and one long project can outlive several agreements.
5. **Amendment.** Owns an amendment number; borrows the parent agreement number if the contract system files it that way.

Records 1 to 3 join with little effort because the project number travels on all of them. Record 5 joins record 4 when amendments are filed against parents. Between records 3 and 4 the borrowing stops: nothing on a time entry names an agreement, and nothing on most agreements names a project. That is a many-to-many relationship with no key, which is why it is the weak link.

The parent guide's Illustrative account makes it concrete: a fictional 240-person analytics consultancy logged a client request, ran the work as a non-billable task, and priced it months later by amendment. Tickets, task and hours line up on the project number at once; tying the hours to the amendment takes either a project number on the contract or someone's memory.

## Step, record, key and system

| Step | Record | Key it carries | Key that points back | System |
|---|---|---|---|---|
| Request | Client request ticket | Ticket ID | Project number | PSA |
| Plan | Non-billable task | Task code | Project number; ticket ID only if entered | PSA or time tracker |
| Effort | Time entry | Entry ID, approval status | Project number and task code | Time tracker |
| Agreement | Statement of work | Agreement number | Client code; project number sometimes | CLM |
| Change | Amendment | Amendment number | Parent agreement number | CLM |

Read the fourth column from top to bottom. Every row points back with a key the row above holds, except the agreement row, which points to a client rather than a project. That one cell decides whether the chain closes on its own.

On the contract side, Ironclad's Contract Families feature is a useful reference for what "filed against a parent" can mean. Its documentation says an amendment is linked to one parent contract, a parent can have several amendments, a side-by-side comparison shows new and updated properties to roll up, and the original terms stay viewable through a Show Amended Values toggle. It rolls up properties, not clauses. So a firm using it can show that the week 16 amendment belongs to the original statement of work, but the reason for the amendment still lives in the PSA ticket and the time codes.

## Where the chain breaks, link by link

Most firms have one or two of these weak points, rarely all of them.

- **Ticket to task.** A free task created by a delivery lead without reference to the request. The hours exist; why they started does not. Ask whether tasks record the ticket that caused them.
- **Task status.** A task whose name says "pilot" long after it became routine. The version change from pilot to ongoing has no date. Ask whether task status or billability changes are logged.
- **Time entry edits.** Hours moved to a billable code after the fact. In Harvest, for example, an approved timesheet is locked and only an administrator can edit it by withdrawing approval; approved, invoiced entries must also be marked uninvoiced first. That means the firm can say whether reclassification happened, and by whom.
- **Hours to agreement.** The weak link above. If the statement of work does not carry the project number, the join is by client and date range.
- **Amendment to cause.** An amendment that changes scope and price but cites neither the request nor the project. The priced change floats free of the work that prompted it.

Why finance cares: U.S. revenue guidance (ASC 606) treats a contract modification as a change in scope or price, or both, that the parties approve. A chain that links the amendment back to the hours is the firm's record of when that change was approved in practice.

## Repairing the weak link with a crosswalk

The usual repair is not a new system. It is a crosswalk: a table, owned by finance or the commercial lead, that maps each agreement number to the project numbers delivered under it. Many firms already keep one for revenue reporting. If it exists, the hours-to-agreement join becomes as reliable as the others for every period it covers.

Ask four questions, and note the answers as given:

1. Does a list mapping agreements to project numbers exist, and who maintains it?
2. Since when, and does it include amendments?
3. Is it updated when a project changes contract, or rebuilt each year?
4. Are there projects with no agreement at all, such as free pilots, and how are they marked?

A firm that answers "yes, since 2021, finance updates it monthly" has a chain that closes end to end for those years. A firm that answers "no" still has two strong joins and a described gap. For firms moving between contract tools, the [CLM migration guide](/guides/clm-migration) explains which parent links tend to survive the move. PSA-side exports are covered for [Autotask](/systems/autotask-psa-data-export) and [ConnectWise](/systems/connectwise-psa-data), and request history in [Jira Service Management](/systems/jira-service-management-export-tickets).

## Who holds each key, and who can authorize

The head of delivery knows the ticket and task keys. Finance operations knows the time tracker and any crosswalk. The commercial lead knows how contracts and amendments are filed. A licensing discussion needs the CEO, COO or managing partner, because client contracts often carry confidentiality and data-use clauses that only the firm's leadership and counsel can weigh.

Partners never ask for or handle raw client records. You record which keys exist, on which records, since when, and who owns them. Before introducing, confirm 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.

What stays unknown until SourceX reviews it: what client contracts allow, how personal data in time narratives would be handled, buyer interest, and what the firm would be paid. This page names Harvest and Ironclad to show where keys commonly sit; it does not imply SourceX has a connector for them or for any PSA. To see what each system loses on its own, read [the before-and-after page](/guides/service-request-to-scope-resolution-missing-context); to score the chain, use the [completeness checklist](/resources/service-request-to-scope-resolution-completeness-checklist). 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 can name the key that joins its hours to its agreements, even if the answer is a finance crosswalk, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce its leadership.

## Sources

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