Stephen Brenish
Most games slip at some point, and a delay on its own rarely sinks a project. What does damage is handling it badly: a publisher who hears about it from a press story, players left guessing, a team that learns the date moved from a social post, a console slot lost because nobody called the platform holder.
By the time you are reading this, you have probably already decided to delay. This is about everything that comes next.
- Tell your publisher first, with a revised milestone plan, not just an apology.
- Announce to players with a range, a reason and proof of progress.
- Cost the delay with your burn rate, not with hope.
- Brief the team before the public hears it, and protect their time afterwards.
- Reschedule with every platform before you announce, especially on console.
Tell your publisher before anyone else
The order matters. If your publisher learns about the delay from your Steam page or a press story, you have damaged the relationship and may have breached your contract. Most publishing agreements require prompt notice of any material change to the delivery schedule, and milestone payments are usually tied to the dates you are about to move. Read the notice and delivery clauses in yours before you pick up the phone.
Then come to the conversation with three things:
- A new target window you can defend.
- A revised milestone plan with specific deliverables attached to each new date.
- A short root-cause summary: what changed, why, and what you are doing so it does not happen again.
Publishers have their own reporting obligations and need something concrete to work with. A revised plan turns “we need more time” into a decision they can approve.
The player-facing announcement
Teams usually miss in one of two directions. Some overpromise (“we’ll be ready by September”) and lock themselves into a second announcement if September slips. Others are so vague (“development is ongoing”) that players assume the worst.
The formula that works is short: name the range, name the reason, show the work.
- Range means “early next year,” not a specific date you are not confident in.
- Reason means one honest sentence about what changed. Not a non-answer, and not a wall of gratitude.
- Show the work means a screenshot, a short clip, or a concrete description of what the extra time is building.
The worst option is saying nothing and quietly missing the date. Players notice, the store page shows a date that has passed, and every week of silence becomes part of the story.
Cost the delay honestly
A delay is rarely free, and the cost is easier to negotiate when you can show it. Build it from your own numbers:
| Cost | How to estimate it |
|---|---|
| Team time | Monthly burn rate multiplied by the months of delay |
| Marketing | Campaign work you must redo or reschedule: trailers, paid placements, events, review-code timing |
| Contract effects | Any milestone payments that move, penalties, or notice requirements in your agreements |
| Platform and store | Slots, featuring or events tied to the old date, and any re-certification work |
| Opportunity | What the team cannot start while it finishes this game |
If you are delaying by more than a few months, revisit how the project is funded, not just the dates. Asking your publisher to restructure milestone payments works far better with a revised schedule that adds a deliverable to de-risk the next milestone than with a request for more time and more money and nothing new attached. If your runway is the constraint, the indie game budget calculator is a quick way to rebuild the numbers, and the game development schedule planner will re-plan your milestones from the new date.
Bring the team through it
The weeks right after a delay announcement are a high-risk window for burnout and attrition. A finish line that moves is harder on people than a hard push toward one they trust.
Hold an all-hands within a day or two of the decision, before the public announcement, where the team hears the real reasons. Leave room for questions and frustration, and acknowledge that it is hard. Then move to the concrete: what the next 90 days look like, what success means, and how you are protecting people’s time. If the delay came from scope, be explicit about what you are cutting so the extra time does not quietly turn into extra work.
Reschedule with every platform
Each storefront handles date changes differently, and the timing on console is the least forgiving.
- Steam lets you change your release date in Steamworks. Do it promptly, so your page never shows a date that has already passed. If you were registered for a Next Fest or planning around a seasonal sale, check the Steam sale and Next Fest calendar against your new date, including the 30-day discount cooldown after release.
- Console platforms need final builds through certification before launch, so a date change close to submission can mean re-entering the certification queue. Talk to your platform contacts before you announce anything public, and confirm what the new date means for your submission. The console certification checklist helps you use the extra time to clear issues that would fail certification.
- Featuring and showcases tied to your old date, such as platform showcases or store promotions, may not move with you. Ask early, and plan your marketing on the assumption that you will need to earn a new slot.
If it happens twice
Acknowledge the first delay directly, use a wider and more conservative window than feels necessary, and rebuild trust through things players can see: regular updates, footage, a demo or a playtest. After a second slip, consistent visible progress does more than any announcement.
Sources
Photo: Walls.io via Pexels
