TAP TAP GO
Record the scope of permission
For each asset, identify the owner, approving contact, permitted channels and any restrictions communicated. Distinguish permission to describe a project from permission to publish a client name, logo, photograph or testimonial. Keep the relevant confirmation where the team can find it. If the situation is unclear, seek clarification before publication rather than relying on an old verbal conversation.
Review new uses separately
A photo approved for a private proposal may not be appropriate for a public campaign. Check whether a new context changes the agreed use. Keep approved derivatives linked to the original asset and note any removal request. Build a substitute set of material so a portfolio does not collapse when a client declines public exposure. This is a workflow for managing permissions, not a legal conclusion about ownership or licensing.
Put the guide to work
Add an expiry or review date where the approval is time-bound or the context is likely to change. The person assembling a new proposal should be able to see immediately whether fresh confirmation is needed. Permission management works best when it is part of asset selection rather than a late-stage interruption.
Hypothetical example
A contractor has permission to discuss a completed project in meetings but wants to use the client logo on a public page. The permission log shows that the new use has not been confirmed. The team asks before publishing and prepares an anonymised alternative.
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.
