Skip to the calendar
What Is Launching
Sign in Add your launch

Sat 21 Nov 2026
All times UTC

A Launch-Day Run-Sheet: The Whole Day, Hour by Hour

Playbook · 9 min read ·

A full-day launch run-sheet with roles, checkpoints, handovers and breaks, laid out by hour so a small team stays in control from check to reply.

Illustration: Tall run-sheet in monospace with hourly rows, time column on the left in 24-hour form, small role tags on the right, dark ink on pale ground

On launch day, decisions are cheap and mistakes are expensive. A run-sheet moves most of the decisions into the days before, so on the day you can follow the plan and keep your attention for people.

This article gives a full-day template with checkpoints, roles and handovers. The focus here is the shape of the whole day, not the opening minutes alone.

What a run-sheet is

A run-sheet is a one-page schedule, with times down the left and actions on the right. It names who does each thing, what to check and what to do if it goes wrong. It is not a plan to be admired. It is a tool that lives on a second screen all day.

Use 24-hour times and state the time zone at the top. ISO 8601, which Wikipedia describes as an unambiguous way to represent dates and times, is a sound basis: write the date as 2026-10-02 and times as 09:00, with the offset beside the heading. If your team is in several zones, add a UTC column.

Roles

Even a one-person launch benefits from naming the hats.

Conductor. Owns the schedule, makes decisions and keeps notes. Usually the founder.

Responder. Answers comments, messages and questions.

Watcher. Monitors the product: uptime, errors, sign-ups, emails.

Promoter. Posts and sends scheduled messages, and watches where traffic comes from.

Scribe. Records what happens, with times.

In a team of one you wear all five, so keep the scope small and the schedule slack. In a team of three, combine them sensibly.

Before the day: set up the sheet

Prepare these items the day before.

  • The run-sheet itself, printed or on a second device.
  • A page of reply drafts.
  • Contact numbers for each team member.
  • A list of scheduled messages and where to pause them.
  • A dashboard open with analytics, error logs and sign-ups.
  • A "red button" note: what to do if the site goes down.
  • Food and drink.

The day, block by block

Times below are relative to the moment your window opens, called T.

T minus 2 hours: preflight

  • Conductor: read the sheet aloud to the team.
  • Watcher: check servers, databases, email sending and third-party services.
  • Promoter: confirm every scheduled message and its time zone.
  • Responder: open the reply drafts, check the inbox, clear notifications.
  • Everyone: eat something.

T minus 30 minutes: final checks

  • Click every link from a clean browser, on desktop and phone.
  • Create a fresh account and complete the main task.
  • Check that the confirmation email arrives.
  • Read the launch page once more.
  • Confirm helpers have the time.

T to T plus 1 hour: opening

In the run-sheet, keep this block short and simply list: open the page as a stranger, post the first comment, send helper messages, publish the first announcement.

Product Hunt's launch guide says you cannot ask people directly to upvote and should ask them to visit and comment. Make that wording part of the helper message in the run-sheet so nobody improvises.

T plus 1 to T plus 4 hours: the surge

Most launches see the highest volume of questions early.

  • Responder: reply in rounds of fifteen minutes, then check technical items.
  • Watcher: every thirty minutes, check errors, load and sign-up completion.
  • Promoter: post the second announcement in a different format.
  • Scribe: log notable events with times: a spike, a bug, a good question.
  • Conductor: decide on fixes. Fix only real faults.

T plus 4 hours: first break and review

Take ten minutes away from screens. Then review three things: the questions you keep getting, the traffic sources and the technical health. Update the reply drafts. Adjust the plan for the afternoon.

T plus 4 to T plus 8 hours: the long middle

Energy dips. Keep the rhythm.

  • Rotate roles if you can, to avoid fatigue.
  • Share a different angle each time you post: a short clip, a customer story, a behind-the-scenes note.
  • Keep thanking people individually.
  • Keep eating.

T plus 8 hours: handover or midpoint

If you work in shifts, this is the handover. The outgoing person writes a short note: open questions, promises made, issues in progress, anything to watch. Read it aloud. If you are alone, write the note for yourself and take a longer break.

T plus 8 to T plus 16 hours: the other time zones

For a global audience, activity moves with the sun. Reply to those who write from other regions. A Show HN-style discussion, as Hacker News's guidance describes, expects the maker to be around to discuss their work, and the same holds on any platform: people like finding someone home.

