Reputifly editorial · Reviewed 27 September 2026 · 2 min read
Collect the files and decisions a project needs without losing track of ownership, versions or permission.
Ask for assets by deliverable
For each page or campaign, list the logo, copy, photographs and business details required. Explain the format and who will approve it. The current Reputifly Cloud page is an asset uploader that generates direct links; do not treat a direct asset URL as a private approval record.
Only upload material suitable for the intended sharing arrangement. Keep private client records and approval discussions in the agreed restricted project system.
Use a simple collection register
| Field | Example |
|---|---|
| Deliverable | Service page hero image |
| Source | Client-provided original |
| Permission | Approved for public website use |
| Owner | Named client approver |
| Status | Awaiting approval / approved / superseded |
| Version | File identifier and approval date |
Review the original before formatting
Check resolution, orientation, legibility and any sensitive information visible in the file. A screenshot suitable for a private discussion may contain details that should not be published. Confirm permission before turning it into a public case-study image.
Make approval specific
Ask the approver to identify the exact version and intended use. An acknowledgement that a file was received is not the same as approval to publish it. Record requested changes beside the asset and keep superseded versions out of the active publication set.
Close the handoff
Before launch, reconcile the register against the actual website or campaign. Confirm that all required assets are present, approved and readable on the target devices. Retain original files so future updates do not depend on a compressed screenshot copied from the live page.
View Reputifly Cloud or discuss the collection workflow for your project.
