Docs

Review applications

Updated Sep 22, 2026
/docs/brands/applications.mdView as Markdown

The application review queue for a campaign — the stage tabs, search, sort, filters, card and table views, and every decision, from approve and reject through scheduling, visit completion, no shows, reschedule requests, notes, and archiving.

Working a campaign's application queueVideo coming soon

Every creator who applies lands in the campaign's application queue. The queue is organized as a pipeline: each application sits in exactly one stage, and your decision moves it to the next.

What this is and when to use it

Use it when:

  • New creators have applied and are waiting on a decision.
  • A creator has booked and you need to record that the visit happened, or that it did not.
  • The creator has posted and you need to record the submission.
  • You want to withdraw a creator who should not be in the pipeline any more.

Do not use it to:

Reviewing applications end to endVideo coming soon

Read the pipeline

The Product Seeding pipeline and its shipping stagesVideo coming soon

The stage tabs sit across the top of the applications page. Each tab shows how many applications it holds.

Visit pipeline (for a Physical campaign):

StageWhat it holdsPrimary action
AssessingNew applications waiting on a decision.Approve
SchedulingApproved creators who still need a visit booked.Create schedule
ScheduledCreators with a booked visit.Mark visit completed
CompletedCreators whose visit is done.Submit the Post
PostedCreators whose content is recorded.Submit the Post

Product Seeding pipeline (for a Product Seeding campaign): Pending, Fulfillment, In Transit, Delivered.

Exit buckets: Rejected, No Show, Archived, and Withdrawn. These tabs render only when they hold something, or when you open them directly.

NOTE — The seeded and visit pipelines are different on purpose. A Product Seeding campaign never shows visit stages, and a Physical campaign never shows shipping stages.

Find an application

  1. Open the campaign's applications from See Applicants on the campaign card, or from the campaign's own page.
  2. Pick the stage tab you want to work.
  3. Use the search box to filter by creator.
  4. Use the sort control. Each stage opens on a sensible default — soonest appointment first for Scheduled, newest applications first for Assessing, and so on. The choices include soonest appointment, latest appointment, creator name A–Z and Z–A, and newest approved first.
  5. Open Filter for stage-specific filters. On Scheduled you can filter by location and by appointment date, with a Today shortcut. On Assessing you can filter by withdrawal history.
  6. Select Reset controls to clear the search, the filters, and the sort in one action.
  7. Switch between Cards and Table with the view toggle. The table lists Creator, Social, Location, Notes, Stage, and Actions in columns; the card view gives each application more room for its status chips.

The page header carries a menu with View Campaign, Share Campaign, Refresh Data, and Edit Campaign, plus a link to the campaign's public page.

IMPORTANT — The campaign header explains a campaign's own state: a campaign in review can take up to 48 hours, and a completed campaign is closed to new creators but keeps its applications and data visible here.

Decide on a new applicant

  1. Open the Assessing tab.
  2. Read the application — the creator's profile, their social accounts, and any notes.
  3. Select Approve to accept the creator. Approval commits on the first click and moves the application on to scheduling.
  4. Select Reject to decline. The Reject application? dialog takes an optional Rejection reason, which is saved with the application and shared with the creator. Confirm with Reject.

If the campaign has an approval limit, the page warns you: Approaching approval limit shows how many slots remain, and Your approval limit has been reached! explains that you must request an increase to approve more creators.

Schedule a visit

Booking a visit and closing it outVideo coming soon
  1. Open the Scheduling tab.
  2. On the application, select Create schedule.
  3. Pick the slot, or the location template with a date and time, then confirm with Schedule visit.
  4. Add an optional note for the creator — it travels with the booking.

NOTE — On a campaign where creators choose their own time, the dialog explains that no agent booking is available: the creator reports the visit themselves. See Campaign schedule.

Record what happened at the visit

  1. Open the Scheduled tab.
  2. Select Mark visit completed on the application.
  3. Read Mark visit completed? — it records the visit as completed, and only visits whose scheduled time has already passed can be marked this way. Confirm with Mark Completed.
  4. When the creator misses the appointment, use Mark no show instead. The Mark as no show? dialog moves the application to the No Show bucket and marks the appointment as missed; it cannot be undone from there.

Ask to reschedule on the same menu sends the creator a request to pick a new time. Fill in Message to the creator (up to 120 characters) and confirm with Reschedule.

Record the posted content

  1. Open the Completed tab, or Posted once content exists.
  2. Select Submit the Post.
  3. Add each post as a row: choose the platform, paste the post URL, and validate it.
  4. Fix anything the row flags — an invalid URL reads Invalid URL., and a URL from the wrong platform reads URL doesn't match <platform>.
  5. Submit when every row validates. The submission is recorded against the creator, and the content is what the campaign reports on.

Keep notes and contact details

  1. Open the application's actions menu.
  2. Choose Edit note to record a brand-side note, or Edit creator note to write a note that is shared with the creator.
  3. Choose Copy email to put the creator's email address on your clipboard, ready to paste into your mail client or CRM.

Take an application out of the pipeline

  1. Open the application's actions menu.
  2. Choose Archive.
  3. Confirm Archive application? — it moves the application to the Archived bucket and removes it from the active pipeline. It stays viewable there, but it cannot be moved back.