# Client system history without inspecting content | SourceX

Canonical: https://refer.sourcex.si/guides/how-to-document-a-client-s-system-history-without-inspecting-content
Last updated: 2026-11-05

Build the timeline from three places that never require opening a record: your own service records (contracts, project tickets, invoices and the software inventory you already keep), what the client's system owners tell you, and decisions only the CEO makes. Write the source beside every answer. If a question can be answered only by searching, counting, sampling or exporting the data itself, it is not yours to answer; leave it blank for the company to fill in when it applies to SourceX.

The timeline is a briefing for the CEO, not an inventory for SourceX. Counting the cutovers in a company that changed platforms several times is covered in [the system-history canvas](/guides/the-company-has-changed-systems-three-times-what-to-ask), and the general idea of describing systems without exposing them in the [metadata-only inventory guide](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems). This page adds the rule those leave implicit: every line on the timeline says how you know it.

## The line between a system's history and its contents

A system's history is its life story: what it is called, who supplies it, what work it records, when it went live, what moved across at each migration, which retention settings apply, who administers it and when it is due to be switched off. Its contents are everything inside: the records, attachments and names, and any figure you could only get by querying them. You can write the first without touching the second, and for a referral you must.

Four verbs cross the line. Each has a version that feels harmless.

| Verb | The harmless-sounding version | Why it crosses the line |
|---|---|---|
| Open | "I'll look at a few old records to see how detailed they are" | You are reading client records for a purpose the client never set |
| Search | "I'll check whether the archive mentions warranty claims" | A search result is a statement about content |
| Count | "A quick count on the tickets table, just for scale" | A query over client data, run for a third party's question |
| Export | "Let me pull one month as a sample" | A copy of client records now exists outside its system |

Much of the history may already be in your files. If your practice follows the CIS Critical Security Controls, Control 2 asks an enterprise to actively manage (inventory, track and correct) all of its software, and its first safeguard keeps an inventory of licensed software with each entry's title, publisher, install date and business purpose, reviewed at least twice a year (paraphrase). Where you maintain that inventory for a client, the first rows of the timeline are written before you speak to anyone.

## The system event that makes the history worth writing down

Nobody needs a timeline until something is about to change. The usual prompts are a system retirement, a migration that will leave history behind, an acquisition that brings a second set of systems, a change to retention or deletion settings, or a vendor's end-of-life notice with a date on it.

The person who commissioned that project, often an IT director, a COO or the owner of the system concerned, is the natural sponsor. Ask that person before you compile anything: a timeline written for a referral uses the client's information for a purpose outside your service, so it needs the sponsor's agreement first and the CEO's before it leaves the company. Under the program the CEO alone decides whether a licensing conversation happens and signs for the company. How to record that agreement is shown in [documenting client consent for a referral](/resources/how-to-document-client-consent-for-a-referral).

## The systems timeline questionnaire

Twelve questions, grouped by what they establish. The middle column limits where an answer may come from; the right-hand column is the label it carries on the page.

| # | Question | Where the answer may come from | Label |
|---|---|---|---|
| 1 | What is each system called, and who supplies it? | Your software inventory or contract records | Our records |
| 2 | What work does it record: orders, tickets, claims, designs, something else? | The system's owner at the client | Owner said, with date |
| 3 | Who administers it day to day? | Your access records or the client's IT lead | Our records |
| 4 | When did it go live? | Your original install ticket or invoice; otherwise the owner | Our records, or Owner said |
| 5 | What did it replace, and what crossed at that migration: full history, balances only or a snapshot? | Your migration project file; otherwise the owner | Our records, or Owner said |
| 6 | Is the older system still readable, read-only or gone? | Your service records or the owner | Our records, or Owner said |
| 7 | Which retention or deletion settings apply, and when were they last changed? | Your configuration notes or the client's compliance lead | Our records, or Owner said |
| 8 | Is a switch-off or end-of-life date set? | The vendor's notice or the project plan | Our records |
| 9 | How many years of history does it hold? | The owner's answer | Owner said, or Estimate |
| 10 | Roughly how much does it hold, in the owner's own band? | The owner only, never a query | Estimate |
| 11 | Who created the records: the company's staff, its customers or both? | The owner's answer; rights are checked later by SourceX | Owner said, or Unknown |
| 12 | Does the CEO know about the idea and want the conversation? | The CEO | CEO said, with date |

Four labels cover every answer. "Our records" names the document it came from. "Owner said" carries a name or role and a date. "Estimate" is a band someone at the client offered, never a number you computed. "Unknown" is a legitimate answer, and on a timeline built from the outside it will be common. Questions this page never asks you to answer at all: what a typical record looks like, whether records contain personal details, how many mention a topic, and what the archive would be worth.

