Organize everything by location
Each deployed site carries its address and map position, the client's own store
number, and its region. Issues, tasks, contacts and equipment all hang off it, so
"what's the story at store 42?" is one page, not four systems.
Issue tracking
Link an issue to the equipment it's about. Move that equipment to another site and
its open issues move with it — no orphaned tickets pointing at the wrong address.
Closing an issue records why: fixed, won't fix, can't reproduce, or external.
Tasks, contacts and equipment
The installer, the store manager, the field tech — on the record and attached to
the right site. Tasks track what still needs doing. Equipment tracks make, model
and serial for every unit you've put in the ground.
Fields that match your hardware
Start from a template built for what you deploy — Level 2 chargers, interactive
kiosks, smart coolers, ATMs — or build your own. Add the service dates, serials and
component types you track, and they sit on every record of that kind, in front of
whoever is scheduling the work.
Tag it once, find it everywhere
Put your own labels on equipment, sites and contacts: pilot install, needs rewire,
Northeast rollout. One page then lists everything carrying that tag, whatever it is
and wherever it sits, so a grouping only your team would think of still works across
every location.
Files where you'd look for them
Photos, PDFs, install guides — attached to any record. A deployment rolls up every
file from its contacts, tasks, issues and equipment, so the site's whole paper
trail is on one page without anyone re-uploading a thing.
Let the people on site report problems
Turn on public reporting for a deployment and store staff can file an issue from a
private link — no login, no account, no phone call. It lands in the same queue your
team already works.
Who changed what, and when
Every edit is recorded against the thing it touched: old value, new value, who did
it, what time. When a serial is wrong or a task quietly changed hands, you can see
how it got that way instead of asking around.
Access that matches the org chart
Viewers read, editors maintain the records, admins run users and billing. Invite
the team by email and let them sign in with Google or a password — support staff
get what they need without getting near your billing.