TAP TAP GO
Store more than the file
For each photograph, chart, case summary or document extract, record its subject, date, source, approved use and owner. Keep the original alongside approved derivatives. Avoid a folder of attractive images with no explanation of what they show. Add a short note about claims the asset supports and claims it does not establish. This makes reuse more deliberate.
Review the new context
Before placing an asset in a different proposal, check whether the audience, claim or distribution channel changes its meaning. A photograph from one project should not imply work on another. A historical chart should not look current simply because it appears in a new design. Keep updates connected to all active uses where practical. The library should make accurate communication easier, not encourage automatic reuse of whatever looks best.
Put the guide to work
Tag assets by the decision they help explain, such as layout, delivery process or team capability. This is often more useful than sorting only by file type. A writer can then find relevant evidence before choosing the most visually attractive item in the folder.
Hypothetical example
A team reuses a successful project image in a new service brochure. The asset record reminds the designer that the photograph shows a specific client installation. A clear caption preserves that context instead of implying the image represents every deployment.
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.
