Work orders on the map

The Map view of the work order queue - see infrastructure work orders as pins, and plan a technician's day as an ordered route of stops.

The Map view shows the work order queue on the same map the Infrastructure module uses - each open work order bound to an infrastructure feature appears as a pin at that feature's location. It is built for the field question a list can't answer: where is today's work, and in what order should I drive it?

Reading the map

• Open work orders draw where their feature is, colored by status - blue for new, amber for in progress, grey for on hold, red for rejected. A work order on a node (a hydrant, a valve) is a dot; one on a segment (a sidewalk stretch, a watermain run) traces the segment itself as a line. A red outline marks an overdue work order. Nearby work orders collapse into numbered clusters; click a cluster to zoom in.
• Every queue filter applies - status, priority, assignee, the "My work orders" toggle, infrastructure scope, and text search all narrow the pins, exactly as they narrow the list.
• Click a pin to open a summary panel with everything the queue knows about the work order: status, priority and type badges, the bound feature, category, due and start dates, assignees, who requested and created it, estimated hours and cost, the description, safety requirements, the task checklist with its progress, and photo thumbnails - plus buttons to open the full work order or hand the location to your phone's navigation app. The same panel adds the work order to a day plan - see below.
• Click any infrastructure feature - a segment or node with no pin on it - to open its detail panel, with a Create Work Order button that opens the form with the feature already attached. Spot a broken sidewalk while planning, raise the job without leaving the map; the new pin appears when you return.
• The basemap switcher, 3D buildings, and any tenant aerial imagery from the infrastructure map are all available here.

Planning a day

Plans are built one stop at a time from the pins. Click a pin, and the summary panel carries Add to a day plan: a strip of upcoming days shows how many stops the technician already has on each (so a light day is visible at a glance), a date field reaches any day beyond the strip, and the button appends the work order as that day's next stop. Managers and Administrators can pick the technician; Staff add to their own plans. If the work order is already on that day's plan, the same control removes it. Adding a stop also assigns the work order to that technician if they weren't assigned already, and planning it for a future day moves the work order's start date to that day (removing a stop leaves both alone). This is how a week or a month fills up one decision at a time - open a work order on the map, drop it on Thursday, move on.

Saved stops are ordinary schedule entries, so they also appear on the Calendar view - the map and the calendar are two views of the same plan.

A work order is planned once

A work order holds a single stop. Pick a different day (or a different technician) for one that is already planned and it moves: the stop it had is removed, the day it left renumbers its remaining stops, and the button reads Move here rather than "Add to plan". The day already holding the work order is outlined in the strip, so you can see where it is before you move it.

The assignment follows the stop in both directions. Adding one assigns the technician; removing one un-assigns them, unless they still hold the work order on another day. Moving a job from one technician to another therefore hands over the assignment with it. When you save a plan in edit mode, the confirmation lists what will move and who will be un-assigned before you commit.

Editing the route

When the day has saved stops, the plan panel appears over the map with the stops in order. Press Edit plan to turn the map into a route builder:

1. Pick the date (defaults to today). Managers and Administrators can also pick the technician; Staff plan their own day.
2. Click pins to add stops. Each stop gets a numbered marker, and a dashed line connects them in order. Click a numbered stop to remove it.
3. Reorder by dragging rows in the stop list, or press Suggest order to let AssetLab sequence the stops by shortest straight-line route.
4. The panel totals the plan as you go: stop count, distance, and an estimated travel time between stops.
5. Save plan. The confirmation lists anything worth a second look before you commit: stops not yet assigned to the technician, stops that are planned for another day and will move here, and stops you dropped, whose assignment goes with them.

Working the plan

When you open the Map view on a day with a saved plan, My day shows your stops in order. Each stop has a Navigate button that opens the location in your phone's maps app (Google Maps) - drive to stop 1, complete the work order, navigate to stop 2, and so on. On the mobile apps this is the intended loop for a field day.

For integrators

Day plans are exposed through the REST API and MCP server as the work_order_schedules resource (scopes work_order_schedules:read / work_order_schedules:write). Filtering by technician_id and scheduled_date returns a technician's day in stop order - one call for "what is my route today".

The one-stop rule is enforced in the database, not just the screen: a second entry carrying a stop_order for a work order that already has one is rejected. Move a stop by deleting the old entry and creating the new one. Entries with no stop_order - calendar scheduling rather than a planned route - are unaffected.