Dispatch that refuses a clash
Drag a job onto a technician. An overlap is refused and the job it clashes with is named; a missing skill only warns, because the software does not know who got certified last week.
MyTradeOps
Field service, for commercial contractsFrom dispatch
From dispatch
to payment.
The whole job in one place — the call, the board, the technician in the plant room, the quote, the invoice, the money. Built for HVAC, plumbing, electrical and refrigeration companies whose customers are property groups, schools, restaurants and industry — not homeowners.
Real data, nothing to install. Sign in as the owner, the dispatcher or a technician and change anything you like.
WO-000142On site
Northgate Property Group
Building A · RTU-2 short cycling on high head pressure
- Their PO
- NPG-2026-0412
- Not to exceed
- $2,500.00
- Response
- On site in 2h 40m — met
- Standard labour
- $88.00 contract
AssignedEn routeOn siteIn progress
- 4 h
- response times measured, not just promised
- 1
- invoice a month, however many sites they have
- 13
- job statuses, every change stamped with who and when
- 2
- languages — the whole product, one switch
One job, from the phone ringing to the money in.
Nothing is retyped between steps, because there are no steps — there is one record that gathers what happened to it. The invoice is built from the hours that were clocked and the parts that were fitted, not from somebody’s memory of the afternoon.
- 01
The call
Customer, site and the unit on the roof. Their PO number while they are still on the phone.
WO-000142 - 02
Dispatch
Drag it onto a technician. An overlap is refused; a missing skill is only a warning.
Assigned - 03
The truck
Arriving stops the contract clock. Time, parts, photos and a signature — one thumb, gloves on.
On site - 04
The invoice
Built from the hours clocked and the parts fitted, at this customer's contract rate.
$1,284.60 - 05
The money
Their PO in the header, and a balance that is the sum of real payment rows.
Paid
Dispatch
A board a human can read.
Technicians as columns, the day as a grid. Drag a job onto somebody and the overlap is refused; a skill or a zone that does not match is only a warning, because software does not know that Ray got his certification last week. Down the left is everything with nobody on it — including the jobs somebody scheduled and never staffed.
- A contract clock on the card: how long is left, or how long ago it ran out.
- Blocked work comes back to the queue once its slot has passed, instead of hiding on the day it was booked.
- Time off is refused the same way a double booking is.
Reports
The number they ask for at renewal.
Compliance per customer, worst first, with the misses listed underneath. Work nobody promised anything about is left out of the figure entirely — padding the denominator is the oldest way to make a percentage look good, and a facility manager who catches you at it does not renew.
- Response measured by when somebody was on site, not when a job was assigned.
- Money, work, estimates and technicians for the month or the quarter.
- Every figure traces back to rows you can open.
Construction
Progress billing the bank already knows.
Schedule of values, monthly applications and retainage, in the shape of the G702 and G703. Print it for the general contractor or the lender. Every figure is frozen when the application is issued, so a printout of March still says what March said, whatever landed since.
- Material delivered and not yet installed is billable, and the form shows it.
- “Less previous certificates” is the last one certified, never the sum.
- Issuing raises an ordinary invoice — there is no second kind of receivable.
Quotes
What the customer opens.
Good, better, best on one page, priced at what their contract says. They pick one, sign it on their own phone, and the approved option becomes the work — and later the invoice — without anybody retyping a line.
- Preview it before it is sent: the same page, not a lookalike.
- Declining asks why, and the answer lands on the estimate.
- The link is rotated whenever a revised quote is sent.
Everything the day needs, and nothing it does not.
One screen in the order of the visit
On the way, arrived, clock, parts, photos, signature. Parts come off that technician's own van without anybody picking a warehouse on a rooftop.
Quotes they sign on their own phone
Good, better, best on a link with no login. Re-sending a revised price retires the old link, so nobody approves a number that no longer exists.
One invoice for forty jobs
Bill a whole period on one document, with their purchase order number on it — and refuse to send it without one when that customer will not pay otherwise.
Maintenance that schedules itself
A contract plans its visits for the whole term and the cron raises each job four weeks out, with the checklist copied in. Nothing renews on its own.
Response times measured, not promised
The clock starts when the job is raised and stops the first time somebody is actually on site. A job with no promise does not flatter the average.
Why this one
Your customer has an accounts payable department.
That single fact is what separates this from software written for somebody who fixes air conditioners in driveways. A company does not pay an invoice because it is correct — it pays it because its own paperwork matches.
Their PO number, end to end
Accounts payable will not pay an invoice without their own purchase order number on it. Mark the account as requiring one and the invoice cannot be sent without it — a refusal, not a warning, because finding out a month later is the expensive version.
The rate they negotiated
Straight time, after hours, a discount on materials. The most specific rule wins, and it is applied where the price is written onto the job — so a quote, the work and its invoice cannot quietly disagree.
One invoice for forty sites
Close a month and every finished job at that customer becomes one invoice, sites as sections, each line carrying the job it came from. A job is billed once, even when two people close the month at the same second.
The promise, on a clock
Four hours for a shutdown, next business day for the rest. Written onto the job when it is booked, measured by when somebody actually arrived, and reported per customer at renewal — with uncovered work left out of the number.
A portal for the facility manager
Their sites, their open jobs, their invoices with their own PO on each — and a way to ask for service that lands in the dispatcher's queue instead of a voicemail. No password to forget: a one-use link.
Progress billing the bank reads
Schedule of values, monthly applications, retainage — in the shape of the G702 and G703, because that is the form the general contractor and the lender already know. Material delivered and not yet installed is billable, and the printout says so.
The truck is the office
Written for a phone held in one hand, with gloves on.
- The day's jobs, and the day either side of it — because checking tomorrow before driving home is what everybody does.
- The unit's whole history before knocking: serial, warranty, and every visit it has ever had.
- One tap for en route, on site, in progress. The customer is told automatically when somebody sets off.
- Time, parts, photos, a checklist and the customer's signature, captured where the work happened.
- Nothing tappable under 44 pixels, and every write carries an id so a retry on a bad signal lands once.
The part you only notice when it is missing.
Field software is judged on the day a customer disputes a number. These four rules are why that day goes well.
Money is integers of cents
Never a float. One routine computes totals, shared by the quote and the invoice, so the two cannot end up a cent apart.
Documents freeze
An invoice copies the billing address instead of joining it. A customer who moves next year does not rewrite the invoices they already paid.
A balance is a sum
Amounts paid are never typed. They are the sum of payment rows, and a refund is a negative one, so the arithmetic can only tell the truth.
Nothing moves without a row
Every status change, every part off a van, every reassignment writes an event with a name on it. A figure nobody can explain is a figure nobody trusts.
You already do all of this. The question is what it costs you.
On a whiteboard
With MyTradeOps
- Where the job livesToday: A whiteboard, a group chat and somebody's memoryOne record with 13 states, every change stamped with who and when
- What the technician carriesToday: A printed sheet, or a call to the office to askThe unit's whole history on their phone, with the gate code
- Their PO numberToday: Chased after the invoice comes back unpaidCaptured on the call, copied to the invoice, refused if missing
- Forty jobs in a monthToday: Forty invoices, and a facility manager who pays none of themOne consolidated invoice for the period
- What a part costToday: Guessed from the last order, or looked up in a drawerOff the technician's van, priced from the customer's contract
- Who is lateToday: Whoever shouts loudestResponse time measured against the contract, per job
Running by the end of the week.
- 1
Set up the company
Branches, tax, the price book and the crew. Twenty minutes with somebody who knows the trade.
- 2
Bring in the customers
The accounts, their sites, and the equipment at each — serials and warranty dates, so the first visit already has history.
- 3
Take the first call
Book it, dispatch it, work it, bill it. The whole loop closes on day one; everything else is depth you grow into.
One price, per technician, everything in it.
Dispatchers, office staff and owners do not count — only the people you send out. No setup fee, no contract, and the implementation is done with you rather than sold to you.
Everything included
Let’s talk
Priced per technician per month. What it comes to depends on how many of you there are and whether you need last year’s data moved across.
- Work orders and the 13-state machine
- Dispatch board, week and month
- The field app, on any phone
- Quotes the customer signs on their own screen
- Invoices, payments and the money ledger
- Consolidated billing by period
- Contract rates and response-time promises
- The customer portal
- Inventory, vans and purchase orders
- Projects, progress billing and retainage
- Maintenance agreements and their visits
- Two languages, one switch
What people ask on the first call.
How long before we are actually running?
A week, and the first day is the long one: your branches, your price book, your crew. Everything after that is entered as the work comes in. Nothing has to be finished before the first job can be dispatched.
Do we have to move our data across?
Customers and their sites, yes — that is the list you cannot work without. History is optional and most shops leave it where it is: the old system stays readable, and this one starts clean on the day you switch.
Will the technicians use it?
It is one screen in the order of the visit — on the way, arrived, clock, parts, photos, signature — and every touch target is a thumb's width. If a technician has to be trained for an hour, the screen is wrong, not the technician.
What happens in a basement with no signal?
The address, the access notes and the equipment history are already on the phone. Every write carries an id so a retry lands once and not twice, and the screen says plainly when something did not go out rather than pretending it did.
Who owns the data?
You do. Every list exports to CSV from the screen you are looking at — filters and all — so the answer to "what if we leave" is a download, not a support ticket.
Does it do residential work?
It will, but it is not built for it. The defaults here assume a commercial customer: contract rates, purchase orders, response-time promises and a portal for a facility manager with several sites. If your work is mostly homeowners, another product will fit you better.
Open it and take a call.
The demo is a real contractor with real jobs, technicians, contracts and invoices. Break anything you like — one button puts it back.