Choose the preview carefully

Show the title, responsible organisation, date, scope and relevant summary. Avoid displaying only an attractive conclusion while removing qualifications that affect its interpretation. Identify whether the preview is an extract, summary or illustrative cover. Keep text large enough to read and provide a clear route to request the complete document where appropriate. A blurred page thumbnail adds atmosphere but little decision value.

Match access to the review

Determine which readers need the full document and who approves that access. Keep sensitive material in the designated review process. If a new edition is issued, refresh the preview and the linked request instructions. Ask someone familiar with the technical subject to confirm that the excerpt does not overstate the document’s conclusion. The aim is to invite an informed question, not turn a complex assessment into a promotional badge.

Put the guide to work

Give the preview a descriptive link label such as request the current assessment rather than a vague download prompt. The reader should understand what they will receive and whether access requires a conversation. Keep the preview’s date aligned with the document referenced by that request process.

Imagine this

Hypothetical example

A project profile uses a report cover as proof of readiness. The revised preview explains what the report assessed and when, then provides a route to the full document. Readers can judge its relevance instead of assuming the cover confirms every project claim.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.