Scheduling Commercial Accounts: Multi-Site Work Orders in 2026

TL;DR

The first commercial account feels like a win, and it is. The second and third are where the trouble starts. A property manager with eleven buildings, a restaurant group with nine sites, a facilities contractor with a portfolio — none of these behave like a bigger version of a residential customer. They are one payer with many addresses, a different person at every door, and a promise about how fast you turn up.

As of August 2026 the practical structure is the same regardless of trade: the billing entity is the customer, each site is a service location beneath it, standing work is generated automatically rather than raised by hand, and reactive calls carry a visible response clock. This guide covers how to build that, what breaks without it, and how to report on a portfolio when the contract comes up for renewal.

The four things residential scheduling does not model

Residential field service is a clean shape. One customer, one address, one contact, one job. Almost every scheduling habit a small service business develops assumes that shape, which is why the first real commercial portfolio is so disorienting.

Four differences do the damage.

One payer, many addresses. If your system treats every building as a separate customer, you have just lost the ability to see the account. You cannot answer "what have you done for us this quarter", you cannot invoice centrally, and your renewal conversation is guesswork. If instead you treat the portfolio as one customer with one address, dispatch has nowhere to send anyone.

The caller is not the decision-maker. The person who reports a problem is usually a site manager, a shift supervisor, or a tenant. The person who authorises spend is elsewhere. The person who pays may be a third company entirely. Getting notifications, approvals and invoices to the right one of those three is most of commercial admin.

Authorisation limits. Commercial agreements commonly say that work under a threshold proceeds immediately and work above it needs a purchase order or written approval first. A technician who does not know the limit either stops unnecessarily or completes work that will not be paid for.

Response-time expectations. Residential customers hope you come soon. Commercial contracts often state it. That turns "we will get to it today" into a measurable commitment you either evidence or argue about.

Structure first: billing entity, then sites

Everything else in this guide depends on getting one data decision right.

Keep the billing entity as the customer record — the management company, the restaurant group, the school district. Then make each physical address its own service location beneath it. Each site carries its own:

• Street address and any gate, dock or parking specifics
• On-site contact name and mobile number
• Access details: key or code location, hours the site can be entered, whether an escort is required
• Equipment and asset history for that building
• Site-specific instructions such as which entrance, which floor, which unit numbers

This is not a nice-to-have. It is the difference between a technician arriving informed and a technician calling the office from a car park. It is also the only structure that lets you answer portfolio-level questions later, because every job is attached both to a site and to the account above it.

The migration pain is real if you have been creating a new customer per building. Do it anyway, and do it before the account grows. The migration guide covers the general mechanics of restructuring customer data without losing history.

Standing work orders: schedule the interval, not the visit

Most commercial value is in recurring authorised work — the quarterly inspection, the monthly filter change, the weekly clean, the seasonal system check. It is predictable revenue, and it is exactly the work that gets missed when it is tracked by memory.

Two rules make it reliable.

Generate it, do not raise it. Each site's interval should be defined once and the visits should appear on the calendar indefinitely. The general pattern is covered in the recurring appointment scheduling guide; the commercial wrinkle is that intervals frequently differ per site within the same account. Building A is monthly because of its air handling load; Building C is quarterly. The account does not have one interval, so do not force one.

Batch by geography, then by account. A portfolio visit should be planned as a route, not as eleven independent appointments that happen to share a customer. If four of the eleven sites are within two miles of each other, they belong in the same morning. The general mechanics are in the route optimisation guide, and the saving on a multi-site account is larger than on residential work because the stops are naturally clustered.

There is one more discipline worth adopting early: record the visit even when nothing was wrong. Commercial customers are buying assurance as much as repair. A quarterly inspection with a logged result and a photo is evidence at renewal; the same visit with no record is indistinguishable from a visit that never happened.

Reactive calls and the response clock

Alongside the standing work sits reactive work, and this is where the contract gets tested.

Decide, in writing and inside the system, what the clock measures. In most agreements a four-hour response means a technician on site within four hours, not the job finished. Say so, because the ambiguity always resolves against you at the review meeting.

Then make the operational side match:

1. Flag it on arrival. A reactive call under a response commitment cannot enter the same queue as everything else. It needs a visible priority the moment it is logged.
2. Dispatch against real availability. Promising a window you have no capacity for is the same failure as overbooking a residential day. The dispatch board should be showing who is genuinely free and where they are, which is what the dispatch software guide covers, and why live technician positions matter more on commercial work than most owners expect.
3. Capture a real arrival timestamp. Not a typed-in-later estimate. The job status lifecycle — dispatched, en route, arrived — produces the evidence automatically if technicians actually tap it.
4. Keep some capacity unbooked. A schedule that is 100% committed cannot absorb a contractual reactive call without breaking a residential promise. The tension between planned and reactive work is the subject of the emergency versus scheduled dispatch guide, and commercial contracts make it sharper because one side of it is enforceable.

Notifications: two audiences, two messages

This is the most common source of friction on commercial accounts, and it is easy to fix.

