The Signal #3: The risk was mentioned three weeks ago. It's not in the register.
The Signal
Every project has risks hiding in plain sight. They’re in the Slack thread where someone said “might not make it.” They’re in the Jira board where three tasks have been overdue for two sprints. They’re in the meeting notes where a vendor concern was mentioned once, nodded at, and never registered.
By the time that risk makes it into the register - if it ever does - it’s usually because something has already gone wrong. And by then it’s not a risk. It’s an issue. You’ve missed the window where early detection would have mattered.
The failure isn’t risk awareness. It’s risk currency. Your register is stale because updating it requires scanning four different tools, classifying what you find, scoring it against what’s already tracked, and formatting it into a row. That’s an hour of admin - every week - and it never wins the priority battle against things that are already on fire.
The Noise
“We’ll add it to the risk register when it becomes a real issue.”
By then you’ve already lost. The entire point of a risk register is early detection - catching the signal before it becomes a problem. If you only register risks after they materialise, you’re running an issues log with extra steps.
The Tool
Here’s the starter prompt. Paste your Jira exports, Slack threads, meeting notes, or email chains in at the bottom. Run it in ChatGPT, Claude, or Gemini.
You are a Senior Risk Analyst. Scan this project data and identify
every risk signal - including ones buried in casual language,
complaints, and passing comments.
For each risk, produce a row in this table:
Risk ID | Description | Category | Probability | Impact | Severity |
Owner | Mitigation (if stated) | Source | Confidence
Categories: Schedule / Budget / Resource / Technical / External /
Stakeholder / Scope
Rules:
- Capture risks even if the language was casual or optimistic
- If no owner stated: [UNOWNED - PM to assign]
- If no mitigation stated: [NO MITIGATION - PM action required]
- Confidence: HIGH / MEDIUM / LOW
PROJECT DATA:
[Paste your data here]You’ll get a table. Some cells will say [UNOWNED] or [NO MITIGATION]. That’s not a failure - that’s the prompt telling you which gaps need closing before Friday.
The Full Toolkit
That prompt is one of five. The complete free pack covers:
- Risk Spotter - scan any project data for risk signals
- Impact Scorer - structured probability × impact assessment
- Mitigation Generator - 4 T’s framework response options
- Risk-to-Issue Escalator - flag materialised risks
- Risk Register Summary Email - stakeholder-ready summary
>> Get all 5 free → projectorpm.xyz/risk-register-processor
P.S. For PMs running weekly risk reviews: the paid version adds a skill and workflow file that run in Claude, ChatGPT, or Gemini - drop in your Jira, Slack, and email exports and your risk register updates are staged for review in one pass. That’s the direction this is heading.
The Signal is a no-filler newsletter by ProjectorPM. One practical AI insight for project managers, as often as there’s something worth saying. Unsubscribe any time.
Yes, AI helped me to write this :)