A monthly recurring charge looks simple until the physical service changes in the middle of a period. An event site adds two units for a weekend. A construction customer moves one unit to a second gate. A unit is exchanged after damage. The driver is asked for an extra pump-out that was not on the standing route. If the account has only a single total unit count, the office may know what to bill but not what the crew should service. If the route has only stops, the crew may know where to go but not which unit was moved or replaced.

This is a portable-unit change-control guide. The broader recurring waste accounts guide covers account setup, route cadence, billing and collections across service types. For a portable account already in service, the practical problem is keeping placed units, future visits and invoices aligned when the physical deployment changes.

Keep the account, site and unit separate

Start with a parent customer account for the commercial relationship, then record each service site and each physical unit placed there. That structure lets the office change one unit without rewriting the customer's entire agreement. Give the unit a stable identifier, status, placement point and service history. The job records what happened to it on a particular visit; the invoice records what the customer owes under the agreement.

CRO's current portable-restroom page describes static recurring routes alongside one-off work, individual unit placement, driver field evidence and recurring billing. Those are published product capabilities, not proof that every customer's commercial change rule is already configured. RapidWorks: portable restroom operations

Use one effective-dated change record

When the customer asks for a change, log one request with the account, site, affected unit IDs, requested date, requested work and the person authorized to agree to any charge. Then make the operational and billing decisions separately:

1. Is the change permanent or temporary? A unit moved for one event may need a temporary route adjustment; a unit moved to a new long-term site needs its future service location updated.
2. Which physical units are affected? Name the units added, removed, relocated or exchanged. A change to the count alone can leave the wrong unit on next week's route.
3. What work happens today? A pickup, delivery, relocation, extra pump-out or failed access belongs to today's dispatched jobs and field results.
4. What changes after today? Update the next service visits only after the physical placement is confirmed. Keep the original cadence visible for audit and customer questions.
5. What changes on the bill? Apply the agreement's effective date, included services and extra-charge rules. Do not assume calendar-day proration when the contract bills by service occurrence or a fixed period.

This is an operating protocol, not an automatic promise made by any software. A system should let the team record the facts and apply its own approved commercial rules.

Walk through a unit move

Suppose a contractor has four units at Site A, serviced twice weekly. On Wednesday, one unit moves to Site B for the remaining three weeks of the month; the customer also requests one additional service before the move. These dates and quantities are illustrative.

Dispatch first records the approved request and assigns the extra visit and move. The driver identifies the physical unit, records the completed service, captures any required photo or signature, and confirms the new placement. The office then updates that unit's future service site and route, leaving the other three Site A units untouched. Billing checks whether the extra visit or changed site affects the contract price. The invoice shows the original recurring service and any separately approved change, with a trace back to the field event.

If the driver cannot reach Site B, do not mark the unit moved. Record the failed attempt, notify the appropriate customer contact, assign the retry, and keep the unit's actual location and future service plan honest. This avoids billing for a placement the field team never completed.

Separate planned service from exceptions

A recurring route is the standing plan, not a claim that every stop happened as expected. Keep three views:

• Future plan: Which placed units are due next and where the crew should find them.
• Dispatched day: Which regular and extra visits were released to drivers, including changes made after the route was built.
• Actual result: Which unit was serviced, moved, exchanged or inaccessible, with the proof and next action.

The plan changes when the customer's enduring service promise changes. A one-off extra service should not quietly multiply into every future week. An inaccessible unit should remain an exception until dispatch resolves it. CRO's portable-restroom product page says its static routes can run alongside one-offs and its driver app captures photos, signatures, billable items and unit locations. Use those records to support the daily distinction between plan and result. RapidWorks: portable restroom operations

Reconcile the recurring invoice to deployed units

Before finalizing an invoice, compare the agreed base service to the actual deployment and visit history:

Do not make the software invent a contract. Some operators bill in advance, some in arrears, and some by completed service. The agreement determines whether a mid-period unit addition is prorated by calendar days, remaining service visits or another rule. The system's job is to retain the facts and support a reviewable calculation.

CRO publishes recurring billing, driver-added billable items and invoices built from completed work. Its portable-restroom page says unit tracking, route work and billing remain connected. Confirm the exact approval and accounting configuration for your business rather than assuming every extra field action should bill automatically. RapidWorks: portable restroom operations, RapidWorks: CRO product

A short weekly exception review

The office should not wait until month-end to discover that a moved unit still sits on the old route. Once a week, compare open change requests with unit placements, upcoming visits, failed stops and unreviewed billable work. Assign an owner and due date to each unresolved mismatch. Close the item only when the physical location, future service and billing decision agree.

Next step: Trace one actual unit move from customer request through driver confirmation, next week's route and the current invoice. If those records disagree, fix the handoff before adding another recurring account. See CRO's portable sanitation workflow.

About the author

Ellery Curran, Marketing Specialist, RapidWorks

Ellery Curran works in marketing at RapidWorks, a software company that serves waste, septic, and heavy equipment operations businesses. She focuses on content that helps operators evaluate and adopt field service technology.