There are two distinct recipients and they want different things at different times. The on-site contact needs the arrival notification, because they physically open the door, unlock the plant room, or move a vehicle. The account or property manager needs the completion record, because they are accountable for the work but have no interest in a text every time a van pulls up at one of forty buildings.

Route them separately. En-route and ETA messages go to the site. Completion summaries, photos and invoices go to the account. Get this wrong in either direction and you generate the two classic complaints: a technician standing outside a locked building, or a manager who first learns about a visit when the invoice lands.

Where the money leaks

Reporting: the conversation you will have at renewal

At some point an account manager will ask what you have done for them, and the quality of your answer determines the renewal.

The report they want is not complicated. Per site: visits completed, standing work compliance against the agreed intervals, reactive calls received, response performance against the commitment, and recurring issues that suggest a capital problem rather than a maintenance one. That last item is the one that earns trust, because pointing out that one building has generated six reactive calls on the same system is you doing their job for them.

None of this is possible if jobs are not attached to sites. It is close to automatic if they are. Broader context on business and facilities data is available through the U.S. Census Bureau, but the numbers that carry weight in a renewal meeting are the ones from your own system about their own buildings.

Should commercial and residential share a calendar?

Usually yes. The instinct to run commercial work in a separate system is understandable and almost always a mistake, because the technicians, the vans and the hours are shared. Two systems means two views of the same finite capacity, and the reconciliation happens in someone's head.

What you actually need is one calendar that can express both shapes: multi-site customers, per-site recurring intervals, priority flags with response tracking, and split notification routing. If your current tool cannot model a customer with more than one address, that is the constraint to solve — not the calendar itself. The selection checklist and the wider field service management software comparison are the right starting points.

What this costs

GetTimePad is $79/mo Starter for one staff member, $199/mo Pro for up to five staff, and $499/mo Agency for unlimited staff. The customer CRM with service history and property details, recurring appointments, the online booking portal, two-way SMS and automatic invoicing are on every plan. Pro adds live GPS tracking, review management, advanced automations and the AI receptionist. Agency adds multi-location support, API access, custom webhooks and priority support, which is where larger portfolio operators usually land.

Extra staff seats are $25/mo on Starter and Pro, the SMS Bundle is $19/mo, and annual billing gives you two months free. There is a 14-day free trial and a live demo with no signup required. Full details are on pricing.

Most companies taking on their first serious commercial portfolio need Pro, because dispatch visibility and automations are what stop the account consuming a full-time coordinator. Multi-location operators running several branches against shared accounts are the Agency case.

Where to start

Take your largest commercial customer and restructure just that one. Create the billing entity, create a service location for every address under it, and move the access notes and contacts out of job descriptions and onto the sites where they belong. Then define the standing intervals per site and let them generate forward for twelve months.

That single account will show you everything the rest need: which access details were never written down, which sites have no named contact, and which recurring work has quietly been missed. Fix those, then repeat. Do not attempt the whole book at once — restructure one account, run it for a month, and let the second one benefit from what you learned.

Frequently asked questions

What makes scheduling a commercial account different from residential work?

A residential job is one customer, one address and one person who answers the door. A commercial account is typically one billing entity with many service addresses, a different on-site contact at each one, a response-time expectation written into an agreement, and an authorisation limit above which work has to be approved before it starts. The calendar has to hold all four of those or the account becomes unprofitable through admin rather than through the work itself.

How do you structure one customer with many service addresses?

Keep the billing entity as the customer record and make each site its own service location beneath it, carrying its own address, access notes, on-site contact and equipment history. This structure is what allows you to invoice the head office while dispatching to the site, and it is what lets you answer the question a property manager will eventually ask, which is what you did across their whole portfolio last quarter.

What is a standing work order and how should it be scheduled?

A standing work order is recurring authorised work at a site, such as monthly filter changes or quarterly inspections, that does not need a fresh approval each time. It should be scheduled as a recurring appointment generated by the system rather than raised manually each cycle, with the site sequence planned geographically so a portfolio visit is one efficient route instead of a month of scattered single stops.

How do you handle response-time commitments on commercial contracts?

Decide what the clock actually starts on and make it visible on the job, because a four-hour response usually means arrival on site rather than completion. In practice that means the reactive call has to be flagged the moment it lands, dispatched against real technician availability rather than a promise, and recorded with a genuine arrival timestamp so you can evidence performance at the contract review instead of arguing from memory.

Who should reminders and notifications go to on a commercial job?

The on-site contact needs the arrival notification because they open the door, and the account or property manager needs the completion record because they are accountable for the work. Sending both to the same person is the most common error, and it produces the two classic complaints, which are a technician standing at a locked door and a manager who first hears about a visit when the invoice arrives.

Can scheduling software handle commercial and residential work on one calendar?

Yes, and running two systems is usually worse than running one imperfectly. What you need is a customer record that supports multiple service locations, recurring appointment generation for standing work, per-site access notes and equipment history, and separate notification routing for the site contact and the account contact. GetTimePad covers multi-location accounts on Pro at $199/mo and adds multi-location and API access on Agency at $499/mo; see pricing.