Plan a UGC production timeline before launch day

Separate launch, approval and first draft

Start with the date the brand wants to publish, then identify when an approved file must be ready for publishing preparation. A first draft is a different milestone. Calling all three “delivery” hides the time needed to review the work and prepare it for use.

Microsoft's Project documentation describes working from a required finish date to identify when work needs to start. Use that as a planning check, not a reason to postpone work until the last possible moment. Once the project begins, update the forecast from actual progress and availability.

Ask the people doing the work for their own estimates. Filming, editing, brand feedback, agreed corrections, final checking and publishing preparation each need a place in the plan. If paid advertising is involved, identify any separate platform-review requirement; do not assume a finished file guarantees the ad can run immediately.

Define what “ready to start” means

For a physical-product video, sending a parcel is not the same as the creator receiving the correct usable product. Likewise, sending a brief does not mean its open questions are resolved or the creator has reserved time. Confirm those prerequisites before treating the production start as settled.

• Brand: confirm the product, approved brief and required references are ready, and name one person who can collect and return decisions.
• Creator: confirm receipt and condition where relevant, unresolved requirements and actual availability for the proposed work.
• Both: agree the output, review windows, included corrections, dates and time zone. Identify weekends or other unavailable days.
• Brand publishing owner: confirm preparation time after approval and any channel-specific steps outside the creator's work.

Microsoft explains that a finish-to-start dependency means one task must finish before the next can begin. Use that idea only where it applies: product-dependent filming needs the product, while confirming the brief may happen during shipping. Writing dates in separate rows does not make their prerequisites disappear.

Work backward with explicit assumptions

This fictional example uses Day 0 as the desired launch boundary. Every offset is a calendar day measured at the same agreed clock time, not a business day. All owners are assumed available in the listed windows. Real plans must replace these invented durations with confirmed estimates and an actual work calendar.

The work from production start to launch occupies seven calendar days: 3 + 1 + 1 + 1 + 1. The two days before the booked start are a separate allowance for readiness uncertainty. Neither number is a typical UGC turnaround or a Stage service promise.

This example assumes the agreed correction round resolves the feedback. If another correction is needed, revise the plan; the approval slot does not mean the brand should accept an unresolved file. A deadline alone cannot guarantee that every task fits.

Keep targets and confirmations separate

Fill one record for each meaningful handoff. Keep the original target visible when the forecast changes. Record “arrival estimated” differently from “received and usable,” and “approval requested” differently from “approved.” This prevents a tentative date from silently becoming a commitment.

Choose check-ins where a decision can still help. For example, agree when to review an unconfirmed arrival estimate before the reserved filming window. The right check-in depends on the carrier information, creator availability and launch constraints; there is no universal daily-message rule.

Recalculate when the product is late

In the fictional plan, readiness at Day −8 uses one of the two reserved days. Readiness at Day −7 uses both. Either can still fit the booked start if the other prerequisites and availability remain confirmed. The allowance does not cover delays of any size.

Now suppose the usable product arrives at Day −6. First reconfirm when the creator can actually begin. If they can begin immediately and every later window stays the same length, production runs −6 to −3, feedback −3 to −2, corrections −2 to −1, final review −1 to 0 and publishing preparation 0 to +1. The forecast launch is Day +1, one day after the original target. If the creator is unavailable at −6, the delay may be longer.

Make the decision explicit: move the content launch, agree a smaller or different deliverable that can realistically fit, or use existing suitable content the brand is permitted to publish. Check the consequences with the responsible people. Do not silently remove review time, assume unpaid rush work or claim an alternative will certainly rescue the launch.

A useful timeline is a shared set of assumptions and decisions that stays current. It helps the brand see a problem early and choose a response; it cannot remove shipping uncertainty or create time that neither party has.