Treat a second practice area as a new review gate

The operational decision

Prevent a working pilot from inheriting unsuitable questions or routing for another team. Operational delegation should be explicit: staff and software need to know which actions are permitted and which require firm review. A smooth workflow is not a substitute for that approval record.

Prepare the workflow

Create a separate scope, script, reviewer and test set for the new area; inspect shared fields for assumptions that no longer apply.

Example wording for approval

“The example second practice area is not active yet. Its intake questions and staff route require separate approval before public callers are invited to use it.”

Worked example

The first fictional pilot handles estate-planning requests, and staff want to add employment inquiries. Copying the script may preserve inappropriate questions, consultation policy or escalation destinations. Create the new area's own approved fields and tests, then review any shared components deliberately. The new area remains inactive until those checks pass. A successful call in the original area proves only that original workflow, not that every legal practice can use the same questions or staff handoff unchanged.

Handoff record

Record these task-specific fields: new practice label, script owner, route owner, readiness status.

Acceptance check

Copy the original script into the new area during review. Identify and remove every question or promise that depends on the first practice area's process.

Related guides