Work Order Management System: How Contractors Choose

The surest way to choose a work order management system is to test it on your own data before you sign. A system worth buying proves four things in a demo: each order has one owner, nothing moves on until its mandatory data is in, every stage has a time limit that late orders must explain, and any manual stage change is recorded with a reason and a date. This guide gives you the selection criteria, ready-made test scenarios, a comparison table and a pre-contract checklist.

What does a work order management system do for an electrical contractor?

A work order management system is where each utility work order is recorded, keyed in by hand or imported from Excel, and then moved through the execution stages: site survey (Kashfia), excavation permits, Projects or Connections, quality, achievement certificate and drawing, until its extract is approved and the order is archived. At any moment it answers three questions: where is the order, who owns it, and is it overdue for its stage?

It is not an accounting package or a full ERP: it tracks each order’s operational path, not ledgers or payroll (see ERP vs a specialised system for contractors). For the wider picture, read our buyer’s guide to electrical contractor software in Saudi Arabia.

Network scale explains why this discipline matters. According to the Saudi Electricity Company’s Q1 2025 results as reported by Argaam, the utility served about 11.37 million customers, added roughly 60,300 new customers in that quarter alone and operated a distribution network of about 816,000 circuit kilometres. These are the utility’s figures, not any contractor’s, but part of the connection and network work behind them reaches contractors as work orders.

On 26 February 2026 the company announced its new name, Saudi Energy (SE), with its core generation, transmission and distribution business unchanged. In this guide we simply call it “the utility”.

Why aren’t spreadsheets and generic task apps enough?

Many teams run on a shared spreadsheet and chat messages. That works at first, but a spreadsheet stores data without enforcing the workflow:

• Unclear ownership: anyone can overwrite the “owner” cell, and nothing shows who took an order or when.
• Silent duplicates: an order logged twice means double effort and misleading figures.
• Messy master data: a district spelled three ways or an undefined city breaks filters and reports.
• Unexplained delays: formulas count days but cannot block a hand-off or demand a reason.
• Lost history: who changed the stage, and why, is rarely documented.

Generic task apps handle assignment and due dates, but they don’t know your workflow out of the box: they can’t tell a site survey from a permit stage, don’t route orders to Projects or Connections by implementing agency, and don’t link an order to its materials, certificate and extract. If you can build that in, you are also the one who has to maintain it.

The gap is more visible in a digitally mature market. The UN E-Government Survey 2024 names Saudi Arabia among the six Asian countries leading the region in the highest (VH) e-government rating class, and cites a 99% internet penetration rate and 98% of government services available online. Against that backdrop, a spreadsheet passed around the office quickly becomes the weakest link. For a broader roadmap, see digital transformation for electrical contractors.

Which core functions should you test?

Start from the questions your operations manager asks every morning, not the vendor’s feature list. These eight functions are the minimum:

Registration and duplicate control

Core order data (subscriber, location, contract, implementing agency, estimated value), automatic numbering, and a hard block on registering the same order twice.

Bulk import with gap detection

An Excel batch reviewed before saving, with undefined cities, districts and work descriptions listed, instead of rejecting the whole file or accepting its errors.

Claiming and ownership

A clear claim action that makes one user responsible, and no access to another user’s order without explicit permission.

District-based dispatch

A distribution screen where a dispatcher assigns orders to users who cover the order’s district and hold the stage’s permission.

Conditional relay

Relay, meaning moving an order to its next stage, happens only after permission, mandatory fields, notes and attachments are checked, and the order is routed to the right stage.

Time limits and delay justifications

A limit in days per stage, overdue orders flagged, and the option to require a justification with files before they move on.

Reassignment and documented stage changes

Move an order to another user from one screen, and correct its stage by hand with a mandatory note and old and new values logged.

Tracking and alerts

A quick lookup of any order’s stage and owner, with alerts when an order enters a new stage and when it is assigned.

How do you test them in a demo?

A rehearsed demo shows a system at its best; these scenarios show how it behaves when things go wrong, which is what your teams will face every day. Run them yourself or have the vendor run them live:

1. Import a file with deliberate errors

   Take a real Excel export and add a row with an unknown district and a row that duplicates an existing order. Expect: a row preview before saving, a downloadable gaps report, and the duplicate skipped and counted.

2. Register the same order twice

   Enter an order by hand, then enter it again with the same order name and work description. Expect: a refusal, not a warning you can click past.

3. Relay without a mandatory file

   Make attachments mandatory for a stage, then try to relay an order without one. Expect: the relay is blocked and the missing item named.

4. Open a colleague’s order

   Sign in as a regular user and try to open an order someone else claimed. Expect: access refused unless you hold permission to view other users’ data.

