# Website client onboarding: week-one review record

Use this after the client has had about a week to operate the site. Replace the examples. Do not record Unknown as Green.

## Review details

- Client:
- Website and production hostname:
- Handoff date:
- Review date:
- Client reviewer:
- Agency reviewer:
- Support or warranty window ends:
- Next review date, if any:

## Status key

- Green: evidence matches the agreed operating state.
- Yellow: usable now, but a correction, clarification, or follow-up has an owner.
- Red: a material journey, access, safety, or ownership problem needs immediate action.
- Unknown: evidence has not been collected. Unknown is not a pass.

## FIRST review summary

| Area | Status | Evidence reviewed | Decision | Owner | Due date |
| --- | --- | --- | --- | --- | --- |
| Flow |  |  |  |  |  |
| Identity |  |  |  |  |  |
| Reality |  |  |  |  |  |
| Safety |  |  |  |  |  |
| Terms |  |  |  |  |  |

## F: Flow

Review the real visitor and staff journeys that matter to this site.

- [ ] Open the production hostname on a representative phone and desktop.
- [ ] Follow the primary call to action from entry page to destination.
- [ ] Submit each critical form with clearly labeled test data.
- [ ] Confirm the intended recipient or system receives the test.
- [ ] Check confirmation, error, and follow-up behavior.
- [ ] Test phone, email, booking, checkout, or map links that are in scope.

Evidence:

Decision:

## I: Identity

Verify ownership and access through real accounts, not a screenshot of an invitation.

- [ ] The client signs in with their own account.
- [ ] The client can complete one agreed routine task.
- [ ] A restricted action is actually restricted or routed for review.
- [ ] Domain, platform, analytics, Search Console, and billing owners are named.
- [ ] Former staff, contractors, and temporary accounts have been reviewed.
- [ ] Recovery contacts and multi-factor methods belong to current authorized people.
- [ ] Application customer permissions are reviewed separately from platform roles, if applicable.

Evidence:

Decision:

## R: Reality

Use first-week evidence to discover questions, not to manufacture a performance story.

- [ ] Analytics collection is confirmed in the intended property or product.
- [ ] Test activity is labeled or excluded from business interpretation where practical.
- [ ] Search ownership and obvious crawl or indexing issues are reviewed.
- [ ] Client questions and attempted edits are listed in their own words.
- [ ] Support requests are grouped by training, setup, defect, or new scope.
- [ ] Low traffic, delayed reports, or missing evidence is recorded as Unknown.

Evidence:

Decision:

## S: Safety

Inspect what changed and whether the agreed recovery route still makes sense.

- [ ] List every production change since handoff.
- [ ] Recheck the affected pages and journeys at phone and desktop widths.
- [ ] Spot-check page titles, headings, images, keyboard access, focus, and changed forms.
- [ ] Confirm each changed page has an appropriate review owner.
- [ ] Locate the relevant history, backup, or checkpoint.
- [ ] Confirm who may restore and what later work or external data must be preserved first.
- [ ] Do not describe this spot check as a comprehensive accessibility or security audit.

Evidence:

Decision:

## T: Terms

Turn every finding into an operating decision.

- [ ] Bugs or missed acceptance criteria are separated from new requests.
- [ ] Training gaps have a shorter instruction, example, or repeat exercise.
- [ ] Access changes have a named administrator.
- [ ] Recurring care has an owner, cadence, and service boundary.
- [ ] Every open item has one owner and one due date.
- [ ] The client knows the support channel and response target.
- [ ] Closure, another review, or an ongoing service has been chosen explicitly.

Evidence:

Decision:

## Client questions from the first week

1.
2.
3.

## Changes made since handoff

| Date | Request | Surface changed | Released by | Evidence checked | Follow-up |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

## Action register

| Finding | Type: defect, training, access, care, or new scope | Priority | Owner | Due date | Closure evidence |
| --- | --- | --- | --- | --- | --- |
|  |  |  |  |  |  |

## Close the review

Choose one:

- [ ] Close onboarding. The client can operate the agreed scope and all material findings are resolved.
- [ ] Continue onboarding. The next review is booked and remaining activation work is named.
- [ ] Move into ongoing care. The service, owner, cadence, and commercial boundary are documented.
- [ ] Escalate. A Red finding blocks safe operation and has an immediate owner.

Client acknowledgement:

Agency acknowledgement:

Notes:
