# Client discovery worksheet

For a prebuilt system, an adaptation or a new build across any business function. Record requirements here; verify availability and fit separately. Use role names and sample records rather than credentials or sensitive client data.

## People and outcome

- Client / project:
- Business function or system:
- Sponsor and acceptance owner:
- Partner implementer:
- Client administrator:
- Employees who will try the first process:
- What should improve, and how will we measure it?
- Target date and constraints:

## First process

- What starts the work?
- Which records are created or updated?
- Who takes each step, and who approves decisions?
- What result marks the work complete?
- What common exception must the first release handle?
- Which current tools or manual steps will this replace or connect to?

## Starting point and scope

- Approach: use an available system / adapt a starting system / build afresh:
- Starting system and version, if applicable:
- Behavior inspected and confirmed:
- Changes needed for the client:
- Required integrations and their owners:
- Included in the first release:
- Deferred or excluded:
- Open questions and who will resolve them:

## Data and access

- Source data, owner and approximate volume:
- Import fields, relationships and matching rules:
- Required cleanup and reconciliation checks:
- Roles allowed to view, create, change, approve or export each record type:
- Sensitive fields and their access restrictions:
- Who authorizes partner and agent access?
- Who administers the workspace after handover?

## Acceptance examples

Complete at least one normal case and one exception. Include a permission check.

| Scenario          | Person / role | Action | Expected result | Evidence and reviewer |
| ----------------- | ------------- | ------ | --------------- | --------------------- |
| Normal process    |               |        |                 |                       |
| Exception         |               |        |                 |                       |
| Restricted action |               |        |                 |                       |

## Proto brief

> We need a [system] for [business function]. Start from [verified starting point, or a new build]. The first release must support [complete process] for [roles], using [records and relationships]. Include [changes] and exclude [deferred scope]. Propose a plan for review, identify gaps and dependencies, and validate it against [acceptance cases].

## Delivery and continuing support

- Sponsor's scope decision and date:
- Data preparation owner:
- Employee training and guidance:
- Go-live decision owner and recovery approach:
- Partner responsibilities after delivery:
- Client responsibilities after delivery:
- Support contact / route and escalation owner:
- How are future changes requested and approved?