---
title: "Work Order Management System: Build One Techs Use on Phones"
url: "https://goremy.ai/blog/articles/build-a-facilities-work-order-tracker-your-techs-can-use-on"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-17T01:00:20.886Z"
updated: "2026-11-17T01:00:20.886Z"
topic: Request Tracking Apps
description: Replace email and spreadsheets with a simple work order management system. Get a copy-ready work order template, a worked example, and an AI prompt.
---

# Work Order Management System: Build One Techs Use on Phones

> Replace email and spreadsheets with a simple work order management system. Get a copy-ready work order template, a worked example, and an AI prompt.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-17

## What is a work order management system?

A work order management system is software that records every maintenance or facilities request from the moment someone reports a problem until the work is finished and confirmed. Each request becomes a single record with a location, a description, a priority, an assigned person, a status and a completion note. Anyone can see where a job stands without asking. For a facilities team, it replaces the shared inbox, the sticky notes and the spreadsheet nobody trusts.

This post gives you the work order template itself, shows how to fill it in with a real example, and walks through building a phone-friendly tracker your technicians will actually open.

## TL;DR

- A work order system only needs **one record per job** with a requester, a location, a priority, an owner, a status and a closing note. Everything else is optional.
- **Techs adopt tools that work on a phone**, take photos in two taps and don't make them type much. If the tool fails that test, they will go back to texting.
- Define **four priority levels and six statuses** before you build anything. Most tracker failures are vague definitions, not missing features.
- A purchased CMMS (computerized maintenance management system) makes sense for heavy preventive maintenance and compliance. A **small custom tracker** makes sense when your real problem is requests getting lost.
- AI is useful for **drafting fields, cleaning up messy email requests and summarizing the backlog**. It should not decide safety priority or invent asset data.
- Measure **time to acknowledge, time to close, and reopen rate**. Those three numbers tell you whether the system is working.

## Why do email and spreadsheets fail for facilities work?

Email works for conversation and fails as a record. A request arrives as "the third floor is freezing," with no room number, no photo and three people copied. Someone replies "on it." Two weeks later nobody knows whether it was fixed.

Spreadsheets fix the record problem and create new ones:

- **Nobody owns the update.** Techs finish a job in a stairwell and have no reason to open a laptop.
- **Requesters can't see status**, so they email again, which creates duplicates.
- **There is no clear intake.** Requests arrive by email, phone, hallway conversation and chat, and someone has to retype them.
- **History is hard to search.** When the same air handler fails for the fourth time, the pattern is buried across tabs.
- **Photos live in texts**, not on the job.

A work order system solves exactly these five problems. It does not need dozens of features to do so.

## Should you buy a CMMS or build your own tracker?

Be honest about which problem you have.

| Your situation | Better fit |
|---|---|
| Requests get lost, duplicated or ignored | Simple custom tracker |
| You need to see who is working on what, today | Simple custom tracker |
| You manage hundreds of assets with scheduled preventive maintenance and meter readings | Purchased CMMS |
| Auditors require specific inspection records and certifications | Purchased CMMS, or a custom build with those fields specified |
| You need inventory with reorder points across multiple storerooms | Purchased CMMS |
| Your workflow is unusual (your approval chain, your cost codes, your building names) | Custom tracker |

If your company already licenses a CMMS or an IT service desk tool, check whether it can be opened to your team before building anything. Many large companies already own one that no one in facilities has been given access to. If it can't be, or if it's too heavy for your techs to use on a phone, a custom tracker is a reasonable answer.

Pricing varies widely by vendor and by seat count, so check each vendor's pricing page rather than relying on a general figure.

## What should a work order template include?

Split the record into three parts, based on who fills it in. Requesters should see only the first part. Dispatchers handle the second. Techs handle the third. This keeps each person's task short.

### Copy-ready work order template

**Part 1: Request (filled in by the requester)**

| Field | Type | Required | Notes |
|---|---|---|---|
| Requester name | Auto from sign-in | Yes | Don't make people retype it |
| Requester phone or email | Auto or text | Yes | For follow-up |
| Building | Dropdown | Yes | Use your real building names |
| Floor / room / area | Text | Yes | "3rd floor, east conference room" |
| Category | Dropdown | Yes | Plumbing, HVAC, electrical, lighting, doors and locks, furniture, cleaning, grounds, other |
| What's wrong? | Long text | Yes | One or two sentences |
| Photo | Upload | No | Strongly encouraged |
| Is anyone at risk right now? | Yes/No | Yes | Triggers immediate dispatcher alert |
| Best time for access | Text | No | "After 5 pm" |

**Part 2: Triage (filled in by the dispatcher or supervisor)**

| Field | Type | Notes |
|---|---|---|
| Work order number | Auto | Sequential, never reused |
| Priority | P1 to P4 | See definitions below |
| Assigned to | Person | One owner, not a team |
| Due date | Date | Set from priority |
| Status | Dropdown | See list below |
| Vendor required? | Yes/No | If yes, add vendor name |
| Internal notes | Long text | Not visible to the requester |

**Part 3: Completion (filled in by the technician)**

