
See the compliance gaps before the deadline
Overdue first, by team and topic, ready for the audit.
- For
- HRLegal / IT
- Routine
- Every week
- Setup
- Juno + 1 tool
- You approve
- every draft
What you get
Example dataSecurity 2026
by Northstar
Course
Updated September 1, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
I want a completion heatmap: groups down the side, topics across the top, and each cell showing how far along that group is. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. Which groups (departments, roles, locations) 2. Which topics, and which courses count for each 3. What “done” means (completed, passed, above a score) 4. The date range Ask these in one message, then wait for my answers. In that same first message, also ask me my role and the team I support, and which HR system we use. Then check each one is connected in this chat; if not, I'll connect it or upload an export. Never guess what is in it. Pull everything you can from Juno; if you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. If a grouping lives outside Juno (e.g. an HR system, if we use one), check it’s connected in this chat; if not, I’ll upload a CSV. Never guess anyone’s group. Confirm definitions with me, then build an interactive artifact: the heatmap with counts per cell, a click-through to the people in each cell, and the three weakest spots with suggested next steps. State definitions, show sample sizes, and grey out cells too small to judge. Don’t assign or notify anyone. If this assistant supports artifacts connected to Juno, build it as an interactive artifact that re-reads Juno each time I open it, and say so; otherwise build it static and show the date the data was read. Routine: after the first run, offer to repeat this every week. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run.
Your AI asks you
- Q1Which groups (departments, roles, locations)
- Q2Which topics, and which courses count for each
- Q3What “done” means (completed, passed, above a score)
- Q4The date range
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: Every week. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
Live viewLive view: when your assistant supports artifacts connected to Juno, the result is an interactive view that reads Juno again each time you open it.
What it connects
- JunoRequired
- HRISSCIM
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Roll out a policy with proof it landed
A short course, a 5-question check and an acknowledgment, with a clear list of who is done.
Every policy change
Remind the people who have not finished
Drafted reminders for the overdue, sent only when you say so.
Every week
Harassment training for every state and role
The right version for each location and role, assigned from HRIS attributes.
HEvery year























