What the reader needs

When showing how a process works, decide whether real customer information is necessary. In many cases, a clearly labelled demonstration document can explain the steps just as well. Use fictional names and values that cannot be mistaken for a live customer record. Avoid placing plausible secret credentials or full payment details in examples. The demonstration should be realistic in structure while making its non-production status obvious to anyone who encounters it outside the original presentation.

How to review it

Create a dedicated example asset rather than repeatedly editing a live document for screenshots. Review the filename, metadata, comments, embedded links and visible content. Ensure the example cannot accidentally send a viewer into a real customer folder or transaction route. Keep it in a separate location from operational records and review it when the workflow changes. If a real case is essential, use the approved permission and redaction process instead of assuming that changing a name is enough.

Imagine this

Hypothetical example

A tutorial explains how to share a project pack using a fictional company and sample files. The links lead only to demonstration assets, and the page labels the scenario clearly. Readers learn the workflow without seeing a client’s actual documents or confusing the example with a live offer.

Make it practical.

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

References & further reading

Further reading: Google Drive: Share files ↗

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