Goal and Scope Definition: Setting a Defensible Study
What this domain tests
Goal and Scope Definition tests whether you can state why a study exists, who will use it, what function is modelled, which impacts and boundaries apply, and which assumptions must be disclosed before data collection begins.
Core rules and concepts
- The goal states intended application, reasons for carrying out the study, intended audience, and whether a comparative assertion will be disclosed publicly.
- The scope defines the product system, function, functional unit, reference flow, system boundary, allocation procedures, LCIA methods and categories, data requirements, assumptions, limitations, and review type.
- Scope is provisional. Iteration is allowed, but changes must be documented and their effect on results explained.
- Data quality requirements should be specified in advance: geography, time period, technology, precision, and representativeness.
Worked example
A coffee company wants to compare capsule and filter brewing for an internal eco-design workshop. The goal is internal improvement, not a public claim. The scope sets the function as "deliver 1,000 cups of coffee at home", includes the brewing machine, coffee, packaging, electricity, and waste, and selects GWP100 plus water use. Because the audience is internal, external critical review is optional, but the company still documents the electricity grid mix and machine lifetime. If the goal later changes to a public marketing comparison, the scope must be revised and a review panel added.
Traps that cost marks
- Writing a vague goal such as "assess environmental impact" without application or audience.
- Defining the functional unit after seeing which result is favourable.
- Omitting capital goods, use phase, or end-of-life without justification.
- Failing to state whether the study supports a public comparative claim.
- Changing boundary or impact method silently during interpretation.