Industry solution

Waste Management & Recycling

From the 5 a.m. rollout to the city's diversion report, on one connected workspace

Routes, trucks and balers, bale quality, hazardous waste manifests, diversion reports and customer service for haulers and recyclers.

Products
8
Challenges
6
Concepts
14
Talk to us about Waste & RecyclingAsk a question
Cardboard bales stacked beside a recycling sort line as a collection truck backs onto the tip floor
MoveTheWheels(opens MoveTheWheels in a new tab)AssetHandler(opens AssetHandler in a new tab)CrewFoundry(opens CrewFoundry in a new tab)BigConsole(opens BigConsole in a new tab)FluidGrids(opens FluidGrids in a new tab)EcoImpactHub(opens EcoImpactHub in a new tab)GovCitizenHub(opens GovCitizenHub in a new tab)Botlit(opens Botlit in a new tab)

The problem

Why waste operations are hard to run from one picture

Many waste operations still coordinate by radio, paper route sheets and spreadsheets, and onboard truck records rarely reach customer service, the shop or the recovery facility. Missed pickups become repeat calls and diversion reports are rebuilt by hand.

A hauler's day starts before dawn and runs on thin margins. Every route depends on a truck passing its pre-trip inspection and a qualified driver, and often a helper, showing up. One hydraulic leak or two call-outs reshuffle the board, and the late starts surface hours later as missed carts and angry calls. Many operations still coordinate this by radio, paper route sheets and a dispatcher's memory.

Downstream, a recovery facility lives with whatever the trucks bring in. Plastic bags and film wrap around the screens and stop the line, contamination lowers bale quality, and buyers downgrade or reject loads when commodity prices are already moving against the seller. Industrial waste teams carry a different burden: manifests that travel from the generator to the receiving facility and must come back signed, with any difference in quantity explained.

Meanwhile cities, commercial customers and producer responsibility programs ask for tonnage, diversion rates and end-market evidence on a schedule. The information exists in scale-house tickets, route records, bale audits and invoices, but it sits in separate systems, so reports are rebuilt by hand and residents' questions are answered by whoever can find the right screen.

Who this is for

  • Director of Collection Operations

    Routes finished on time with the trucks and crews available, fewer go-backs, and overtime that does not creep up every holiday week.

  • Fleet Maintenance Manager

    Pre-trip defects and service on packer trucks turned into planned work, not roadside breakdowns and a short spare line at rollout.

  • Recovery Facility (MRF) Manager

    Cleaner inbound loads, fewer screen wraps and baler stops, and bales that pass the buyer's inspection instead of coming back as claims.

  • Environmental Compliance Manager

    Every hazardous waste manifest closed with the signed copy back, quantity differences explained and evidence ready when a customer asks.

  • Municipal Contract and Sustainability Lead

    Monthly tonnage and diversion figures for each contract and commercial customer that trace back to scale tickets and hold up to review.

  • Customer Service Manager

    Fewer repeat calls about missed carts and holiday schedules, and residents and businesses told what happened without waiting for a callback.

A day in the life

The story behind the solution

The Tuesday after a holiday at Kestrel Ridge Waste & Recycling

