Keep the record and the reason together.
Three fictional profiles / a common product use case
Keep the source and scope attached to the work.
A reason to include each candidate and explicit unanswered questions
The next owner needs enough context to understand the deliverable.
Record what would remove a candidate as clearly as what added them.
A named owner should be able to accept, revise or reject the direction.
Define a relevant example
Record the audience, product category and kind of demonstration the brief requires. Save source examples and explain why each is relevant. A large audience in an unrelated category may be a weaker fit than a smaller, relevant body of work.
Treat headline metrics carefully
Keep the date, metric definition and source with any number you record. Public views and engagement do not independently verify sales, audience quality or the likely outcome of a collaboration. Note when useful information is not available.
Illustrative photography / not customer workPrepare the questions for your team
Before outreach, list the terms, rights, availability and results that need direct verification. Keep notes separate from verified statements. This checklist supports a review process; it does not contact creators or determine who your team should hire.
Write a reason for every candidate
Start with a category and use case, then identify content that is relevant to the question. Save the source example and explain why it belongs. A profile count or follower headline is not a substitute for content context. Make the inclusion rule clear enough that another reviewer could apply it to a new candidate without guessing what the first researcher meant.
Leave the partnership questions open
Audience fit, product relationship, permissions and availability need separate checks. Do not imply a creator is an affiliate, customer or willing partner because a product appears in a post. Give the shortlist a review owner and record what still needs verification before outreach. No outreach is performed by this demonstration.
Try it on one small piece of work.
Choose one category question and a small product set. Record the identity, source and observation date before looking at a change. Create a separate list of commercial facts to verify. Ask another reviewer whether the available evidence supports the proposed next step, or whether the record needs further investigation first.
The exercise can end with a decision to wait. Missing product identity, an inconsistent comparison window or an unverified relationship can be a reason to investigate further. Keep that reason in the record so the next person understands why a promising-looking observation did not become a commercial recommendation.
Questions for the person reviewing the handoff.
- Is the product identity consistent across the comparison?
- Can I inspect the source and date behind the observation?
- Which commercial facts remain unverified?
- Who owns the next review or verification task?
The reviewer should be able to answer these questions from the handoff itself. Add a missing source reference or a clear unknown rather than relying on a verbal explanation that disappears after the meeting.
Use the planning templates for this workflow ↗Use the structure. Verify the substance.
This guidance helps organize product and creator research. Content observations do not establish verified sales, inventory or commercial relationships. TikTokData is in development and no live commercial feed is connected.