Operations

Connections to Other Modules

Operations is the center of scheduled and reactive work, but it does not operate in isolation. Work orders, checklists, and schedules link directly to Service Desk, Risks, Calendar, Inbox, and Forms so that a reported problem becomes a planned job, field findings become follow-up tickets, and every record stays connected for audit.

Service Desk to Operations

When an issue or request in Service Desk needs physical work, you can convert it into a work order without retyping the details.

  • Create a work order from an issue or request to schedule, assign, and track the job. Title, description, priority, and location carry over automatically.

  • Attach an existing work order to an issue or request when the work is already planned. The original record and the work order stay linked, so progress is visible from both sides.

The original ticket and the work order each show the link, so progress is visible from both sides. Images copied from an issue or request are badged Service desk in the work order gallery, so field evidence and office reports are easy to tell apart. See Creating Work Orders from Issues or Requests for the full steps.

Operations to Service Desk

Field work often surfaces new problems. You can raise a Service Desk ticket straight from a work order checklist step so the finding is logged immediately and linked to the job that found it.

  • Report an issue from a flagged checklist step. The issue is created with the work order and step already attached, so context is preserved.

  • Submit a service request from a checklist step when the finding needs planned work rather than an urgent fix.

Quick-submit options let you send a short note immediately, or open the full form to add severity, photos, and category before submitting. See Reporting Issues and Submitting Service Requests for details.

Risks

Risk assessments can be surfaced inside a work order when the job requires acknowledging hazards before starting.

  • Linked assessments appear on the work order detail page when the site has risk data attached to the target location or asset.

  • Acknowledgement may be required before a worker can start the job, depending on site settings.

Users need permission to view risk assessments in order to see this section on a work order.

Calendar and Inbox

Assigned work is surfaced where people already look for their next task.

  • Inbox Active tab shows individually assigned work orders that are planned and due today, overdue, or unscheduled, as well as work orders that are already in progress. You can start or continue the job directly from the card.

  • Calendar events can be used as triggers for planned work schedules. When a schedule is set to fire on a named calendar event, the system generates the work order based on the event date and any offset you configure.

Forms

Forms can be raised in the context of a work order and linked back to it.

  • Related form requests appear on the work order detail page, so you can see submissions that were collected during or alongside the job.

  • Issue and request forms accept a linked work order, so a form submitted from the field is tied to the correct job record automatically.

What stays connected

Because every link is stored as a record-to-record relationship, you can move from a Service Desk ticket to the work order that resolved it, from a checklist step to the issue it raised, or from a work order to the form submissions completed on site. This keeps audit trails complete and avoids duplicate data entry across modules.

Was this helpful?