Ready for Work

The Ready for Work feature adds a quality gate to your routes. A route must be explicitly marked as "Ready for Work" before it becomes visible on worker dashboards and triggers client notifications. This prevents incomplete or draft routes from cluttering dashboards and avoids premature reminders for routes still being planned.

How It Works

Every route has a Ready for Work status that defaults to Not Ready for newly created routes. When a planner finishes organizing a route — assigning activities, team members, and confirming the sequence — they mark the route as ready. This signals that the route is finalized and workers can rely on it.

Route Lifecycle with Ready for Work

1. Create route — A new route is created in Draft status, Not Ready.
2. Assign team members — Route moves to Assigned status.
3. Add and order activities — Planner drags activities into the route.
4. Mark as Ready for Work — Planner clicks the toggle to mark the route as ready.
5. Route appears on dashboards — Workers can now see the route (if the organization setting is enabled).
6. Notifications are scheduled — Client reminders are queued (if the notification gating setting is enabled).

Using the Toggle

The Ready for Work toggle is located in the route card header on the Route Planner page.

Marking a Route as Ready

1. Navigate to the Route Planner.
2. Find the route you want to mark as ready.
3. Click the Ready for Work toggle in the route card header.
4. The route card updates to show a green "Ready" badge.

Unmarking a Route

1. Click the Ready for Work toggle again to unmark the route.
2. The route returns to "Not Ready" status.

warning

Unmarking a route may hide it from worker dashboards and cancel any pending client notifications, depending on your organization settings.

Toggle Availability

The toggle is only available when the route is in certain statuses:

Route Status	Toggle Available?	Reason
Draft	No	Assign at least one team member first
Assigned	Yes	Route can be marked as ready
In Progress	No	Route is already being worked on
Completed	No	Route is finished
Cancelled	No	Route has been cancelled

Mark All Ready

Below the toolbar on the Route Planner, a Mark All Ready button appears when there are eligible routes that haven't been marked as ready yet. It marks all eligible routes for the selected date as ready in a single action.

1. Navigate to the Route Planner.
2. Select the date whose routes you want to mark as ready.
3. Click the Mark All Ready button below the toolbar.
4. Confirm the action in the dialog that appears.

This is useful when you plan all routes for the next day and want to release them to workers at once.

Organization Settings

Two organization-level settings control how Ready for Work affects dashboards and notifications:

Setting	Effect
Only show Ready for Work routes on dashboard	When enabled, non-ready routes are hidden from the dashboard and worker schedules. Activities not assigned to any route are always shown.
Only send reminders for Ready for Work routes	When enabled, client notifications are only scheduled for activities on ready routes. Notifications are deferred until the route is marked ready. This applies to both automatic scheduled notifications and manual daily dispatch via the Send Reminders button.

Both settings default to off. When disabled, all routes appear on dashboards and all activities trigger notifications normally — the Ready for Work toggle still works as a visual indicator but has no filtering effect.

tip

When Only send reminders for Ready for Work routes is enabled and you open the Send Reminders dialog from the Route Planner, a warning will appear showing how many routes are excluded because they haven't been marked as ready yet. This helps you decide whether to mark routes as ready before dispatching.

These settings are configured on the Organization Settings page.

What's Next?

• The Route Planner Page — Learn about the full dispatch board interface.
• Organization Settings — Configure dashboard and notification gating settings.
• Scheduled Notifications — Understand how notifications are queued and sent.