T plus 16 hours onward: wind down

  • Final reply sweep. Answer every unanswered comment.
  • Final post: a thank-you.
  • Save evidence: screenshots, comments, sign-up numbers.
  • Write the day's summary in three lines.
  • Plan tomorrow: who does what first thing.
  • Sleep.

Checkpoints, not constant checking

It is tempting to watch numbers every minute. Replace it with checkpoints: every thirty minutes in the first four hours, every hour after that. At each checkpoint ask three questions: is the product healthy, is anyone waiting for a reply and is anything unexpected happening? Between checkpoints, work on conversation.

When things go wrong

Put contingency into the sheet.

Site down. Watcher informs the conductor, who posts a short, honest message where people are asking, and the watcher restores service. After restoring, post an update.

A serious bug. Acknowledge it publicly, say when you expect a fix and fix it. Do not hide it.

A hostile thread. Responder replies once, calmly, and reports abuse if needed.

A scheduled message is wrong. Promoter pauses and corrects it, then posts a short correction.

Helper no-show. Do not chase. Carry on.

Exhaustion. The conductor calls a break. Mistakes multiply when people are tired.

Keep the notes

The scribe's log is the most valuable output of the day. Each entry has a time, what happened and what you did. After the launch, it tells you how the day actually flowed, which messages worked, when questions peaked and where the product struggled. Next time, your run-sheet will be better.

Sample extract

A snippet of a run-sheet might look like this. 2026-10-02, UK time (UTC+01:00). 07:00 preflight read-through. 08:30 final click-through, desktop and phone. 09:00 window opens, page live, first comment posted. 09:05 first announcement sent. 09:15 helper messages, one by one. 09:30 first reply round. 10:00 first watcher checkpoint. 11:00 second reply round. 13:00 first break and review. 14:00 second announcement, new angle. 17:00 handover note. 20:00 thank-you post. 22:00 final reply sweep and evidence saved. 22:30 stop.

On this site

The launch calendar and the coming-soon list show booked launches week by week, and weeks begin on Monday in UTC, so you can fit your run-sheet to your week. With a paid launch you choose that week on the submit page; a free listing waits its turn in the free queue. A launch entry is currently $5. The about-founders page names the people behind What Is Launching.

Adapting the sheet to a solo launch

If you are alone, simplify without abandoning the structure. Replace roles with time blocks: for the first four hours you are responder first and watcher second, checking the product every half hour. From hours four to eight, alternate twenty minutes of replies with ten minutes of promotion and technical checks. Schedule two proper breaks and one real meal. Tell your audience in advance when you will be offline, and state the hours with their time zone. Prepare a pinned note on your page that says when you will next be replying. Honesty about your availability is better than a promise of constant presence that you cannot keep.

Tools you actually need

A run-sheet works on paper. A shared document is better if others are involved. A simple timer helps you keep checkpoints. A second screen for analytics and logs lets you watch the product without losing your place in the conversation. A text file of reply drafts speeds up the routine answers. Nothing more is required, and extra tools add more places to look at the moment you most need to focus.

After the day

Within twenty-four hours, turn the scribe's log into a one-page summary: what happened, when, what worked and what you would change. File it with your calendar and run-sheet. When you plan your next launch, start by reading it. The learning compounds, and the second run-sheet is usually twice as good as the first.

Keeping a calm tone

The mood of the team shapes the tone of every reply. Agree in advance that nobody will send a message in anger, that any hostile comment gets a ten-minute pause before a response and that apologies are quick and specific. Small rituals help: a shared joke at the handover, a glass of water at each checkpoint, a pause to read a nice comment aloud. Launch day is long, and a team that stays kind to each other tends to stay kind to its audience.

The takeaway

Write the day down before it happens: roles, times with zones, checkpoints, handovers and a plan for failure. Then follow it, keep a log and look after yourselves. On launch day, the best thing a founder can be is organised and kind.

Questions and answers

What is a run-sheet?
A run-sheet is a timed list of what happens, who does it and what to check, used on the day to keep everyone coordinated.
How many people do I need on launch day?
One can manage a small launch with a tight scope. Two or three allow shifts, with one person on replies, one on technical checks and one on promotion.
How should I write times in the run-sheet?
In 24-hour form with the time zone stated, and ideally with a UTC reference so distributed teams read the same moment.
When should I stop on launch day?
When the window closes or your agreed shift ends. Plan a handover, a meal and sleep. Replies can resume the next morning.

Sources

Support