Decide
Score delivery risk
Upload your tickets and get a delivery risk score for every initiative.
Last updated 2026-11-14
What does this tutorial cover?
Risk Radar tells you which initiatives are likely to slip, using only the ticket export you already have. You drop in a CSV from Jira, Linear or a spreadsheet, and Specky groups the tickets into initiatives (epics, or sprints when there are no epics) and gives each one a delivery risk score from 0 to 100.
In the video the upload screen offers a second way in: Try with sample data loads made-up initiatives, so you can see a result before touching your own data. The results lead with an overall risk score, counts of at-risk and on-track initiatives, and a Systemic Risks box for patterns that repeat across initiatives, such as late delivery or scope creep. Click any initiative to see the factors behind its score, each with a short sentence explaining why.
The scores come from fixed rules, not from the AI, so the same file always gives the same result. The rules look at scope changes, estimation drift, dependencies, overdue work, overloaded assignees and tickets left open too long. The AI only steps in when you ask for an executive summary, a one-page write-up you can copy and send to leadership.
How do you do it, step by step?
- Open Risk radar from the sidebar, or search for Risks with ⌘K.
- Drop your CSV on the upload area, or click Try with sample data.
- Read Overall Risk and the Systemic Risks box.
- Click an initiative to see what drives its score.
- Click Exec Summary to get a short write-up for leadership.
Transcript
Drop in a Jira, Linear or spreadsheet export, or try it with sample data first. You get an overall risk score and the patterns across initiatives, like late delivery. Scoring follows fixed rules. The AI only writes the optional summary for your execs.
Read more
- Risk Radar · Upload a ticket export and get a delivery risk score for every initiative.