Every policy change, acknowledged.

Juno trains everyone a policy affects and collects each acknowledgment.

Global-eWalkMeCellebriteeToroJFrogGongCintJobber

A new policy is out. Now everyone has to read it.

Emails, reminders, and a spreadsheet of who signed: every policy change turns into weeks of chasing.

Tuesday, 4 pm: the new version, rolled out in one conversation

Legal published data retention policy v3. Roll it out to everyone it applies to, with a check and an acknowledgment.

Claude

See which version each person viewed, next to their score

  • Version Consumed

    Each learner's record names the published version of the course they saw.

  • See it next to the score

    The quiz result and attempts appear on the same row as the version.

  • Record the type of proof

    A signature, a certification, or a pass: the record says which one.

  • Filter, save, export

    Filter to one policy, save the view, and export it as a CSV.

Narrow it to exactly the people the clause applies to

  • Choose who is covered

    Role, department, location, or employee type decides who is covered.

  • Include or exclude contractors

    Contractors are an employee type, so a rule can include or exclude them.

  • Start with a dry run

    A dry run counts the people a rule will reach before anything is sent.

  • Approve the scope

    The compliance owner approves the scope before anyone is assigned.

For the people who join after this rollout: Company & Department-Wide Orientations

Start the rollout from the change itself

  • Your LLM reads the changes

    Your model reads what changed between the two versions of the document.

  • Set the priority

    Each change gets one of three priorities: Mission-critical; Important, not urgent; or Nice to know.

  • Where your policy lives

    Your LLM reaches Confluence, Notion, SharePoint, or your GRC tool.

  • Update the existing course

    Last year's course is updated as a draft, then published as the new version.

Juno acts within your existing Juno permissions, over OAuth, with no API keys.

The same process works for a product release: Release & Product Update

See securitySee Juno in your LLM

No one has to keep a follow-up list

  • Send due-date notifications

    Notifications go out 7 days before, 1 day before, and 2 days after.

  • Nudge and Notify

    Two automation actions that run on rules you set, for anyone who hasn't started.

  • Give managers their own list

    Each manager sees who on their team is overdue.

  • Track certification expiration

    Each certification you create has its own expiration date and reminders.

  • Done means done

    Reminders stop for each person once their work is complete.

From Tuesday to the 30th, on the calendar

  1. Tue4 pm

    Legal publishes v3
  2. Wed

    Scope signed off

    1,412 people

  3. Wed

    Assigned
  4. Day 7

    Reminders sent to those who haven't started
  5. Day 14

    88% acknowledged v3
  6. Day 30

    Day 30

    • Up to date: 1,389
    • Exceptions signed off: 23

Compliance seasons planned in advance

These teams planned their compliance season before it started. Here is how it went, in their words.

“Running our compliance season with Juno was a huge success. With everything planned out in advance from automated assignments and reminders to real-time analytics, we were able to drive 100% completion across the org.”
Rotem W.Senior Global L&D Partner, Cloudinary
“…smooth, structured, and highly effective… over 90% completion across the company, and the process felt completely under control from start to finish.”
Marion D.People Experience Partner, Efficy

Trained thousands on key topics including compliance, information security, financial monitoring and personal safety.

85–98% completion on mandatory programs

76% of employees rated Juno 9 or 10

Raiffeisen Bank case studySeptember 2025

How fast your organization responded

The number to watch is the time from publication until everyone affected is up to date on this version.

Try it

  • Roll out a new policy with proof of completion

    A short course, a 5-question check, and an acknowledgment, with who's done.

    The prompt

    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.

  • A completion heatmap by team and topic

    Teams down the side, topics across the top, gaps visible before the deadline.

    The prompt

    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.

  • Find training that's out of date

    Claude checks your courses against your source of truth and lists what to fix first.

    The prompt

    Your AI asks you

    Where your source of truth lives, which topics matter most, what counts as a recent change

    I want to find training in Juno Journey that no longer matches how things actually work today. 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 our source of truth lives (product docs, release notes, policies) 2. Which topics or courses matter most 3. How recent a change must be to count 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 upload the documents. Only flag drift you can show evidence for. Read the relevant Juno courses, quizzes and journeys, compare each claim to the source, and give me a table: course, what it says, what the source says now, severity, suggested fix. This is a review, not an edit: change nothing yet. Offer to draft updated versions of the top items; after I approve, save them as drafts and don’t publish until I say so.

All promptsNew to Juno? See it in a demo

Your resellers and your customers are bound by documents too

  • PartnersA partner who hasn't re-attested is a risk with a contract attached.
  • CustomersCustomer users acknowledge the new terms before they continue.

Frequently asked questions

How do we roll out a new policy and make sure everyone acknowledged it?

Start from the change. Your LLM reads the new version, finds the people it applies to, and updates last year's training. You approve the scope, and each person acknowledges the version they saw.

Which version of the policy did each employee acknowledge?

Juno records it. Training Analytics' Version Consumed field names the published version each learner saw, on the same record as their score and date. Filter to one policy and export the results.

How do you know employees understood a policy, beyond receiving it?

Add a knowledge check with a real passing score, a number of attempts, and a time limit. The result sits next to the version the person viewed. Time spent measures engagement only.

Do we need policy management software or a learning platform?

They do different jobs. Policy management software holds the official document and its versions. Juno is not your policy repository: it brings the people a policy applies to up to date and records each acknowledgment. Many teams use both.

What counts as a policy acknowledgment: a signature, a certification, or a quiz?

All three, and you choose: a signature within the training, a certification awarded by rule, or a pass on a knowledge check. Your legal counsel decides what your policy requires.

How do we handle a policy that only applies in some countries or to some roles?

Define the scope with criteria: role, position, department, location, group, and employee type. A dry run counts who it reaches first. For a version per state or country, see HR & Workplace Conduct.

Can our LLM read our policy in Confluence or SharePoint and assign the training?

Yes, when your LLM is connected to both: to the policy's tool through its own MCP connection, and to Juno through Juno's MCP server. Juno does not monitor your documents. Your LLM starts the work, and you approve it.

Does an AI decide who has to take compliance training?

No. The system does the work, and people approve it. Publishing, assigning, and notifying each wait for an explicit review, and drafts stay hidden from learners. Our Security page explains how we handle data.