This system map belongs to the knowledge handover gaps guide, which explains what a practice acquisition puts at risk. Use it when a client says they "have everything in the wiki" and you need to know whether one gap can actually be followed end to end.
The four systems that hold one handover gap
A gap is never in one place. The documented procedure lives in one system, the exception in another, the sign-off in a third, and the proof that the handover was reviewed in a fourth.
| System | Record it holds | Linking key | Typical owner |
|---|---|---|---|
| Shared checklist workbook | Handover line items, signed by outgoing and incoming teams | Process name, sometimes a page link | Operations director |
| Knowledge base | Process pages with version history, editor and date | Page ID or URL; version number and date | Knowledge base administrator, with page owners |
| Project tracker | Tickets with exception notes, unresolved questions and answers | Ticket key; engagement or client code | Delivery lead or tracker administrator |
| Deliverable record | Client sign-off of the corrected work product | Engagement code and deliverable name | Engagement partner |
Two supporting sources often fill gaps: the transition agreement, which may require departing staff to answer questions in writing, and email, where many client acceptances still sit. Map them, but treat them as secondary; neither carries a reliable key.
The linking keys, one join at a time
Each join has a key on each side, and each breaks in a predictable way.
| Join | Key on the left | Key on the right | Breaks when |
|---|---|---|---|
| Checklist line to page | Page link or exact page title | Page ID | The checklist names the process, not the page |
| Page version to date | Version number | Editor and timestamp in page history | History is deleted, or the page is copied into a new space |
| Page to exception ticket | Link or comment pointing to the ticket | Ticket key, ideally linking back | The exception lived only in a comment with no link |
| Ticket to deliverable | Engagement code on the ticket | Engagement code on the sign-off | Sign-off kept in email, not the tracker |
Confluence Cloud keeps a version history for every page; two versions can be compared, and restoring an older one saves it as the newest without deleting later versions. That makes the version key reliable as long as the page survives. A deleted page waits in the space trash until purged, and purging removes every version and attachment; deleting a single version is permanent. On the tracker side, Jira has no built-in report of when a field value changed, so the timing of a question and its answer sits only in each issue's History tab. Other tools behave differently, and the firm's own administrator should confirm what its systems keep. Partners should not describe a product's export or retention features to a client as fact.
ConfluenceOne fully joined gap (Illustrative)
A fictional 230-person compliance consultancy, the same one used in the worked June year-end case. The table shows every key needed to rebuild one gap. Values are invented.
| Record | System | Key value (Illustrative) | Joined to |
|---|---|---|---|
| Checklist line "Filing process documented: yes" | Checklist workbook | Row 41, links page "Annual filing preparation" | Process page |
| Process page, version 14 | Knowledge base | Page 88213, v14, dated March | Checklist row 41 |
| Exception comment on non-December year-ends | Project tracker | Ticket FIL-1207, 2021 | Page 88213 by subject only |
| New team's question about a June client | Project tracker | Ticket FIL-3390, engagement C-0577 | FIL-1207 by a later link |
| Departing manager's written answer | Project tracker | Comment on FIL-3390 | Page 88213 v15 |
| Process page, version 15 with exceptions section | Knowledge base | Page 88213, v15, dated August | FIL-3390 by link |
| Client acceptance of corrected filing | Deliverable record | Engagement C-0577 | FIL-3390 by engagement code |
Read the "Joined to" column. Every link is explicit except one: the 2021 exception comment matches the page by subject only. That single weak join is common, and it is worth naming in an introduction as an open question rather than smoothing over.
Where the map most often breaks, and what to ask
You do not need access to any system to test the map. Ask the operations director and the administrators these questions and note the answers as metadata:
- Does the handover checklist link to pages, or only name processes?
- Is page version history intact, or have spaces been copied, merged or purged?
- Do tracker tickets carry an engagement or client code, and since when?
- When an exception was found, was it linked to the page, or only mentioned in a comment?
- Where do client sign-offs live: in the tracker, a document system or email?
- Is any space cleanup, tracker consolidation or tenant migration scheduled, and on what date?
Answers like "copied into a new space last year" or "sign-offs are in partners' inboxes" do not rule a firm out. They tell SourceX which joins can be rebuilt and which cannot.
If the firm keeps procedures in shared drives instead of a wiki, the same four joins can run through file revision dates and email; introducing a company with no formal knowledge base covers that case. For wikis as a record type, see internal knowledge bases. During a sale, the seller transition period guide and the IT handover checklist cover the dates when access usually changes.
From the map to an introduction
Once the map is filled in, it supplies most of a referral: the systems, years covered, the joins that hold, the one that does not, and who owns each. The referral brief template puts those answers on one page the owner can forward. Keep it to metadata: no page text, ticket content or client names.
The firm needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions. What stays unknown until SourceX reviews it: which record classes the firm may license, what client details must be removed, SourceX's current data needs and any offer.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the map shows that at least three of the four joins still hold and a migration date is approaching, register as a partner, check the firm against who qualifies and read the program terms before the spaces move.