Skip to content

PREPARATION GUIDE

Build a source pack for your announcement

Connect each material claim to its source, record limitations and prepare a reviewable evidence pack.

Interlocking evidence links connecting a claim to a source index

List the claims before collecting files

A source pack connects the material statements in a release to the information that supports them. Start with the draft and highlight statements about dates, availability, quantities, comparisons, permissions and other details a reader could reasonably question. Give each claim a short reference in a separate working list. This is more useful than sending a large folder and expecting a reviewer to infer which file supports which sentence.

Keep the list proportionate to the announcement. A simple factual update may need only a few sources. A release with several comparisons or separate versions will need more careful mapping. The purpose is traceability, not an impressive volume of attachments.

Choose sources that support the precise statement

For each claim, identify the closest available source and the relevant passage or record. A broad background page may explain a topic without supporting a particular launch date or product capability. Record what the source actually establishes, including any conditions that narrow its meaning.

When a statement comes from an internal record, identify the record owner and the revision used. If the source cannot be shared publicly, explain how an authorised reviewer can inspect it privately. Do not put confidential documents into a public asset folder merely to make them easy to link.

Keep dates, definitions and limits visible

A source can be accurate and still be unsuitable for the sentence you have written. A figure may refer to a different period, a different geography or a different definition. Write those boundaries next to the claim so that they survive revisions of the draft. Avoid combining figures that were collected on incompatible bases.

If a date is provisional, keep that status visible in the working record. If a comparison excludes some products or uses an unusual definition, explain the exclusion. A limitation is part of the factual basis of the announcement; hiding it creates work and confusion later.

Organise the handoff around review questions

Create a short index with the claim, the source location, the relevant passage, the date checked and the person who can answer questions. Use filenames that remain meaningful outside your own computer. Identify the release revision the index belongs to, especially when several people are editing simultaneously.

Test the handoff from the recipient's perspective. Open shared links using the intended access level and confirm that essential files can be read. Remove obsolete duplicates from the handoff while retaining your own revision history. A reviewer should be able to find the current evidence without choosing between several unexplained versions.

Recheck the pack when the copy changes

Treat a changed factual sentence as a reason to revisit its source entry. A small wording change can turn a narrow supported claim into a broad unsupported one. Check captions, headlines and quotations too; they can introduce assertions that never appeared in the main body.

Before approval, resolve open questions or revise the draft to reflect what is known. Preserve the final source index with the approved release. If a later correction is needed, that record helps explain which information was used and what changed. It does not make the announcement permanently correct; it makes the review process understandable and easier to revisit.