Write the first practice-area pilot scope

The operational decision

Keep the managed legal pilot bounded enough for the firm to approve and test. A reliable intake workflow needs an owner after launch. Staff availability, practice scope and public contact routes change, so the operating record should explain who can update the system and how changes are verified.

Prepare the workflow

List one practice area, office, intake script, calendar condition and escalation tree; identify what requires a new scope agreement.

Example wording for approval

“This example pilot covers one approved intake path. Additional practice areas, offices and integrations need separate review before they become part of the live service.”

Worked example

The fictional plan includes one practice area, one office, one script and three routing destinations. During setup, staff request a second office and a case-management write. Add those as proposed changes with separate dependencies rather than assuming the original price and approval cover them. The scope record should show what is active, conditional and excluded. A useful final review asks the operator to explain those distinctions without relying on informal sales conversations or a broad feature list.

Handoff record

Record these task-specific fields: practice area, included routes, excluded work, approver.

Acceptance check

Ask to add a second practice area during setup. The workflow should treat it as a scope change with its own script and test requirements.

Related guides