Website Launch Risk Score: What Agencies Should Track Before Go-Live

Quick answer

A website launch risk score helps agencies decide whether a client site is ready for go-live by ranking the likelihood and impact of unresolved launch risks. Track blocker severity, time to launch, overdue client-owned tasks, missing ownership, access safety, approval status, QA risk, SEO migration risk, and recent movement before making the launch decision.

Best for

Agency owners, project managers, account managers, producers, and launch coordinators who need a practical way to see whether a client website launch is on track, at risk, blocked, or ready with known exceptions.

What to do next

1. List the launch risks that could affect go-live.
2. Score each risk by severity, likelihood, ownership, timing, and client-side dependency.
3. Review the score daily in the final 10 business days before launch.
4. Escalate high-risk items with one owner, one next action, and one decision deadline.

Shipperly workflow: Shipperly helps agencies keep client-side website launch work moving by organizing launch requests, assigning ownership, detecting risk, surfacing blockers, drafting follow-ups for agency review, and recording final launch approval for operational reference.

What is a website launch risk score?

A website launch risk score is a simple way to rank the unresolved issues that could affect a client website go-live. It turns scattered launch signals into one decision view: what is safe, what needs watching, what is high risk, and what blocks launch.

The score should not be a vanity metric. It should help the agency answer practical questions:

• Can this site go live on the planned date?
• Which issue is most likely to delay launch?
• Which client-owned task needs escalation?
• Which access path is unclear or unsafe?
• Which approval is missing?
• Which risk can move to post-launch with client approval?
• Which risk should stop launch until it is resolved?

A launch risk score borrows the basic project risk idea of likelihood and impact, then adapts it for agency launch work. Website launches have a few risks that generic project boards often hide: DNS ownership, safe access, late client content, stakeholder approval, redirects, forms, tracking, and launch-day availability.

The goal is not to make launch feel more complicated. The goal is to make hidden risk visible early enough to do something about it.

Why agencies need a risk score before go-live

Most website launches do not fail because the agency forgot that work existed. They get shaky because the team cannot tell the difference between normal unfinished work and true launch risk.

A project may look almost done while still carrying serious exposure:

• The site is built, but the client has not approved the homepage claims.
• QA is mostly complete, but the lead form routes to the wrong inbox.
• The launch date is Friday, but nobody knows who can update DNS.
• The client says "looks good," but no final approver is named.
• The redirect map exists, but high-traffic URLs have not been tested.
• The agency asked for access, but the client is about to paste credentials into a general task thread.

A risk score gives the launch team a shared language for those situations. Instead of saying "we are almost there," the team can say:

The build is close, but the launch risk score is high because DNS ownership, final approval, and two client-owned content approvals are unresolved within three business days of go-live.

That is the kind of sentence that helps an account manager, client lead, and production team make the same decision.

For the broader readiness check, see website launch readiness: how to know if a site is actually ready to go live. For specific blocker categories, see the agency guide to launch blockers.

What should a website launch risk score include?

A useful website launch risk score should track the risks that actually change the go-live decision. For agencies, that usually means a mix of technical, client-side, approval, and timing signals.

Do not track every tiny task in the score. Track the factors that change confidence.

How to calculate a website launch risk score

Use a score that is simple enough for a daily launch review. A complicated model will not survive a busy launch week.

Score each factor from 0 to 3.

Then score the core categories.

Add the points.

The exact thresholds can change by agency. What matters is consistency. If every launch uses the same scoring model, the team can compare risk across projects without relying on whoever is loudest in Slack or email.

Which launch risks deserve the most weight?

Some factors should carry more weight than others because they can stop the launch even when the site looks polished.

Final approval risk

A website is not ready to launch just because feedback slowed down. The agency needs a clear launch decision from someone with authority.

Track:

• Final approver name
• Backup approver, if needed
• Approval status
• Known exceptions
• Approval date
• Launch scope covered by the decision

A vague "looks good" message is not the same as final launch approval. Shipperly can help record approval for operational reference, but it is not a legal e-signature tool. If the client requires a formal legal signature, use their approved signing process.

Access and DNS risk

Access risk gets dangerous when it is discovered late. The agency may need DNS, hosting, CMS, analytics, tag manager, CRM, or integration access, but that does not mean clients should share secrets casually.

Do not ask clients to paste passwords, API keys, recovery codes, private tokens, SSH keys, payment credentials, or other secrets into Shipperly, email, chat, spreadsheets, project comments, or general forms.

Safer paths include:

• Inviting the agency as a user
• Creating a temporary user account with the least access needed
• Having the client's IT or admin contact complete the action directly
• Using a secure password manager when credential sharing is truly necessary
• Sharing only non-sensitive links, screenshots, confirmations, or status updates inside Shipperly

Score access risk high when the owner is unknown, the launch window depends on a third party, or the only proposed path is unsafe credential sharing.

Client-owned task risk

Client-owned tasks can look harmless until the launch date gets close. The agency may be done internally while waiting on content, legal review, form recipients, DNS confirmation, CRM routing, leadership approval, or stakeholder feedback.

Track:

• Owner
• Due date
• Status
• Blocker reason
• Launch impact
• Last update
• Whether the task needs the Client Lead to delegate internally

A client task should not remain assigned to "the client" when it affects launch. Name the stakeholder or assign it to a Client Lead who can route it inside the client organization.

QA, forms, and conversion risk

A site can look ready in staging and still fail where it matters most.

Score QA risk high when any of these are untested or failing:

• Contact forms
• Lead routing
• Booking or calendar links
• Checkout, donation, or payment paths
• Search and filters
• Downloads
• Login or gated content
• Mobile navigation
• Error states
• Confirmation emails
• CRM or marketing automation handoff

Do not stop at "the form submitted." Confirm that the right person receives the submission and knows what to do with it.

SEO migration and analytics risk

For redesigns, rebuilds, and platform changes, SEO and analytics should be part of the launch risk score.

Score this category high when:

• Redirects are incomplete or untested.
• High-traffic URLs have no destination.
• Staging noindex settings may carry over.
• Analytics is installed but not receiving test events.
• Conversion tracking is not verified.
• Sitemap, robots.txt, canonicals, or metadata are not reviewed.
• Important internal links are broken.

A website launch risk score should make these issues visible before DNS changes, not after traffic or lead tracking drops.

A practical launch risk score template

Use this template in the final 10 business days before go-live.

This is intentionally plain. The value is not a fancy formula. The value is that the team can see the launch story in one place.

Daily workflow for reviewing launch risk

Use this workflow once a launch is within 10 business days of go-live.

1. Recalculate the score daily

Risk changes quickly near launch. A content item that was low risk last week can become high risk when the launch date is two days away.

2. Review the highest-scoring category first

Do not start with the easiest task. Start with the risk that can most affect go-live.

Examples:

• Final approval is missing.
• DNS owner is unclear.
• Client-owned legal review is overdue.
• Redirects for top pages are untested.
• Forms submit but do not reach the right team.

3. Assign one next action

Every high-risk item needs one owner and one next action.

Weak:

Follow up on DNS.

Stronger:

Ask Maya, the Client Lead, to confirm whether IT or the agency will update DNS by Tuesday at noon. If IT owns it, request the launch-window contact.

4. Draft the client follow-up for review

When a client-owned item is high risk, the follow-up should be direct without sounding panicked.

Example:

This is now a launch-risk item because the DNS owner is not confirmed and our go-live window is Friday morning. Can you confirm the admin contact by Tuesday at noon, or should we move the launch window?

Shipperly can help draft follow-ups like this for agency review. The agency should review the message before sending, especially when it involves approval, access, legal review, or timeline changes.

5. Record the decision

End the review with one of these decisions:

• Ready to launch
• Ready with exceptions
• Watch
• At risk
• Blocked
• Move launch date
• Waiting on client
• Waiting on agency

If a risk is accepted as a known exception, record who accepted it and what happens after launch.

Common mistakes when scoring website launch risk

Treating all open tasks equally

A missing secondary image and a broken lead form are both open tasks, but they do not carry the same launch risk. Score by go-live impact, not task count.

Waiting until launch week to score risk

The score is most useful before the final scramble. Start at least 10 business days before launch, then review daily as the date gets closer.

Giving vague client tasks a low score

A task assigned to "client" with no person, due date, or status should not be treated as low risk. If it affects launch, name the owner or route it through the Client Lead.

Ignoring silent risks

A quiet client is not always a low-risk client. No update on a critical item for several days should raise the score, especially near launch.

Letting unsafe access pressure slip through

Last-minute access issues can tempt teams into unsafe habits. Track the action needed, not the secret. Use safer access paths and keep sensitive credentials out of general task fields and comments.

Treating the score as a replacement for judgment

A score helps prioritize attention. It does not replace launch judgment. If one issue can create serious client harm, the agency should escalate it even if the total score looks moderate.

Using AI follow-ups without agency review

AI can help draft clearer follow-ups, but client launch communication often needs human context. Shipperly drafts follow-ups for agency review; it should not be treated as an autonomous email sender.

How Shipperly helps agencies track launch risk

Shipperly is an AI launch coordinator for website agencies. It helps agencies keep client-side website launch work moving by organizing launch requests, assigning ownership, detecting risk, surfacing blockers, drafting follow-ups, and recording final launch approval.

For a website launch risk score, Shipperly helps the agency see:

• Which client-owned launch tasks are overdue
• Which requests are blocked or unassigned
• Which owner is responsible for the next action
• Which access-related items need safer handling
• Which launch blockers are still unresolved
• Which risks should appear in the AI Launch Brief
• Which follow-up drafts need agency review
• Which final approval record is missing or complete

That gives the launch team a clearer daily question: what risk needs attention today?

For teams managing several launches at once, pair this score with a broader prioritization view. The workflow in how agencies can prioritize multiple website launches without missing risks is a good next step.

FAQs

What is a website launch risk score?

A website launch risk score is a simple rating that helps agencies identify how likely unresolved issues are to affect go-live. It usually considers blocker severity, time to launch, client-owned tasks, access readiness, QA, SEO migration, ownership, recent movement, and final approval.

How do you score website launch risk?

Score each launch risk from 0 to 3 based on severity: no known risk, watch, at risk, or blocked. Add the scores across categories such as time pressure, client tasks, ownership, access, approval, QA, SEO, and recent movement. Use the total to decide whether the launch is low risk, watch, high risk, or critical.

What should agencies track before go-live?

Agencies should track launch blockers, overdue client-owned tasks, unassigned requests, final approval, DNS and hosting ownership, safe access paths, forms, redirects, analytics, SEO migration items, critical QA issues, launch-day owners, and known exceptions before go-live.

Is a launch risk score the same as launch readiness?

No. Launch readiness is the overall go-live decision. A launch risk score is one input into that decision. The score highlights where risk exists so the agency can resolve blockers, document exceptions, or move the launch date with better evidence.

Can Shipperly automatically send client follow-up emails about risk?

Shipperly can draft follow-ups for agency review, but agencies should review client launch messages before sending. That is especially important when the message involves deadlines, final approval, access, legal review, or a possible launch-date change.

A good website launch risk score helps agencies stop guessing in the final stretch. It shows which issue can actually affect go-live, who owns the next action, and whether the launch is ready, watch, high risk, or blocked.

Shipperly gives website agencies a focused way to manage those client-side launch risks, from overdue requests and blockers to agency-reviewed follow-up drafts and final approval records. If launch week currently depends on memory, inbox searches, and informal status updates, a risk score is the first step toward a cleaner go-live decision.