Run performance review cycles from Google Calendar

A review cycle is a calendar problem before it is a people problem. Give an Orkeste agent the cycle dates and the list of managers and reports; it creates the events in Google Calendar or Outlook once HR approves, then posts reminders to managers in Slack before each deadline.

The problem

HR sends the cycle email, then spends three weeks chasing. Deadlines slip and the 1:1s are booked in the last two days.

How the workflow runs

Runs: When you start the cycle, then every week until it closes.

  1. Read the cycle: The agent reads the dates and the people from Airtable, Notion or the run.
  2. Prepare the events: It prepares the self-review deadline, the feedback window and the 1:1s.
  3. Approve: The batch of events waits in Validations for HR.
  4. Create the events: Approved events are created with the right attendees.
  5. Remind: Each week, it posts the upcoming deadlines to the managers' Slack channel.

No event lands in anyone's calendar before HR approves the batch.

Who does what

What this workflow does not do

Works with your stack

Questions about this workflow

Can it see who is late?

Only if you track submissions somewhere it can read, such as an Airtable table. It then names the late reviews in the reminder.

Can it move the 1:1s if someone is away?

No. Agents create events but do not move or delete them. Managers move their own 1:1s.

Does it work with Outlook calendars?

Yes for creating events, through the Microsoft connector. It does not read Outlook calendars.

Related workflows

Keep reading