Appointment is the Field job

Native Field’s operational “job” is the assigned Appointment, not an independently mutable copy of the work order.

Screen path: Today or Jobs → row → /app/jobs/:appointmentId. The title bar shows the work-order number as nested context. Native Field is not the Field PWA.

Work order
    ↓
one or more appointments
    ↓
technician receives the assigned appointment / Field job

Preconditions

The server only projects Field-ready appointments: not Draft work orders, not Unscheduled, assigned to this Active technician. Buying the app does not create that assignment.

Loop

1. Office opens a work order and creates/assigns an appointment.
2. Field pulls the appointment into Drift.
3. You execute your assignment on that appointment.
4. Complete job completes the appointment. Office Complete on the work order is a later CMS step.

The work-order number on a row is nested context. Draft work orders never appear. Preventive maintenance, estimate conversion, and finding follow-up create Draft work orders in the office — they are not Field jobs until office Opens, adds an appointment, and assigns you.

Field never creates work orders.

What works / does not work

	Works	Does not work
Several appointments on one WO	Each is its own Field job	Treating the WO as the Field job
Finding follow-up Draft	After office assigns a visit	Auto-creating a Field job from Add a finding
Unscheduled WO in CMS	Not a Field job	Appearing on Today/Jobs

If you see the work order in the CMS but not in Field: Draft, Unscheduled, or unassigned. Ask office to date and assign the appointment.

Related: Today · Web appointments.