Observation collection

Sustainability Analyst collects observations for a selected reporting period and revision. Each observation can retain a description, quantity, unit and observation date with its source reference. Pending, Accepted and Rejected distinguish the recorded outcome when the team examines whether an observation belongs in the reporting work.

The collection action keeps an operation run and numbered steps. These records give the team a way to investigate the collection attempt if the outcome is uncertain. Data Steward checks the evidence basis and source mapping before Sustainability Reviewer is asked to rely on the collected scope.

• Select the period. Sustainability Analyst begins from the reporting cycle being prepared. Check its organization and source identity before collecting facts. An observation should be attached to the period whose measurement basis explains what the value means.
• Retain the measured context. Record the source reference alongside the quantity, unit and date. Keep the consent or evidence basis available where it applies to the source. A description should help another person recognize the event or measurement without relying on an informal explanation.
• Inspect the collection outcome. Follow the operation run and its numbered steps. A failed or uncertain step needs investigation before the team treats the collection as complete. The existing operation identity helps distinguish a repeated request from another reporting task.

Agree the source fields and the mapping version with Data Steward. Decide which unit and observation date belong to the reporting case. The team should understand whether a source date describes the measurement itself or when the evidence was made available.

Set the conditions for accepting an observation and the reason for returning a questionable source fact to its owner. Agree how the analyst locates an existing collection run after a delayed response. Sustainability Reviewer needs the same source revision and evidence context that the collection action used.

Use the April Operations Review rehearsal period. Collect an observation whose date falls in April and whose source reference opens the expected supporting record. Inspect its quantity and unit with Data Steward before the analyst treats it as suitable evidence for the period.

Add another observation dated in May. Ask the team to identify the mismatch and determine the appropriate recorded outcome. The source reference should remain available during the investigation. Resolve the reporting scope before the reviewer is asked to decide on the April revision.

Then repeat a collection request using its existing operation identity. Inspect the run and steps to establish what happened. If a step is failed or uncertain, follow its input and output references rather than assuming that another visible observation means every intended effect succeeded.

• Observation Review Queue — Pending observations with quantity, unit, date and source context.
• Operation Step Outcomes — Numbered collection steps and their recorded outcomes.

Follow Evidence collection and validation, then use Review and result handoff.