This is a sample of the readiness report every DeploySeal campaign produces — rendered by the same code as a real one. All names and data are illustrative. See it sealed

Seal your next release →
This record is unsealed. Read it, then press the seal to sign off.

DeploySeal · Readiness record · sample

Q2 Homepage Redesign

yourstore.co.za · Staging · Full Site Launch · target ship 4 May 2026

Ref DS-3F2A91C0 · v2 · v2 · Not yet sealed · Generated 3 May 2026, 09:20 UTC

Reopened from v1 on 1 May 2026 — “VAT fix for #2 needs a retest before we ship — reopening for the retest results.”

Signed 2 of 3 · waiting on Release owner

APPROVEDAPPROVEDAPPROVEDAPPROVED

Marc Patel

Lead developer

APPROVEDAPPROVEDAPPROVEDAPPROVED

Lindiwe Naidoo

Store owner

Sample Approver

Release owner

Ready — awaiting sign-off

Awaiting sign-off from Release owner · 0 open blockers · 4 of 4 issues resolved or waived · 4 of 4 testers completed · 2 signatures on record

Q2 Homepage Redesign has passed every launch rule. All 4 invited testers completed their tasks, and every issue raised has been resolved, verified on retest, or formally waived. Marc Patel and Lindiwe Naidoo have signed this release; 1 of the 2 signatures carries stated conditions.

