
Guides
7 things to check in dumpster rental software
Dumpster rental software has to model the container, not the job: the five records worth capturing, four measures that matter, and what no system can fix.
What to take away
- A system for this trade has to model one thing properlythe container as an object with an identity, a location and a state. Software that treats a job as the primary record will lose track of your steel.
- The schema matters more than the features. If the data is right, reports follow; if it is wrong, no dashboard rescues it.
- Software automates whatever process you already have, including the parts that do not work. Fix the process on paper first.
- Four measurements tell you almost everything about a container rental operation, and all four come from records you should be keeping anyway.
What a system in this trade must model
Most field service software is built around a job: a customer, a date, a technician, an invoice. That model works for a trade where the asset goes home at night.
Yours does not. Your assets are distributed across dozens of addresses, unattended, for days at a time, and any of them can be swapped, damaged or forgotten. So the container has to be a first-class record with its own identity and history. A job is something that happens to a container, not the other way around.
Test any system on that point before looking at anything else. Ask it to show you every container, where each one is, what state it is in, and how long it has been there. A system that cannot answer that quickly is a system you will end up shadowing with a spreadsheet.
The minimum data schema
| Record | Fields that matter | Why |
|---|---|---|
| Container | Unit number, size, state, current location, job it is on, date out, expected back, purchase and repair history | This is the asset register and the availability picture in one place |
| Job | Customer, address, exact placement, material, access notes, authorized contact, agreed pull arrangement | Every field here prevents a specific failed trip |
| Move | Type, date, time, container number entered on site, driver, photographs | The move is the event that keeps the register honest |
| Disposal | Weigh ticket, weight, facility, cost, attached to the job rather than the day | Without this, no cost per job is real |
| Exception | Blocked placement, refused load, damage, failed trip, with a cause | This is the improvement backlog |
Five record types. Everything else is reporting. An operation that captures these five accurately can run on a spreadsheet longer than most owners expect, and an operation that does not will struggle on any platform.
Five records to capture
- Containerunit number, size, state, location
- Jobcustomer, address, placement, material, access
- Movetype, date, container number, driver, photos
- Disposalweigh ticket, weight, facility, cost
- Exceptionblocked, refused, damage, failed trip, cause
The field people underestimate is the container number entered at the move, on site, by the driver. Reconstructed afterward it is a guess, and guesses are how containers get lost inside your own records.
The four measurements
Turn time. Elapsed days from a container leaving the yard to the same container being available again. Measured per unit from real timestamps, not estimated. This is the number that decides how much revenue your existing steel can produce.
Four measurements that matter
- Turn timedays from yard to available
- Availabilityshare of owned containers dispatchable
- Moves per truck-daycompleted moves divided by working days
- Contribution per turnrevenue less disposal, drive time, handling
Availability. The share of owned containers that are actually dispatchable on a normal day, after damage, repairs and units sitting full. Owned and available are different numbers and only one of them serves customers.
Moves per truck-day. Completed moves divided by working days, with failed trips shown separately. This measures whether your geography and your schedule are working.
Contribution per turn. Revenue less disposal, drive time and handling. This is the number that tells you whether the work you are winning is work worth having.
Watch those four monthly and you will spot most problems before they reach a bank statement.
The denominator problem
Every measure above has a denominator, and denominators are where reporting quietly lies.
Denominator traps in reporting
Measure
- Turn time
- All containers averaged
- Availability
- Owned steel
- Moves per truck-day
- Days truck ran
Misleading denominator
- Turn time
- Per unit from real timestamps
- Availability
- Size customer asked for
- Moves per truck-day
- All working days
Correct denominator
- Turn time
- Availability
- Moves per truck-day
So define each measure once, in writing, including what is excluded. Then leave the definition alone, because a measure whose definition moves is a measure you cannot compare across months.
What software cannot fix
Three things, and buying a system to solve them wastes both the money and the year.
It cannot make a booking complete. If the intake does not capture the exact placement, the material and an authorized contact, the software will faithfully store an incomplete booking and the driver will still arrive to a locked gate. That discipline lives in the operations and workflow guide.
It cannot decide what your terms are. Rental period, weight allowance and overage rate are commercial decisions, and a system will simply apply whatever you set, which is why they belong in the reasoning in the pricing and profit guide first.
It cannot keep your steel in service. Availability comes from inspection and repair habits, described in the delivery and maintenance guide, and constrained by the equipment choices in the equipment and setup guide.
Choosing and moving
- Write your five record types and the four measures on one page before speaking to any vendor. That page is your specification.
- Ask each candidate to demonstrate the container view, live, with more than one container in more than one state.
- Load a sample of your own real jobs during a trial, including a swap and a refused load, and see whether the awkward cases survive.
- Test the export. Ask specifically how you get your container register, job history and weigh tickets out in a usable format.
- Check who can see and change what, since a driver, an office person and an owner need different access.
- Run the trial through a busy week rather than a quiet one, because a quiet week tests nothing.
- Keep the paper process running alongside until the reports from both agree.
Step four decides how trapped you are later. A system you cannot leave is a system whose price will rise.
Protecting the records
Once the register, the job history and the weigh tickets live on a computer, they are business-critical. Losing them means losing your asset history, your billing evidence and your tax file at once.
NIST publishes quick-start guides written for small businesses covering the basics in plain terms. The Cybersecurity and Infrastructure Security Agency keeps material aimed at small and medium businesses on the same ground.
For an operation this size, the practical minimum is a backup you have actually restored from, separate accounts for separate people, and multi-factor authentication on anything holding customer data.
Some of these records also have to exist for other reasons. The Internal Revenue Service sets out what a business is expected to keep in support of income, expenses and assets.
Vehicle and load records sit alongside them. The Federal Motor Carrier Safety Administration publishes cargo securement rules that include provisions for roll-on, roll-off and hook-lift containers. What your operation must be able to show is a question for that agency and your state. What else has to be documented is jurisdiction-specific and is covered in the licensing and compliance guide.
Where a system also holds your customer list and your enquiry history, it becomes a marketing asset too, and how that is used sits in the marketing and growth guide.
Common questions
Can a small operation run on a spreadsheet?
For a while, yes, provided the five record types are captured properly. The point where it stops working is usually the second truck, when two people need the same view at the same time.
Should I choose industry-specific software or something general?
Judge it on the container view rather than on the industry label. Some general tools handle assets well and some industry tools do not.
What is the most common implementation failure?
Migrating a broken process. If container numbers were not being confirmed at the move before, they will not be confirmed after, and the new system will simply record the same gaps faster.
How many measures should I track?
Four is enough to run on. Adding more usually means none of them get looked at, and the four above cover capacity, availability, productivity and profit.
Do I need GPS on the containers?
It answers where a unit is and not why the record was wrong. Fix the move confirmation habit first, then decide whether tracking is still worth the cost.







