# PSA export missing context: before and after | SourceX

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

A single-system export loses the reason for the scope change. The PSA export shows a request that never closed, the time tracker shows effort nobody charged for, and the contract system shows an amendment with no visible cause. Each is accurate and each looks complete. Only when the three are joined on a shared project code does the record explain itself: a short no-charge trial that ran far past its window, an account review that caught it, and a priced amendment that settled future work while the earlier effort was written off.

This page reads one Illustrative account twice, first as three separate exports and then joined. 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.

## Before: three exports, three partial stories

The account is Illustrative and built for this page. A fictional 160-person managed IT services provider supports a regional logistics client under a master services agreement and a monthly retainer for business-hours help desk cover. The client's operations director asks whether the provider could also watch overnight alerts, "just for a two-week trial." Here is what each system's export says on its own.

**PSA export.** A service request opened in week 1, category "trial", status still open. No due date, no linked follow-up, no reference to any agreement. Read alone, the request is simply pending.

**Time tracker export.** 78 no-charge hours on a task called "Trial: overnight alerts" across 10 weeks: 3 hours a week for the first two, then 9 hours a week as on-call engineers absorbed it into their rota. Approved timesheets, nothing invoiced. Read alone, the provider gave away a lot of engineer time for no stated reason.

**CLM export.** The master agreement, the retainer schedule, and an amendment signed in week 11 adding overnight monitoring at $2,500 per month from week 12. Read alone, the client bought a new service.

All three readings are reasonable, and all three miss what actually happened.

## After: the same account joined on the project code

| Week | Source | Event |
|---|---|---|
| 1 | PSA | Request logged as a two-week no-charge trial |
| 1 to 2 | Time tracker | 6 hours of overnight cover, as agreed |
| 3 | PSA | Trial end passes; request left open, no follow-up |
| 3 to 10 | Time tracker | Cover joins the on-call rota at triple the effort |
| 10 | PSA | Quarterly service review flags the open trial |
| 11 | CLM | Amendment prices overnight monitoring from week 12 |
| 11 | Finance | 78 earlier hours written off |

Now the record holds one labeled exception, an agreed two-week trial that ran ten weeks without a price, and one outcome: past effort absorbed, future effort billed. That is a commercial decision with its reasons attached, which is what makes the history useful for teaching a system how services firms handle scope.

## What each export drops, and where the context lives

| Lost without context | Single export shows | Where the missing context usually lives |
|---|---|---|
| That the work began as a no-charge trial | Time tracker: a task name only | PSA service request |
| The agreed trial length | Nothing in time or CLM | PSA request notes or the client's email |
| When the trial turned into standing work | Nothing; no system records the change | Inferred from hours tripling after week 2 |
| How much unbilled effort was given | PSA and CLM: nothing | Time tracker hours on the task |
| Whether the amendment priced new or existing work | CLM: amendment terms only | PSA request plus time history |
| What happened to the earlier hours | Nothing in PSA or CLM | Finance write-off record |
| Whether hours were later reclassified | Time export shows current codes only | Time tracker approval and unlock history |

The third row has no home. No system records the moment a trial became standing work, so it can only be read from the joined record. That gap is also where the accounting question sits. U.S. revenue guidance (ASC 606) says a contract modification can be approved in writing, orally or by customary business practice, and can exist when scope is approved before price. Weeks 3 to 10 sit in exactly that gray area.

The last row is checkable in some tools. Harvest's help center, for example, says approved timesheets are locked and only an administrator can edit them by withdrawing approval, so a firm on Harvest can say whether trial hours were ever moved to a billable code.

## The amendment that hides its own history

The contract record deserves a second look because it is the export people trust most. Ironclad's Contract Families feature, for example, links an amendment to its parent contract and keeps original terms viewable through a Show Amended Values toggle. That preserves what changed in the contract. It does not preserve why: the feature rolls up properties, not clauses, and nothing in it records the eight extra weeks of unpriced cover that led to the change.

So a firm that exports only its CLM history hands over a clean list of amendments with prices. A firm that can join those amendments to request tickets and hours hands over the negotiations behind them. If the firm has changed CLM tools, the [CLM migration guide](/guides/clm-migration) explains which parent links usually survive. Time entry narratives add a further layer, covered on the [time entry narratives page](/data-types/time-entry-narratives), and PSA history is described in the [PSA ticket history report](/resources/psa-ticket-history-report) and the [Autotask ticket history export page](/systems/autotask-psa-ticket-history-export). The general pattern of records missing their reasons is discussed in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

## Who can describe the gap, and who signs off

Three people can each describe one export: the head of delivery for the PSA, finance operations for the time tracker, and the commercial lead for the contract system. Ask each which part of the story their system holds and whether a project code appears in all three. The keys themselves are laid out in [the record chain page](/guides/service-request-to-scope-resolution-record-linkage).

None of them can authorize a licensing discussion. That is the CEO, or the managing partner where the firm uses that title, because client contracts often carry confidentiality and data-use clauses. Partners never ask for or handle raw client records; you record systems, years, rough volumes and owners.

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 narratives would be handled, whether a buyer wants this record type, and what the firm would be paid. To score how complete the chain is, use the [completeness checklist](/resources/service-request-to-scope-resolution-completeness-checklist). 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 can say where the request, the hours and the amendment each live, and that a project code ties them, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce its leadership.

## 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
