What to Include in UGC Proof Requirements

2026-09-09

Proof requirements should make review easier, not create a surprise assignment after production. Define what evidence is needed for each deliverable and explain what it demonstrates.

Distinguish Files From Published Posts

For content-only work, the final video or image files may be the deliverable. Check that the files open, match the requested format, and correspond to the agreed version. For published work, also request the post URL, publishing account, date, and final caption. A screenshot alone can omit context that a working link provides.

Specify Timing

If you need performance screenshots, agree on when they should be captured and which metrics matter. A screenshot taken immediately after posting cannot be compared fairly with one taken several days later. Include the capture date with each submission and avoid treating estimates as verified results.

Keep the Handoff Organized

Use a consistent naming pattern that identifies the campaign, deliverable, and version. Keep captions, links, and usage notes alongside the relevant asset. Avoid asking creators to expose private messages, account credentials, or unrelated audience information as evidence.

Review Exceptions Explicitly

If a link is unavailable or a required screenshot cannot be obtained, document the reason and discuss an alternative. Do not quietly substitute another post. Review the submission against the original requirements and provide one consolidated list of missing items. This keeps proof collection focused on the work rather than on unnecessary administration.