| Field | Type | Notes |
|---|---|---|
| Work performed | Long text | What was actually done |
| Parts or materials used | Text | Free text is fine to start |
| Time spent | Number (hours) | Rough is fine |
| Completion photo | Upload | Proof and future reference |
| Follow-up needed? | Yes/No | Creates a linked new order |
| Completed at | Timestamp | Auto |
| Requester confirmed fixed? | Yes/No | Closes the loop |

**Priority definitions (adjust the targets to your own policy)**

- **P1 Emergency:** safety risk, active flooding, no heat or cooling in an extreme-weather situation, security breach. Acknowledge immediately. Work starts the same day, often within the hour.
- **P2 Urgent:** a space can't be used or a business process is blocked. Target: within one business day.
- **P3 Routine:** works but needs repair. Target: within a week or so.
- **P4 Scheduled:** projects, cosmetic work, non-urgent improvements. Scheduled when capacity allows.

**Statuses**

1. New
2. Assigned
3. In progress
4. Waiting (parts, vendor or access)
5. Completed (tech finished)
6. Closed (requester confirmed, or auto-closed after a set number of days with no objection)

Add "Cancelled" for duplicates and withdrawn requests, so they don't clutter the backlog.

## What does a filled-in work order look like?

Here is an illustrative example for a company campus with three buildings, one dispatcher and five technicians.

**Part 1 (requester)**
- Requester: Dana Ortiz, dana.ortiz@example.com
- Building: Building B
- Location: 2nd floor, room 214
- Category: HVAC
- What's wrong: "Room is very warm all afternoon, thermostat shows 79 and doesn't respond."
- Photo: thermostat display
- Anyone at risk: No
- Best time for access: Before 10 am

**Part 2 (dispatcher)**
- Number: WO-1042
- Priority: P3 Routine (it bumps to P2 if the room hosts client meetings this week)
- Assigned to: Marcus
- Due: five business days out
- Status: Assigned

**Part 3 (technician)**
- Work performed: "Replaced thermostat batteries, recalibrated. Found the damper actuator sticking; adjusted and lubricated. Temp reading 72 after 30 minutes."
- Parts: 2 AA batteries
- Time: 1.5 hours
- Follow-up needed: Yes, "inspect actuators on rest of floor 2," which becomes WO-1051
- Requester confirmed fixed: Yes

Notice the follow-up. A good tracker captures "while I was there, I noticed..." as a new job instead of leaving it in someone's head.

## How do you build the tracker step by step?

1. **List your real buildings, areas and categories.** Walk through your last 50 requests and group them. If a category gets used twice a year, fold it into "other." Fewer choices means cleaner data.
2. **Agree on the priority definitions and statuses** (use the ones above as a start). Get the facilities lead to sign off. These are the rules the system will enforce, so arguing about them later is expensive.
3. **Decide who sees what.** Requesters see only their own orders. Dispatchers see everything and can assign. Technicians see their own queue and can update status. A manager sees reports. This needs sign-in, not a shared link.
4. **Design the technician screen first.** It should show "my open jobs," sorted by priority, with big buttons: Start, Waiting, Complete. Photo upload is one tap. Test it on a real phone, with gloves if that's your reality.
5. **Design the request form second.** Four or five fields and a photo. If it takes more than a minute, people go back to email.
6. **Set up notifications.** The requester gets an email when the order is created, assigned and completed. The dispatcher gets an alert for anything marked "someone is at risk."
7. **Load your open backlog.** Import what's currently in your spreadsheet or inbox so day one doesn't start from zero. (The AI prompt below helps with this.)
8. **Run a two-week pilot** with one building and two technicians. Fix what annoys them. Then expand.
9. **Retire the old channels.** Send an auto-reply from the old facilities inbox that points to the new form. If email still works as an intake, the form won't get used.

## Which AI prompts help with a work order system?

AI helps in three places: designing the tracker, converting messy history into clean records, and summarizing what's open. Paste these into the AI assistant your company has approved. Do not paste names, personal details or confidential information into a tool your company hasn't cleared.

### Prompt 1: Draft the tracker specification

```
I manage facilities for [number] buildings at a large company. I want a simple internal
work order tracker used on phones by [number] technicians, [number] dispatcher(s), and
employees who submit requests.

Write a plain-English product specification covering:
- Three user roles (requester, dispatcher, technician) and what each can see and do
- A request form with these fields: [paste Part 1 of the template]
- Dispatcher fields: [paste Part 2]
- Technician completion fields: [paste Part 3]
- Priority levels: [paste definitions]
- Statuses: [paste statuses]
- Email notifications at creation, assignment and completion
- A manager view showing open orders by priority, average time to close, and orders
  older than 14 days
- Mobile-first screens for technicians with large buttons and one-tap photo upload

List any questions you need answered before this could be built.
```

Check the answer for fields you didn't ask for. If the AI added "cost center" and "asset ID," decide whether you really track them. Extra fields become blanks that people skip.

### Prompt 2: Turn email requests into work order records

