How Crew Meter works

1. Add your assets

Sign up, name your assets, choose how each one should be tracked. Skid steers and trucks usually have a meter — pick hours, miles, kilometers, count, or days. Trailers, compactors, pumps, attachments, and small tools usually don't — pick estimated use, use count, calendar-only, or inspection-driven tracking.

Multiple meters per asset is fine — a truck with both an odometer and an engine-hour meter tracks both.

2. Print and stick the QR codes

Crew Meter exports a printable PDF in five Avery layouts (full page, 4-up, 6-up, 10-up, 30-up). Print on weatherproof labels, stick them where they'll survive jobsite life — fender, dashboard, hood, control panel, trailer tongue, tool handle.

The QR token is stable across reprints. If a sticker gets destroyed, print a new one with the same token and scanning history continues unbroken.

3. Set up maintenance schedules

For each asset, define the services that need to happen on a schedule:

• Meter-based: "Engine oil every 250 hours"
• Calendar-based: "Annual inspection every 365 days"
• Use-count-based: "Belt check every 50 cycles"
• Combined: any combination — "Whichever first" or "All required"

Templates let you define a "Caterpillar 320 Excavator" once with all its standard services, and every excavator you add inherits the schedule. Same idea works for trailers, generators, or any reusable asset profile.

4. Operators scan and submit use

An operator opens Crew Meter, taps Scan, and points at the QR code.

If the asset has a meter, Crew Meter prompts for the current reading.

If it doesn't have a meter, the operator can log estimated hours, use count, inspection status, or a simple "used today," depending on how that asset is configured.

If they're offline (no cell, no Wi-Fi), the entry queues locally and syncs the next time they have signal. The submit always succeeds — no failed scans, no lost data.

If a QR sticker hasn't been registered yet (or was scanned by accident), the entry still gets recorded — it lands in the admin review queue with the raw QR token, so nothing is dropped silently.

Non-metered assets still get tracked

Crew Meter doesn't require an hour meter or odometer. For non-metered assets, you choose how usage should be tracked:

• Estimated hours — "ran the compactor about 4 hours today"
• Number of uses — every scan is one use, service after N uses
• First use of the day — daily inspection / pre-use log
• Inspection / checklist completion — pass/fail with optional photos
• Calendar interval only — "annual safety check" or "tire rotation every 6 months"

That means trailers, compactors, attachments, pumps, small tools, tanks, forms, and other jobsite assets can all have QR-based maintenance history.

5. Crew Meter watches the schedules

Behind the scenes, every entry updates the consumption math. When a maintenance task crosses 80% of its interval, the asset moves to "warning" state. At 100% it's "due", past 100% it's "overdue". Each crossing fires exactly one push notification — no spam.

Admins see a maintenance dashboard with every asset grouped by status. Anything that needs attention is at the top. Healthy assets stay out of the way.

6. Log services when they happen

When a service gets performed (oil change, filter swap, tire rotation, annual inspection, repair), an admin or mechanic creates a service record. Pick the asset, the date, who did it (in-house or vendor), the cost, and which scheduled tasks it satisfied. Add photos of the parts replaced.

The maintenance clocks reset based on which tasks the service satisfied. The cost rolls up into per-asset and (if you use CrewBonus) per-job cost reports.

7. Pre-use checklists (optional)

If you want operators to inspect equipment before use, define a checklist — "brakes functional", "no fluid leaks", "lights working", "tire pressure", "load secure". Each item can pass-fail with optional photo and notes. Failures can log only, notify admins, or block the machine until cleared.

Frequency is configurable: every scan, first scan of the day per asset, first scan of the day per operator, or every N scans.

CrewBonus integration

If you also use CrewBonus, link the accounts and the integration just works:

• Operators clocked into a job can scan equipment from inside CrewBonus — one shared session, no re-login
• Asset usage attributes to the active job automatically (or operator-picked when clocked out, or marked as shop / non-job work when off the clock)
• Cost reports show asset hours rolled up against job labor cost in CrewBonus
• One signup covers both apps

---

Setup examples

Five concrete examples of how different assets get configured:

Skid steer

Track engine hours. Oil every 250 hours. Grease every 40 hours. Daily pre-use checklist (fluids, tracks, attachment lock).

Trailer

No meter. Track calendar inspections (every 90 days), tire pressure check (weekly), light check (pre-use), and use count (track every load hauled).

Plate compactor

No hour meter. Operator logs estimated use ("ran it about 3 hours today"). Service every 50 estimated hours. Plus a calendar-based filter change every 6 months as backstop.

Truck

Track odometer miles AND engine hours. Tire service by miles, oil by engine hours, annual inspection by calendar. Daily pre-trip checklist.

Pump

Track estimated runtime or use count. Service after configured runtime hours or 6 months — whichever comes first.

Small tool (chainsaw, drill, generator)

Track issue/return inspections, repairs, and replacement history with a QR sticker. Calendar-based annual safety check. Optional use count if it's heavily used.