Renata runs operations for a hauler that serves three municipal contracts and several thousand commercial accounts from two yards, a transfer station and a single-stream recovery facility. Monday was a holiday, so every residential route slides a day: Tuesday runs Monday's streets, the rest of the week follows a day behind, and Saturday becomes a collection day. The day below is fictional, but anyone who has run collection through a holiday week will recognize every moment of it.

  1. 4:40 a.m. · The yard

    Two trucks down, two drivers out

    Before the first truck leaves, the pre-trip inspection on side-loader 214 turns up a hydraulic leak at the arm, and a rear-loader is still waiting on a packer cylinder from last week. Two drivers have called out. The only spare is a rear-loader, which means route R-12 now needs a helper on the back and a driver cleared to run that truck. The night supervisor is working it out on a whiteboard while the rest of the fleet idles at the gate.

    How this is solved: Trucks down and drivers out before the 5 a.m. rollout

  2. 9:50 a.m. · Customer service

    Maple Hollow says recycling was missed

    R-12 left fifty minutes late on the spare and ran its streets out of order. By mid-morning the city's missed-collection line has logged a dozen reports from the Maple Hollow subdivision, and more arrive by phone. Some carts were never lifted; others were not at the curb when the truck passed. Nobody can tell which is which without radioing the driver, and the city's contract expects every genuine miss collected by the next day.

    How this is solved: Missed pickups that turn into repeat calls and go-backs

  3. 11:30 a.m. · Recovery facility

    Film on the screens, a claim on the bales

    The recovery facility has stopped the line twice this shift so a crew can cut plastic film off the fiber screen, and the two-ram baler missed a tie on a cardboard bale. Loads from two residential routes came in full of bagged recyclables. Then an email lands from a paper mill: last week's load of cardboard bales has been downgraded for moisture and plastic, and the buyer wants a credit.

    How this is solved: Contaminated loads, wrapped screens and downgraded bales

  4. 1:15 p.m. · Industrial services

    A signed copy that never came back

    The industrial unit hauled six drums of spent plating solution for a metal finisher five weeks ago. The treatment facility accepted them, but the signed manifest copy never came back, and the customer's environmental manager is now asking for it. Another manifest for a lab pack shows thirteen containers received against fourteen shipped. Both live in a filing cabinet and a shared inbox.

    How this is solved: Hazardous waste manifests that never come back signed

  5. 3:30 p.m. · Contract reporting

    A diversion report due Friday

    The Eastmere Township contract requires a monthly report of tons collected by stream, what was diverted and where it went. A regional grocer with fourteen stores also wants its own diversion figures for its sustainability report. Renata's analyst is copying scale tickets into a spreadsheet and estimating how much of the recycling ended up as facility residue.

    How this is solved: Diversion and circularity reports rebuilt by hand every month

  6. 5:10 p.m. · The phones

    Holiday-week questions that never stop

    Customer service has taken calls all day: is my pickup today or tomorrow, which cart does a pizza box go in, can I book a couch pickup, why was my recycling tagged. A restaurant wants an extra lift before the weekend and a contractor needs a roll-off swapped. Each answer lives on a different screen, and many callers ring back because nobody could say what happened on their street that morning.

    How this is solved: Holiday slides, sorting questions and commercial service changes

None of this needs a new department. It needs the truck, the crew, the stop record, the bale, the manifest and the report to live in products that are designed to pass work to each other. That is the solution concept on this page: Burdenoff products each doing their own job, sharing one sign-in, one set of roles and one record of who did what.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Trucks down and drivers out before the 5 a.m. rollout

