EcoImpactHub
Carbon Ledger Across Scope 1, 2 and 3
The ledger where every invoice, fuel and refrigerant line lands as a scoped entry with its emission factor, and moves from recorded to verified.
Industry solution
Sustainability numbers that trace back to the work behind them
Carbon, sourcing, freight and nature evidence captured where the work happens and carried into a disclosure your assurer can follow.

The problem
Sustainability teams are asked for assured, comparable figures, yet the data sits with facilities, logistics, procurement, ecologists and suppliers, and reaches the report through spreadsheets nobody can fully trace.
Sustainability reporting has moved from voluntary narrative toward something that looks a lot like financial reporting. Regimes such as ISSB-based standards and the EU's ESRS expect emissions figures that can be assured, credible transition plans and, increasingly, nature-related information, and customers add their own questionnaires on top. Expectations rose faster than the data plumbing: most sustainability teams are small, sit outside the operational systems, and still assemble their numbers from invoices, exports and emails once a quarter or once a year.
The hardest data belongs to other teams. Electricity, fuel and refrigerants sit with facilities and maintenance. Freight sits with logistics. Farm plots, supplier declarations and certified volumes sit with procurement and field officers. Camera traps and restoration plots sit with ecologists and contractors. Scope 3 is mostly other companies' data. Every hand-off adds a spreadsheet, a copy and a judgment call that nobody writes down.
Assurance then asks exactly the questions that process cannot answer: where did this figure come from, which factor was used, who approved it, and why does it differ from the board pack. The answer is not another reporting tool bolted onto the end of the chain. It is capturing evidence in the systems each team already works in, and keeping one definition of each metric all the way to the disclosure.
Head of Sustainability
A footprint, targets and a transition plan the board, investors and customers can challenge without the numbers moving each time.
ESG Reporting Manager
Line items that trace to source, one definition per metric, and an assurance sample answered with links rather than folders of attachments.
Carbon Accounting Analyst
Activity data that arrives on its own, sourced factors with vintages, and fugitive, transport and purchased-goods emissions built from records, not guesses.
Responsible Sourcing Manager
Plot-level due-diligence evidence and certified mass-balance positions ready before a buyer, certifier or regulator asks.
Site Ecologist or Nature Lead
Species trends read against survey effort, monitoring devices that keep working, and restoration evidence kept on the site record.
CFO or Financial Controller
Sustainability figures under the same discipline as financial ones, and capital decisions that show their effect on reduction targets.
A day in the life
Ana Moreira runs sustainability and ESG reporting for Greenhollow Sugar & Bioenergy, a fictional group that crushes cane at two mills, distills ethanol, exports power from a bagasse cogeneration plant and buys cane from its own estates and several hundred contracted growers. Her team is four people. In the last week of the quarter, every thread of the job pulled at once.
Monday, 7:40 a.m.
Ana opens the quarter-close workbook and finds Mill A's electricity invoices still missing; the site administrator is on leave and the PDFs are sitting in her inbox. Worse, a maintenance supervisor mentions in passing that the chiller on the refined-sugar packing line was topped up with refrigerant twice since July. Both top-ups were written on paper job cards. Neither reached Scope 1, and Ana has no idea how many other assets have the same story.
How this is solved: Scope 1 and 2 data stuck in invoices, meters and job cardsTuesday, 10:15 a.m.
A beverage customer asks for plot-level evidence, under its own no-deforestation policy, that no cane in last quarter's sugar came from land cleared after the policy's cut-off date. An hour later the ethanol buyer asks for sustainability declarations on two September shipments. Grower plots are mapped by field officers in three formats, the customer's policy wants a boundary for every plot while eleven growers are still recorded as a single GPS point, and the certified-volume balance lives in a spreadsheet one colleague updates on Fridays. The carbon intensity on each declaration is still a default value, because nobody has totaled the growers' fertilizer and diesel.
How this is solved: Chain-of-custody claims that buyers and certifiers can checkTuesday, 3:30 p.m.
The same beverage customer wants the footprint per tonne of sugar delivered, transport included. Ana's transport figure is a spend-based estimate from freight invoices, and a haulage rate rise pushed it up this year although volumes were flat. Down the corridor, the logistics planner knows every truck, tanker and rail wagon to the port, but the two teams have never used the same numbers.
How this is solved: Freight emissions estimated from spend instead of lanes and loadsWednesday, 6:50 a.m.
Samuel Owusu, the group ecologist, calls from the riverside corridor the group is restoring along the edge of Estate 3. The draft update for the community liaison committee shows river otter detections down by half since the rains. Walking the transect, he has found three camera traps with flat batteries and one with a full memory card. He cannot tell the committee whether the otters left or the cameras stopped watching.
How this is solved: Biodiversity trends that mistake a data gap for a declineThursday, 2:00 p.m.
At the capital committee, the engineering director asks to overhaul the fuel-oil auxiliary boiler at Mill B that carries the distillery through the off-season. Ana learns about it from the agenda. The CFO, Daniel Hartmann, asks what each option does to the 2030 target, and whether the solar power purchase agreement really covers the share of electricity everyone assumes it does.
How this is solved: A transition plan that lives in slides, not in capital decisionsFriday, 4:45 p.m.
The assurance provider sends its sample: twenty-five line items, each needing its source, calculation and approval. Ten minutes later the board chair emails to ask why Scope 2 rose when electricity use fell. Ana finds three slightly different Scope 2 figures across the report draft, the board pack and a customer questionnaire, each pulled from a different spreadsheet on a different day.
How this is solved: Disclosure and assurance season without the evidence scrambleBy Friday evening not everything was finished, but nothing was a scramble either: each figure Ana sent out pointed at a record that someone else in the business had already created for their own work. That is the idea behind putting these products side by side.
Challenges and how they are solved
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
Two weeks after quarter-end, the carbon analyst at a multi-site food manufacturer is rebuilding Scope 1 and 2 by hand: electricity invoices forwarded as PDFs by three site administrators, a fuel-card export for the delivery vans, and a standby-generator diesel log typed up from a clipboard. Nobody has sent refrigerant figures, because top-ups live on maintenance job cards; the chiller on packing line 2 had 21 kilograms added over two visits, and that fugitive release never reaches the footprint. When an invoice straddles two quarters, the analyst prorates it by hand and hopes the next person does it the same way.
Quarter-close takes weeks, fugitive emissions are routinely missed, and prorating choices go undocumented, so a figure cannot be rebuilt when an assurer or a new analyst asks how it was made.
FluidGrids is designed to collect electricity bills and fuel-card statements daily, split a bill spanning two quarters by day count and note the method, then file each line in EcoImpactHub with the original document attached. Refrigerant top-ups technicians log on AssetHandler work orders are designed to reach Scope 1, and repeat top-ups on one machine prompt a leak check. EcoImpactHub applies a sourced emission factor and marks each line verified.
Technical detail
A FluidGrids workflow on a daily schedule reads invoice PDFs from a shared mailbox and fuel-card exports from a drive folder, extracts kilowatt-hours, liters and billing periods, and is designed to split each billing period across reporting periods by day count, recording the method on the draft entry so the proration can be rebuilt. Each draft is designed to reach EcoImpactHub as a carbon entry with the source file attached. AssetHandler keeps chillers, boilers, generators and vans as assets; a refrigerant top-up recorded on a work order is designed to become a fugitive-emissions record sent to EcoImpactHub as a Scope 1 entry, and repeat top-ups on one asset are designed to prompt a leak inspection. EcoImpactHub applies the sourced factor to each entry and moves it from recorded to verified, and AssetHandler reads those metrics back to rank energy and emissions by asset.
Scope 1 and 2 are assembled continuously from documents and work orders that already exist, fugitive emissions are counted, and every line carries its source file and factor.
EcoImpactHub
The ledger where every invoice, fuel and refrigerant line lands as a scoped entry with its emission factor, and moves from recorded to verified.
FluidGrids
The daily schedule, with retries, that runs the invoice and fuel-card collection workflow so activity data arrives without anyone forwarding it.
AssetHandler
Is designed to turn refrigerant top-ups recorded on work orders into gas-specific Scope 1 entries, using GWP values from the EcoImpactHub factor library, and to flag the assets that keep leaking.
Works with EcoImpactHub
Challenge 2 of 6
The responsible-sourcing lead at a soybean crusher that buys from several hundred smallholder farms gets two requests in one morning. A food brand selling into Europe needs plot geolocation and evidence that no farm behind last quarter's soybean oil cleared forest after the cut-off date, for its own due-diligence statement. A fuel blender wants the sustainability declaration for a certified biodiesel feedstock shipment, which means showing that certified volume sold this period does not exceed certified input bought. The plot maps sit with field officers in three formats, a dozen plots over four hectares were mapped as a single point rather than a boundary, and the mass-balance account is a spreadsheet one person updates when they remember.
Answers take days, one missing boundary can hold up a shipment, and an over-issued certified claim puts both the certification and the customer relationship at risk.
Healthy Bowl is designed to map the boundary of each grower's plot, check it against the deforestation cut-off date, and turn growers' fuel, fertilizer and land records into cultivation emissions. TheGlobalFuel is designed to keep the certified balance, adding certified deliveries, subtracting certified shipments and blocking any sustainability declaration the balance cannot cover. At period end, the same records go to EcoImpactHub, so the report cites what the buyer saw.
Technical detail
Healthy Bowl is designed to hold the out-grower side: each plot mapped as a boundary and checked against the deforestation cut-off date, each grower's fuel, fertilizer and land records turned into cultivation emissions, and each delivery recorded as a trace batch. Certified intake batches are designed to pass to TheGlobalFuel with their plot-check status and cultivation carbon intensity, where a mass-balance ledger credits them, debits each certified offtake shipment, blocks any declaration the balance cannot cover, and attaches the declaration and chain-of-custody certificate to the shipment's provenance trail. At period end, TheGlobalFuel is designed to pass each shipment's declaration number, certified volume and carbon intensity to EcoImpactHub, and Healthy Bowl the plot-check status per intake batch and the cultivation emissions as Scope 3 Category 1 purchased-goods entries, so the report cites the same records the buyer saw.
Plot evidence, grower emissions, certified balances and shipment documents are designed to answer a due-diligence request from records, not from a scramble through field officers' laptops.
Healthy Bowl
Maps each out-grower plot, checks it against a cut-off date and exports a plot-level deforestation-free statement for the buyer.
Healthy Bowl
Turns each grower's fuel, fertilizer and land records into cultivation emissions that are designed to flow to TheGlobalFuel as the intake batch's carbon intensity and to EcoImpactHub as Scope 3 Category 1 purchased-goods entries.
TheGlobalFuel
Credits certified feedstock in, debits certified sales out, and blocks any sustainability declaration the period balance cannot cover.
Works with Healthy Bowl, EcoImpactHub
Challenge 3 of 6
The carbon analyst at a consumer-goods distributor reports transport emissions as a spend-based estimate: freight invoices multiplied by an average factor per dollar. When a retailer asks for emissions per pallet delivered on its own lanes, the number cannot be produced. Meanwhile the transport planners know every lane, load weight, distance and mode, because they plan routes and dispatch trucks every day. Moving a regular trunk lane from road to rail would cut emissions, but nobody can say by how much, and a freight rate increase makes the reported figure rise even when nothing physical changed.
Transport emissions behave like a pricing artifact, customer requests go unanswered, and mode-shift decisions are made without the carbon side of the trade-off.
MoveTheWheels already knows each shipment's lane, cargo, vehicle and distance, and is designed to turn that into a carbon estimate per shipment, so price rises stop moving the number. Planners and the carbon team use the same EcoImpactHub emission factors, and FluidGrids is designed to bring in fuel use for company-owned vehicles. Lanes and carriers are ranked from cleanest to most carbon-heavy, and customers get figures for their own lanes.
Technical detail
MoveTheWheels already records each shipment's lane, cargo, vehicle and route distance. Its freight emissions view, an extension of the green analytics on its roadmap, is designed to turn those into tonne-kilometers and estimated CO2e per shipment, and to add rail as a mode alongside road, air and ocean. For the own fleet, FluidGrids is designed to pass liters per vehicle from the fuel-card export (the same one behind Scope 1) to MoveTheWheels for the fuel-based method; contracted carriers use mode-specific distance factors drawn from the EcoImpactHub factor library, so both teams calculate with the same numbers and vintages. Lanes and carriers are ranked by intensity with a method label on every figure. At period end, MoveTheWheels is designed to send contracted freight to EcoImpactHub as Scope 3 Category 4 transport entries tagged with lane and method; own-fleet fuel is already in Scope 1, so it is not sent twice.
Transport emissions move with tonnes and kilometers rather than freight prices, customers get lane-level figures, and mode shifts are weighed with their carbon effect in view.
MoveTheWheels
Estimates CO2e for every shipment from distance, load and mode, ranks lanes and carriers by intensity, and shows the saving of a proposed mode shift.
Works with EcoImpactHub, FluidGrids
EcoImpactHub
The sourced factor library, with a source and valid year on every factor, that the freight estimates are designed to draw on, so both teams calculate the same way.
Challenge 4 of 6
An ecologist at a quarrying company prepares the quarterly update for the community liaison group on the wetland restored beside the working face. Acoustic recorders and camera traps are the evidence, and the headline chart shows bat passes down by a third since spring. On her next visit she finds two recorders with water in the housing and a camera whose card filled in the first week of the quarter, all silent for most of it. Survey effort was never recorded next to detections, battery swaps are tracked on a whiteboard in the site office, and the restoration contractor sends planting survival counts as a spreadsheet at year-end.
A monitoring gap can be reported as a population decline, or a real decline dismissed as a gap, and restoration commitments to regulators and neighbors rest on evidence nobody can reconstruct.
EcoImpactHub is designed to count the nights each camera and recorder was actually working, so a dead battery shows up as a gap in coverage, not a drop in wildlife. A device that goes quiet is designed to raise a work order for the field technician in AssetHandler, and the completed visit appears on the coverage timeline. Restoration work and planting survival counts sit on the same site record.
Technical detail
EcoImpactHub holds the site, its species list and every observation from camera traps, recorders, transects and community reports, with photo evidence and GPS. Its survey-effort view is designed to count working device-nights per camera and recorder, so trends are read as detections per unit of effort and silent devices are flagged instead of counted as zero. The cameras, recorders and water-quality sondes are kept as assets in AssetHandler, where battery swaps, card changes and calibrations run as preventive maintenance. A device that stops reporting in EcoImpactHub is designed to raise an AssetHandler work order for the field technician, and the completed service visit is designed to update device uptime on the coverage view. Restoration activities and survival counts sit on the same site record.
Nature updates are designed to show detections alongside survey effort, device downtime surfaces within days instead of at quarter-end, and restoration evidence builds up on the site record.
EcoImpactHub
Reads species trends per unit of survey effort and marks which devices were actually working, so a gap is never read as a decline.
Works with AssetHandler
AssetHandler
The maintenance calendar where battery swaps, card changes and sensor calibrations for field monitoring devices are designed to run as owned, dated preventive work.
Challenge 5 of 6
At a capital committee meeting in a mid-sized manufacturer, the engineering lead asks for approval to overhaul a twenty-year-old fuel-oil boiler for another decade of service. The company published a 2030 Scope 1 and 2 reduction target last year, but the sustainability team hears about the overhaul the day before, from a forwarded agenda. The target lives in the annual report; the boiler's maintenance history, book value and remaining life live in the maintenance system; the power purchase agreement meant to cover a third of electricity demand sits with procurement in a contract folder. Nobody can show the committee what either option does to the pathway.
Long-lived equipment gets renewed like for like, the gap to target widens quietly, and the transition plan cannot be defended when investors ask how it is funded.
AssetHandler is designed to show the capital committee an old boiler's yearly carbon beside its book value and total cost of ownership, for overhaul versus replacement, so cost and carbon are weighed together. The committee's decision would then be noted against the 2030 target in EcoImpactHub. TheGlobalFuel tracks what the solar power purchase agreement actually delivers, so the renewable share rests on deliveries, not contract size.
Technical detail
EcoImpactHub holds the baseline, the 2030 target and the emission factors, and tracks the target through its lifecycle against the verified ledger. AssetHandler is designed to read the boiler's fuel-oil entries and factor from EcoImpactHub (it already reads EcoImpactHub metrics) and show tonnes of CO2e per year beside book value and total cost of ownership, for overhaul versus replacement, so the committee reads cost and carbon in one comparison. The committee's choice is designed to be recorded on the EcoImpactHub target as a note or linked evidence. TheGlobalFuel holds the solar power purchase agreement as a buy-side electricity contract that tracks delivered against contracted volume, and is designed to send delivered megawatt-hours and retired certificates to EcoImpactHub as market-based Scope 2 inputs, so the renewable share rests on deliveries rather than nameplate.
Decisions on long-lived equipment are taken with their effect on the target in view, and the renewable share in the plan rests on delivered power rather than on contract capacity.
EcoImpactHub
Keeps the baseline, the target and progress against it in one place, with the factors used to value the emissions of each option.
AssetHandler
Shows an asset's book value, depreciation and total cost of ownership: the financial half of a repair-or-replace decision on equipment like the boiler.
TheGlobalFuel
Models the solar power purchase agreement as a buy-side electricity contract whose delivered volume, not nameplate, sets the renewable share.
Challenge 6 of 6
Three weeks before the annual report goes to print, the ESG reporting manager at a listed group receives the assurance provider's sample: eighteen line items, each needing the source records, the calculation and the approvals behind it. Scope 2 no longer agrees across documents: the board pack was built from an export taken before a late invoice correction, and the customer questionnaire picked up a supplier's restated emission factor that the report draft has not. The water figure in the draft uses a definition that changed mid-year. An audit committee member has also asked why market-based Scope 2 rose while location-based Scope 2 fell.
Assurance findings, restatements and late nights; confidence in the numbers erodes with every version, and board questions get answered by whoever happens to remember.
EcoImpactHub builds the report from verified line items, each linked to the records behind it, so the assurer's sample is answered with links rather than attachments. SemanticFed is designed to keep one agreed definition of each figure, so a corrected invoice changes the report, the board view and customer questionnaires together. BigConsole's planned explain feature would answer questions such as why Scope 2 rose, citing the records behind each reason.
Technical detail
The hand-offs are designed to run in a fixed order. First, EcoImpactHub verifies the ledger and assembles the report from framework-tagged line items, each traceable to the entries behind it, through draft, review and published. Second, SemanticFed is designed to define scope2_market_based, water withdrawal and the people metrics once, in a versioned model over the EcoImpactHub ledger and the utility data FluidGrids collects. Third, the report line item, the board console and the questionnaire export are designed to resolve that one definition, so a restated factor or corrected invoice changes all three together. Fourth, FluidGrids feeds the underlying certificate and meter datasets into BigConsole datasinks; BigConsole is designed to render the board ESG console, and its planned Explain panel is designed to answer why Scope 2 rose, citing the dataset and field behind each finding, such as fewer renewable certificates retired in the second half.
Every disclosed figure has one definition and a traceable source, the assurance sample is answered with links rather than attachments, and board questions get cited answers.
EcoImpactHub
Builds framework-tagged reports from traceable line items, with reviewer discussion and clear draft, in-review and published states.
SemanticFed
Is designed to define each disclosure metric once in a versioned model and trace it to its sources and to the report lines and consoles that use it.
BigConsole
Is designed to answer a board question, such as why a figure moved, with short findings, each cited to the dataset and field behind it.
How it fits together
Each product is designed to hand a defined record to the next, with EcoImpactHub as the ledger in the middle and SemanticFed and BigConsole carrying one version of each figure to its readers. Two records also run sideways: a silent monitoring device in EcoImpactHub is designed to raise an AssetHandler work order, and FluidGrids passes certificate and meter records into BigConsole.
To EcoImpactHub: Draft carbon lines with the original document and how bills were split
To EcoImpactHub: Refrigerant top-ups as Scope 1 lines, plus device service visits
To EcoImpactHub: Contracted freight emissions by lane, with how each was calculated
To TheGlobalFuel: Certified deliveries with plot checks and cultivation emissions attached
To EcoImpactHub: Shipment declarations, certified volumes and solar power actually delivered
To SemanticFed: The verified carbon ledger and the report lines
To BigConsole: One agreed set of ESG figures for the board view
Step 1 of 8: Collect activity data
Technical detail
Products in this solution
Carbon ledger, nature evidence and disclosures
Holds each Scope 1, 2 and 3 line with its sourced emission factor, alongside reduction targets, wildlife sightings and restoration projects. It builds the sustainability report so each line traces back to where it came from.
Technical detail
Holds Scope 1, 2 and 3 entries with sourced emission factors, reduction targets, species observations and restoration projects, and assembles framework-tagged reports whose line items trace back to source.
Equipment, refrigerants and monitoring devices
Keeps boilers, chillers, vehicles and field sensors with their maintenance jobs and costs, and ranks their energy and emissions using EcoImpactHub figures. It is designed to log the refrigerant top-ups technicians record on work orders, so they reach the footprint.
Technical detail
Keeps boilers, chillers, vehicles and field sensors as assets with work orders and cost history, reads EcoImpactHub metrics for its sustainability view, and is designed to log refrigerant top-ups recorded on work orders.
Activity-data collection and delivery
Reads invoices, statements and files on a set schedule, pulls out the quantities that matter, and passes them straight into BigConsole, instead of people forwarding spreadsheets.
Technical detail
Runs scheduled workflows that read invoices, exports and files, extract the quantities that matter, and feed datasets into BigConsole datasinks instead of forwarded spreadsheets.
Grower plots, cultivation emissions and trace batches
Is designed to map growers' plots, check them against the deforestation cut-off date, work out cultivation emissions and record deliveries. Growers can already share records with financiers and consultants, with consent and for a set time; this design extends that sharing to buyers.
Technical detail
Is designed to map out-grower plots, check them against a deforestation cut-off date, estimate cultivation emissions and record deliveries as trace batches, extending its consented, time-bounded sharing (already built for financiers and consultants) to buyers.
Chain of custody, mass balance and energy contracts
Follows certified product from plant to delivery with certificates attached, is designed to keep the mass-balance account, and can hold a power purchase agreement to track the power actually delivered.
Technical detail
Follows certified product from plant to delivery with certificates attached, is designed to keep the mass-balance position, and can hold a power purchase agreement as a buy-side electricity contract with delivered volumes.
Freight emissions by lane and carrier
Already knows each shipment's lane, cargo, vehicle and distance, so its planned freight emissions view is designed to work out transport carbon from what physically moved, not from what the freight cost.
Technical detail
Already holds each shipment's lane, cargo, vehicle and route distance, so its planned freight emissions view is designed to calculate transport emissions from physical movement rather than from freight spend.
One agreed definition per ESG metric
Is designed to define each reported figure once, keep every change to that definition on record, and trace it to its sources, so the report, the board view and customer questionnaires all show the same number.
Technical detail
Is designed to define each disclosure metric once in a versioned semantic model over federated sources, with lineage, so the report, the board console and questionnaires resolve the same number.
Board ESG console with cited explanations
Shows the board its ESG figures in one view, and is designed to explain what changed, with each reason pointing to the records behind it.
Technical detail
Renders ESG datasets as a board console, and is designed to explain what changed with findings cited to the dataset and field behind each one.
All eight products run on Burdenoff Workspaces: one sign-on for the sustainability team, site staff, suppliers and assurers; role-based access that can give an assurer read-only evidence and nothing more; one audit trail across every entry and approval; and one bill.
Concept gallery
15 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.
EcoImpactHub
The ledger where every invoice, fuel and refrigerant line lands as a scoped entry with its emission factor, and moves from recorded to verified.
FluidGrids
The daily schedule, with retries, that runs the invoice and fuel-card collection workflow so activity data arrives without anyone forwarding it.
AssetHandler
Is designed to turn refrigerant top-ups recorded on work orders into gas-specific Scope 1 entries, using GWP values from the EcoImpactHub factor library, and to flag the assets that keep leaking.
Works with EcoImpactHub
Healthy Bowl
Maps each out-grower plot, checks it against a cut-off date and exports a plot-level deforestation-free statement for the buyer.
Healthy Bowl
Turns each grower's fuel, fertilizer and land records into cultivation emissions that are designed to flow to TheGlobalFuel as the intake batch's carbon intensity and to EcoImpactHub as Scope 3 Category 1 purchased-goods entries.
TheGlobalFuel
Credits certified feedstock in, debits certified sales out, and blocks any sustainability declaration the period balance cannot cover.
Works with Healthy Bowl, EcoImpactHub
MoveTheWheels
Estimates CO2e for every shipment from distance, load and mode, ranks lanes and carriers by intensity, and shows the saving of a proposed mode shift.
Works with EcoImpactHub, FluidGrids
EcoImpactHub
The sourced factor library, with a source and valid year on every factor, that the freight estimates are designed to draw on, so both teams calculate the same way.
EcoImpactHub
Reads species trends per unit of survey effort and marks which devices were actually working, so a gap is never read as a decline.
Works with AssetHandler
AssetHandler
The maintenance calendar where battery swaps, card changes and sensor calibrations for field monitoring devices are designed to run as owned, dated preventive work.
AssetHandler
Shows an asset's book value, depreciation and total cost of ownership: the financial half of a repair-or-replace decision on equipment like the boiler.
TheGlobalFuel
Models the solar power purchase agreement as a buy-side electricity contract whose delivered volume, not nameplate, sets the renewable share.
EcoImpactHub
Builds framework-tagged reports from traceable line items, with reviewer discussion and clear draft, in-review and published states.
SemanticFed
Is designed to define each disclosure metric once in a versioned model and trace it to its sources and to the report lines and consoles that use it.
BigConsole
Is designed to answer a board question, such as why a figure moved, with short findings, each cited to the dataset and field behind it.
Pitch kit
Sustainability teams are asked for assured, comparable numbers, but the evidence lives with maintenance, logistics, procurement, ecologists and suppliers. Burdenoff products are designed to capture it in the tools those teams already use, from refrigerant top-ups and freight lanes to grower plots and camera traps, and carry it into one carbon ledger and one set of metric definitions, so every disclosed figure traces back to the record that produced it.
Questions
No. The products are designed to keep your evidence, calculations and approvals traceable, so an independent assurance provider or certification body can follow them. EcoImpactHub is not a certification body or a regulator, and nothing on this page is verification, assurance or advice on what your disclosures must contain.
Technical detail
No. The products are designed to keep evidence, calculations and approvals traceable so that an independent assurance provider or certification body can follow them. EcoImpactHub is not a certification body or a regulator, and nothing on this page is verification, assurance or advice on what your disclosures must contain.
EcoImpactHub is designed to tag each report line to the Greenhouse Gas Protocol, the Global Reporting Initiative, the TCFD climate-risk recommendations, CDP, the SASB industry standards, or a framework you define. Newer rules, like the IFRS S2 climate standard or the EU's reporting standards (ESRS), can be set up as your own framework; your advisers still decide what each requires.
Technical detail
EcoImpactHub is designed to tag report line items to the GHG Protocol, GRI, TCFD, CDP and SASB, or to a custom framework you define. Newer regimes such as IFRS S2, which carries forward the TCFD recommendations, or the EU's ESRS can be set up as custom frameworks; your own advisers stay responsible for deciding what each regime requires of you.
No. Most teams would start with EcoImpactHub plus the product that holds their hardest data: AssetHandler for equipment and refrigerants, Healthy Bowl or TheGlobalFuel for farm or commodity supply chains, MoveTheWheels for freight. SemanticFed, FluidGrids and BigConsole earn their place as more teams supply figures and more people read them.
Technical detail
No. Most teams would start with EcoImpactHub plus the product that holds their hardest data: AssetHandler for equipment-heavy sites and refrigerants, Healthy Bowl or TheGlobalFuel for agricultural or commodity supply chains, MoveTheWheels for freight. SemanticFed, FluidGrids and BigConsole earn their place as more sources and more readers of the numbers appear.
Healthy Bowl already lets growers share records with financiers and consultants, with consent and for a set time; sharing with buyers is part of this design, not available today. A grower or cooperative would decide what a buyer sees and for how long. Across the products, each colleague, supplier or assurer gets only the records and actions they need.
Technical detail
Healthy Bowl's consented, time-bounded, read-scoped windows are built today for financiers and consultants; windows for buyers are part of this design, not available today. The idea is that a grower or cooperative decides what a buyer can see and for how long. Across the products, role-based access in Burdenoff Workspaces scopes each colleague, supplier or assurer to the records and actions they need.
Yes. Protecting them is part of the design. EcoImpactHub includes safeguards for sensitive species and site details, so staff, contractors and community members can record sightings without exposing at-risk wildlife in exports or shared views.
Technical detail
Yes, that is part of the design. EcoImpactHub includes safeguards for sensitive species and site data, so observations from staff, contractors and community contributors can be recorded without exposing at-risk populations in exports or shared views.
No. Only FluidGrids is available now; the other products are pre-launch or in early access. This page describes a proposed solution, and some parts, such as the refrigerant log, the mass-balance ledger, the freight emissions view, the survey-effort view and the ESG metric definitions, are new ideas designed for this industry. Talk to us about what fits and when.
Technical detail
FluidGrids is generally available; the other products are pre-launch or in early access. This page describes a solution concept, and some surfaces shown here, such as the refrigerant log, the mass-balance ledger, the freight emissions view, the survey-effort view and the ESG metric definitions, are new concepts designed for this industry. Talk to us about which parts fit your program and when.
Related domains
Challenges solved
A connected solution for farmer cooperatives, producer companies and agri-food supply chains: field intelligence, cold chain, logistics, traceability and rural finance on connected records.
Challenges solved
A cross-product solution concept for oil and gas, mining, renewables and utilities: equipment reliability, cargo readiness, methane and water compliance, site security and turnaround crews.
Challenges solved
A solution concept for discrete and batch plants: ManufacturedOps with AssetHandler, CrewFoundry, MoveTheWheels and EcoImpactHub, connected by automation and analytics.
Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.
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.