Skip to main content

Reviewing Events

Efficient event review is critical for security operations. This guide covers workflows for reviewing Anava events and making quick decisions.

Event Review Workflow

Standard Review Process

Event Review Workflow

Queue Management

Events appear in the review queue when:

  • Detection confidence is above threshold
  • Alert is triggered
  • Push notification sent
  • Manual flag added

Quick Triage

Triage View

The triage view is optimized for rapid review:

┌────────────────────────────────────────────────────────────┐
│ Event Queue 12 pending │
├────────────────────────────────────────────────────────────┤
│ ┌──────────┐ 14:32:15 | Entrance-Main │
│ │ │ Profile: After Hours Security │
│ │ [thumb] │ Detection: Person (95%) - Not authorized │
│ │ │ [Verify] [Dismiss] [Investigate] │
│ └──────────┘ │
├────────────────────────────────────────────────────────────┤
│ ┌──────────┐ 14:28:03 | Gate-North │
│ │ │ Profile: Perimeter Watch │
│ │ [thumb] │ Detection: Vehicle (88%) │
│ │ │ [Verify] [Dismiss] [Investigate] │
│ └──────────┘ │
└────────────────────────────────────────────────────────────┘

Triage Actions

ActionWhen to UseEffect
VerifyConfirmed real eventMarks as verified, logs action
DismissFalse positiveRemoves from queue, optionally logs reason
InvestigateNeeds more infoOpens detailed view
EscalateRequires supervisorRoutes to escalation queue

Keyboard Navigation

KeyAction
VVerify current event
DDismiss current event
IInvestigate (open details)
EEscalate
NNext event
PPrevious event

Detailed Review

Analysis View

Open event details for full investigation:

┌─────────────────────────────────────────────────────────────┐
│ Event Analysis │
├────────────────────────────┬────────────────────────────────┤
│ │ Overview │
│ │ ├─ Time: 14:32:15 │
│ │ ├─ Camera: Entrance-Main │
│ [Full Image] │ ├─ Profile: After Hours │
│ with bounding │ ├─ Trigger: AOAS Person │
│ boxes │ └─ Confidence: 95% │
│ ├────────────────────────────────┤
│ │ AI Analysis │
│ │ "Person detected at entrance │
│ │ during after-hours period. │
│ │ Individual is not wearing │
│ │ visible badge or uniform. │
│ │ Appears to be approaching │
│ │ the door with intent to │
│ │ enter." │
├────────────────────────────┴────────────────────────────────┤
│ Objects Detected │
│ ┌──────────┐ ┌──────────────────┐ ┌─────────────────┐ │
│ │ Person │ │ Not Authorized │ │ No Badge │ │
│ │ 95% │ │ 88% │ │ 92% │ │
│ └──────────┘ └──────────────────┘ └─────────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ Question Responses │
│ • Authorized personnel? No │
│ • Employee or visitor? Unknown - no badge visible │
│ • Threat assessment: Low - no concerning items visible │
│ • Description: Male, approx 30-40, dark jacket, jeans │
├─────────────────────────────────────────────────────────────┤
│ Actions │
│ [Verify Threat] [False Alarm] [Need More Info] [Escalate] │
└─────────────────────────────────────────────────────────────┘

Comparing with Context

Use context tools to make decisions:

ToolDescription
Recent EventsSee prior events from same camera
Similar DetectionsFind similar objects across cameras
TimelineView events over time period
Live ViewCheck current camera feed

Adding Notes

Document your review:

┌─────────────────────────────────────┐
│ Add Review Note │
├─────────────────────────────────────┤
│ Classification: [Verified Threat ▼] │
│ │
│ Notes: │
│ ┌─────────────────────────────────┐ │
│ │ Confirmed unauthorized access │ │
│ │ attempt. Individual fled when │ │
│ │ TTS activated. Notified site │ │
│ │ security at 14:35. │ │
│ └─────────────────────────────────┘ │
│ │
│ Follow-up Required: [Yes ▼] │
│ Assign to: [Security Manager ▼] │
│ │
│ [Save Note] │
└─────────────────────────────────────┘