5. Relay an overdue order

   Make delay justifications mandatory for a stage, pick an order past that stage’s limit and try to relay it. Expect: a justification with files is required first, and supervisors can then see it in the stage list and distribution screen.

6. Reassign one order, change another’s stage

   Reassign one order to another user, then move a second order back a stage by hand. Expect: the new assignee shows as the first order’s current user straight away, and the stage change needs a mandatory note and is logged with old value, new value and date.

7. Watch the alerts

   Relay one order, assign another from the distribution screen, then check the message log: what went out, to whom and when. Expect: a message when the order enters its new stage, an instant alert for the assignee, and each message marked as sent successfully or failed.

Spreadsheet, generic task tool or specialised system: which fits?

The table compares the three options on the points the scenarios test. The specialised column describes ELX; generic tools vary by product and setup.

How does ELX manage work orders from receipt to archive?

ELX is a bilingual (Arabic/English) system built for electricity-network contractors in Saudi Arabia. Matrix hosts and operates it as a cloud service, and your team uses it in the browser. It carries each utility work order from registration to archive, and archiving happens automatically once the order’s extract is approved. See ELX work order management software for the full module. The screen and button names below are ELX’s default labels, and they can be renamed in your company’s instance.

Registration and import

Orders are created with subscriber, map location, contract, implementing agency and estimated value, and numbered automatically, optionally with a per-contract sequence. ELX refuses a new order whose name and work description match an existing one. A “check issues” tool finds orders with a missing, unknown or inactive district and lets you correct them on the same screen.

The “Import” button loads an Excel file into a review grid with a progress bar. ELX lists the cities, districts and work descriptions not yet defined in your guides (master data), offers a downloadable gaps report, suggests each order’s administrative office from its district, can apply one branch or contract to every row, and on save skips and counts rows that duplicate existing orders.

Claiming, dispatch and relay

Users claim an order from their stage list with “Open”, which assigns it to them and records the received date; no one else can open it without “Show other users’ data”. In manual-relay stages, the order first lands on that stage’s distribution screen, where a dispatcher assigns it to a user from the list ELX shows for the order’s district and stage. When the assignment is made in stages such as survey, permits, projects and quality, the assignee gets a real-time in-app alert and a browser notification.

“Relay” saves the stage data and moves the order only after the relay permission and the mandatory fields, notes and attachments are checked, routing it to permits when needed and to Projects or Connections by implementing agency. Our guide to utility work order stages covers the full sequence.

Time limits, reassignment and stage changes

Each stage has a limit in days, counted from relay or from receipt depending on settings, and overdue orders are highlighted in a different colour. When justifications are mandatory, an overdue order cannot be relayed until one is entered with its files. See stage time limits and delay justifications.

The re-assignment screen shows supervisors the assigned orders in each stage basket with the assignment date and current user, so they can move an order to another active user or remove the assignment. A manual stage change, to any stage from work order to drawing, needs a mandatory note, lets the authorised user pick who handles the order in the new stage, and is logged with old value, new value and date. These rights are granted per screen and action from the permissions matrix; for more, read about user permissions and audit trails.

Tracking and alerts

The work order status search in the header shows any order’s stage, owner and status, with links to its full report, attachments, certificate and materials balance. The operations dashboard shows pending versus overdue orders for each stage, within the user’s own branches and districts.

When an order enters a new stage, ELX sends a Telegram message in the background, and a WhatsApp message when that channel is enabled, to users who can view that stage’s screen, have notifications on and have a registered number. Sending never holds up the relay, and the message log shows whether each message was sent successfully or failed. See instant notifications.

What should you confirm before you sign?

Review this list with your operations, warehouse and finance leads, and tick only what you verified yourself, not what you were promised:

• All seven scenarios were run on our data, with results recorded.
• Stage names match our actual workflow with the utility, or can be renamed.
• Each stage has a time limit, and we know whether it counts from relay or receipt.
• Permissions are granted per screen and action, with relay as a separate right.
• Each user’s data is scoped to their branches and districts.
• Manual stage changes need a note and appear in a reviewable log, and the re-assignment screen shows who currently holds each order.
• The Arabic/English interface and the alert channels (in-app, Telegram, WhatsApp) suit our teams.
• We have written answers on hosting, data location, backups, training, support and pricing, plus a plan to move open orders out of Excel.

With ELX, several of these answers are settled up front. There are no servers to set up on your side, because Matrix hosts and operates the system as a cloud (SaaS) service. Matrix also trains your users, migrates your existing Excel data (work orders, materials and master data), customises screens, reports and stages to your needs, and provides technical support over WhatsApp from a button in the ELX header. For pricing and the rest of the list, ask for written answers during the demo.

To run these scenarios on ELX with your own data, request a demo and bring a sample of the work order file you use today.