# Client AI editing plan

Use this worksheet before inviting a client to edit a website with AI. Replace the examples with the controls and responsibilities of the actual project.

## 1. Choose the editing surface

- [ ] Content fields only: the client changes predefined text, images, or structured records.
- [ ] Component/page builder: the client assembles approved components or sections.
- [ ] Full-site agent: the client can request changes that may modify code and layout.

Why this surface fits the client's recurring work:

What it must not expose:

## 2. Map the work

| Request type | Example | Route | Enforced by | Human check | Release authority |
|---|---|---|---|---|---|
| Client can do | Update opening hours |  |  |  |  |
| Review required | Replace homepage hero image |  |  |  |  |
| Agency only | Change form destination |  |  |  |  |
| Agency only | Add analytics or third-party code |  |  |  |  |

“Enforced by” should name a real control such as a role permission, page permission, branch rule, or content schema. Write “process only” if the boundary is an instruction rather than a technical restriction.

## 3. Configure and test the client account

Client account:

Assigned project/site:

Assigned role:

Can edit:

Can review/comment:

Can approve:

Can publish/deploy:

Can invite others:

Can reach billing, secrets, code, customer records, or form submissions:

Tested with the actual client role on:

- [ ] One allowed task succeeds.
- [ ] One restricted task is blocked or routed correctly.
- [ ] The account cannot see unrelated client projects.
- [ ] The publish/deploy behavior matches the agreement.
- [ ] The recovery operator is named.

## 4. Client edit brief

**Page or area:**

**Exact outcome:**

**Source material:**

**Keep unchanged:**

**Check before release:**

**Stop and ask if:**

Example:

> On the Contact page, change the Saturday hours from “9 a.m. to 1 p.m.” to “10 a.m. to 2 p.m.” Keep all other hours, layout, styles, links, and form behavior unchanged. Check the updated text at phone and desktop widths and confirm the same hours are not repeated elsewhere. Stop and ask if another page contains a conflicting schedule.

## 5. Release record

Change requested by:

Business facts approved by:

Preview or checkpoint reviewed:

Checks completed:

Released by:

Release date:

Recovery contact:

Known external systems that a website restore will not reverse:

## 6. Illustrative worked example

Assumptions: a fictional neighborhood clinic has a five-page brochure website and contact form, but no checkout or patient portal. Its marketing coordinator maintains hours, staff bios, and approved photographs. The agency maintains forms, integrations, layout, and code.

| Request | Route | Why |
|---|---|---|
| Correct a staff bio | Client can do, then preview | Bounded copy change with a named fact owner |
| Replace an approved staff photo | Client can do, with mobile and alt-text check | Content change can still affect crop and layout |
| Announce holiday hours | Review required | Date and opening-time accuracy have business consequences |
| Change the contact form recipient | Agency only | Integration behavior and private destination are involved |
| Add an online booking system | New scope | This changes workflow, data handling, and testing requirements |

This example is a starting point, not a claim about a real clinic or an automatic platform policy.