AssetHandler(opens AssetHandler in a new tab)CrewFoundry(opens CrewFoundry in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

Every morning the rollout depends on two things the night supervisor cannot see in one place: which trucks passed pre-trip inspection and which people can legally run them. Collection trucks are not interchangeable. An automated side-loader route runs with one driver, but moved onto a rear-loader spare it needs a helper on the back and a driver trained on that body. Service intervals by engine hours come due unnoticed, licenses and medical cards lapse, call-outs arrive before dawn, and in a holiday week the slid routes land on the next day's board. The supervisor rebuilds it on a whiteboard from memory, and a late gate becomes the afternoon's missed pickups.

What it costs

Late rollouts cascade into missed pickups, overtime and go-backs, while trucks run past their service intervals because nobody could see them coming due.

How the products work together

AssetHandler is designed to show which trucks failed their morning check or are due for service, so the dispatch board only offers trucks fit to run. CrewFoundry shows which drivers and helpers are cleared for each kind of truck. When a one-person route moves onto a spare that needs a helper, the supervisor sees the gap and fills it before the gate opens.

How it works — technical detail

Technical detail

AssetHandler is designed to hold each collection truck's body type, pre-trip defects, preventive service due by engine hours and open work orders. Its fleet uptime board is designed to share with MoveTheWheels dispatch which units are off road and which spares are ready, so a route is not assigned to a truck with an open defect. CrewFoundry keeps each driver's and helper's license class, medical card, body-type training and call-outs, and is designed to show MoveTheWheels only the people cleared to run each truck. When an automated side-loader route moves onto a rear-loader spare, or Monday's slid routes are added to Tuesday's board, MoveTheWheels is designed to flag the missing helper from the CrewFoundry roster before the gate opens, and the defect becomes an AssetHandler work order with the truck's service history attached.

The outcome it is designed for

Rollout starts from a board that already knows which trucks and people can run, so the spare, the helper and the work order are sorted before the gate opens.

The concepts behind it

Challenge 2 of 6

Missed pickups that turn into repeat calls and go-backs

GovCitizenHub(opens GovCitizenHub in a new tab)FluidGrids(opens FluidGrids in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

After a late or out-of-order route, missed-pickup reports pile up through the city's line, the phones and email. Some carts were skipped; others were not at the curb when the truck passed, or were blocked by a parked car. Customer service cannot tell which is which without radioing the driver, so every report becomes a go-back, trucks double back across town, and residents whose carts were never out get the same answer as those who were genuinely missed. The city contract sets a deadline for collecting genuine misses, and the city keeps count.

What it costs

Unneeded go-backs burn truck hours and overtime, genuine misses wait too long, and the contract record fills with complaints the hauler cannot answer with evidence.

How the products work together

Residents report a missed cart once on the city's portal, with a photo if they have one. The driver's app is designed to note whether each cart was lifted, skipped, blocked or not out. Real misses are grouped into one return trip, the rest get the driver's photo as the answer, and residents see the outcome on their request without calling again.

How it works — technical detail

Technical detail

Where the city runs GovCitizenHub as its resident portal, the report arrives there as a tracked grievance with the address, stream and a photo, and the resident gets a reference number. FluidGrids is designed to pass each report from the city's portal to the hauler's MoveTheWheels board and match it to the route and stop, where the driver's app is designed to record a lift, a skip, a blocked cart or a cart not out, with a timestamped photo. The route supervisor works a missed-pickup board: genuine misses are grouped into a go-back for the nearest truck with capacity, and reports where the cart was not out are answered with the photo. FluidGrids then carries each outcome back to the resident's GovCitizenHub request, so the city's timeline shows collected, scheduled or not out, without a callback.

The outcome it is designed for

Go-backs run only for carts that were truly missed, residents see what happened on their street, and the contract record carries the evidence.

The concepts behind it

Challenge 3 of 6

Contaminated loads, wrapped screens and downgraded bales

BigConsole(opens BigConsole in a new tab)FluidGrids(opens FluidGrids in a new tab)AssetHandler(opens AssetHandler in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)

The problem

A recovery facility lives with whatever the trucks bring. Bagged recyclables and plastic film arrive with residential loads, wrap around the disc screens and stop the line while a crew cuts them free, and a baler pushed hard misses ties. Weeks later a buyer downgrades a load for moisture, plastic or out-of-spec material and asks for a credit. The plant manager suspects which routes are the problem, but tip-floor audits sit on clipboards, scale-house tickets in another system and line stops in a maintenance log, so nobody can connect a bad load in one week to a claim the next.

What it costs

Every contaminated ton is handled twice and landfilled at a cost, line stops cut throughput, and downgraded bales give back revenue that commodity prices already squeeze.

How the products work together

Weigh tickets, load inspections and bale weights are designed to come together on one BigConsole screen that shows which routes bring in the most contamination and which bales buyers pushed back on. AssetHandler records every baler and screen stop and its cause. When a route's loads keep failing inspection, its drivers are prompted to tag the carts on those streets on the next collection day.

How it works — technical detail

Technical detail

FluidGrids is designed to collect scale-house tickets, tip-floor contamination audits and outbound bale weights and push them into BigConsole data sinks, the connection the two products are built around. BigConsole brings them together in a recovery facility console: contamination by route and hauler on the way in, residue rate, bale grades by commodity and buyer claims on the way out, each figure traced to its tickets. AssetHandler keeps the balers, screens and optical sorters as assets and logs each stop with its cause and work order, and FluidGrids is designed to carry AssetHandler's stop minutes into the same data sink, so a spike in film wrap sits beside the routes that brought the film. When a route's load audits run above its contamination limit, FluidGrids is designed to add a cart-tagging task to that route in MoveTheWheels for its next collection day, so the driver's app prompts a tag at the carts on those streets.

The outcome it is designed for

The plant manager can show which routes drive contamination and line stops, target cart tagging there, and answer a buyer's claim with the bale's own records.

The concepts behind it

BigConsole

Recovery Facility (MRF) Contamination and Bale Quality Console

Inbound contamination by route beside residue, bale grades and buyer claims, so a downgraded load can be traced back to the trucks that fed it.

Works with FluidGrids, MoveTheWheels, AssetHandler

Concept pagefor Recovery Facility (MRF) Contamination and Bale Quality Console on the BigConsole website (opens in a new tab)

AssetHandler

Recovery Facility Baler and Screen Downtime Board

Every baler, screen and sorter stop with its cause, work order and minutes lost, and preventive service by run hours, with its parts, planned around shift changes.

Works with FluidGrids, BigConsole

Concept pagefor Recovery Facility Baler and Screen Downtime Board on the AssetHandler website (opens in a new tab)

Challenge 4 of 6

Hazardous waste manifests that never come back signed

MoveTheWheels(opens MoveTheWheels in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

Final copies of hazardous waste manifests come back late or not at all, container counts differ between what was shipped and what the receiving facility recorded, and the chase depends on someone remembering to check a filing cabinet, a driver's clipboard or a shared inbox. Some final copies arrive on paper and others are filed electronically, so the evidence lands in two places. When a copy is late or a count does not match, the generator has deadlines for following up, and the hauler is the first one they call.

What it costs

A missing signed copy or an unexplained quantity difference becomes the customer's compliance problem, and the hauler's standing with that customer rides on finding it fast.

How the products work together

Every manifest is designed to be tracked from the customer's dock to the receiving facility, with drums counted at both ends. Each morning, late final copies are chased and flagged to the compliance manager before the customer's deadline. When the copy arrives, it is filed with the load and the customer is told.

How it works — technical detail

Technical detail

MoveTheWheels is designed to carry each manifest as a shipment: generator pickup, transporter and truck, receiving facility, waste descriptions and container counts, with the driver's copy and the facility's weight ticket stored on the record. A manifest return tracker lists every open manifest by days since shipment, quantity shipped against quantity received, and whether the final copy, paper or electronic, is back. FluidGrids is designed to run a scheduled workflow each morning that checks open manifests, emails the receiving facility when a copy is late, alerts the compliance manager before the customer's follow-up window closes, and logs each chase on the manifest's timeline. When the final copy arrives it is attached to the shipment and the customer is notified.

The outcome it is designed for

Missing copies and quantity differences are chased from the day they are late, and the customer gets the signed copy or a clear status instead of silence.

The concepts behind it

Challenge 5 of 6

Diversion and circularity reports rebuilt by hand every month

EcoImpactHub(opens EcoImpactHub in a new tab)FluidGrids(opens FluidGrids in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)BigConsole(opens BigConsole in a new tab)AssetHandler(opens AssetHandler in a new tab)

The problem

Each municipal contract asks for a monthly report of tons collected by stream, tons diverted and where each material went, and commercial customers want their own diversion figures, often with the emissions from their waste, for their sustainability reports. The analyst copies scale tickets into a spreadsheet, subtracts an estimate of the recovery facility's residue, and emails a file nobody can trace back. When a city sustainability office asks why the diversion rate moved, the answer takes a week.

What it costs

Figures that cannot be traced to tickets weaken the hauler's position at contract renewal and with commercial customers who must defend their own disclosures.

How the products work together

Each month, FluidGrids passes weigh tickets, route tonnage and the recovery facility's records to EcoImpactHub, for each contract and each business customer. EcoImpactHub is designed to work out the diversion rate, subtract what the facility had to throw away, and prepare the monthly report and each customer's statement. Every number can be traced back to its tickets.

How it works — technical detail

Technical detail

Each month FluidGrids is designed to pass the scale-house tickets, route and account tonnage from MoveTheWheels, and the recovery facility's load audits and outbound bale records into EcoImpactHub's diversion ledger, using the same records it sends to the BigConsole data sinks. The ledger is designed to show tons by stream for each contract and customer, recycling net of residue, organics, metals and landfill, each line tied to its tickets and marked recorded or verified. The same activity feeds EcoImpactHub's carbon ledger, where the emissions from a customer's waste and the fleet's fuel are calculated with the factor shown on every line, and its reporting assembles each contract's monthly report and each customer's statement. AssetHandler reads the resulting EcoImpactHub metrics, so fuel, emissions and waste diverted also appear beside each truck and site.

The outcome it is designed for

The monthly report and each customer's statement come from the same traced figures, so a question about the diversion rate is answered from the ledger.

The concepts behind it

Challenge 6 of 6

Holiday slides, sorting questions and commercial service changes

Botlit(opens Botlit in a new tab)FluidGrids(opens FluidGrids in a new tab)MoveTheWheels(opens MoveTheWheels in a new tab)GovCitizenHub(opens GovCitizenHub in a new tab)BigConsole(opens BigConsole in a new tab)

The problem

In holiday weeks and at every change of season, the same questions come in again and again: whether collection slides a day, what goes in which cart, when yard waste starts again. Commercial customers call to add a lift, change a container size or swap a roll-off at a job site, and each request is written down by an agent and re-keyed for dispatch, sometimes a day later. The answers live on different screens and most calls are handled in one language, so hold times climb just when residents and businesses most need an answer.

What it costs

Hold times rise in exactly the weeks customers most need an answer, and service changes that carry revenue wait behind simple questions.

How the products work together

Botlit is designed to answer questions about pickup days, holiday changes and sorting in the caller's language, at any hour. When a business asks for an extra pickup, a bigger container or a roll-off swap, FluidGrids passes the request to MoveTheWheels as an order for the right route. Residents booking a bulky pickup get a link to the city's form to pay the fee. Anything else reaches a person.

How it works — technical detail

Technical detail

Botlit is designed to answer residents and businesses on web chat and messaging, in their own language, from the hauler's collection calendar, holiday slide notices and sorting guide, citing the page it used. When a business asks for an extra lift, a container size change or a roll-off swap, the Botlit agent is designed to trigger a FluidGrids workflow that opens a MoveTheWheels order with the account, container and requested day, ready to be placed on the right route. When a resident on a city contract wants a bulky-item pickup, the same kind of workflow is designed to open a prefilled request in the city's GovCitizenHub portal and send the resident the link to pay the fee in that form. Whether a street was done is answered from the route completion figures BigConsole holds. Anything Botlit cannot answer is designed to reach a person with the conversation attached.

The outcome it is designed for

Routine questions are answered at any hour in the caller's language, service changes reach dispatch complete, and agents spend their time on calls that need a person.

The concepts behind it

How it fits together

How one holiday Tuesday moves through the products, from pre-trip to diversion report

One collection day, followed from the yard at dawn to the month-end report. Each step shows one product doing one job and what it is designed to hand to the next.

  1. To MoveTheWheels: Which trucks can run today and which spares are ready

  2. To MoveTheWheels: Who is cleared to drive or ride each truck today

  3. To FluidGrids: What happened at every stop, with photos and weights

  4. To FluidGrids: Each resident report with its address and reference number

  5. To BigConsole: Tons, load inspections, bale weights and finished streets

  6. To Botlit: Which streets are done, for Botlit to look up

  7. To FluidGrids: Bulky pickup and extra-lift requests started in the chat

Step 1 of 8: Clear the trucks

How each hand-off works — technical detail

Technical detail

  1. 1. AssetHandler — Clear the trucks: Turns pre-trip defects and service due by engine hours into work orders, and marks which packer trucks are off road and which spares are ready.Hands to MoveTheWheels: Trucks fit to run, spares available and open defects, shared with the dispatch board.
  2. 2. CrewFoundry — Clear the crews: Checks each driver's and helper's license class, medical card and truck-type training against today's call-outs, and flags routes without a cleared crew.Hands to MoveTheWheels: Drivers and helpers cleared per truck type, designed to be the only people offered for dispatch.
  3. 3. MoveTheWheels — Run the routes: Is designed to dispatch routes and record every lift, skip, blocked cart, contamination tag and weigh ticket, with the driver's photo.Hands to FluidGrids: Stop records, photos and weigh tickets, designed to be collected by FluidGrids.
  4. 4. GovCitizenHub — Take the resident's report: As the city's resident portal, logs a missed-pickup or bulky-item request with address, stream and photo, issues a reference number and shows its timeline.Hands to FluidGrids: Each new report with its address, stream and reference, designed to start a FluidGrids workflow that reaches the hauler.
  5. 5. FluidGrids — Match and pass along: Matches reports to stop records, sends genuine misses to the go-back board, posts outcomes to the city's request and pushes tickets and line stops into BigConsole data sinks.Hands to BigConsole: Keyed data sink rows for tons, load audits, bale weights, line stops and finished streets; the month's totals also go to EcoImpactHub.
  6. 6. BigConsole — Show the facility and the streets: Renders contamination by route, residue rate, bale grades and buyer claims, and street-by-street route completion, each figure traced to its tickets.Hands to Botlit: Route completion figures a Botlit agent can query when a resident asks about a street.
  7. 7. Botlit — Answer the caller: Answers schedule, holiday slide, sorting and street-status questions in the caller's language, citing its source, and hands anything else to a person with the conversation.Hands to FluidGrids: Bulky-item and service requests started in chat, as workflow runs.
  8. 8. EcoImpactHub — Report diversion: Takes the month's tickets, tonnage and facility residue from FluidGrids, builds the diversion ledger by contract and customer, adds emissions lines and assembles the reports.Hands to AssetHandler: Emissions and diversion metrics that AssetHandler reads beside each truck and site.

Products in this solution

What each product brings

  • MoveTheWheels

    Routes, stop records, go-backs and manifests

    It is designed to run the collection day: which truck does which street, what the driver saw at each stop, return trips for real misses, business service changes, and hazardous waste paperwork from pickup to signed copy.

    Technical detail

    Technical detail

    Its routes, dispatch board and shipment records, with its planned driver app, are designed to carry a collection day: every lift and exception with a photo, go-backs grouped by truck, commercial service orders and manifests from pickup to final copy.

    Visit MoveTheWheelsAll concepts

  • AssetHandler

    Packer truck, baler and screen maintenance

    It is designed to keep trucks, balers and screens running: problems found at the morning check, service coming due, repairs in progress and why the sort line stopped.

    Technical detail

    Technical detail

    Designed to hold pre-trip defects, preventive service by engine hours or run hours, work orders and stop logs for trucks, balers, screens and sorters, with EcoImpactHub metrics shown beside each asset.

    Visit AssetHandlerAll concepts

  • CrewFoundry

    Driver and helper readiness

    It shows which drivers and helpers are cleared for which trucks today, and is designed to keep anyone not cleared off the dispatch board.

    Technical detail

    Technical detail

    License class, medical cards, truck-type training and call-outs for drivers, helpers and sorters, designed so dispatch only offers people cleared for the truck.

    Visit CrewFoundryAll concepts

  • BigConsole

    Recovery facility and route consoles

    It is designed to give the plant manager one screen for contamination, bale quality and buyer claims, and to give Botlit the list of streets already done.

    Technical detail

    Technical detail

    Consoles over data sinks fed by FluidGrids: contamination by route, residue, bale grades, buyer claims and line stops, plus route completion figures Botlit agents can query.

    Visit BigConsoleAll concepts

  • FluidGrids

    Hand-offs and daily checks

    It is designed to pass news between products: a resident's report to the right route, a late manifest to the compliance manager, the day's weights to the facility screen and the month's totals to the diversion report.

    Technical detail

    Technical detail

    Workflows designed to pass city reports to the hauler's stop records, run the morning manifest check, push tickets, load audits, bale weights and line stops into BigConsole data sinks, carry monthly tonnage to EcoImpactHub and turn chat requests into orders.

    Visit FluidGridsAll concepts

  • EcoImpactHub

    Diversion, circularity and emissions reporting

    It is designed to turn weigh tickets into the monthly diversion report for each city contract and each business customer, with emissions included and every figure traceable.

    Technical detail

    Technical detail

    A diversion ledger designed for each contract and customer, alongside its carbon ledger with the factor on every line, with reports assembled from figures traced to their tickets.

    Visit EcoImpactHubAll concepts

  • GovCitizenHub

    City resident portal for reports and bulky items

    It is the city's resident portal: residents report a missed cart or book a bulky pickup once, pay any fee in the same form and follow what happens, with reports designed to reach the hauler.

    Technical detail

    Technical detail

    Tracked grievances with location and photo, stepped requests with the fee paid inside the form, and timelines residents can follow, for city sanitation departments, with reports designed to reach the contracted hauler.

    Visit GovCitizenHubAll concepts

  • Botlit

    Resident and business answer desk

    It is designed to answer the questions that fill holiday weeks, in the caller's language and at any hour, pass service requests along, and hand anything it cannot answer to a person.

    Technical detail

    Technical detail

    Agents designed to answer from the hauler's calendar, holiday schedule and sorting guide on web chat and messaging, query BigConsole dashboards, start FluidGrids workflows for service requests and hand off to staff.

    Visit BotlitAll concepts

One platform underneath: Burdenoff Workspaces

Burdenoff Workspaces is the shared foundation: one sign-in for dispatchers, mechanics, plant staff and customer service, role-based access so each team sees only what it should, one record of who did what across every product, and one bill.

Concept gallery

Every concept in this solution

14 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Waste & Recycling solution in one minute

Burdenoff brings a waste operation's moving parts into products designed to work together. AssetHandler and CrewFoundry clear trucks and crews before rollout, MoveTheWheels runs routes, go-backs and manifests, FluidGrids passes the work between them, BigConsole shows contamination and bale quality, EcoImpactHub builds diversion reports from traced tickets, and Botlit and the city's GovCitizenHub portal answer residents. One sign-in, one set of roles, one bill.

  • Trucks with open defects and crews not cleared are designed to be kept off the rollout board before the gate opens.
  • Missed-pickup reports are designed to be checked against the driver's stop record and photo before a go-back is sent.
  • Contamination by route is designed to sit beside bale grades and buyer claims at the recovery facility.
  • Hazardous waste manifests are designed to be chased every morning until the final copy is back.
  • Monthly diversion reports and customer statements are designed to trace back to scale tickets.
Email it

Questions

Frequently asked

Is this for private haulers or for city sanitation departments?

Both. A private hauler can use the route, fleet and crew tools on their own. A city sanitation department can run the resident request tools as its own portal, and a hauler on a city contract works with that portal. The answer desk, facility screens and diversion reporting fit either.

Technical detail

Technical detail

Both. The products are designed around the work rather than who owns the trucks. A private hauler uses MoveTheWheels, AssetHandler and CrewFoundry to run routes, fleet and crews. A city sanitation department can run GovCitizenHub as its resident portal for reports and bulky-item requests, and a hauler serving a city contract works with the city's GovCitizenHub portal, with FluidGrids designed to pass reports and outcomes between the two. Botlit, BigConsole and EcoImpactHub serve either.

Do we have to replace our scale house, routing or billing systems?

No. FluidGrids is designed to collect information from the systems you already use, such as weigh tickets and billing records, and pass it along. You can start with one problem, like missed pickups, and add more later.

Technical detail

Technical detail

No. FluidGrids is designed to collect records from the systems you already run, such as scale-house tickets, onboard truck computers or billing exports, on a schedule or as they arrive, and pass them to the products that need them. You can start with one challenge, such as missed pickups or manifest tracking, and add others later.

Does manifest tracking make us compliant with hazardous waste rules?

No. It is designed to keep every manifest, final copy and quantity difference visible and chased on time, with a record of each follow-up. Meeting the rules is still your responsibility; the product gives you reminders and evidence, not legal advice.

Technical detail

Technical detail

No. The manifest return tracker is designed to keep every manifest, its final copies and any quantity differences visible and chased on time, with a record of each follow-up. Meeting the rules remains the responsibility of the generator, transporter and receiving facility; the products provide reminders and evidence, not legal advice.

Can our commercial customers see their own diversion figures?

Yes, by design. Each business customer is designed to receive a statement built from its own weigh tickets, and can be given a view of only its own sites. Every figure shows where it came from, so their sustainability team can check it.

Technical detail

Technical detail

Yes, by design. EcoImpactHub builds a statement for each commercial customer from the tons and tickets on its account, and a BigConsole console can be shared view-only with row-level access limited to that customer's own sites. Every figure carries its tickets and the emission factor used, so the customer's sustainability team can check it.

Can it follow our own collection calendar, holiday slides and sorting rules?

Yes, by design. You are meant to set up your own service areas, pickup days, holiday changes, sorting guide, fees and team roles inside the products. Nothing is built specially, and each product keeps its own name.

Technical detail

Technical detail

Yes, by design. Service areas, route days, holiday slides, the sorting guide Botlit answers from, bulky-item fees and team roles are meant to be configured inside the products rather than built specially for you, and each product is offered under its own name.

Are these products available today?

No, not yet. The products have not launched, and several parts shown here, such as the missed-pickup board, the driver's photo app and the diversion ledger, are plans rather than finished features. A demo shows what exists today.

Technical detail

Technical detail

Not yet. The products are pre-launch, with early-access waitlists open. Several surfaces shown here, such as the missed-pickup board, the manifest tracker, the recovery facility console, the sort-line downtime board and the diversion ledger, are illustrated ideas rather than finished features, and others, such as the driver's stop-exception app with photo capture and EcoImpactHub's waste tracking, are on each product's roadmap. This page describes a solution concept: how the products are designed to work together. A demo walks through what exists today.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.