> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Emission Event Statuses for Workflow

> Efficiently manage your emission workflow with smart status tracking that automatically prioritizes work and ensures nothing falls through the cracks.

<img className="block dark:hidden" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/emission-event-statuses-hero-light.png" alt="Emission Event Statuses workflow overview" />

<img className="hidden dark:block" src="https://mintlify.s3.us-west-1.amazonaws.com/sensorupinc/images/emission-event-statuses-hero-dark.png" alt="Emission Event Statuses workflow overview" />

## What are Emission Event Statuses?

Emission Event Statuses help you efficiently manage your emission workflow by automatically organizing events into four clear categories. Instead of manually tracking which emissions need attention, the system provides instant visibility into what requires action versus what's already handled, allowing you to focus your team's efforts where they matter most.

<CardGroup cols={3}>
  <Card title="Instant Prioritization" icon="clock">
    See critical events requiring immediate action within seconds of logging in
  </Card>

  <Card title="Zero Missed Events" icon="shield-check">
    Automated status tracking ensures no emission falls through the cracks
  </Card>

  <Card title="Smart Workflow" icon="brain">
    System intelligently moves events through your workflow without manual effort
  </Card>
</CardGroup>

## Why Use Emission Event Statuses?

<CardGroup cols={2}>
  <Card title="The Problem" icon="triangle-exclamation">
    **Without status management:**

    * Time wasted sorting through resolved events
    * Critical emissions missed in cluttered lists
    * Manual tracking prone to human error
    * No clear workflow for field teams
    * Compliance gaps from poor organization
  </Card>

  <Card title="The Solution" icon="lightbulb">
    **With Emission Event Statuses:**

    * Instant visibility into priority work
    * Automated workflow reduces manual tasks
    * Clear action items for every team member
    * Compliance-ready audit trails
    * Efficient resource allocation
  </Card>
</CardGroup>

## Understanding the Four Status Types

The system organizes every emission event into one of four statuses, each with a clear meaning and required action:

<CardGroup cols={2}>
  <Card title="🟢 Open" icon="flag">
    **Default status for new events**

    **What it means:** This emission needs immediate attention and action.

    **Your action:** Prioritize these events for investigation and field response. These are your highest priority items.
  </Card>

  <Card title="🟡 In Progress" icon="clock">
    **Work has started**

    **What it means:** Someone is actively working on this emission, but it's not fully resolved yet.

    **Your action:** Continue working through required tasks or monitor progress if assigned to another team member.
  </Card>

  <Card title="🔵 Closed" icon="check-circle">
    **Fully resolved**

    **What it means:** The emission has been completely addressed and all required actions are finished.

    **Your action:** Use these events for reporting and compliance documentation.
  </Card>

  <Card title="⚪ False Alarm" icon="x-circle">
    **Not a real emission**

    **What it means:** Investigation determined this was a false positive detection.

    **Your action:** Filter these out of your active work queue - no further action needed.
  </Card>
</CardGroup>

## Getting Started

<Info>
  **Ready to streamline your emission workflow?** Follow these quick steps to start using status-based prioritization immediately.
</Info>

<Steps>
  <Step title="Access Your Emission Events">
    Log into SensorUp and navigate to the Emission Events page. You'll see all events with their current status displayed.
  </Step>

  <Step title="Filter by Priority">
    Click the status filter and select "Open" to see only events requiring immediate action. This gives you a clean, prioritized work list.
  </Step>

  <Step title="Take Action">
    Start with the first Open event. The system will automatically move it to "In Progress" when you begin working, and to "Closed" when complete.
  </Step>
</Steps>

## How Status Changes Work

### Automatic Updates

The system intelligently updates statuses based on data completeness, field actions, and verification results. Understanding these rules helps you predict when events will change status automatically.

#### Events Stay OPEN When Missing Critical Information

The system keeps events in **Open** status until all required data is available:

<AccordionGroup>
  <Accordion title="Missing End Time" icon="clock">
    **What this means**: The emission appears ongoing - system hasn't confirmed it stopped

    **Why it stays Open**: Without an end time, we can't determine if the emission is resolved

    **How to resolve**: Field verification to confirm emission has ceased, or system detection of emission end
  </Accordion>

  <Accordion title="Missing Start Time" icon="calendar">
    **What this means**: System can't determine when the emission began

    **Why it stays Open**: Timeline is incomplete for proper assessment

    **How to resolve**: Field investigation to establish when emission likely started
  </Accordion>

  <Accordion title="Active Monitoring Alarms" icon="bell">
    **What this means**: Continuous monitoring system triggered an alarm needing investigation

    **Why it stays Open**: Alarm indicates ongoing issue requiring attention

    **How to resolve**: Investigate monitoring alert and address underlying cause
  </Accordion>

  <Accordion title="Active Work Orders" icon="wrench">
    **What this means**: Field crew has an active work order for this emission

    **Why it stays Open**: Work is in progress but not yet complete

    **How to resolve**: Complete field work and mark work order as finished
  </Accordion>
</AccordionGroup>

#### Automatic Status Transitions

<CardGroup cols={2}>
  <Card title="Open → In Progress" icon="arrow-right">
    **Triggers automatically when:**

    * Work order is created and assigned to field crew
    * Team member takes first action on the event
    * Investigation or repair work begins
  </Card>

  <Card title="In Progress → Closed" icon="check">
    **Triggers automatically when:**

    * All required data is collected (start/end times)
    * No active monitoring alarms remain
    * Field crew marks work as complete
  </Card>
