Influencer Campaign Timeline Template and CSV
Plan an influencer campaign with human-owned dates, dependencies, confirmation states, and next decisions from shortlist to publication.
An influencer campaign timeline should show who owns each event, what it depends on, whether its date is confirmed, and what decision comes next. It should not assume that every creator follows the same number of days from first contact to publication.
Download the influencer campaign timeline CSV and replace or delete its fictional example rows. This is a manual project-planning sheet, not a recipient list for DM Studio and not an automatic scheduler.
Plan decisions, not a universal countdown
A fixed schedule such as “follow up on day 3, receive a draft on day 10, publish on day 14” hides the facts that actually control the project. A creator may need more information before accepting. A physical product may not be part of the campaign. A draft review may require a named approver. Publication may depend on both parties confirming the final asset and date.
Use actual dates only after the person responsible has checked the dependency. If a date is still being discussed, leave it blank and mark the status accordingly.
| Phase | Event or decision | Evidence needed before a date is confirmed | Typical owner |
|---|---|---|---|
| Shortlist | Approve the creator for contact | Reviewed public fit and contact preference | Campaign lead |
| Proposal | Send the first proposal | Approved ask and correct contact route | Outreach owner |
| Brief | Confirm scope and next decision | Creator interest, deliverables, usage, budget path, and open questions | Campaign lead |
| Product | Confirm selection and shipping, if applicable | Creator choice, consent to receive, and a private delivery process | Logistics owner |
| Draft | Receive and review the draft, if requested | Agreed format, reviewer, and feedback route | Content reviewer |
| Publication | Confirm final asset and publication date | Required approvals and creator confirmation | Campaign lead |
| Closeout | Record the outcome and next action | Public link or agreed completion evidence | Campaign lead |
These phases are options, not mandatory stages. Skip product shipping for a digital-only UGC project. Skip draft review when it was not agreed. A no-obligation gift does not automatically create a draft or publication deadline.
What each CSV column is for
| Column | Enter |
|---|---|
campaign_id | Your internal label, with no private address or authentication data |
phase | Shortlist, proposal, brief, product, draft, publication, or closeout |
event_or_decision | One observable event or one decision to make |
owner | The person or role responsible for checking it |
planned_date | A working date chosen by the owner |
confirmed_date | The date both the necessary parties have confirmed, if any |
status | A manual state such as not started, waiting, confirmed, complete, or held |
source_or_dependency | The brief, reply, approval, shipping confirmation, or other evidence |
next_decision | What someone must decide after this row changes |
notes | Short context that does not expose private shipping or account data |
Keep planned and confirmed dates separate. Moving a working date does not rewrite what the creator confirmed. Likewise, a sent proposal is not an accepted brief, and a shipment in transit is not proof of receipt.
Build the timeline in four passes
- Add only applicable events. Start with the campaign's real path. Do not add shipping or publication merely because the template includes them.
- Assign one owner per row. The owner checks the dependency and updates the manual status. “Team” is less useful than a named role.
- Record the source. Link or name the approved brief, creator reply, internal decision, or public post that supports the status. Keep private delivery details in an appropriate restricted system.
- Write the next decision. Examples include “confirm whether the creator wants the brief,” “approve the final asset,” or “hold until usage is agreed.” This keeps a waiting row from becoming an implied approval.
Fictional worked example
Suppose the fictional brand Northstar Desk asks a creator for two paid UGC videos for its brand-owned social account. The campaign does not require a post on the creator's account and does not ship a product.
| Phase | Event | Planned date | Confirmed date | Status | Source | Next decision |
|---|---|---|---|---|---|---|
| Proposal | Send scope summary | 2026-12-02 | Not started | Approved first-message draft | Send or hold | |
| Brief | Confirm two video concepts and brand-social use | Waiting | Creator reply and brief | Agree scope or revise | ||
| Draft | Review two video drafts | Not started | Accepted scope | Approve or request an agreed revision | ||
| Publication | Confirm brand-social release | Not started | Final approved files | Choose release date |
The blank dates are intentional. They prevent an internal guess from appearing to be a creator commitment. The timeline does not predict success or automate reminders.
Checks before sharing the sheet
- Every row describes one event or decision.
- Every active row has one owner and a source or dependency.
- Unconfirmed dates remain blank or clearly marked as planned.
- Optional product, draft, and publication stages are included only when agreed.
- The sheet contains no private address, access token, password, or real customer data.
- Status updates are manual and do not imply reply detection or automatic scheduling.
Use the collaboration brief template before confirming dates, and the content approval checklist when a draft enters review. If the proposal will go by Instagram DM, review the candidate and message with the outreach list guide. DM Studio can preview the prepared recipients and message before you start sending; keep milestone decisions and dates in this manually updated timeline.