Skip to main content
Run your business · Workflow recipes

Workflow recipes

Prepare the team for a newly won job

Use a won roofing job to assign site access, materials and start-date checks before the crew arrives.

Updated September 19, 2026 3 min read

An accepted roofing estimate needs a clear handoff to the people who will do the work. Carry the customer and opportunity into an assigned checklist.

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 home 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.

Client onboarding showing a fictional checklist and source opportunity.
The shared onboarding workflow with fictional demo data. Use the source record and saved result to follow the example; this image is not a live customer result. Select the image to view it full size.

Work through this example

Northline has won a replacement job, but the homeowner has a locked gate and the materials delivery is still being confirmed.

Prepare. Create separate tasks for gate access, material availability and the proposed start date.

Assign. Give the office the access check and the delivery owner the materials check, with dates before the planned start.

Check. Complete each task only after its confirmation is recorded; an agreed estimate alone does not establish readiness.

Complete the workflow

  1. Open Pipeline and inspect the won opportunity, customer and agreed scope.

  2. Open Client onboarding and select that opportunity. Prepare these tasks: Confirm site access; check material availability; confirm the start date.

  3. Give each task a description, due date and valid assignee. The plugin accepts one to ten tasks in a plan.

  4. Choose Review workflow, then Request approval. Check the exact owners and dates before selecting Approve & create tasks.

  5. 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

A job-start checklist with an owner and due date for each commitment. 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

Add a job record or dispatch screen in a source extension when crew scheduling needs its own lifecycle.

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.