Crew and truck board
Every crew and truck for the day on one screen, with its jobs and any open issue shown beside it.
A manager oversight app for local moving companies puts the day's crews, trucks, estimate visits and open job issues in one board, so the general manager can move a crew before a late move becomes a lost afternoon. We would build it as a bespoke product, with a browser dashboard for the office and a phone screen for dispatch.
A local moving company can lose an afternoon to a single late estimate. The sales visit ran long, so the next estimator arrived late. A crew finished a two-bedroom move later than planned, and the truck meant for the next job is still parked at the old address. None of those problems looks serious at 8 a.m., and by noon they have stacked up. A single late estimate can push back the entire next day's loads.
Most often the first warning is a crew lead's phone call to the general manager. An oversight app shows the chain of events in one place: which crew is behind, which truck is free and which estimate visit is still open. That lets the manager move people while there is still time to keep the afternoon on schedule.
The first release should show the day's moves and estimate visits on one board, grouped by crew and truck. Each job carries its crew size, its time window and any open issue, such as a pending parking permit or an access note the crew has not acknowledged.
Assignments work as a drag from the open queue onto a crew's day, with a warning when the crew size does not match the job or a truck is already booked elsewhere. Weekly reports show jobs completed, average crew hours per move, damage claims opened and the share of estimates that became booked moves.
At 6:50 a.m. the manager pulls up the board and spots a three-person crew assigned to a condo move that has not checked in. The building's loading dock is booked by another company until 9 a.m., and the truck's parking permit is still pending with the city.
He moves that crew to a two-person job starting at 8 a.m. and sends the condo move to an afternoon slot, which the customer accepts through the app. He then reassigns a truck that finished early and asks the office to chase the permit, with the request logged against the job.
By 8:30 every crew has a job, the permit shows a status update and the late-job list is empty. The end-of-day report records each change and its reason, so the Monday review starts with facts rather than memory. The owner reads the same summary on a laptop and never has to ask the dispatcher for one.
Every crew and truck for the day on one screen, with its jobs and any open issue shown beside it.
A job turns amber when the crew size and the move do not match.
Pending permits, access notes and damage claims stay on the job until someone closes them.
Jobs completed, crew hours per move, damage claims and the estimate-to-booking share, reviewed weekly.
We need the crew roster with crew size and roles, the truck list with capacity and service schedule, and the estimator calendar. We also need the job sheet your office uses today, since the board is built from those fields. A copy of last month's job sheets is usually enough to start.
If dispatch runs in a job management package, we check which export or API it offers before any design work starts. Each person sees only what the job needs: the general manager sees every crew, dispatchers see the board, and estimators see their own visits.
The most common mistake is putting every job sheet field on the board. The manager needs the status, the crew and the open issue at a glance. Keep the board to those fields and link the rest to the full job for anyone who needs the detail. A board that stays readable on a phone at the curb is part of the design, not an afterthought.
Another mistake is ignoring the estimate side of the business. Estimators who cannot see crew availability promise dates dispatch cannot cover, and the late move often starts there. Put estimate visits and move days on the same calendar from the first release.
A focused first build of this kind starts at $4,500. The main drivers are the number of crews and trucks on the board, the job system the app reads from and the reporting the team wants at launch. Those decisions matter more to the final number than the screen count.
We contain scope by launching with the board, assignments and three or four core reports. Additional reports and integrations are quoted separately, so the general manager can decide which upgrade is worth the money after a few months of real use. We also review the first month of reports together, so the team knows which numbers they actually act on.
No. The dispatcher still moves crews and speaks with customers. The app gives that person a live board, flags conflicts before they happen and records every change, so the general manager can review the day without asking for a summary.
Yes. Estimate visits appear on the same calendar as move days, so estimators and crews are never booked into the same window or onto the same truck by mistake. The timing rules for estimates are set during scoping.
Most general managers start with jobs completed, crew hours per move, damage claims and how many estimates turn into bookings. Other reports come later, once a question keeps coming up that the standard set cannot answer.
Our starting point is $4,500. Crew count, the systems the board reads from and the reports you need at launch set the final number, which we confirm in writing before development begins.
Describe how a typical move day runs from estimate to delivery, and we will sketch a board your dispatchers can use.