Work Orders

Work orders turn sold or approved project scope into executable field work.

What A Work Order Contains

A work order is tied to a project and can include:

• a scheduled date and time
• a route
• one or more line items
• work items for installable or serviceable scope
• derived inventory requirements such as film rolls
• operational notes used in scheduling and field execution

Work Order States

The standard lifecycle is:

1. Draft
2. ReadyToSchedule
3. Published
4. Completed

Why Publishing Matters

Publishing is the handoff point between internal preparation and field-facing execution. Once published, the work order becomes part of the operational schedule and downstream field processes can treat it as ready.

Scheduling Data

Tempr exposes scheduler data for resources and work orders through internal API endpoints. That allows calendar and routing views to display planned work alongside route ownership and timing.

Field And Mobile Behaviors

The v3 work-order API supports authenticated actions such as:

• list work orders
• get a single work order
• upload work-order photos
• mark a crew as en route

These capabilities are documented in the API tab because they are often consumed by field tools or mobile clients rather than directly by the main admin UI.

Inventory Relationship

Some work orders depend on assigned inventory before execution. In the work-order model, film-related work items can be checked for assignment completeness so operations can catch shortages before install day.

External Sharing

Tempr also supports tokenized external work-order previews for cases where a non-logged-in recipient needs a controlled view of the document.

Best Practices

• do not publish a work order before confirming route, schedule, and material readiness
• use photos and field updates to keep project status accurate
• treat work-order completion as an operational milestone, not just a scheduling label