```
Below are [number] maintenance request emails. For each, produce one row with:
Building, Floor/Room, Category (choose only from: plumbing, HVAC, electrical,
lighting, doors and locks, furniture, cleaning, grounds, other), Short description
(under 20 words), Suggested priority (P1 to P4 using the definitions below), and
"Needs clarification" (yes/no, with what is missing).

If the building or room isn't stated, write "UNKNOWN". Do not guess.
Flag any request that mentions injury, fire, smoke, gas, flooding, exposed wiring or
a security concern with "SAFETY REVIEW".

Priority definitions: [paste]

Emails:
[paste]
```

### Prompt 3: Summarize the backlog for a weekly meeting

```
Here is an export of open work orders (CSV). Summarize for a facilities weekly meeting:
the five oldest open orders, any location or category with three or more orders in the
last 30 days, orders waiting on parts or vendors for more than 7 days, and anything
that looks like a repeat of an earlier order. Present as short bullet lists. Do not
invent causes.

[paste data]
```

### Where AI should not be trusted

- **Safety priority.** Let AI flag candidates for review, but a person decides whether something is an emergency. A wrong "routine" on a gas smell is the worst possible error.
- **Guessing locations or assets.** If the email doesn't say which room, the right output is "unknown." Check for invented room numbers.
- **Costs, code compliance and warranty questions.** AI doesn't know your contracts, local codes or equipment history.
- **Diagnosing the repair.** Techs know the building. A chatbot's guess about a cause can send someone down the wrong path.
- **Counts and averages.** When summarizing exports, spot-check totals against the source. Language models can miscount.

## What makes a work order app work on a phone?

Technicians judge a tool in the first week. These are the details that decide adoption:

- **It works in a browser** without an app-store install, so new hires and contractors can use it at once.
- **Big tap targets** and few fields. A tech in a mechanical room should be able to mark a job complete with a thumb.
- **Photos first.** Taking a before and after photo should be quicker than typing a sentence.
- **Handles weak signal.** Basements and stairwells have poor coverage. Test where your techs actually work, and note whether the tool saves or fails when the connection drops.
- **Fast sign-in.** If it asks for a long password every shift, people stop. Use your company's single sign-on if you can.
- **A "my jobs" default view**, not a giant list of everything.
- **Voice dictation works** in the notes field. Most phones support it already.

## How do you roll it out so people use it?

Tools fail on habit, not on features. A few practices that help:

- **Involve one respected technician in the design.** Their opinion about the completion screen matters more than yours.
- **Make the tracker the only way to assign work.** If a supervisor texts a tech a job and the tech does it, the system is bypassed. Reply with the work order link instead.
- **Show requesters the status page.** Once people can see "assigned to Marcus, due Friday," the "any update?" emails drop.
- **Don't over-collect.** If you can't say who will read a field, remove it.
- **Review weekly for the first month.** Look at orders stuck in "New," orders with no completion notes and categories that are mostly "other." Fix the form, not the people.

## Which numbers should you track?

Start with three:

1. **Time to acknowledge:** how long from submission to assignment.
2. **Time to close:** from submission to completion, by priority.
3. **Reopen rate:** how often the requester says it isn't fixed.

Add backlog age (how many orders are older than 14 days) and repeat locations (the same room or equipment appearing again and again) after the first month. Repeat locations are how you justify replacing equipment instead of patching it, which is often the most valuable thing a tracker teaches you.

## Can you build this tracker without a developer?

Yes. With [Remy](https://goremy.ai), you describe the tracker in plain English, using the template and spec prompt above, and it builds a full-stack web app with sign-in, roles, a database, photo uploads and email notifications, then deploys it to a live URL. A typical first build takes about an hour. It builds mobile-responsive web apps, not native iPhone or Android apps, which suits technicians opening a link. Pricing is a flat monthly platform fee plus AI usage at cost, so check the pricing page before you commit. Ask your IT or security team about approval before putting company data in any new tool.

## Frequently Asked Questions

### What is the difference between a work order and a service request?

A service request is what someone asks for: "the sink is leaking." A work order is the internal job created to fix it, with an owner, a priority and a completion record. Many systems combine them, with the request form creating the work order. Keeping the requester's part short and the internal part separate gives you both.

### Do I need a CMMS for a small facilities team?

Not always. A CMMS is valuable when you manage many assets with scheduled preventive maintenance, inventory or compliance records. If your main pain is requests getting lost and nobody knowing status, a simple tracker built around the template above often covers it. You can move to a CMMS later, and a clean export of your work order history will make that move easier.

### How many fields should a work order form have?

Keep the requester's form to about five fields plus an optional photo. Put the longer set of fields on the dispatcher and technician screens, where the people filling them in have a reason to. Every field you can't tie to a decision or a report is a candidate to delete.

### Can AI assign priority to work orders automatically?

It can suggest a priority, and that helps with sorting a large backlog. A person should confirm anything involving safety, security, water, gas, electrical hazards or extreme temperatures. Treat the AI's priority as a draft, and ask it to flag anything uncertain for review instead of making a call.

### How do I get technicians to actually update work orders?

Make updating faster than not updating. Show only their own jobs, make Start and Complete single taps, let them add a photo instead of typing, and stop assigning work through text messages. Then use the data in ways that help them, such as justifying parts, proving workload or getting repeat problems fixed properly.
