FLEET-OPS-001 · Dashboard mockup

Sun For Rent
Fleet

Built from Zac's Fleet Tracker as it stands today. Real serials, models, customers, cities and dates. Nothing here writes back to anything, and no phone number, email or site address made it into the file.

The fleet today

The home screen, and the road to it

Ops is the one to look at. It is variant C's map with variant A's counts in a band above it, which is the edit Zac asked for after the 2026-08-24 call. Everything below it is kept for reference: the four screens that got us here, unchanged.

Current · Zac’s pick

Ops

The map from C with the counts from A in a full-width band above it rather than sitting on it, so the numbers are bigger and the map is uncovered. Click a number and the map, the model tiles and the list all narrow together. Zoom and pan, a pickups-and-deliveries layer, and the yard broken out by model for the what-can-go-out-today question.

Open Ops →
Variant A

Tile-first

Big counts across the top, click one to drill into it. The most familiar shape and the least opinionated about how the morning goes.

Open A →
Variant B

Worklist-first

One prioritised list of what needs a decision today, each row saying why it is there. Counts demoted to a thin strip.

Open B →
Variant C

Map-first

The map is the home screen and the counts sit on top of it. Click a location to pull its units up underneath.

Open C →
Superseded

Map with the counts on it

The first pass at merging A and C, with the numbers sitting on top of the map. Zac's answer was to lift them off it, which is what Ops does. Kept so the two can be compared side by side.

Open A+C →
Shared view

Fleet map

Every unit by location, filterable by status and by kind, with a table of locations and the units no map can show.

Open the map →
Shared view

Single unit

Everything the sheet knows about one trailer, its service position, and a history built only from dates that actually exist.

Open a unit →
For the conversation

What we need from you

Seven things the mockup could not answer on its own, each of which changes what the real dashboard should do.

Read the questions →

Two things the data said

Not sparse. Empty. Every forward-looking feature anyone might want from a fleet dashboard, including "what is coming back in the next two weeks", has nothing to compute from until this column gets filled in. That is why it is the biggest number on every screen here.

This is a gap in the record, not proof the work never happened. It is what Chris leaving looks like when you go looking for the schedule he kept in his head.

What is real and what is not

Real: serial, model, city and state, customer company, on and off rent dates, job numbers, service dates, priority group, generator serials.

Discarded before the data was written: contact names, phone numbers, emails, delivery street addresses.

Assumed here, but since corroborated: the 90-day routine service interval is what Linxup already has configured on three trailers. Every overdue count on every screen rests on that number.

Map pins are city centres, not sites. City is all the tracker knows.


What we need from you

Answers here change the build, not just the wording.

Linxup already says 90 days. Is that the fleet number? Linxup has "General Service, every 90 days" set on three trailers, all three now overdue. So 90 days is not a guess any more, it is a number somebody chose and nobody is running on. Confirm it and every overdue count on these screens becomes real.
Is "projected off rent" a habit worth enforcing? If yes, the dashboard nags for it daily. If not, say so now and the forward-looking half of this comes out.
Does "available" mean ready to go? Right now it is one word covering a unit in the yard, a unit awaiting service, and a unit nobody has looked at.
Should the three stolen units stay in the fleet count? They are counted today, which makes the fleet look three units bigger than it is.
Fourteen units have gone quiet on the GPS. What does that mean? Linxup lists them as "Online" while its own export shows they have not checked in for over a day, one of them since 25 June. Is that a dead tracker, a flat battery, or a unit nobody has looked at? Each answer sends a different person to a different place.
Linxup already has the service form. Use it, or build our own? It records service type, date, who completed it, hours, cost, notes and photo attachments, it is already paid for, and it is on the phone Sal will have in his hand. Nobody has ever put a record in it. Configuring that is far cheaper than building it.
Which of these three screens is your morning? Pick one to build properly, or take pieces from each. Both answers are useful.