Assign harassment training to everyone who needs it: the right variant per state, supervisors included.
Example data
Juno assigns the right version to each person automatically, catches every new hire and every promotion, and shows you who is done before the deadline.

Harassment prevention
Matched by the rule after her promotion: the supervisor variant, New York.
Steps: 0 of 3Due: Apr 27
Example data
Tracking who needs which version in a spreadsheet is how people get missed, and how risk builds up.
How it works
1Trigger & Signal
2Knowledge Design
Your LLM + Juno MCP
3Delivery & Adoption
4Measure
Current against their own rule, and what they would do three weeks laterAssign harassment training to everyone who needs it: the right variant per state, supervisors included.
Example data
MonMar 9
TueMar 10
Matched by the rule
WedMar 11
Supervisor status · HR · Wed 10:15
MonApr 20
Reminder
FriApr 24
Completed
MonApr 27· Due
MonMay 18
Three weeks later
Example data
As of September 2026, the states that mandate this training set different audiences, variants, deadlines and frequencies. Which apply to you is a question for your counsel.
JunoAssign the supervisor variant to every people manager in New York, due relative to assignment
86 would be assigned. Here's the rule, ready when you are.
Harassment prevention · Supervisors
It'll be created paused.
Example data
Role, position, department, location, group and employee type decide who is bound.
A hire, a promotion or a move re-runs the rule for that person.
See who the rule would assign before anything goes out.
Set relative to the assignment, so every joiner gets their own clock.
SCORM, xAPI and LTI modules run as they are, variants included.
Employees, supervisors and each state's version, assigned by the same rule.
All Users who have finished Harassment preventionmust retake this training every 2 years, before it lapses.
If a person has not completedtheir training 2 daysafter their due date, send them a nudge.
Example data
Your team defines each certification, and a rule awards it.
After a checkpoint, at the end of a journey, by attendance, or by hand.
Every certification carries its own validity, and the date it lapses.
The course comes back on its schedule, with no one rebuilding the list.
Seven days before, one day before and two days overdue, then a nudge.
Where a code of conduct asks for a name, the learner signs inside it.
When the rule itself changes: Roll Out Policy Updates
Completion is what the tooling could count. It was never what the obligation was for.
The EEOC Select Task Force co-chairs, June 2016: “Too much of the effort and training to prevent workplace harassment over the last 30 years has been ineffective.”
Scenario check
Sent May 18, three weeks after the due date
A member of your team tells you a colleague keeps commenting on her appearance. What do you do today?
Thank her, write down what she said, tell her it will not stay with me, and report it to HR today, not after I speak to the colleague.
By department
Example data
A question lands three weeks after the course, about a real situation.
People write what they would do, not which box to tick.
Manually, by the AI, or the AI suggests and your validator confirms.
See where the standard landed and where the course needs another pass.
The conversation after a report is a manager's: Manager Development
You've completed Harassment prevention v3
Example data
Slice the record to one state, one variant, one date range.
Each row keeps the published version the learner took.
Certificate or signature, recorded per learner and activity.
A CSV of the view, as filtered, runs in the background.
Every obligation, in one picture: Compliance
A short course, a 5-question check and an acknowledgment, with a clear list of who's done.
Your AI asks you
The policy document, who must complete it, the deadline, acknowledgment or quiz
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. 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.
Teams down the side, topics across the top, so the gaps show up before the deadline does.
Your AI asks you
Which groups and topics, which courses count, what "done" means, the date range
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. 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.
Claude groups the questions people keep asking and answers each one in plain words.
Your AI asks you
Where the questions show up, which time range, who it's for, who confirms answers
I want to turn the questions people keep asking into a short FAQ lesson in Juno Journey, so answers are easy to find. 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. Where the questions show up (a chat tool, a helpdesk, email, a forum) 2. Which time range 3. Who asks them, and who the lesson is for 4. Who should confirm the answers Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste/upload an export. Only use questions you actually find, and count how often each comes up. Search Juno first: if a course already answers a question, link to it instead of rewriting it. Show me the top questions with draft answers, each with its source, and mark “needs expert check” where unsure. After I approve, build the FAQ lesson with a 3-question check as a draft. Don’t publish, assign or notify anyone until I say so.
“Smooth, structured, and highly effective… the process felt completely under control from start to finish.”
Trained thousands on key topics including compliance (5,200), information security (4,885), financial monitoring (~5,400) and personal safety (5,981).