How to collect missing creator campaign screenshots without repeated follow-ups

The sponsored posts are live, but the campaign report still has gaps. One creator sent a view count. Another sent account-wide data for the month. A third says a requested metric isn't visible in their dashboard.

Make each request specific to one delivered content item: what it is, which metric you need, the reporting period, and the context the evidence should retain. Keep what you already have, follow up only on the gaps, and record unavailable data with a reason.

This guide covers reporting after a collaboration. If you're assessing a potential partner's past performance, use the pre-collaboration metrics checklist. A creator who has completed a campaign shouldn't need to resubmit an entire media kit to close out a few missing figures.

Build a content-level collection list first

Before asking for “all campaign data,” list the content that actually went live. Give each item its own entry, check the reporting scope agreed for the collaboration, and identify what is still missing.

Keep at least these details for each item:

• Content identity: creator account, platform, content link or recognizable reference, and publication date.
• Requested metrics: the agreed measures, retaining the platform's original labels where useful.
• Reporting scope: lifetime totals as of a particular time, or a selected date range. Record the capture time separately.
• Evidence received: screenshots, exports, or a read-only report link supplied by the creator, with a reference to where the material is stored.
• Collection status: complete, outstanding, or unavailable with a reason.

OneCrew helps teams organize creator records and collaboration communication. Review the recorded messages to confirm what reporting was promised, then add the content links, locations of received materials, and a short list of missing items to the creator's notes. A teammate can pick up the specific gap instead of sending another generic questionnaire.

If a metric wasn't part of the agreement, explain why it would help and ask whether the creator can provide it. A new request should be treated as a new request, rather than an overdue deliverable.

Ask for evidence that answers the reporting question

For a reach-focused review, start with the relevant content's viewing or reach data. Add the available engagement metrics if engagement reporting was agreed. “We might need it later” is a weak reason to request a creator's entire account history or other clients' campaign data.

Use the following as a selection guide. Platforms and content formats do not all offer the same fields.

The party holding the order records should supply them. A creator's view-count screenshot cannot explain the brand's sales report by itself. Keep link clicks and purchases in separate fields.

Platform labels matter too. YouTube distinguishes thumbnail impressions from views, and some off-platform thumbnail displays are excluded from its impression count. Preserve the dashboard's metric name rather than trying to reconcile unlike figures. See YouTube's explanation of thumbnail impressions for the definitions.

Preserve context without collecting unrelated information

A number by itself is difficult to use. Ask for enough context to identify the account or content, metric name, and any displayed date range. The creator can state the capture time in the reply. Use the same content link or reference to connect multiple screenshots.

Data for September 10–16 and lifetime data captured on September 16 describe different reporting windows. Keep cumulative totals labeled as cumulative; keep date-range figures with their actual range. Do not treat the two as interchangeable.

Creators can redact unrelated clients, other collaborations, and private information while retaining the context needed for this request. Two linked screenshots or an appropriate export can work when one image cannot show everything. Account passwords are unnecessary.

Make the first email easy to act on

Check what has already arrived before writing. Reviewing the existing email thread in OneCrew helps you account for previous attachments and prepare a draft focused on the remaining items. The creator shouldn't receive a fresh request for everything just after sending half of it.

These complete examples use a fictional collaboration. Replace the names, content references, metrics, reporting window, and deadlines with the actual agreement. Check that the platform and content format provide the requested data.

Email 1: Collect the reporting already agreed

Subject: Portable-light campaign reporting: videos A and B

Hi Maya,

Thank you for completing the portable-light collaboration. We've recorded the two links you sent: video A is the September 10 unboxing, and video B is the September 12 product-testing video.

As agreed, could you send the views, likes, and comments for each video, using lifetime totals through September 19 at 6 p.m. Beijing time? If your dashboard only supports a selected date range, please state the actual start and end dates.

Please retain a recognizable title or thumbnail, metric labels, and the displayed reporting range in the screenshots or export, and note the capture time in your reply. Label the files A and B so we can match them to the videos. You can redact unrelated client or private information.

Please reply with the screenshots or export by September 20 at 6 p.m. Beijing time. If a metric isn't available, let me know which one, whether it appears in your dashboard, and whether another form of evidence is available. We'll record that separately.

Thank you! Alex

In the actual email, add the content links or use references both sides have already agreed on. “Last week's post” leaves too much room for confusion.

Email 2: Ask only for the missing details

Subject: Reporting received: two details still needed for video B

Hi Maya,

Thank you. We have everything for video A and have received the view-count screenshot for video B. There's no need to resend the full set.

We're missing two details: video B's comment count, and whether the view count shown is a lifetime total or covers a selected date range. Could you send a relevant screenshot of the comment count and confirm the view count's reporting period and capture time in your reply?

If comments aren't visible in that dashboard, please let me know and we'll note the reason. Would September 21 at 6 p.m. Beijing time work for you? If not, please suggest a time you can send the remaining information.

Thanks for helping us complete the record. Alex

Email 3: Close the reporting window while preserving the gap

Subject: Confirming the status of video B's comment data before reporting closes

Hi Maya,

We're preparing the campaign report on September 23. Video B's comment data is the only item still outstanding; everything else you've sent is recorded.

Could you confirm by September 22 at 6 p.m. Beijing time whether you can still provide it? If so, please let me know when. If it isn't available in your dashboard, a brief explanation of the current situation is helpful.

If the information hasn't arrived by the reporting cutoff, we'll mark that field as pending rather than entering zero, then update the record when the material arrives.

Thank you for confirming. Alex

Check the evidence before transferring the figures

Match the account and content first, then check the reporting period, metric labels, and values. If two screenshots conflict, describe the specific difference—such as different selected date ranges—and ask for clarification. “Why doesn't this match?” gives the creator more work to figure out.

A screenshot shows what the supplied image displayed at capture time. Clear formatting alone does not authenticate its source, and missing evidence alone does not establish dishonesty. Resolve questions by checking the particular content, reporting scope, and available supporting material.

Use this record for each content item:

Creator / platform / campaign:
Content link or reference / publication date:
Agreed metrics and original platform labels:
Reporting date range or lifetime cutoff:
Capture time / evidence location:
Received:
Outstanding items and reasons:
Next reply date / internal owner:
How missing data will appear in this report:

Keep “not received,” “unavailable in the dashboard,” and “zero” distinct. For example, if eight of ten expected content items have complete evidence, state that the current report covers eight. This is an illustrative recording method: do not enter zeros for the other two and include them in an average.

After checking the reply, update the creator's OneCrew notes with the evidence location, latest confirmed status, and remaining items. The next email can pick up from that point instead of repeating the original collection request.

Good reporting collection makes the next request clear and keeps unsupported conclusions out of the report. Start with the campaign's communication records in OneCrew, separate what has arrived from what is missing, and prepare a draft that asks only for the outstanding details. The report can move forward while its gaps remain visible.