A finished DBA-835 Topic 3 emissions baseline reconstruction example, rebuilding a retailer's purchased-goods emissions from spending records and separating later method changes from real reductions. Searches like "dba 835 topic 3 assignment example", "dba835 topic 3 sample" and "dba-835 topic 3 example" land here.
What a finished DBA-835 Topic 3 emissions baseline reconstruction looks like
The finished reconstruction starts from what the retailer holds for its chosen base year: invoices by supplier and product category, freight bills, and almost no emissions data from the factories that make its sofas and tables. Purchased goods are therefore estimated by the spend-based method, multiplying dollars spent by average emission factors for each category. The paper states what that method implies. A price rise increases estimated emissions with no change in any factory, so spending is deflated to base-year prices. A move from average factors to supplier-reported data can shift the total sharply, and the paper applies the GHG Protocol's recalculation approach, restating the base year when the method changes significantly. Its final section sets out a reporting rule: every later year's change is split into the part from real activity and the part from method.
How a DBA-835 Topic 3 example is structured
The reconstruction is built in six parts. The opening explains the target the board wants to announce and why a target without a defensible base year is a promise measured against nothing. The second inventories what the base year actually recorded and what it did not, category by category. A third part builds the spend-based estimate, with the source of each emission factor named and the deflation step shown. The fourth tests how sensitive the total is to the choice of factor database, running the estimate with two recognized sources and reporting the difference. Fifth comes the recalculation policy: which changes, such as an acquisition or a switch to supplier data, trigger restating the base year, and the significance test the retailer will apply. The paper ends with the reporting rule that separates activity change from method change in every subsequent year.
What the base year actually recorded
Invoices, freight bills and a handful of supplier reports make up the evidence, and the paper lists each category that has no measured emissions data at all.
Spending converted with average factors
Dollars spent in each product category are multiplied by published average emission factors, which the paper labels an estimate of the category rather than of the suppliers.
Prices removed before emissions are estimated
Spending is restated in base-year prices, since otherwise inflation alone would raise estimated emissions while every factory kept operating exactly as before.
Two factor databases compared
Running the estimate with two recognized sources of emission factors shows how much of the baseline depends on a database choice rather than on the retailer's purchases.
A policy for restating the base year
Following the GHG Protocol, acquisitions and significant method changes trigger recalculation, so each later year is compared with a baseline built the same way.
Method change split from real change
Each future report divides the year's movement into the effect of changed purchasing or production and the effect of changed estimation, and publishes both parts.
Where marks go in DBA-835 Topic 3
Reconstructions lose most heavily when the base-year figure is presented as a measurement. A spend-based estimate multiplies dollars by industry averages, and printing it without saying so lets readers take it for factory data. Papers that skip deflation build inflation into the baseline and later report falling prices as falling emissions, or rising prices as failure. Choosing an emission factor database without testing another hides how much of the total rests on that choice. The most consequential gap is the absence of a recalculation policy, because the first switch to supplier-reported data will then move the total and invite a claim of progress nobody earned. The advocacy error runs the other way as well: presenting the baseline as a solid foundation for an ambitious target overstates what estimated data can bear.
Get a DBA-835 Topic 3 example written to your instructions
Send the DBA-835 Topic 3 instructions and the rubric posted in your classroom, with the company or data case your section provides. We write a custom example to them, with the base-year evidence inventoried, the estimation method named, prices removed, factor sources compared, a recalculation policy set and method change separated from real change, in 24 to 48 hours. The first one is free.
DBA-835 Topic 3 questions, answered
What is the spend-based method?
A way of estimating supply-chain emissions by multiplying the money spent in each purchase category by an average emission factor for that category. It needs only financial records, which is why companies often start with it. Its limitation is that it describes an average producer, not the company's actual suppliers, and it moves with prices. The example uses it for the base year and labels it plainly as an estimate.
Why would a company restate its base year?
Because comparisons over time mean something only if both years are measured the same way and cover the same business. The GHG Protocol provides for recalculating the base year after structural changes such as acquisitions and after significant changes in method or data. Without restatement, a switch to better data can look like a reduction, or an increase, that no operational change caused.
Can supplier-reported data be trusted more than averages?
Often, but not automatically. Supplier figures describe the actual factories, yet they vary in method, boundary and verification, and a supplier with a strong incentive to appear efficient may report favorably. The example treats supplier data as an improvement to be checked rather than a replacement to be accepted. The retailer is a composite, and the reconstruction is DBA-835 coursework, not a reporting or assurance opinion.