Equipment sitting idle costs more than equipment that breaks.
BayGauge is a utilization and maintenance platform built for multi-location auto repair operations.
It turns every lift, rack, and machine on the floor into a measured asset, so a shop group can see exactly
where capacity is tight, where it's wasted, and where a piece of equipment should move, get repaired, or
get retired, all backed by real usage data instead of a hunch.
Multi-location, multi-tenantIsolated per company at the database layer
4 role tiersAdmin · Manager · Technician · Viewer
StatusActively in development, early access
True Utilization
Active work time ÷ available business hours
Occupied-but-paused, downtime, and idle time are excluded, so this is work actually done.
Fed by 4 connected signals today (session logs, work-order correlation, technician pause
reasons, maintenance events), and architected to accept telemetry, power draw, and vision sensors later
without a schema change.
22
Equipment categories seeded on signup, from alignment racks to ADAS calibration rigs
Utilization buckets every machine is reduced to: Active, Passive, Downtime, Idle
12
Metrics selectable in the self-serve Report Builder, any grouping, any date range
01
The Universal Utilization Engine
An alignment rack, a tire changer, a wheel balancer, a vehicle lift, and an ADAS calibration rig don't
naturally report the same kind of data. Rather than build a different integration for each, BayGauge reduces
every piece of equipment to the same four buckets of business-hours time, using one new fact a technician
already knows: why a running session isn't active work.
Active
A session is running and hasn't been paused, so the machine is genuinely being worked.
Passive
Occupied but paused, like "waiting on parts" or "technician stepped away," logged in one tap.
Downtime
Flagged for maintenance. Excluded from utilization entirely, so a broken machine never masquerades as an idle one.
Idle
Available time left on the table, measured against real business hours rather than a flat 24/7 assumption.
Why it matters: a naive formula (occupied ÷ available) rewards a machine that's tied up doing
nothing. True Utilization only counts time someone was actually working, which makes it the number that
justifies a purchase, a transfer, or a retirement, not just a busy-looking dashboard tile.
Detection sources
Shown directly on every machine's page, this is an honest account of what's measuring utilization today, and what the engine is already built to accept.
Equipment activity log
Work-order correlation
Technician pause logging
Maintenance & downtime events
Power consumption
Network / IoT telemetry
Motion / vibration sensors
Computer vision
02
Day-to-day operations
What owners see and what technicians touch on the shop floor are two different surfaces, tuned for two
different jobs.
Dashboard
A fully customizable home screen — drag any tile or section to reorder it, hide what you don't need,
minimize a section down to its title, all saved per person — covering fleet utilization, trend lines
weighted by available minutes, maintenance status, cost of ownership, technician usage, and a live top/bottom-5
equipment ranking, filterable by location, equipment, or technician across 7/30/90-day windows.
Equipment detail
The richest page in the app: start/stop history, the full utilization breakdown, an Asset Decision card
with reasoning, a 13-tile performance summary, cost-of-ownership math, service history, preferred vendors,
location-transfer log, and a reservation calendar, all on one machine's page.
Kiosk / Start-Stop
A tap-to-use shop-floor grid, grouped by category, scoped to one location. Start Use, tag a repair order,
pause with a reason, or flag maintenance, all from a shared tablet, with no login friction beyond the
technician's own account.
Locations & hours
Per-location cards with utilization, an embedded team roster, and a weekly business-hours editor.
Hours directly gate the utilization math, so a location closed Sundays never gets penalized for
"idle" time it was never open for.
Equipment status
What it means
available
Ready to use, counted toward capacity.
in_use
A session is currently running.
maintenance
Flagged and out of service, excluded from utilization as downtime.
off
Reversible power-down. Ends any live session, excluded from tracking, can be turned back on anytime.
retired
Permanent. History is preserved (unlike delete, which is irreversible and removes it).
03
Maintenance & alerts
Any team member can flag a problem from the floor; only an admin or manager signs off on the fix. A daily
background job turns due-dates into real emails and texts, without ever sending the same alert twice.
Flagging, built for a shop floor
An 11-item reason list (leak, unusual noise, electrical, worn part, safety interlock, out of calibration,
won't power on, and more) generalized across tire changers, lifts, and diagnostic gear, plus an
optional photo or video, stored privately per company.
Completion & cost capture
Closing out a repair optionally records the real dollar cost, which feeds
cost-per-hour reporting and the Repair-vs-Replace call down the line.
Configurable reminders
Admins pick which lead times fire (any mix of 30/14/7/3/1/0 days out) and how often an overdue item
repeats (1-30 days), plus extra recipients beyond staff, scoped company-wide or to one location.
Real delivery, real dedupe
A daily job emails (Resend) and texts (Twilio) every admin/manager plus configured recipients,
with each alert keyed to its due-date cycle so an "upcoming" reminder fires exactly once, and an "overdue" one
repeats on schedule instead of spamming daily.
04
Capacity & asset intelligence
Two engines sit on top of the same utilization data, both requiring a minimum of five sessions in the last
30 days before they'll speak up, so a single slow week never gets mistaken for a trend.
Asset Decision Engine: one call per machine, every 90 days
Every active machine gets exactly one of seven standardized calls, evaluated in strict priority order so the
most severe applicable one always wins:
RETIREUtilization ≤15% and meaningful downtime, meaning the machine isn't earning its floor space.
REPLACEDowntime ≥8% while demand (utilization/peak) is still real, meaning the machine itself is the bottleneck.
REPAIROverdue or already in maintenance, or elevated downtime with a maintenance history.
EXPANDPeak-hour utilization ≥85% and overall ≥55%, suggesting the location may need another unit.
RELOCATESitting at ≤25% here while a same-category peer runs ≥75% at another location.
OPTIMIZEHigh occupancy but low job-efficiency, or stuck in a 20-45% gray zone.
MAINTAINNone of the above, meaning the machine is doing what it should.
Every call ships with plain-language reasons tied to the exact numbers behind it, a confidence level, and a
dollar impact estimate, though only when one is honestly computable from data on file. A decision
history is kept every time the call changes, and once a manager marks a decision "addressed," the engine
automatically compares utilization 30 days before vs. after and grades its own recommendation as Improved,
Worse, or No change.
Capacity Recommendations: fleet-wide patterns
Add capacity
Peak-hour crowding plus healthy overall demand at one location.
Reduce or reallocate
Sustained utilization under 20%, meaning more of this category isn't justified.
Scheduling optimization
Same category running hot at one location and cold at another, a technician-time fix rather than a purchase.
Utilization gap
Two sibling machines at the same location, one working hard, one barely touched.
05
Reporting
A fixed dashboard for the questions every owner asks weekly, and a fully self-serve builder underneath it
for the ones nobody thought to ask in advance.
Reports dashboard
Period-over-period comparisons (this week vs. last, this quarter vs. last), a most-used-equipment
ranking, a cross-location peer comparison for the same category, and a long-horizon utilization benchmark
that quietly builds itself as the page gets visited.
Report Builder
Pick a date range, group by location/region/category/equipment or by day/week/month/quarter/year,
choose from 12 metrics, sort, drill into the individual sessions behind any row, compare two rows
side-by-side, export to CSV, and save the view for next time.
06
Repair orders, vendors & activity
The connective tissue between equipment time and the actual job it went toward.
Repair orders
Tag a session with an RO number, either while starting a machine or after the fact, and every
minute of equipment time rolls up to that job automatically. Built as the hook a shop management
platform's own RO would plug into.
Vendor directory
Specialist vendors per equipment category, surfaced automatically the moment a machine in their
specialty gets flagged, with one tap to call or email, right where the problem was raised.
Activity log
A plain-English, company-wide feed of the last 150 events (sessions, maintenance, fleet changes,
and team changes) for anyone asking "what happened here?" A dedicated Security view filters straight
to sign-ins, password and email changes, and account access, the audit trail without the noise.
Reservations
Book a machine ahead of a job. Double-booking is prevented by a database-level exclusion constraint,
not just an app check, so it's physically impossible even under simultaneous requests.
07
Team, roles & access
Four roles, enforced twice: once for the interface, and again at the database layer, so a role
boundary holds even against a direct API call.
Admin
Every location, unrestricted
Manages other admins
Billing & notification settings
Full Asset Intelligence
Manager
Same tools as admin
Scoped to assigned location(s)
Can't touch admin accounts
Full Asset Intelligence
Technician
Start / stop / pause / flag
Own assigned location(s) only
No fleet/team management
Personal usage history
Viewer
Read-only, company-wide
Full dashboard & reports
Blocked from any action
Owner / investor seat
A team member can belong to more than one location, a genuine departure from a single
"primary location" model, and useful the moment a shop group shares technicians across sites.
Every account can turn on two-factor authentication from a personal security page, and a
locked-out user isn't stuck waiting on an admin, they can request their own password-reset email
right from the sign-in screen. Admins and managers can also fix a typo'd employee email in place,
with the old address automatically notified of the change.
08
Signup, billing & the platform underneath
A new shop is self-serve from the front door, with no manual account provisioning on our end.
Instant onboarding
One form creates the company, a first location with sensible default hours, 22 pre-seeded equipment
categories, notification defaults, and the admin's own login, all atomically, with a 30-day trial
applied automatically.
Billing, ready to switch on
Plan and trial state are tracked from day one (trial / active / past due / canceled). Payment
processing isn't live yet by design, and nothing is charged during early access.
What's underneath
The parts that don't show up in a screenshot but decide whether the numbers can be trusted.
Company data isolated at the database layer
Role limits enforced again in the database, not just the UI
Reservation conflicts prevented by a database constraint
Full audit trail on every asset decision
Optional two-factor authentication, any account
Every sign-in and sign-out logged
Alerted on any login-email change
Enterprise SSO (SAML)
09
Pricing
Priced per location, not per seat, at every tier: unlimited team members and every location in a shop
group are included, so a busy floor never costs more to track than a quiet one.
Starter
Everything a single shop needs to see what its equipment is actually doing.
$185 / location / monthor $1,850 / location / year
No credit card required to start. Every new shop gets a full 30-day trial with the entire product
unlocked, so there's a real answer to whether this actually helps before anyone's charged anything.
Worth a closer look?
BayGauge is in active development and early access right now, and the fastest way to see whether this
fits your locations is a short walkthrough of your own numbers.