Acceptance criteria for influencer deliverables are the observable requirements a creator’s submission has to meet before signoff. Put them in the brief, assess them against the delivered files and record any remaining item with a clear correction and deadline.
What is a checkable requirement?
Write each acceptance criterion so two reviewers can reach the same result. “Show how the tote closes in the first ten seconds” is checkable. “Make it feel more premium” describes a creative preference that needs a reference or a more specific direction.
- List the deliverable, file type, dimensions, caption and destination for each platform.
- Identify claims that require substantiation and the disclosures that must appear where the audience encounters the endorsement. FTC Endorsement Guides Q&A
- Define the reviewer, review window, correction process and any contractual link between acceptance and payment.
What happens when a submission partly passes?
Record each item’s disposition. Fictional example. A creator submits a horizontal video cropped from a vertical source, the final caption and a post preview without the required link.
| Item | Requirement | Decision |
|---|---|---|
| Video | Vertical 1080 × 1920 export with the full product demonstration visible | Return for a new export |
| Caption | Approved copy and readable disclosure | Accept the caption as submitted |
| Link | Tested campaign URL present in the agreed placement | Keep open until the creator supplies a working preview |
Treat the overall package as pending if the brief requires all three items. If the team wants to waive a requirement, record who has authority to approve the exception and notify the creator in writing.
What should the final approval record show?
Keep the version references and approved files, along with the date and identity of the reviewer. Check that the published placement matches what you accepted. Later’s workflow documentation illustrates an implementation of draft submission and review. Later Influence draft review
For creator-post ads, run a separate platform preflight once the deliverable has been accepted.
Add each criterion to the deliverable checklist. Use the revision workflow for outstanding fixes and send the agreed payment trigger and approval evidence to the payout reviewer.
Build a brief that can be tested
Start with what the creator needs to deliver and why the audience needs it. A useful example requirement is “Show the shopper removing the laptop while the tote remains upright.” That gives a reviewer an observable moment. Identify any supporting footage and whether the creator can choose the setting. Document a specific time limit where the placement requires it. Keep formatting details near the asset reference rather than scattered across several messages.
List the required variants independently. A creator may owe a clean export and a version with captions. If one file is for paid promotion, include the appropriate cropping and claims instructions as agreed. Define which caption, account, product link and disclosure travel with each version. Add the intended review method, such as opening the actual file and testing the URL in a preview.
- VideoWrong aspect ratio. Return for replacement export.
- CaptionMatches the reviewed text. Accept as submitted.
- LinkMissing from the preview. Keep this criterion open.
- PackagePending until the required items pass or a waiver is documented.
Split the review into technical and content checks
A technical reviewer can verify playable files, export dimensions, duration, subtitles and link destinations. A content reviewer can check the product demonstration, claims, headline or disclosure. In a lean team, one person may perform both roles. The record should still distinguish the two decisions so a replacement export can be checked for the right things.
When a deliverable fails, mark the failed criterion and path to acceptance. A blurry logo or clipped caption may be repairable without reshooting. A misleading claim may require a new script and independent review. Send the creator one combined packet with the current asset ID, required changes and deadline. Any resulting change to payment or scope should refer back to the agreement.
Decide how to handle missing and waived items
Fictional package. The approved caption has an accurate link and text, the final video is the wrong orientation, and the creator has supplied an organic post draft without the required link visible in the agreed location. Mark the caption accepted, the video requiring a new export, and the link pending in the publish preview. If the brand decides to accept a different aspect ratio, record who authorized the change and which placements remain possible.
Keep the package status fit for the agreed trigger. When a fixed fee is payable after full acceptance, a technically accepted caption may leave the package in review. Where the agreement allows payment on separate milestones, finance can verify each milestone in its own record. Give the creator a clear breakdown of what remains to be delivered, rather than putting the entire negotiation into a free-text status.
Check the post after acceptance
Acceptance of a draft and verification of an actual post can be separate events. Identify who opens the public placement, which details they check and how they confirm the date. Capture the link, timestamp and matching asset version. For a post that shows a different crop, caption or destination, bring the affected requirement back to the proper reviewer. A reviewer should be able to find the approved package from the visible link without relying on a last-minute chat message.
Close the review by giving finance and operations the information they need. Operations needs the correct file and any planned changes. Finance needs the agreed fee trigger, the evidence ID, date and approval owner. The creator should be able to see what was accepted and whether anything remains open.
Review a timed product demo with variant deliverables
Fictional launch. The brief requests a 30-second vertical proof, a 10-second cutdown and a caption. The vertical proves how a laptop can be removed without moving a lunch container. The cutdown requires that same action to remain visible. The reviewer accepts the main video and finds that the short edit ends a second before the laptop removal finishes. Give that edit a specific fix and keep the main video’s acceptance in the ledger.
The team can choose to run only the full video while the creator corrects the short one, if the campaign and agreement allow it. Note that this choice changes the published placement schedule. The owner should be able to find exactly which version was accepted and which still needs a correction. Save a new review if the short edit needs different claims, disclosures or placement.
Close out the review with evidence someone else can open
A complete approval record includes the asset IDs, agreed format and review date, whether each requirement passed, and who made the decision. A partial approval also includes the follow-up item, next reviewer and deadline. For an approved alternate use, record which placements it covers. Make the approval clear enough for finance to assess whether the fixed-fee trigger passed and for the publisher to load the right files from the same packet.
Define separate tests for the master and each export
Fictional handoff. A headphone brand orders one vertical demonstration plus a clean copy for an approved brand channel. The creator supplies two files. The creator-post version contains the correct disclosure and captions, and the critical detail is visible with the expected interface overlays. In the clean version, a caption still says “link in my bio,” which cannot work on the brand placement. Treat the exports as separate items in the acceptance record. Preserve the creator post’s passing tests and send a narrow correction for the clean file.
| Requirement | Where to check | Decision in the example |
|---|---|---|
| Visible microphone setup | Both final exports | Pass |
| Caption and placement-specific CTA | Each final export | Creator post passes, brand export needs a revision |
| Sound clearance for planned use | Rights record for each destination | Confirm before brand distribution |
| Link opens intended offer | Actual link and destination | Creator post approved once verified |
| Delivery version | File identifier and final caption record | Log separately for both exports |
Before assigning the work, confirm which requirements belong in the agreement. Include the product details the creator must visibly demonstrate, the files and captions they must submit and whether the approver will inspect a private preview or final downloadable file. Make each test observable. A reviewer can check that the connector is visible at the expected moment. A requirement to feel premium gives them less guidance about what to accept.
Record partial acceptance and the remaining decision
An approval note should identify the item and version, criteria checked, approver and any permitted follow-up. In the fictional package, the clean-copy hold remains visible even when the creator post is accepted. If the agreement assigns a separate fee to each deliverable, the record can show which fee has cleared and which awaits acceptance. If one package fee depends on both, keep the accepted item in the tracker but leave the payment status at the applicable contract milestone. The producer should avoid inventing a proration rule during review.
Ask a second person to reproduce the decision from the packet. They should be able to open the exact export, place it in the intended context, identify the failing line and explain which work can proceed. When the creator supplies the corrected brand version, verify the changed line and check that earlier accepted details survived the edit. Record the final acceptance on the revised file. Send finance the accepted record together with the agreed payment trigger so it can decide from the same evidence.
Calibrate two reviewers with the same sample asset
Before accepting live work, have reviewers separately mark a sample with one passing criterion, one failing criterion and one judgment that requires clarification. Compare their results and rewrite ambiguous checks. In the microphone demonstration, “connector is visible” can mean the viewer sees the port or that they can see the plug engage. The brief may need the latter because the purpose is to show correct setup. Clarify the expectation in advance and label the example.
Distinguish objective checks from subjective review where both belong in the agreement. An objective requirement might name the approved product name or file format. A brand voice check can specify the degree of flexibility and the person with final judgment. If a reviewer invents a new preference after delivery, ask that person to categorize it as a change request before counting it against acceptance. The creator can then see which work corrects an agreed criterion and which work would change the scope.
When confirming acceptance, summarize any accepted deviation and its limitation. For example, a cropped frame might be approved for a vertical creator post because the relevant detail is fully visible there. Treat that as a decision about the named version and placement. If a horizontal cut is proposed for another channel, verify how the detail survives that crop before carrying the approval over.
