Every onboarding wave, one calendar.

Build the program once, then run it for every wave on one calendar.

Forty people start Monday, in three countries.

The sessions live in five calendars, two hosts are on leave that week, and the four who start late fall through the cracks.

Plan a month of onboarding in one conversation

Plan October: 120 hires across 6 offices. Group them into cohorts, schedule orientation, and start each role's ramp-up.

Claude

Every onboarding in flight, on one plan

  • The program is the template

    A weekly grid of events with day, time, duration, instructor, and location, and no maximum length.

  • Each cohort is a scheduled run

    Set a start date, and every session date is calculated from the program.

  • Run many cohorts from one program

    Every wave runs from the same template, each with its own dates.

  • Switch between calendar and list views

    Drag a session to reschedule it, or view the cohort as a list.

  • Track RSVPs and attendance

    Each attendee RSVPs to every session, and attendance is recorded for each one.

  • Edit the program once

    Change an event in the program, and every session generated from it updates too.

One shared week, then a ramp for each role

The cohort is the unit of planning, never the unit of experience.

  • Share the first week

    The cohort shares the company orientation and the live sessions of its week.

  • Then ramp up by role

    After the week, each person follows the ramp assigned for their role.

  • Track progress per person

    You plan the wave once and still track each hire's progress individually.

Company & Department-Wide OrientationsRole-Based Ramp-Up

Every wave from the same program, adjusted in minutes

  • Add a day

    Use the + button to add a day when a cohort's week needs one more.

  • Set instructors and rooms once

    Set them per event in the program, and every cohort inherits them.

  • Add late starters

    Add attendees when the cohort is created, or later, when someone starts late.

  • Invite external guests

    Send calendar invitations, with no Juno account needed.

Read the wave before you run the next one

  • Compare cohorts

    Every cohort's milestones, side by side on one plan.

  • Break down by office

    The same milestones broken down by office, inside each cohort.

  • Spot offices falling behind

    See which office is falling behind before the next wave starts.

  • Decide what changes

    You decide what changes for the next wave. Nothing moves on its own.

Try it

  • Build a 30-60-90 day onboarding journey

    Three phases for one role, a checkpoint quiz per phase, your courses reused.

    The prompt

    Your AI asks you

    The role, what "ramped" looks like at 30/60/90, any existing material, who signs off

    I want a 30-60-90 day onboarding journey in Juno Journey for one role, so new hires ramp on a clear path instead of a pile of links. 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 role and the team 2. What “ramped” looks like at day 30, 60 and 90 3. What material we have outside Juno, if any, and where 4. Who signs off at each milestone Ask these in one message, then wait for my answers. For material outside Juno, check that source is connected in this chat; if not, I’ll connect it or upload files. Don’t invent our processes. Search Juno first and reuse existing courses and quizzes wherever they fit. Then propose the journey: three phases, the courses in each, a checkpoint quiz per phase, and the gaps you’d fill with short new courses. After I approve the outline, build the new pieces and the journey as drafts. Don’t publish, assign or notify anyone until I say so.

  • 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.

  • A learning digest for every manager

    One view per manager: who finished, who's overdue, and one suggested nudge.

    The prompt

    Your AI asks you

    Which managers or teams, which numbers matter, the period, anything from outside Juno

    I want a learning digest for every manager: who on their team finished what, who’s overdue, and one thing to follow up on. 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 managers or departments to include 2. Which numbers matter (completions, overdue, scores, time spent) 3. The period it covers (e.g. the last 7 days) 4. Whether to add anything from outside Juno, and from where Ask these in one message, then wait for my answers. Check anything outside Juno is connected in this chat; if not, I’ll upload an export. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Never fill in numbers you can’t read. Build an interactive artifact: one view per manager with their team’s progress, overdue items and a suggested nudge. State definitions, data gaps and counts. Show me a sample for one manager first. Nothing runs on a schedule; tell me how to refresh it. Don’t send it to anyone or notify learners.

All promptsNew to Juno? See it in a demo

“We had to onboard 100 new hires remotely and connect them directly with their teams' objectives and workflows. Using Juno's onboarding path, we decreased the time and manpower involved by 20% and were able to finalize the process within a month.”
Hili B., HR & OD Expert at Kaltura.Hili B.HR & OD Expert, Kaltura
“Setting up integrations like HRIS and SSO is straightforward, which saves a lot of manual work.”

300+ learning programs, reaching up to 5,500 employees per course

Alexander D.Product Owner, Raiffeisen BankG2

Onboarding a new customer account or a new partner works the same way.

Frequently asked questions

How do we onboard people who start on different dates?

Run one cohort per start date from the same program. Someone who starts late joins a cohort after it is created, or the next wave's, and still gets the ramp for their role.

How do we onboard many hires at once across countries?

Build the program once and create a cohort for each wave. Every cohort is on one calendar, with progress per cohort and per office.

What is the difference between a program and a cohort?

A program is the template week. A cohort is one scheduled run of it, with its own start date and attendees.

Can we change the plan once a cohort is scheduled?

Yes. Drag a session to move it, add a day or attendees, and edits to the program carry into the next wave.

Can external speakers or guests join onboarding sessions?

Yes. Guests get calendar invitations and need no Juno account, and attendance is recorded per session.

How do we track progress across onboarding cohorts?

Against each cohort's milestones, per cohort and per office, so you see which office is behind before the next wave starts.

Does Juno replace our HRIS for onboarding?

No. Your HRIS, such as Workday, remains the source of start dates, offices, and roles, and people sync into Juno from it. Your LLM reads the plan you request and works in Juno, which groups the hires into cohorts, schedules the sessions, and prepares each role's ramp. Nothing reaches anyone before you approve the plan.