
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.
- For
- HRLegal / IT
- Routine
- Every policy change
- Setup
- Juno + 2 tools
- You approve
- every draft
What you get
Example dataAll ActivitiesCompliance 2026 by department+ Create ViewGroup by Department
Compliance 2026 by departmentUsersUnits
DepartmentUsersOverdue usersCompletion rate (of assigned)
Sales423Users 42 · Overdue users 388%
HR120Users 12 · Overdue users 0100%
Product361Users 36 · Overdue users 194%
Marketing184Users 18 · Overdue users 471%
Customer Success242Users 24 · Overdue users 283%
Finance90Users 9 · Overdue users 0100%
PolicySecurity 2026
Security 2026
by Northstar
Course
Updated September 1, 2026
Average score86%
Avg time to complete18 min
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
Works in Claude, ChatGPT, Copilot
I want to roll out a new policy in Juno Journey with proof that everyone who needs to has read and understood it. 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. The policy document (upload it, or tell me where it lives) 2. Who must complete it (departments, locations, roles) 3. The deadline 4. Acknowledgment, a quiz, or both 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 docs or knowledge base 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. If the document lives in a tool outside Juno, check it’s connected in this chat; if not, I’ll upload it. Stick to what the policy says; don’t add rules. Search Juno for older versions of this policy training and update rather than duplicate. Then plan a short course (what changed, what it means for you, examples), a 5-question check with a pass mark, and an acknowledgment step. Show me that outline, the audience and the due date first, then build as drafts. Don’t publish, assign or notify anyone until I explicitly approve. Routine: after the first run, offer to repeat this for every policy change. 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
- Q1The policy document (upload it, or tell me where it lives)
- Q2Who must complete it (departments, locations, roles)
- Q3The deadline
- Q4Acknowledgment, a quiz, or both
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 policy change. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
- SharePointvia your AI assistant
- Google Drivevia your AI assistant
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Remind the people who have not finished
Drafted reminders for the overdue, sent only when you say so.
Every week
See the compliance gaps before the deadline
Overdue first, by team and topic, ready for the audit.
HLive viewEvery week
Harassment training for every state and role
The right version for each location and role, assigned from HRIS attributes.
HEvery year























