RouteForgeSign in

The service event is sacred. Run your routes like it.

RouteForge is the route-native operations platform built for refuse haulers — recurring stops, exception capture in the field, and audit-grade service events shared by dispatcher, driver, and office.

The refuse-route problem

Generic CRMs weren't built for the way refuse runs. Routes change mid-day. Drivers find blocked carts, contaminated loads, missed bins. Exceptions live in text messages and end-of-day paper. Billing leaks. Disputes don't resolve.

Route execution chaos

Stops get added and skipped without a clean record. Dispatch and the driver disagree on what happened.

Exceptions lost in transit

Contamination photos sit in a driver's phone. Overflow charges never make it to the invoice.

Billing leakage

Extra pulls, contamination fees, and roll-off swaps don't reconcile back to accounts cleanly.

No audit trail

When a customer disputes a charge, "the driver said so" isn't a record. You need a timestamped, signed, photo-backed service event.

What RouteForge does

Six things every refuse operator gets out of the box.

Route-native dispatcher

Drag-and-drop sequencing, live route progress, exception flags, account lookup. One board, one shared truth.

Exception capture in the field

Contamination, overflow, blocked access, missed bins — captured in three taps with photo, geo-stamp, and reason code.

Refuse-native domain

Roll-off swaps, front-load lifts, residential carts, disposal tickets. Container types and lift types are first-class — not custom fields.

Driver mobile PWA

Built for gloved hands and bad signal. Stop completion in three taps. Background-sync when the network comes back.

Audit-grade service events

Every stop produces a structured, timestamped, immutable record — the canonical source of truth for billing, disputes, and dispatch recovery.

Multi-tenant for operators

Manage your fleet today. Add a second operating company tomorrow. Org-scoped from the database up.

How it works

Step 1

We seed your operation

Accounts, service locations, containers, and routes — imported from your spreadsheet or built with you in a guided session.

Step 2

Drivers run their routes

Mobile-web PWA on whatever phone they have. No app store. Works on poor connectivity.

Step 3

Dispatch sees reality

Live progress, exceptions as they happen, route-finished summaries before the truck is back at the yard.

Step 4

Office reconciles cleanly

Service events flow to billing with exception codes attached. Disputes resolve from one timestamped record, not a text thread.

Request a demo

Tell us a little about your operation. We'll respond within one business day to schedule a walkthrough on a seeded demo org you can poke at yourself.

RouteForge — Route-native operations for refuse haulers