Identifying environmental aspects means finding the interactions associated with the organisation’s activities, products and services. The task comes before significance scoring. A carefully designed matrix cannot correct an inventory that omits maintenance, contractors or an important release pathway.
The aspects and impacts overview explains the full assessment cycle. Use the examples guide as a source of questions, while building the actual inventory from evidence about your organisation.
Define the boundary and team
Start with the EMS scope, locations, activities and organisational interfaces. Decide how the work will be divided so that shared areas and outsourced activities do not fall between teams.
Include people who understand operations, maintenance, purchasing and relevant environmental responsibilities. A coordinator can organise the process, but one person working from a desk is unlikely to know every temporary practice or unusual condition.
Explain the purpose in practical language. The team is identifying interactions that affect environmental conditions, not simply collecting anything labelled green or producing the highest possible number of register entries.
Map activities at a useful level
Break the operation into processes or tasks that can be observed. Receiving, storage, production, cleaning, maintenance, dispatch and waste handling are common prompts, but the right structure depends on the business.
For each activity, consider inputs, outputs and potential releases. Inputs may include materials, water and energy. Outputs may include products, emissions, wastewater, waste and noise. Potential releases may occur when equipment or handling arrangements fail.
Keep the level of detail consistent enough to compare entries. A whole factory in one row and an individual printer in another can distort attention. Split activities where conditions, impacts or controls differ materially.
Observe ordinary and less visible work
Walk the relevant areas with people who perform the tasks. Compare the written process with actual practice, including temporary storage, cleaning methods and maintenance access.
Arrange observation of shifts or activities not represented during the first visit. Weekend work, start-up and contractor tasks may create interactions absent from the daytime routine.
Ask neutral questions: what happens when this container is damaged, when equipment stops, or when the normal collection is delayed? The answers can reveal aspects that an idealised process map misses.
Use records to test the picture
Review material inventories, utility data, waste information, discharge records, incident reports and maintenance history. These sources can show quantities, patterns and unusual events.
Check records against observation. A chemical purchased regularly but absent from the inventory needs investigation. An unused drain shown on a drawing may still receive wash water in practice.
Do not assume that a missing record means the interaction does not occur. Record the gap, identify the likely owner and obtain enough evidence to support the assessment. Where estimation is necessary, state the basis and limitations.
Trace interactions into impacts
For each aspect, describe the environmental change that could result. Investigate pathways and receptors where they affect the decision. Resource demand and emissions can also have effects outside the site boundary.
Distinguish environmental impacts from business consequences such as cost or enforcement exposure. Both may matter, but the aspect inventory needs to preserve the environmental relationship.
Avoid broad entries such as pollution or environmental risk. Identify the material, release or demand involved. Clear wording allows the later evaluation to address real conditions rather than a vague category.
Include operating conditions and change
Consider normal operation, abnormal conditions and foreseeable emergencies. Use site knowledge and history to select credible situations rather than attempting to list every theoretical event.
Review planned changes before implementation where possible. A new material, increased storage volume or changed contractor can alter interactions even if the main product remains unchanged.
Record the relevant condition with the entry. Otherwise, different assessors may evaluate a routine activity and an emergency scenario as if they were the same situation, producing scores that cannot be interpreted.
Consider control and influence across stages
Ask about relevant stages before and after the organisation’s own operation. Purchasing specifications, design, transport, customer information and end-of-life arrangements may offer influence over environmental interactions elsewhere.
Define that influence realistically. A purchaser can request information or set contractual expectations without controlling all supplier operations. A designer may influence material use and repairability even where production is outsourced.
A life cycle perspective provides a structured set of questions. It does not automatically require a detailed quantitative life cycle assessment for every product or service.
Check completeness before scoring
Review the draft inventory with process owners. Look for missing support activities, shared facilities, outsourced work and different operating conditions. Compare similar areas to identify inconsistent treatment.
Then apply the organisation’s significance method. Keep identification evidence and uncertainty accessible so that later scores can be explained. If important information remains missing, decide what interim arrangements and investigation are needed.
Finally, connect the inventory with a review process. New equipment, incidents, complaints and changing environmental conditions can reveal gaps. Identification is successful when it produces a credible picture that can support controls and decisions, rather than a static list completed once for an audit.
Include a way for staff to suggest missing interactions after the first assessment. A short report from someone performing an unusual task can reveal a gap that a formal workshop did not encounter.