Unit pins
The unit moved.
Now the pin does too.
Every unit's exact spot lives on the site map, not just the address. When a foreman drags two toilets to the outfield fence, the driver who finds them moves the pin from the field: to the phone's GPS, or by hand on the satellite map. The office sees it live, with who, when, and how far.
screenshots/unit-pins-driver-job-map.png
Why a pin, not an address
A site is an address. A unit is a spot on it.
A portable toilet sits on a customer site for months, and the site can be a forty-acre jobsite or a county fairground. The street address gets the truck to the gate. The pin gets the driver to the unit: the north corner of the lot, by the trailer, the infield gate. Every customer site in PortaPro has a map of pins, and every pin carries the units that sit there, tagged serials like #1019 or untracked counts like three standards and one ADA.
Pins used to be frozen once the office dropped them. Units are not. A foreman drags two toilets to the outfield fence, a crew walks a handwash station across the site, a customer shifts a unit to the other gate. In every other product that means the map is wrong until someone in the office redraws it. In PortaPro the driver who finds the unit in its new spot fixes the record on the spot, and the fix carries its own evidence.
The mechanism that matters: a pin is a cluster, not a single unit. A phone's GPS is accurate to a few metres in the open. That separates the infield from the outfield fence, about ninety metres, with room to spare. It cannot separate two units in a bank a metre apart, and PortaPro does not pretend it can. So the thing that moves is the pin with its unit list, and when only some of a cluster moved, the driver says which ones and they get a pin of their own. Honest precision is what makes this work for the operators who never serialized their fleet, which is most of the industry.
From the job sheet
Six things a driver can do to a pin.
Open the job, tap a pin. Everything below happens from one sheet, in the field, in a few taps, and each one is written to the pin's history and the job's notes. On the right: the Move sheet as the driver sees it, and the same sheet with Only some switched on.
The pin snaps to the phone's GPS. The sheet shows the live accuracy radius before the tap and records it with the move. A loose fix, worse than 25 metres, is refused rather than saved as fact.
Under a canopy or between buildings, the driver drags the pin on the satellite map instead. Recorded as adjusted by hand, with no accuracy radius claimed.
Two of five units moved? The driver ticks the two. They get their own pin at the new spot; the other three stay where they were. Both pins keep an accurate unit list.
On a delivery, the job's assigned serials and untracked counts go on the ground at a new pin. Standing on an existing pin adds to it instead of creating a duplicate beside it.
Scan the printed QR tag on a unit to place or move that exact unit. The tag is marked deployed. A tag from another company's unit resolves to nothing.
Behind a locked fence, or the customer wants it moved on a date? Leave an orange flag and a note. It clears itself the moment someone moves the pin.
screenshots/unit-pins-move-sheet.png
screenshots/unit-pins-split-sheet.png
What the office sees
Live on the map. Written in the history.
The map updates as it happens
The customer's GPS Pins map in the office redraws while the driver is still standing at the unit. No refresh, no end-of-day sync, no phone call to ask where it went.
Every move has a who, a how, and a how far
The pin's history reads in plain words: Moved 87 m to the driver's GPS (±5 m). One unit moved to new pin “Scale house”. Placed by the office in July. The pin shows who moved it and how many times, and the job carries one note per action.
The office can move pins too
Move on map in the pin editor drags a pin through the same audited action. And on a unit that carries a hardware tracker, the drift banner offers Move pin to tracker position, or a flag the next driver sees on their map.
screenshots/unit-pins-office-history.png
Old way vs PortaPro
The old way vs. PortaPro
What happens the week after a unit gets moved.
A unit gets moved on site
The driver radios it in and the office guesses at a new dot on the map, or nobody updates anything and the next driver hunts
PortaPro:The driver standing next to the unit taps its pin and moves it to their position, with the GPS accuracy recorded
Two of five units moved
The whole pin moves or none of it. Either way the map is wrong about three units
PortaPro:Only some splits the cluster: the two get their own pin at the new spot, the three stay put
Poor GPS under a canopy
A 40-metre fix gets saved as if it were exact
PortaPro:A loose fix is refused. The driver drags the pin on the satellite map instead
Units without serial numbers
Can't be located at all; bulk inventory has no home on the map
PortaPro:Untracked counts sit on pins, and they move and split exactly like tagged units
Who moved it, and when
Nobody knows. The dot is just somewhere else now
PortaPro:Every move records the person, the method, the distance, a note, and an optional photo, on the pin and on the job
No signal at the site
The update never happens
PortaPro:Saved on the phone, sent when signal returns
FAQ
Questions operators ask
Do drivers need special hardware?
Does moving a pin change the invoice?
Can any driver move any pin?
What happens when GPS is bad?
What if the unit went to a completely different site?
Does it work without signal?
What about units we don't tag or serialize?
Get Started
Watch a pin move from the field.
Book a walkthrough: a driver taps a pin, it snaps to their GPS, and the office map updates while you watch.
Get started in under 2 minutes.
