Bulk Operations and Deployment

Selecting jobs

Select jobs using the checkboxes on job cards in the work queue, board, or timeline views.

When at least one job is selected, the selection dock appears showing:

• The number of selected jobs
• Available bulk actions: Bulk edit, Propose slots, Shift dates, Build run, Deploy, Clear

Selection persists across view changes — you can select jobs in the board, switch to the map to check geography, then switch back.

Bulk editing

The Bulk Update drawer edits up to 100 jobs at once. Each field has its own toggle so you change only what you intend.

Opening the drawer

1. Select one or more jobs.
2. Click Bulk edit in the selection dock.
3. The drawer opens with all toggles off.

When exactly one job is selected, the drawer prepopulates form fields from that job. When multiple jobs are selected, fields start at defaults (the toggles remain off either way).

Available field toggles

How toggles prevent accidental overwrites

Only enabled toggles are sent to the server. If you enable just the Assignee toggle and change the engineer, the other fields (date, equipment, crew size, etc.) are not touched on any of the selected jobs.

This is critical for multi-job edits — you can reassign 20 jobs without disturbing their individual scheduling or equipment settings.

Saving

Click Preview Changes before applying. The preview shows valid, warned, and blocked jobs, plus route suggestions when the selected work overlaps route clusters.

Click Apply only when no jobs are blocked. The update:

1. Sends only the toggled fields to the server.
2. Validates each job against the update (e.g. rejects if new blocking warnings would be introduced).
3. Applies optimistically to the local state for instant visual feedback.
4. Triggers a background refresh to confirm server state.

Deployment lifecycle

Jobs progress through a two-state lifecycle:

Draft  →  Deployed

What makes a job deploy-ready

Use the Ready pipeline stage to see all jobs that pass these checks. Target-month records are useful for capacity planning, but they are not deploy-ready until they are converted to an exact date and time. Provisional and Date offered records also remain outside Ready until the booking becomes Confirmed or Do not move.

How to deploy

1. Select the jobs you want to deploy.
2. Click Deploy in the selection dock.
3. Review the deployment preview:
   • Jobs that are ready show a green check
   • Jobs that are blocked show the blocking reason
4. Move blocked or target-month work out of the batch or correct it before confirming.
5. Confirm the deployment.

What deployment does

Deployment acceptance indicators

After deployment, the planner can track whether each engineer has seen their schedule:

How acknowledgement works:

When an engineer opens their My Day Run in the mobile app, the server automatically marks all of that day's deployed stops as acknowledged. No button press is needed — opening the day run is sufficient. This is recorded silently without delaying the response.

Checking acknowledgement status:

• Pipeline stages: Use Deployed to review released work, then inspect cards or map pins for acknowledgement state.
• Map view: Map pins use an amber tone for sites with unacknowledged deployed work. The popup shows an acknowledgement summary (e.g. "2 acknowledged / 1 awaiting").
• Overview stats: Scheduler overview warning buckets include awaiting and acknowledged counts for reporting and downstream views.

When acknowledgement resets:

Re-deploying a job (after a schedule change, engineer reassignment, or duration change) clears the acknowledgement. The badge returns to Deployed ○ until the engineer opens their day run again. This ensures engineers always see the latest version of their schedule.

What resets deployment

Any scheduling change to a deployed job resets it back to draft:

• Changing the scheduled date
• Changing the assigned engineer
• Changing the estimated duration

This ensures engineers always see the latest plan. The job must be re-deployed after changes.

Undoing changes

Every scheduler mutation is logged with a before/after snapshot. Undo remains available from scheduler history-backed workflows where the route exposes it.

Undo restores the job to its state before the change. Only the most recent change per job can be undone.

Propose slots and re-plan a day

Use Propose slots when selected work needs feasible engineer and time combinations. Review the batch, decline any unsuitable row, and apply the remainder only while the preview is current. Planner changes invalidate a stale preview so it cannot overwrite newer decisions.

Use Re-plan day from the week timeline when a date needs broader recovery. Choose whether to redistribute work on the same day or shift it to another date, then review affected customer promises and any work the preview could not place. The workflow preserves unaffected crew assignments and offers undo after a successful apply.

Batch inspection creation

When you need inspections across multiple systems at a site:

1. Click Batch schedule visits in the page header.
2. Select the site and systems.
3. Choose inspection type — annual or 6-monthly.
4. Assign an engineer and set scheduling fields.
5. Review and create.

Up to 50 inspections per batch. Each inherits site data and scheduling rules.

How scheduled work reaches engineers

The flow from scheduler to field:

1. Office team creates or imports work into the scheduler.
2. Planner assigns an engineer, sets a date, and adds operational metadata.
3. Planner deploys the batch.
4. Engineer receives a notification email.
5. Engineer opens the mobile app and sees the day run — a route-ordered list of today's jobs. This silently acknowledges the deployed work; badges change from Deployed ○ to Deployed ✓ in the planner's view.
6. Engineer navigates to each site, runs inspections, completes work orders.
7. Completed work flows back to the admin portal for review, defect management, and invoicing.

The scheduler is the critical handoff point. Work that is not deployed does not reach the field.

Example: end-of-week deployment cycle

1. Monday-Thursday: Schedule and assign work for next week using board and timeline views.
2. Thursday afternoon: Use the Week Timeline for next week to verify coverage.
3. Thursday: Filter by Ready → review the batch.
4. Thursday: Select all ready jobs → Deploy.
5. Friday morning: Engineers receive notifications and can preview next week's work.
6. Friday/weekend: Planners review Deployed work and acknowledgement indicators — engineers who haven't opened their day run are flagged.
7. Monday: Engineers execute the day run from the mobile app. Badges update to Deployed ✓ as each engineer opens their route.

Troubleshooting