# Client audit report — working template

Project: [name] · Reviewer: [name] · Date/timezone: [date] · Source/environment: [exact reference]

## Decision needed

[What can the client decide from this report? Explain the main task, affected audience, priority and recommended next action in plain language.]

## Scope actually examined

Routes: [list]
Tasks/states: [list]
Devices/browsers: [list; distinguish emulation from physical devices]
Access and permission: [read-only, local fixtures, approved live tests]
Not checked: [explicit gaps]

## Priorities

| Finding | Observation | Impact (not invented revenue) | Evidence | Owner | Next decision |
|---|---|---|---|---|---|
| [ID] | [reproducible fact] | [who is blocked/confused and why] | [reference] | [name] | [specific action] |

## Worked example: JCR-04

**Fictional Juniper Cycle Repair. Written demonstration only; no real client, website test, screenshot or business outcome.**

Observation: The service action says “Book a repair,” while its described destination is an email inquiry without an appointment calendar.

Why it matters: The label sets an expectation the next step does not fulfill. We cannot infer a conversion or revenue impact from this observation.

Recommended direction: Ask the owner whether the journey should remain inquiry-first. If yes, use “Ask about a repair” and a factual explanation of what happens next. Preserve the URL. Do not add an unsupported reply-time promise.

Priority: P1 for task clarity in this illustrative scenario. A confirmed broken send action would take precedence.

Dependency: Owner confirms workflow. Designer updates visible/accessibility copy. Developer verifies destination and wrapping.

Acceptance: Label predicts an inquiry; visible and accessible names agree; 320px layout and keyboard path remain usable. Actual email receipt requires a separately approved one-send test.

Status: **Open / needs decision.** The proposed fix is not implemented or runtime-verified by this example.

## What the client approves

- [ ] Factual description and business process
- [ ] Scope and exclusions
- [ ] Estimate and any provider/test costs
- [ ] Exact release/test action, if requested

Approval record: [person, wording, date, exact scope]. A report is not approval to deploy.

## Remaining work and review trigger

[Each open/deferred item needs an owner, a next action and a condition/date for revisiting it.]