How this verdict is decided (launch-policy/5)
  1. Any Critical or High severity issue that is not verified fixed on retest, closed, waived, or a duplicate blocks launch.
  2. A "Fixed" claim that has not been retested still counts as open.
  3. At least 50% of invited testers must have completed their tasks; otherwise the release is at risk.
  4. Remaining open Medium, Low or Trivial issues do not block launch, but are listed for the approver to accept.
  5. Every required task must have at least one recorded pass from an invited tester (admin previews do not count), and no tester's latest result on it may be a fail — a failed result stays on the record until that tester re-runs the task to a pass. Skipped results never block. Until then the release is at risk and sign-off is blocked.
  6. If any tester's verdict is "Do not approve", the release is at risk; it may still be signed, but only with stated conditions.
  7. Signing an At Risk record requires an "Approve with conditions" decision listing at least one condition.
  8. When launch safeguards are required, every safeguard must be declared or marked not applicable — with the rollback plan, monitoring and change summary written out, and a reason given for anything marked not applicable — before sign-off; until then the release is at risk. Safeguards are declared by the team, not verified by DeploySeal.
  9. Only issues explicitly waived (won't fix) are accepted risks; an issue closed as a duplicate is record hygiene and is counted, not accepted.
01

What was tested

Testing was carried out against the Staging environment (https://staging.yourstore.co.za). The whole site was in scope. Testers were asked to complete 4 tasks, of which 3 are required for sign-off. Observed telemetry — page coverage detail, devices, testing effort, page performance and security posture — is in the appendix.

Verified by build marker.

Build observed during testing: 4f2a91c (27 Apr 20261 May 2026).

Environment
Staging (Staging)https://staging.yourstore.co.zawidget last seen 1 May 2026, 16:20 UTC
Pages in scope
Whole site
Timeline
Created 24 Apr 2026Testing opened 27 Apr 2026Closed 2 May 2026

Instructions given to testers: “Shop as a customer would. Use the test card ending 4242. Report anything that feels wrong, not just what breaks.

Coverage14 distinct pages opened across 87 page views (whole site in scope) · 2 browsers · 2 device types · detail in the appendix

Traceability register · 4 tasks · 3 required

Task · expected outcomeRequiredVerified byIssuesOutcome

1.Browse to a product and add it to the basket

Desktop and mobile.

Expected Basket count updates and the mini-basket shows the right line, price and quantity.

Yes
  • Marc Patel
  • Sarah Khumalo
  • Thabo Mokoena
  • Lindiwe Naidoo
NonePassed

2.Complete checkout with a test card

Expected Order confirmation page loads with an order number; card ending 4242 is charged once.

Yes
  • Marc Patel then · changed: “retested after the CTA fix was deployed
  • Sarah Khumalo
  • Thabo Mokoena
  • Lindiwe Naidoo
  • #1Retested · Fixed
Passed

3.Confirm VAT and shipping on the order summary

Expected Subtotal, 15% VAT and shipping are itemised and add up to the total charged.

Yes
  • Marc Patel
  • Sarah Khumalo
  • Thabo Mokoena
  • Lindiwe Naidoo
  • #2Retested · Fixed
Passed

4.Open the order confirmation email

Check links and branding.

Expected Email arrives within two minutes; every link resolves to the new storefront.

Optional
  • Marc Patel
  • Sarah Khumalo
  • Thabo Mokoena
  • Lindiwe Naidoo
NonePassed
02

Who tested, and how far they got

4 of 4 invited testers have completed their tasks. Every task has at least one recorded pass. Asked whether they would put this site in front of their own customers, every tester who answered said yes, 1 of them with reservations noted below.

PersonasTested by 2 customers · 1 stakeholder · 1 developer

Customers: 1 approve · 1 with reservations · Stakeholder: 1 approves · Developer: 1 approves

Verdicts3 of 4 testers approve · 1 approves with reservations · 0 do not approve

Sarah Khumalo

Sales lead, yourstore.co.za

ApprovesCompletedCustomer

4/4 tasks · 2 issues raised · started 27 Apr 2026 · verdict 28 Apr 2026

Checkout is faster than the old site. Happy to put customers on it.

Thabo Mokoena

Content, yourstore.co.za

Approves with reservationsCompletedCustomer

4/4 tasks · 1 issue raised · started 27 Apr 2026 · verdict 29 Apr 2026

Fine to go live, but the hero image on 3G is genuinely slow — please keep the week-2 fix on the plan.

  1. Verdict history
  2. Approves · 29 Apr 2026, 09:31 UTC
  3. Approves with reservations · 29 Apr 2026, 09:40 UTC · changed: “Tried the homepage on 3G after approving — it is slow enough to say so.”

Lindiwe Naidoo

Store owner, yourstore.co.za

ApprovesCompletedStakeholder

4/4 tasks · 1 issue raised · started 28 Apr 2026 · verdict 1 May 2026

Marc Patel

Lead developer, Studio

ApprovesCompletedDeveloper

4/4 tasks · started 27 Apr 2026 · verdict 30 Apr 2026

Retested the CTA fix on an SE — good.

Acceptance matrix · ✓ pass · ✗ fail · – skipped · · not attempted

Tester1234
Sarah Khumalo
Thabo Mokoena
Lindiwe Naidoo
Marc Patel
03

Mobile testing

Every phone-required task was verified on a phone by 2 of 3 testers.

Verified on phoneRequired for sign-off2/3 testers on a phone2 passed · 0 failed of 2 phone tasks3 of 7 issues filed from a phone

Tested on a phone: Sarah Ndlovu, Marc Botha

04

Issue register

4 issues were raised during testing (1 critical, 1 high, 1 medium and 1 low). 4 have been resolved or waived and 0 remain open.

Critical1 issue

#1Mobile checkout CTA is cut off

Retested · Fixed

Bug · reported by Sarah Khumalo on 27 Apr 2026 · resolved 30 Apr 2026 · while verifying “Complete checkout with a test card” · /checkout

screenshot · 184 KB · sha256 3f9c… · redactedsession replay · 1.1 MB · sha256 a81d…

High1 issue

#2VAT missing from cart subtotal

Retested · Fixed

Bug · reported by Lindiwe Naidoo on 28 Apr 2026 · resolved 1 May 2026 · while verifying “Confirm VAT and shipping on the order summary” · /cart

screenshot · 141 KB · sha256 6b2e…session replay · 842 KB · sha256 c5f0…

Medium1 issue

#3Hero image uncompressed on 3G

Waived — won't fix

Performance Issue · reported by Thabo Mokoena on 29 Apr 2026 · resolved 1 May 2026 · /

screenshot · 94 KB · sha256 d7a2…

Agreed with the client to ship and fix in the post-launch image pipeline work scheduled for week 2.

Low1 issue

#4Footer link opens in same tab

Closed

Ux Feedback · reported by Sarah Khumalo on 28 Apr 2026 · resolved 29 Apr 2026 · /

screenshot · 119 KB · sha256 e9c4…

Screenshots, session replays and device context for each issue are held in the DeploySeal record and linked from every issue above. Each stored file is fingerprinted (SHA-256) at upload; the full hashes are in the appendix.

05

Accepted risks

1 issue was consciously accepted rather than fixed for this release. The reason recorded for each is reproduced below so the approver knows exactly what they are signing off with.

Medium

#3Hero image uncompressed on 3G

Won't fix

Agreed with the client to ship and fix in the post-launch image pipeline work scheduled for week 2.

Accepted 1 May 2026, 17:02 UTC

06

Fixes and retests

2 fixes have been verified by a tester on retest. 3 retest cycles were recorded in total.

2

Verified fixed

0

Awaiting retest

0

Fixed, not verified

0

Failed retest

Retest cycles · ✗ failed · ✓ passed · oldest first

IssueTrailCyclesFailedNow
#1Mobile checkout CTA is cut off21Retested · Fixed
#2VAT missing from cart subtotal10Retested · Fixed
07

Launch safeguards

Declared

Declared by the approver’s team — attestations, not observations. DeploySeal records who declared them and when; it does not verify them.

Declared by Marc Patel on 2 May 2026, 13:30 UTC

Required · complete
SafeguardStatusAs declared

1.Rollback plan — how this launch is undone and who can do it

DeclaredSwap the App Service deployment slot back to the previous theme build; Marc or Lindiwe can do it from the Azure portal in under five minutes.

2.Monitoring & alerting — how we’ll know if it breaks

DeclaredCheckout 5xx-rate and order-rate alerts to #ops; Sentry release tagged 4f2a91c.

3.Backups verified before launch

DeclaredNightly database snapshot restored to staging on 1 May and checked.

4.Stakeholders notified of the go-live window

Not applicableReasonLindiwe and Priya are the stakeholders and both are on the signer list; the store team was briefed on 28 April.

5.Change summary — what customers will notice

DeclaredNew storefront theme and homepage; checkout, account and order flows are unchanged.
08

Sign-offs on record

Signed 2 of 3 — waiting on Release owner. 2 people have signed this release. 1 of the signatures is an "approve with conditions" — the conditions signed under are reproduced beside it. Each signature is bound to a sealed copy of this report, identified by its version number and SHA-256 digest, so what was approved can always be reproduced exactly.

Marc Patel · Admin

Approved

2 May 2026, 13:47 UTC

All blockers retested against build 4f2a91c. Release approved.

Identity: verified org login · email confirmed · marc@studio.dev

Covers sealed record v1 · sha256:9c1e6f0b2a7d4e8f5c3b1a9d7e6f4c2b8a0d1e3f5c7b9a2d4e6f8a0c1b3d5e7f

Lindiwe Naidoo · Stakeholder

Approved with conditions

2 May 2026, 14:02 UTC

Reviewed the full task map on desktop and mobile. Approved for go-live.

Signed under 2 conditions

  1. Hero image compression ships in the week-2 image pipeline work, as agreed on issue #3.
  2. Checkout error rate is watched for the first 48 hours after launch.

Identity: verified org login · email confirmed · lindiwe@yourstore.co.za

Covers sealed record v2 · sha256:4b8d2f6a0c3e5a7b9d1f3c5e7a9b1d3f5c7e9a1b3d5f7c9e1a3b5d7f9c1e3a5b

09

Changed since sealed

Nothing has changed in the record since the last signature.

10

Record history

This is v2 of the record. Every sealed version is frozen and stays verifiable as it was; a reopen cuts the next version and its reason is printed here.

  1. v1Opened26 Apr 2026, 10:00 UTCRecord created
  2. v1Sealed30 Apr 2026, 17:30 UTCMarc Patel, Lindiwe Naidoosha256:9c1e6f0b2a7d4e8f
  3. v2Reopened for changes1 May 2026, 08:05 UTCVAT fix for #2 needs a retest before we ship — reopening for the retest results.Marc Patel
  4. v2Sealed2 May 2026, 14:05 UTCMarc Patel, Lindiwe Naidoosha256:4b8d2f6a0c3e5a7b
11

Verification and limitations

Sealed record
Version 2 · frozen, awaiting signaturessha256:4b8d2f6a0c3e5a7b9d1f3c5e7a9b1d3f5c7e9a1b3d5f7c9e1a3b5d7f9c1e3a5b
Rules applied
launch-policy/5
Generated
3 May 2026, 09:20 UTC

This report records what was tested, what was found, and who accepted the result. It is evidence of acceptance and authorisation — it is not proof that the release contains no defects. Testing covered the tasks and pages listed in section 01 only.

Generated by DeploySeal · every action timestamped in UTC

Sample document

A

Appendix — observed telemetry

What the widget observed while testers worked: which pages were opened, on which browsers and devices, when each tester was active, what their browsers measured, and the response headers and TLS seen on the site. Recorded for the reader who wants to check the coverage behind the verdict; nothing here changes the verdict above, and nothing here is a penetration test.

Page coverage

No page scope was defined for this campaign, so coverage is reported against what was actually opened: 14 distinct pages across 87 page views.

Devices observed · from page visits and issue reports

BrowserOperating systemDeviceTestersPage viewsIssues
ChromeWindowsDesktop2412
SafariiOSMobile2281
SafarimacOSDesktop1181

Testing effort · recorded activity only — no hours are estimated

Testing window: 27 Apr 2026, 08:30 UTC – 1 May 2026, 16:20 UTC · 87 page views across 14 distinct pages.

TesterFirst activityLast activityPage viewsDistinct pages
Sarah Khumalo27 Apr 2026, 10:02 UTC28 Apr 2026, 11:00 UTC3111
Thabo Mokoena27 Apr 2026, 13:40 UTC29 Apr 2026, 09:30 UTC198
Lindiwe Naidoo28 Apr 2026, 07:55 UTC1 May 2026, 16:20 UTC2210
Marc Patel27 Apr 2026, 08:30 UTC27 Apr 2026, 09:30 UTC159

Page performance · as observed by testers

Field data from testers’ own browsers during testing — not a lab benchmark. Each row is the median of what testers saw on that page; amber marks a median above Google’s “needs improvement” threshold (LCP 2.5 s, CLS 0.1, INP 200 ms).

PageSamplesLCP (median)CLS (median)INP (median)
/Homepage43.1 s0.040120 ms
/cart41.4 s0.02090 ms
/checkout41.9 s0.13160 ms

Evidence artifacts · SHA-256 of every stored file

IssueKindCapturedSizeSHA-256
#1screenshot · 390×844 · redacted27 Apr 2026, 09:11 UTC184 KB3f9c2b7e1a4d8c6f0b5e9a2d7c1f4e8b6a0d3c5e9f2b7a1d4c8e6f0b3a5d9c2e
#1session replay27 Apr 2026, 09:11 UTC1.1 MBa81d4c7e2f9b0e3c6d5a8f1b4e7c0d2a9f6b3e8c1d4a7f0b5e2c9d6a3f8b1e4c
#2screenshot · 1440×90028 Apr 2026, 11:04 UTC141 KB6b2e9d4a1c7f3e0b8d5a2f9c4e1b7d0a3f6c9e2b5d8a1f4c7e0b3d6a9f2c5e8b
#2session replay28 Apr 2026, 11:04 UTC842 KBc5f0a3d8b1e6c9f2a5d8b1e4c7f0a3d6b9e2c5f8a1d4b7e0c3f6a9d2b5e8c1f4
#3screenshot · 390×84429 Apr 2026, 09:43 UTC94 KBd7a2f5c8e1b4d7a0f3c6e9b2d5a8f1c4e7b0d3a6f9c2e5b8d1a4f7c0e3b6d9a2
#4screenshot · 1440×90028 Apr 2026, 14:19 UTC119 KBe9c4b7a0d3f6e9c2b5a8d1f4e7c0b3a6d9f2e5c8b1a4d7f0e3c6b9a2d5f8e1c4

Security posture

Observed response headers and TLS for https://staging.yourstore.co.za, captured 2 May 2026, 09:00 UTC. It is not a penetration test or vulnerability scan.

HTTPS reachablehttps://staging.yourstore.co.za · captured 2 May 2026, 09:00 UTC
ObservationObservedValue
http:// redirects to httpsPresent
TLS certificate expiryPresentvalid until 19 Jul 2026, 23:59 UTC
Strict-Transport-SecurityPresentmax-age=31536000; includeSubDomains
Content-Security-PolicyAbsent
X-Content-Type-OptionsPresentnosniff
X-Frame-OptionsPresentSAMEORIGIN
Referrer-PolicyPresentstrict-origin-when-cross-origin
Permissions-PolicyAbsent
Server software disclosurePresentnginx

Cookies set on first response · flags only, values are never stored

.Nop.Customer · Secure · HttpOnly · SameSite=Lax

.Nop.Antiforgery · Secure · HttpOnly · SameSite=Strict

Your first report is about 10 minutes away — start a free trial or head back to deployseal.com.

Sample Readiness Report — DeploySeal · DeploySeal