Instagram follower check: request the minimum evidence the decision needs

Map each decision to evidence

List the actual tasks: size eligibility, audience geography, content performance or paid-media permission. They should not all become a request to send every dashboard screenshot. Remove fields that would not change the current decision. A smaller, well-defined evidence request is easier to answer and review.

The metric-definitions guide helps explain why a number is needed. The creator should understand the purpose rather than guess whether the brand is conducting an open-ended investigation. More information does not automatically improve the judgment. Decide which condition can be checked publicly, which requires voluntary evidence and which is not necessary until a later commercial stage. This keeps early research proportionate and avoids demanding extensive private reporting from people who have not yet been told what the assignment involves.

Use public records where sufficient

Public material can support account identity, work samples and approximate size. It does not automatically establish audience geography or private performance. Preserve the URL, date, raw display and precision. Leave absent information unresolved rather than infer that the creator meets a condition because nothing contradicts it.

The account-identity guide helps avoid matching the wrong person. If public size evidence is sufficient for exploratory research, do not ask every initial lead for a complete private analytics package. Move the conversation forward with the information already available. Request additional evidence once the assignment and mutual interest are clearer. This creates a staged process in which the burden corresponds to the decision, rather than collecting everything at the first contact because the team has not agreed what it actually needs.

Request a dated summary rather than a personal list

When audience geography matters, state the target market, reporting window and summary field you need. Allow unrelated information to be redacted and retain the date and source description of the supplied file. A targeted request is more useful than a broad demand for proof that the audience is good.

Do not request a full list of individual followers to establish an aggregate regional share. Summary evidence has limitations too. Label whether it was supplied by the creator or obtained through an authorized tool. A dashboard-looking image is not automatically independently verified. Ask a clarifying question when the window or field is unclear, and keep the answer with the record. The aim is enough evidence for the stated condition, not unrestricted access to everything the creator can see.

Explain authorization when necessary

If a connected-account tool is genuinely needed, explain which data it reads, why, who can see it, how long access lasts and how it can be withdrawn. “This is our standard process” is not a complete explanation. The brand should also know how it handles records already obtained after access ends.

Meta Safety Center advises users not to share login details and describes permission-status management. A scoped authorization process is different from sending a password to a brand. Do not conflate the two. Check the actual tool’s current requirements rather than promise a specific permission scope based on a generic integration label. If the team cannot explain the access it requests, pause that route and use a more limited evidence method while the requirement is clarified.

Do not equate limited access with suspicion

A creator declining unrelated access may simply be setting a reasonable boundary. Ask whether the field is genuinely required and whether a narrower alternative can support the condition. Refusing to share a password is not a fraud signal. Do not punish a sensible access boundary by attaching an unsupported authenticity label.

If an essential condition cannot be verified, the brand may decide not to proceed with this purchase. Record the reason as insufficient evidence for the assignment, not proof of cheating. The review-memo guide helps separate observation from conclusion. This distinction matters for future work: someone unsuitable for a data-heavy campaign may still be appropriate for a production-only commission that does not require the same private audience evidence. A proportionate process keeps those options visible.

Worked example: reduce the request

Suppose the initial request asks for a full follower list, three months of every dashboard and account login. The actual conditions are target-country audience relevance, current size and one relevant work sample. Reduce the request to a public snapshot, a dated geography summary and the work link. These are hypothetical process choices, not a claim that every project can use the same evidence.

The revised request may not answer every possible question, but it can support a defined initial screen. If the next stage requires advertising permissions, explain and obtain those separately. Research-stage evidence should not silently become continuing account access. Keep the request, response and decision together so a new teammate can see what was authorized and does not assume a supplied screenshot implies consent to connect another tool or reuse private data for unrelated research.

Make the request answerable and closable

The message should name the project, requested fields, date requirement, redaction options, recipient and next step. Close the request when the decision is made. Handle the material according to the agreed purpose rather than leave unsuccessful candidates’ files indefinitely in an ownerless shared folder.

Use the metric-definitions guide, account-identity guide and review-memo guide to move the collaboration forward with appropriate evidence. QuickKOL can help prepare research and personalized outreach; access to private account information still requires the relevant person’s authorization. A good follower check produces a clear decision and a limited evidence record. It should not turn a routine commercial conversation into an unexplained demand for permanent control of the creator’s account.

How do you ask when a screenshot is insufficient?

Name the missing element: date, window or field definition. Ask for that clarification first instead of saying prove you are real. If the evidence still cannot support a hard condition, mark it unverified and explain its effect on this assignment. A specific question is easier to answer and less likely to imply an accusation that the available facts do not support.

Research date, evidence and limitations

Sources reviewed October 23, 2026. Workflows are editorial recommendations. All worked examples are hypothetical, not client results, creator rankings or quotations.