Work Order Management

Keep the request, responsibility, and work history together.

REQQER gives facility teams one central Requests Console for managing one-time Work Orders alongside recurring Scheduled Tasks—without losing the distinction between them.

Prioritize the work, assign responsibility, document progress, keep On Hold items visible, and get back to recently completed work quickly.

REQQER Requests Console showing Work Orders and Scheduled Tasks

One working list

See the work that needs attention without opening every Req.

The Requests Console is the working center for Desktop REQQER. Built-in views handle common questions immediately; detailed filtering and interactive summaries are available when you need to narrow the list further.

Fast built-in views

Move among All Open Reqs, Work Orders, Scheduled Tasks, My work, On Hold items, and Reqs closed within the last 24 hours.

Find the exact subset

Use detailed filters for dates, status, Type, Work Order versus Scheduled Task, frequency, Item, Location, assignment, vendor, Department, priority, and more.

Act from the list

See assignment, Due Date, status, Scheduled Task and attachment indicators—and assign available staff directly from the Console when permitted.

Explore the Requests Console

Scan broadly, identify the issue, narrow the list, and act.

The deeper controls are there when you need them without forcing every user through a complicated workflow for ordinary work.

REQQER Requests Console

Working view

One central list for current work.

The default Console presents Open work while keeping one-time Work Orders and recurring Scheduled Tasks distinguishable and immediately accessible through built-in views.

Built-in Work Orders, Scheduled Tasks, My, On Hold, and Recently Closed views.
Calendar-style icon identifies Scheduler-generated work; paperclip indicates attachments.
Assignment, Due Date, Type, Location, status, and other working information remain visible in the list.

Work Orders and Scheduled Tasks

Manage them together without pretending they are the same thing.

A Work Order is one-time work. A Scheduled Task is an individual occurrence generated from a recurring Scheduler definition. Both are Reqs and both can appear in the Requests Console, but REQQER preserves the difference because recurring obligations need their own history and future schedule.

One-time Work Order

Created for a specific issue, service need, walkthrough finding, or other non-recurring request.

  • Can normally be closed immediately
  • Activity can document what was done
  • Attachments and communication remain with the Req

Scheduled Task occurrence

Generated from the Scheduler as one separately trackable occurrence of recurring work.

  • Own Due Date and Activity history
  • May require Activity, form responses, or supporting documentation before closure
  • Closing one occurrence does not erase the recurring program

Keep work accountable

Track what happened, what is waiting, and who is responsible.

A

Activity + Work Duration

Record work performed, progress, communications, next steps, and the actual time spent. Prior Activity remains part of the Req history.

On Hold without disappearing

When work cannot proceed, permitted Desktop users can place the Req On Hold so it remains visible and trackable rather than being mistaken for completed work.

Reopen when needed

Users with appropriate permission can reopen a completed Req from the Requests Console when additional work is required.

I

Internal responsibility

The Internal Assignee identifies the in-house person responsible for managing and ensuring completion of the Req.

V

External Vendor work

An outside specialist can be assigned while the Internal Assignee remains responsible for follow-up, documentation, and proper completion.

Documents stay connected

Photographs, reports, proposals, certifications, and other supporting files remain associated with the work instead of being separated into unrelated folders and inboxes.

Req lifecycle

Keep the work visible from request through completion.

The individual Req becomes the shared operational record rather than a disposable ticket number.

CreateIssue or need captured
PrioritizeType · Priority · Due Date
AssignInternal and/or Vendor
PerformActivity · Duration · Files
Hold if neededRemain visible while waiting
CompleteHistory retained · reopen if needed

Multiple ways in, one managed process

Bring requests into REQQER instead of chasing them across channels.

One-time Work Orders can be captured through the interface appropriate to the person reporting the issue, while the resulting work enters the same management process.

DesktopSingle request entry
Batch EntryMultiple walkthrough findings
MobileField creation and updates
Quick EntryLogin-free staff submission
Email / VoicemailSupported inbound channels

Related capabilities

Work Order Management is the operational center—not an isolated module.

See Work Order Management in context

See how your current request process would work inside REQQER.

We can focus a demonstration on request intake, assignment, daily work management, Mobile workflows, documentation, or the relationship between Work Orders and recurring Scheduled Tasks.