State what the diagram represents

Tap Tap Go’s document and portfolio resources can include a process or responsibility diagram. Explain whether it shows the current workflow, a proposal or an illustrative example. Define important arrows and groupings. A polished diagram should not make a proposed integration or partnership look operational when it has not been confirmed.

Provide a readable companion

Add a short explanation of the central relationship and the questions still open. Ensure the diagram remains understandable at the size people will view it. Where detail is dense, offer a suitable larger resource rather than forcing everything into a small preview. The profile should help the reader grasp the structure without mistaking visual completeness for implementation readiness.

Imagine this

Hypothetical scenario

A hypothetical team shares a proposed onboarding flow. The diagram is labelled as a discussion model, and the companion text identifies responsibilities still to be agreed. It does not imply that the entire process is already deployed.

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.