**Method note.** Twelve questions, assembled on 2026-10-27. What a company lists when it applies, and what SourceX completes with it, comes from SourceX's how-it-works page; the size and rights tests from its screening page and its Version 2026-10-22.2, since replaced by version 2026-11-04 terms; and the inventory fields an MSP may already hold from CIS Control 2. It has not been tested on client engagements, and nothing has been published on how often an outside-in timeline matches what a company later lists.

## The custodian's notes, the owner's answers, SourceX's review

Three parties touch the timeline, and none does another's job.

| | Your firm, as technical custodian | The company: system owners and the CEO | SourceX |
|---|---|---|---|
| Contributes | Rows 1, 3 to 8 from service records, kept under your contract's confidentiality | Rows 2, 9 to 12; corrections to everything else | Nothing until the company applies |
| Decides | Nothing about licensing | Whether the timeline leaves the company, and whether to talk to SourceX at all | Fit, rights and the processing route, after it has the company's own description |
| Never does | Query, open or copy records; hold the company's inventory | Hand you files to "help" | Ask a partner for the company's records |

When the company applies, it lists its systems, its years of history and what can be exported, with no records changing hands, and SourceX completes the inventory with the company and runs its rights check. SourceX also says the companies that qualify list at least five systems, so a timeline that shows the CEO quickly how many systems the company has run is useful preparation. It stays the company's preparation. Section 4.2 of the unsigned partner agreement sample gives a partner no authority to pass on a supplier's inventory, records, raw data or personal information, and section 4.4 bars a partner from collecting or keeping dataset copies through the program without separate written authorization. Partners never see, upload or handle a company's records, inventory or data room, even when their IT work would let them.

## A property manager's fifteen years on one page (Illustrative)

Illustrative. A 310-person property management company has used the same MSP since 2010. Systems, dates and sources are invented, and no outcome is implied.

| Year | Event | System | How we know |
|---|---|---|---|
| 2010 | Accounting platform goes live | On-premises accounting | Our records: original install ticket |
| 2013 | Maintenance requests move into a hosted work-order app | Work-order app | Owner said: facilities director, March 2026 |
| 2018 | Email and files move to a cloud suite, mailboxes migrated with full history | Cloud suite | Our records: migration project file |
| 2021 | A tenant CRM replaces spreadsheets | CRM | Our records: license invoices |
| 2024 | A new maintenance platform replaces the work-order app, which is kept read-only | Maintenance platform | Our records: cutover ticket |
| 2026 | The read-only work-order app is due to be switched off in November | Work-order app | Our records: vendor's end-of-life notice |

Three blanks stay blank on purpose: the volume band for work orders (the facilities director will estimate it if the CEO wants to proceed), whether requests typed in by tenants count as the company's own records (a question for SourceX's rights review), and the CEO's view (not yet asked). The November switch-off is the one fact that sets timing. It is documented, so it is a fair reason to put the question to the CEO this quarter; it is never a reason to copy the old app's records "while we still can".

## Handing the timeline to the CEO, not to SourceX

Take the page to the sponsor, then to the CEO, in a short meeting or as a one-page note. The CEO may correct it, add to it, keep it or bin it. If the CEO wants the conversation, your introduction note carries only what the CEO confirms: the company's name, the CEO, the peak full-time headcount as the CEO states it, and the number of systems and span of years in plain words. The timeline itself stays with the company, which can use it when it applies.

Leave out anything a console produced: inventory exports, admin screenshots, license reports and storage graphs. Leave out estimates of value and any claim that the company will be accepted. If the client sits outside the U.S., keep the published rule in its own words: 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.

## When an outside-in timeline misleads

- **Systems you never managed.** Departmental software bought on a credit card never reached your inventory. Ask the owner what is missing rather than assuming the list is complete.
- **History before your contract.** Your records start when you were hired. Earlier eras are "Owner said" at best.
- **Installs are not retention.** An inventory shows that software was installed, not what it still holds. Deletion settings and real deletions can differ.
- **Vendor-hosted systems.** Where records sit in a supplier's platform, that supplier's terms can bear on rights, which only SourceX's review settles.
- **Labels that fall off.** An "Estimate" retyped into an email becomes a fact. Keep the label on every copy, or leave the figure out.
- **Groups.** If the client belongs to a larger group, a parent and its subsidiaries share one reward cap, and whether a sister company's earlier contact with SourceX changes anything for you is decided in SourceX's duplicate review.

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

Once the CEO has seen the timeline and wants to talk, [sign up as a partner](/register), set the CEO's own figures beside the [screening criteria](/who-qualifies) and the [program terms](/terms), and send an introduction that carries none of your service records.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://www.cisecurity.org/controls/inventory-and-control-of-software-assets
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
