Run your business · Workflow recipes
Workflow recipes
Start a client engagement with a shared checklist
Assign access requests, an engagement owner and kickoff preparation from a won advisory engagement.
Updated September 19, 2026 3 min read
A new advisory engagement has been won, but delivery needs access, source material and a kickoff date. Put that preparation in a checklist attached to the customer.
What you combine
Before you start
Use an authorized workspace with Client onboarding and Overdue commitments enabled in Plugins, a won opportunity, and valid task assignees. These plugins start disabled. Confirm the source opportunity belongs to the customer you intend to onboard.
Explore the professional services workspace with fictional records. Use it to inspect the shared screens and simulated actions; configure real forms or provider connections in a workspace you control.
Work through this example
A fictional Ledgerstone client has agreed to monthly advisory work. The engagement owner needs access to the approved source reports before kickoff.
Prepare. List the agreed reports and access channel in the request task, without copying passwords into a task description.
Assign. Make the engagement owner responsible for verifying access, and give the coordinator a separate kickoff task.
Check. Open the source report using the intended account before completing the access task. Keep missing access visible at kickoff.
Complete the workflow
-
Open Pipeline and inspect the won opportunity, customer and agreed scope.
-
Open Client onboarding and select that opportunity. Prepare these tasks: Request access through the approved channel; assign the engagement owner; arrange kickoff.
-
Give each task a description, due date and valid assignee. The plugin accepts one to ten tasks in a plan.
-
Choose Review workflow, then Request approval. Check the exact owners and dates before selecting Approve & create tasks.
-
Inspect the execution result, then open the created tasks in Tasks & approvals. Run Overdue commitments later to review tasks whose due dates have passed.
Check the result
An assigned kickoff checklist attached to the won engagement. The tasks retain their source opportunity, and Tasks & approvals shows their saved state. Checklist creation is the start of delivery; update each task as the customer work happens.
Adapt it for your business
Adapt task templates in source for different service lines; keep client identity and task creation in the existing services.
For a coded variation, use Build an extension and include this example’s decision, owner and completion check in your development brief. Keep customer identity and task history in the shared services.
What to check
If the source or an assignee changed, correct the input and prepare a fresh preview. For an uncertain execution result, inspect the original receipt before retrying with the same request identity. Confirm the existing tasks before submitting another checklist.
Plugins must be enabled for their operations to run. Hosted infrastructure and connected providers may have costs; AI conversations use your configured model. Keep each human decision required by the action’s policy, and verify the result in the source screen before relying on it.