Report Management & Response

When AI Safety Research teams submit findings from agentic and human-validated testing, you need to review, respond, and take action. All reports are part of The Consolidated AI Product Safety Pipeline workflow. This phase is crucial for improving your AI systems. Here's how to effectively manage AI safety reports on AIRTA Systems.

Video Tutorial

Manage AI Safety Reports on the AIRTA Systems Platform

In this guide we show you how to manage reports on the AIRTA Systems Platform. AI Compliance needs a human-in-the-loop AI product compliance to ensure consumer safety. Turnkey package including compliance documentation, researcher-led safety testing, post market monitoring, FRIA & product liability directive assurance.

Accessing Reports

1. Go to your dashboard.
2. Click AI Safety Reports or View Reports.
3. See all submissions in one organized list.
4. Filter by status, date, severity, team, or team member.

Understanding Report Status

• Submitted: New report awaiting your review.
• Pending: You're reviewing or requesting more information.
• Accepted: You've confirmed the issue is valid.
• Rejected: The issue is not valid or not applicable.

Reviewing Individual Reports

1. Click on any report to view full details.
2. Read the vulnerability description carefully.
3. Review steps to reproduce the issue.
4. Assess the potential impact and severity.
5. Consider the team's recommendations.
6. Review team member attributions and contributions.

Report Components

• Title: Brief description of the issue.
• Description: Detailed explanation of the problem.
• Steps to Reproduce: How to recreate the issue.
• Expected Behavior: What should happen normally.
• Actual Behavior: What actually happens.
• Impact Analysis: Potential consequences.
• Recommendations: Suggested fixes or mitigations.

Team Submissions Explained

Team Attribution

• Team Lead Submits: The team lead typically submits reports on behalf of the team
• Member Credits: Multiple team members can be credited on submissions
• Team Points: Points are distributed to the team, not individuals
• Per-Program Tracking: Team points are tracked per program
• Team Reputation: Successful submissions build the team's overall reputation

Understanding Team Contributions

• View which team members contributed to each finding
• See team coordination notes and internal collaboration
• Understand the collaborative nature of team-based testing
• Recognize that multiple perspectives strengthen findings

Responding to Reports

For Valid Issues

• Accept the report and acknowledge the team's work
• Thank the team lead and credited team members
• Award team points (distributed across the team)
• Create a plan to fix the issue
• Update the team lead on your progress
• Consider feedback on team collaboration quality

For Invalid Issues

• Reject the report with a clear explanation to the team lead
• Provide specific reasons why it's not valid
• Suggest how the team could improve their approach
• Maintain professional communication
• Offer constructive feedback for future submissions

Managing Mitigation

• Track remediation progress.
• Document actions taken.
• Update risk assessments.
• Notify relevant stakeholders.
• Schedule follow-up reviews.

Best Practices

• Respond to reports within 48 hours.
• Be specific in your feedback.
• Maintain detailed records of all actions.
• Communicate regularly with team leads through Messages.
• Provide feedback on team collaboration and deliverables.
• Build long-term relationships with high-performing teams.
• Learn from each report to improve your systems.