Event Classification

Classification Categories

CategoryDescriptionExample
Verified ThreatConfirmed security eventUnauthorized person
Verified AlertConfirmed non-threatEmployee without badge
False PositiveIncorrect detectionShadow detected as person
Equipment IssueCamera/system problemLighting triggered motion
Needs ReviewRequires supervisorAmbiguous situation

Classification Impact

Classifications help:

  • Track true positive rates
  • Identify tuning needs
  • Document incident history
  • Improve AI prompts

Response Actions

Immediate Response

ActionHow
Trigger TTSClick "Play Announcement"
Alert SecurityClick "Notify Team"
Lock DownTrigger I/O output (if configured)
Start RecordingSend command to VMS

VMS Integration

If VMS is connected:

Response Actions:
├── Start PTZ Tracking
├── Begin High-Quality Recording
├── Display on Video Wall
├── Trigger Alarm
└── Send to Mobile App

Follow-Up Actions

Create follow-up tasks:

  • Assign to team member
  • Set due date
  • Attach event evidence
  • Track resolution

Batch Review

Reviewing Multiple Events

For efficient batch processing:

  1. Filter to similar events

    • Same camera, time range, detection type
  2. Use batch actions

    • Select multiple events
    • Apply same classification
  3. Document once

    • Add note to group
    • Link related events

Batch Classifications

Select multiple events and:

ActionEffect
Verify AllMark all as verified
Dismiss AllClear queue for false positives
Flag for ReviewSend to supervisor queue

Quality Metrics

Review Performance

Track your review efficiency:

MetricTargetYour Performance
Events reviewed/hour60+--
Average review time< 30 sec--
Accurate classifications95%+--
Escalation rate< 10%--

Detection Accuracy

Monitor detection quality:

This Week's Stats:
├── Total Events: 1,247
├── True Positives: 892 (71.5%)
├── False Positives: 312 (25.0%)
├── Needs Tuning: 43 (3.5%)
└── Profiles Affected: Security After Hours (highest FP rate)

Escalation Workflow

When to Escalate

Escalate when:

  • Confirmed threat requires response
  • Classification is uncertain
  • Policy violation detected
  • Multiple related events

Escalation Process

Escalation Process

Escalation Categories

PriorityCriteriaResponse Time
CriticalActive threatImmediate
HighConfirmed intrusion< 5 minutes
MediumPolicy violation< 30 minutes
LowReview needed< 4 hours

Reporting

Shift Reports

Generate end-of-shift reports:

Shift Summary: 2024-01-15 (Day Shift)
├── Events Reviewed: 156
├── Verified Threats: 3
├── False Positives: 12
├── Escalations: 2
├── Average Response Time: 45 sec
└── Cameras with Issues: 2 (noted)

Incident Documentation

For verified incidents:

  1. Complete event classification
  2. Add detailed notes
  3. Attach evidence
  4. Generate incident report
  5. Export for records

Best Practices

Efficient Review

  1. Use keyboard shortcuts
  2. Review in batches by camera/profile
  3. Address high-priority first
  4. Document as you go

Accurate Classification

  1. Review full context before deciding
  2. Check similar recent events
  3. Use "Needs Review" when uncertain
  4. Provide feedback for false positives

Consistent Documentation

  1. Use standard classification terms
  2. Include relevant details in notes
  3. Link related events
  4. Complete required fields

Troubleshooting

Queue Overwhelmed

If events are backing up:

  1. Apply aggressive filters

    • Focus on high-confidence only
    • Review critical cameras first
  2. Use batch dismiss

    • Clear obvious false positives
    • Document reason once
  3. Tune profiles

    • Increase confidence thresholds
    • Adjust trigger sensitivity

Missed Events

If real events are being missed:

  1. Lower confidence thresholds
  2. Add object types to skill
  3. Review trigger configuration
  4. Check camera positioning