</CardGroup>

#### Auto-Close Conditions

Events automatically move to **Closed** status when these conditions are met:

* ✅ **Complete Timeline**: Both start and end times are established
* ✅ **No Active Alarms**: All monitoring systems show normal operation
* ✅ **Work Complete**: No active work orders or field tasks remain
* ✅ **Verification Confirmed**: Camera inspection or survey confirms resolution

### Manual Controls

You maintain full control and can override the system when needed:

<AccordionGroup>
  <Accordion title="When to Manually Close Events" icon="hand">
    Use manual closure when an emission is resolved through means the system doesn't automatically track, such as:

    * Field crew confirms repair completion outside the system
    * Equipment replacement resolves the underlying issue
    * Operational changes eliminate the emission source
  </Accordion>

  <Accordion title="Marking False Alarms" icon="warning">
    Mark events as False Alarm when investigation reveals:

    * Satellite or drone detected something other than methane
    * Weather conditions caused false readings
    * Equipment reflection or interference created false positive
    * No physical emission source can be identified
  </Accordion>

  <Accordion title="Reopening Closed Events" icon="refresh">
    Reopen events when:

    * An emission reappears after initial repair
    * Additional investigation reveals the issue wasn't fully resolved
    * New detection data suggests the event is still active
  </Accordion>
</AccordionGroup>

### Bulk actions

You can update multiple emission events at once using bulk actions:

<Steps>
  <Step title="Select events">
    Select rows in the emissions table by clicking on them. To select multiple rows quickly, click on a row, hold Shift, and click on another row further down to select all rows in between.
  </Step>

  <Step title="Choose an action">
    At the bottom of the page, select **False Alarm** or **Close**.
  </Step>

  <Step title="Add explanation and confirm">
    Add an Explanation for the action and click **Confirm**. A success message will display to confirm the action was successful.
  </Step>
</Steps>

<Tip>
  To undo a bulk action, click on the event and use the **Undo False Alarm** or **Undo Close** button at the top of the blade.
</Tip>

## Common Use Cases

### Daily Priority Management

**Scenario**: You're a field operations manager starting your day and need to assign work to your team.

**Workflow**: Filter events by "Open" status to see all unresolved emissions. Assign based on location and severity, knowing the system will track progress automatically.

**Result**: Your team works efficiently on real priorities without time wasted on already-handled events.

### Compliance Reporting

**Scenario**: You need to prepare monthly emission reports for regulatory compliance.

**Workflow**: Filter by "Closed" status for the reporting period. The system provides complete audit trails showing detection, response, and resolution for each event.

**Result**: Fast, accurate compliance reporting with documented evidence of proper emission management.

### False Alarm Management

**Scenario**: Field investigation reveals a satellite detection was actually equipment reflection, not a real emission.

**Workflow**: Mark the event as "False Alarm" with investigation notes. The system removes it from active work queues while preserving the record.

**Result**: Clean work lists focused on real emissions, with historical record maintained for analysis.

## Special Facility Considerations

<Warning>
  **Enhanced Verification Required**: Certain facility types have additional verification requirements that affect status behavior.
</Warning>

Some facilities require enhanced verification protocols:

* **Extended Open Periods**: Events may stay "Open" longer than at standard facilities
* **Manual Verification Required**: Even when automated systems show no issues, events need human confirmation
* **Enhanced Accuracy**: Stricter verification standards ensure proper oversight of critical operations

**This is intentional behavior** - high-priority facilities require extra caution to ensure nothing important is missed.

## FAQ / Troubleshooting

<AccordionGroup>
  <Accordion title="Why do some events stay Open longer than others?" icon="question">
    Several factors can keep events in Open status:

    * Missing start/end time data requiring field verification
    * Cannot identify specific equipment source (need more precise location)
    * Continuous monitor alarm needs investigation
    * High-priority facility requiring enhanced verification
  </Accordion>

  <Accordion title="How do I know what action to take on an Open event?" icon="question">
    Open events typically need one of these actions:

    * Dispatch field crew for investigation
    * Review monitoring alarms for additional data
    * Check if emission source can be more precisely identified
    * Coordinate with operations for equipment status
  </Accordion>

  <Accordion title="Can I change a status back if I made a mistake?" icon="question">
    Yes, you can reverse most status changes:

    * Reopen Closed events if the emission returns
    * Undo False Alarm if investigation was incorrect
    * Manually close In Progress events if resolution happens outside the system
  </Accordion>

  <Accordion title="What if my event doesn't fit the standard workflow?" icon="question">
    Use manual status controls for exceptional situations:

    * Skip automatic progressions when appropriate
    * Add detailed notes explaining the unique circumstances
    * Coordinate with your team lead for non-standard cases
  </Accordion>
</AccordionGroup>

***

## Related Features

<CardGroup cols={2}>
  <Card title="Emission Event Model" icon="database" href="/use-sensorup/emission-operations/technical-specifications/emission-event-model">
    Understand the complete data structure behind emission events and how information flows through the system.
  </Card>

  <Card title="Event Management Workflow" icon="workflow" href="/use-sensorup/emission-operations/event-management/getting-started-with-event-management">
    Learn the complete workflow for managing emission events from detection through resolution.
  </Card>
</CardGroup>

## Feedback & Support

<Warning>
  **Found an issue with status tracking?** Contact support immediately to ensure proper emission management and compliance.
</Warning>

**Having trouble with workflow efficiency?** Share your feedback to help us improve status automation and prioritization features.
