In this article
A source ledger connects one sentence to the material that supports it. Keep the observation, your interpretation and the unanswered question in separate fields so the next writer can use the research without changing its meaning.
A ledger row someone else can check
Editorial demonstration: the product observation below comes from a public page. The outreach idea and draft are examples written for this article, not a message sent to the company.
| Field | Completed entry |
|---|---|
| Company / page | Rocketlane — SaaS customer onboarding software |
| Source URL | rocketlane.com/saas-customer-onboarding-software |
| Observed | 10 October 2026 |
| Event date | Not established. This is a product page, not evidence of a launch or expansion. |
| Observation | The page describes customer onboarding and implementation software, including collaboration with customers. |
| Interpretation | A practical customer-handoff example could be relevant to a publication about implementation work. |
| Unknown | Whether the company wants to contribute an example or who owns that decision. |
| Used in | Demo editorial invitation below; no company-wide growth or operational-pain claim. |
Turn the row into a complete message
Demo subject: A customer-handoff example for an implementation guide
Hello Rocketlane team,
Your SaaS onboarding page describes collaboration between implementation teams and their customers. I’m preparing a practical guide about the handoff from a sales promise to an implementation plan.
Would someone on your team be open to contributing one anonymized example of the information an implementation owner needs at kickoff? A short outline covering the promised outcome, the customer’s responsibility and the first milestone would be enough.
If another team owns editorial contributions, could you point me in the right direction?
Thanks,
Avery
Demo editorial project
The message uses the supported product fact and asks about the unknown. It does not assert a partnership, internal problem or current buying need.
Correct the sentence, not just the research note
| Draft claim | Why it fails | Usable replacement |
|---|---|---|
| As your German team grows, onboarding must be getting harder. | In this separate fictional example, the source only announced an independent distributor. | I saw your announcement of a German distributor. Who handles product training for new distributor staff? |
If the announcement covers only one product line, put that scope in the ledger and the sentence. If it merely says products are available in Germany, remove the distributor claim too.
Keep a short correction trail
Changed source: [URL and date observed]
Old claim: [the sentence that depended on it]
New supported claim: [exact scope now established]
Affected work: [account note, email, article brief]
Status: [each affected item corrected, or held for review]
Retain conflicting sources when they disagree. An official product page can establish the company’s offer; a customer complaint can establish what that customer reported. Neither proves an unobserved internal cause. A reply can resolve the unknown, so record it beside the original hypothesis.
Download the source-ledger worksheet (CSV). Use the campaign handoff to package the record and the email rewrite to check the final sentence.