DEV Community

Tick & Ship
Tick & Ship

Posted on Edited on

How to get client sign-off on a staging site

Client approval on a staging site often happens in the least formal way possible. Someone gets a link in email or Slack, looks around for a few minutes, and replies "looks good" or "let's go live."

That message feels like a finish line. It usually is not. A typo, a broken form, or a missed page turns up later, and nobody can say what was actually approved, by whom, or on which version of the site.

A better sign-off is a simple, shared record of the review that just happened.

Why a casual "looks good" is a weak record

Informal approval fails in predictable ways. It is not specific: "looks good" does not say whether the client checked the mobile layout, tried the forms, or opened any page beyond the home page. It is easy to lose, because email and chat threads move on. And if a new staging build goes up during the review, nobody can say which version they saw.

None of this requires anyone to be difficult. It is just what happens when the review has no structure.

What a useful sign-off should include

You do not need a legal contract. You need a record that a stranger could pick up later and understand. At a minimum it should answer five questions:

  1. Who reviewed the site?
  2. When did they review it?
  3. Which URL, and which version, did they look at?
  4. What did they check, item by item?
  5. What still failed, or was blocked, and was that accepted for launch anyway?

A named person, a date, and a specific URL matter because memory fades and staging moves. Item-by-item outcomes matter because looking at the site is not the same as checking a form on a phone. Open issues can still be accepted for launch, as long as both sides agree they are known.

If any of those five pieces is missing, you have a comment, not a sign-off.

Freeze the build before you ask for a review

The review only counts if everyone is looking at the same site. Deploy the build you want approved, then stop pushing changes to that URL until the review is done.

Give the client one URL, not a mix of preview links. Use content that looks real enough, because people comment on placeholder text instead of the layout. If the staging site has basic auth, send that password separately, and make it view-only, not CMS or hosting access. Say what this round is for: a final functional review is not a new design critique. If you need to keep building, do it on another branch or another preview.

Send a checklist, not an open-ended request

"Please take a look and let me know what you think" puts all the work on the client. You will get either silence or a random assortment of comments. A checklist is kinder, because it tells them what "done" looks like.

Keep the list in plain language. The client is confirming that the site is ready for their customers, not doing a design critique for your internal team. A practical list often includes:

  • Every page in the agreed sitemap loads, including legal, 404, and thank-you pages.
  • The site looks right on the client's own phone and computer, not only on yours.
  • Names, phone numbers, addresses, prices, hours, and other facts are correct.
  • Navigation, links, forms, images, and calls to action work as expected.
  • Test prices, dummy content, or a staging banner that should not go live are either gone or clearly marked.
  • Anything still unfinished is written down as a known issue, not left as a surprise.

Add project-specific items on top of that, such as a booking flow, a language toggle, or a widget the client cares about.

For each item, ask for a clear outcome: Pass, Fail, or Blocked. Pass means it works, as far as the client can tell. Fail means it is wrong or broken, with a short note about what they saw. Blocked means they could not test it, for example because a login was missing.

If something fails, the note should say where it happened and what they expected. "The submit button on the contact page does nothing on my iPhone" is useful. "I don't love this" belongs in a design conversation, not a launch review, unless those changes are still in scope.

How to run the review itself

Send the checklist and the staging URL together, and give a deadline. A review with no end date tends to sit in an inbox. A short message is enough:

The staging site is ready for review at [URL]. Please work through the attached checklist on your phone and your computer. For each item, mark Pass, Fail, or Blocked, and add a note if something is wrong. If a problem is acceptable to you for launch, say so on that item. Please finish by [date]. Once you confirm, we will treat this as the version you approved.

Ask them to type their name, or to reply in a way that clearly says who approved it. A thumbs-up emoji on a group chat is a weak record.

If they mark items as failed, fix those items, freeze the build again, and send back only the failed items for recheck. Do not ask them to re-review the entire site unless the changes could have broken something else.

When they are done, save the completed list, the date, the URL, and the name of the person who signed off somewhere both of you can find later. A PDF or similar snapshot helps, so the record cannot drift as later edits happen.

Silence is not sign-off. If the deadline passes with no reply, send one reminder, then wait for an actual confirmation. Launching because nobody answered is how "I never approved that" gets said later.

What to do with the record after they sign

Keep the record with the project, not only in the original email thread. It is useful when you go live, when a later issue raises questions about scope, and when you close the project. If some items were accepted as known issues, leave them in the record. A sign-off can be honest about unfinished work. It just should not pretend those items were never discussed.

A small tool that does this in one pass

If you want the checklist, the client's responses, and the final record in one place, Tick & Ship is built for that step. You send a staging checklist as a magic link. The client marks Pass, Fail, or Blocked, types their name, and both of you get a sealed, timestamped PDF by email. They do not need an account.

You can also run the same process in a document, a shared list, or email, as long as the five questions above are answered and the record is saved. The process matters more than the tool.

The habit to keep is simple. Freeze the staging site, send a clear list, get a named and dated response, and keep that snapshot after the site goes live.

Want a ready-made version? Grab the free Website Launch Sign-Off Checklist and duplicate it into your own Notion.

Top comments (0)