How to plan a live-ops content calendar
By Jordan Blackman · Updated September 16, 2026
A live-ops calendar is a set of promises: to players about what is worth returning for, and to your team about what it can deliver. Filling every week with an event is not the same as having a plan.
Start with the behavior you want to understand or improve. Then choose an event, offer or experience that gives players a good reason to take part.
Give every event a job
Write down who the event is for, what they will do and why that should be enjoyable. A progression event might help engaged players use an underplayed system. A collection event might give returning players a clear short-term goal. A purchase offer needs a use that makes sense in that context.
Be explicit about the commercial question. Are you testing a new paid benefit, trying to increase repeat participation or finding out whether an offer replaces purchases players would otherwise have made? These require different measures.
Plan from the team's actual capacity
Work backward from the player-facing date. Include design, implementation, art, localization, configuration, quality assurance, support preparation and release dependencies. Reusing a familiar format can still require meaningful work.
Record the owner, decision date, dependencies and fallback for each event. Leave space for maintenance and learning. A calendar that assumes every feature will ship on time is a list of hopes.
A practical calendar entry
For each planned activity, capture these seven things:
Player and purpose. Who is eligible, and what worthwhile experience will they have?
Activity and reward. What do players do, receive and keep? Make the rules understandable.
Commercial hypothesis. What might change, and why? Separate that assumption from established evidence.
Dates and dependencies. Include preparation, testing, launch, end time and review—not just the live window.
Production owner. Who can resolve the remaining decisions, and what capacity is reserved?
Measures and guardrails. Track participation, completion and total revenue alongside the specific outcome. Check retained activity, complaints and unintended effects.
Next decision. State what would justify repeating, changing or stopping the format.
An illustrative four-week sequence
This is a planning example, not a recommended cadence for every game.
Week 1: Establish the baseline. Review recent activity and purchase patterns. Check event configuration and prepare support. Decide which comparison will be meaningful.
Week 2: Run one focused event. Use a familiar format to test a specific reward or offer hypothesis. Keep other major changes limited where practical, so the result is easier to interpret.
Week 3: Review and recover. Examine who participated, what happened afterward and whether revenue shifted between offers. Resolve player issues and leave room for production work.
Week 4: Repeat with a reason. Make one justified change or run the next planned activity. Do not call a larger number a win until you have considered audience differences, exposure and ordinary variation.
Coordinate the whole player experience
Align in-game messages, store presentation, community updates and customer support with the same rules and dates. Check time zones, eligibility, reward delivery and what players see after an event ends.
Novelty can give people a reason to look; familiarity can make participation easier. The right balance depends on the product and audience. Use the calendar to make that tradeoff deliberately.
Turn the calendar into a learning loop
Keep a short review beside each entry: what happened, what remains uncertain and what the team will do differently. Total results matter more than one event's isolated sales. An offer that borrows from next week's purchases may need a different decision from one that creates lasting value.
See how capacity changes the recommendation
In my illustrative battle-pass-or-bundle example, the recurring production commitment is part of the decision. Compare both options, then reveal how a proven seasonal pipeline or weakening retention changes my recommendation.
Compare the production commitments · See what changes my recommendation
Is your calendar busy without moving growth?
I can help your team connect the player experience, production capacity and commercial question—then define the work and the next test.
See how I work with your team · Tell me about your product
Related: How to price your in-app purchases
