juno journey
Book a demo

Plan every onboarding wave from one calendar.

When hundreds of people start every month, onboarding is a planning problem. Build the program once, as a week of sessions; run it as a cohort for every wave, with real dates, instructors, rooms and attendees, on one calendar.

Book a demo

4.7 / 5G2

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

How it works

1Trigger & Signal

  • Workday / your HRISStart dates, offices, roles

2Knowledge Design

Your LLM + Juno MCP

  • Runs the onboarding program as a cohort for the wave
  • Dates every session
  • Adds the attendees
You approve the plan

3Delivery & Adoption

  • The new hires
  • The instructors
  • External guestsCalendar invites, no account needed

4Measure

Every cohort's progress, on one plan

Plan a month of onboarding in one conversation

Plan October: 120 hires across 6 offices. Group them into cohorts, schedule orientation, start each ramp.

Claude

Every onboarding in flight, on one plan

  • The program is the template

    A week grid of events: day, time, duration, instructor and location. No maximum length.

  • The cohort is the run

    A start date, and every session date calculated from the program.

  • Many cohorts, one program

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

  • Calendar and list views

    Drag a session to adjust it, or read the cohort as a list.

  • Attendees and RSVP

    Each attendee answers per session, and attendance is kept for each one.

  • Edit the program once

    Change an event in the program and the sessions it generates inherit it.

Same week together, a different ramp each

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

  • The week, together

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

  • Then the role

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

  • Read per person

    You plan the wave once; each hire's progress is still read person by person.

Company & Dpt-Wide OrientationsRole-Based Ramp-Up

Every wave from the same program, adjusted in minutes

  • As many cohorts as waves

    One program runs as a cohort for every start week you plan.

  • Dates calculated

    Set the start date, and every session date follows from the program.

  • Drag to move

    Move a session in the calendar view by dragging it to its new slot.

  • Extend by a day

    Add a day to a cohort with the +, when its week needs one more.

  • Instructor and room

    Set per event in the program, and inherited by every cohort.

  • Late starters

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

  • RSVP and attendance

    Each attendee answers per session, and attendance is kept per session.

  • External guests

    Invited by calendar, with no Juno account needed.

Read the wave before you run the next one

  • Per cohort

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

  • Per office

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

  • The office behind

    The office that is slipping shows before the next wave starts.

  • Your call

    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, and the courses you already have reused where they fit.

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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, 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

    New to Juno? See it in a demo
    The prompt

    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.

    Your AI asks you

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

    New to Juno? See it in a demo
    The prompt

    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.

Every prompt

“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

An account intake and a partner intake are the same operation.

Questions people ask.

How do we onboard people who start on different dates?

Run one cohort per start date from the same program. Each cohort takes its own start date, and Juno calculates its session dates from the program's week. Someone who starts late can be added to a cohort after it is created, or to the next wave's cohort, and still gets the ramp for their role.

How do we onboard many hires at once across countries?

Build the onboarding program once, then create a cohort for each wave. Every cohort carries its own dates, instructors, rooms and attendees, and all of them sit on one calendar, so every onboarding in flight is visible at once. Progress reads per cohort and per office, so the office that is behind shows early.

What is the difference between a program and a cohort?

A program is the template: a week grid of events, each with a day, a time, a duration, an instructor and a location, with no maximum length. A cohort is one scheduled run of it: a start date, session dates calculated from the program, and its own attendees. One program runs as many cohorts as you have waves.

Can we change the plan once a cohort is scheduled?

Yes. In the cohort's calendar view you drag a session to move it, and you extend the cohort by a day with the +. Attendees can be added after the cohort is created. Edit an event in the program and the sessions it generates inherit the change, so the next wave starts from the updated week.

Can external speakers or guests join onboarding sessions?

Yes. External guests are invited to a cohort's sessions by calendar invitation and do not need a Juno account. Your own hosts are set per event in the program as its instructor, together with the room, and every cohort created from that program inherits both. Each attendee answers per session, and attendance is kept per session.

How do we track progress across onboarding cohorts?

Read every cohort against its milestones on one plan, per cohort and per office: orientation done, role ramp started, first check passed. The office that is behind shows before the next wave starts. What changes for the next wave is your decision, and nothing is published, assigned or sent before you approve it.

Does Juno replace our HRIS for onboarding?

No. Your HRIS, such as Workday, stays the source of start dates, offices and roles, and people sync into Juno from it. Your LLM reads the plan you ask for and drives Juno, which groups the hires into cohorts, dates the sessions and prepares each role ramp. Nothing reaches anyone before you approve the plan.