Creating a report

Use this page to get a shareable analysis across one or many runs, without writing the scripts or the write-up yourself.

Your report automations can write a report on each new mission. You can also ask the agent for a custom report, one that pulls from many missions, focuses on one topic, or answers a question specific to your team.

Starting a report

Example prompts

• "Create a report summarising performance across my last 10 missions"
• "Compare battery drain rates between firmware v2.2 and v2.3"
• "Analyse all campus survey missions for anomalies"
• "Build a cross-device comparison for missions from this week"
• "The field team says AUV-03 aborted its dive around 14:32. Write a report on what happened and whether we've seen it before"

What reports can contain

Custom reports can include a mix of:

• Narrative analysis: written explanation of the findings
• Charts: interactive line, bar, or scatter plots
• Maps: geographic views with mission paths
• 3D trajectories: for missions with 3D position data
• Metrics: key stats with trends (up/down/neutral)
• Timelines: chronological event sequences
• Images: images from your mission data
• Replay links: open Replay at the moment that backs a finding
• Downloadable files: CSV exports or processed data

Refining your report

After the agent writes a report, iterate through conversation:

• "Add a section comparing latency across devices"
• "Focus more on the GPS signal loss events"
• "Include a chart showing altitude over time"
• "Remove the battery section and expand on navigation"

Go back and forth as many times as you need. The report updates with each request, and Version history keeps the earlier versions.

Recurring reports

To get a report on each new mission or on a schedule, set up a recurring report. See Recurring reports for the steps, or ask the agent: "Every Monday at 9am, summarise last week's missions."

Alloy writes the report automatically and adds it to your Reports page.