The whole team’s day, on one screen, in their own daylight.

Every teammate gets one 24-hour bar, washed with their local time of day (deep indigo at night, cream at midday, rose at dusk), so a single glance tells you who’s awake, who’s working, and who’s asleep. No timezone math. Then Find Times, weighted proposals, and the Review inbox share one green / amber / red vocabulary you learn once.

Built for internal recurring meetings on a distributed team. Keep your booking page for external clients: FairlyRemote™ works alongside it.

Try the sample team →

One bar per teammate, painted with their daylight

This is the screen you live on. Each teammate’s 24 hours run left to right, tinted by the sky where they are: indigo through the night, pale blue at dawn, warm cream at midday, rose at sunset. A live clock and a status pill (Working, Flex, Busy, Sleeping) sit on the right, and the blue bracket marks their working window. Switch Mode to recolour the same bars for Fairness, Availability, or Overlap: same rows, different question.

  • Four view modes: Local times, Fairness, Availability, Overlap, one click apart
  • 180+ cities with automatic DST handling
  • Real calendar events overlay each bar as chips, in everyone’s local time
  • Live clock, working-hour bracket, and a golden ★ where the team overlaps
SAMPLE Sample team. 5 people across 5 timezones. Explore freely, nothing here is yours yet.
Overview Find Times Mode Dashboard REVIEW
2 Avail 1 Flex 1 Busy 1 Sleep Today, Jul 24 9am to 12pm (3/5)
Alex New York · GMT−4 9:00 AM Working
Standup
12a36a9a12p36p9p11
Emma London · GMT+1 2:00 PM Working
Sync
12a36a9a12p36p9p11
Priya Berlin · GMT+2 3:00 PM Busy
Busy
12a36a9a12p36p9p11
Yuki Tokyo · GMT+9 10:00 PM Flex
Review
12a36a9a12p36p9p11
Sam Bangkok · GMT+7 8:00 PM Sleeping
12a36a9a12p36p9p11

The awkward slots rotate automatically

You don’t manage a fairness number; the algorithm keeps it in the background. Each teammate is scored across four dimensions (Accommodation, Flexibility, Social, Rest) that roll up into one slot label: Low / Modest / Neutral / Notable / High impact. Recent meetings count more than old ones, which fade over about a month. That’s what nudges the next Find Times, the next vote, the next booking toward whoever’s due a turn. Deterministic math you can predict and override, never a black box.

  • 30-day half-life decay so recent patterns lead
  • Four dimensions roll up to one team score (0 to 100)
  • Personal, team, and admin views, on the Dashboard when you want them
  • 7d / 30d / 90d / historical ranges available, not required
Dashboard · Fairness · Your view
82 balance

Modest impact this month

Recent meetings stay close to fair across all four dimensions, so nothing needs your attention.

Accommodation
88
Low impact
Flexibility
82
Modest impact
Rest
91
Low impact

Drag a window on the timeline. Get ranked slots.

Arm Find Times and a scan window appears right on the day-cycle bars: drag its handles to set a length, and every hour is scored on availability, sleep disruption, evening intrusion, recent accommodation history, and calendar conflicts. Slots are ranked across the next 14 days and labelled with the same impact vocabulary as the timeline: Low / Modest / Neutral / Notable / High. Golden windows highlight where everyone’s in their working zone. When you like a slot, Create the meeting or Propose it to a vote: both are one tap from the window.

  • Ranked across the next 14 days, not just “next free slot”
  • Same impact labels everywhere: Low / Modest / Neutral / Notable / High
  • Golden ★ windows highlight the best team overlap
  • Calendar-conflict detection from synced calendars (Team+)
Find Times 1h Golden window
Create 1h3/5 free Propose
Alex New York 9:00 AM
12a36a9a12p36p9p11
Emma London 2:00 PM
1h
12a36a9a12p36p9p11
Create 1h3/5 free Propose
1
Tue 14:00 UTC 9am NY · 2pm London · 11pm Tokyo ★ Golden window
4/5 in working hours No one’s asleep Calendars clear Low impact
85
2
Wed 09:00 UTC 4am NY · 9am London · 6pm Tokyo
No one’s asleep NY before working hours Notable impact
70
3
Tue 22:00 UTC 5pm NY · 10pm London · 7am Tokyo
Tokyo flex hours London late evening High impact
50

The team picks. Weights reflect who’s already accommodated.

Hit Propose to post a shortlist; teammates vote with weights between 0.5× and 2× that reflect recent accommodation history, so the people who’ve taken the awkward slots have more say in the next one. Auto-suggest pulls candidates from team overlap windows. Participants can vote by link without an account. The surfaced winner is the team’s call, not the algorithm’s, and it lands in the Review inbox, where one tap creates the meeting.

  • Weighted votes from 0.5× to 2.0× based on recent accommodation
  • Auto-suggest slots from team overlap and impact scores
  • No account needed for participants, share via link
  • Winners flow into Review → create the meeting in one tap
Weekly standup · 5 votes in
Weighted vote · 5 in closes in 3h 25m
10:00 UTC Low impact
8.44 votes
14:00 UTC Modest
5.93 votes
08:00 UTC Notable
3.62 votes
17:00 UTC High
2.11 vote

Ballots count 0.5× to 2× by who’s recently taken the awkward slots. Guests can vote by link, no account needed.

One place for what needs a decision

The Review cluster in the toolbar is the app’s to-do list. Four inboxes, each with its own badge count: Scheduled events awaiting your accept or decline, Proposals waiting on your vote, things you’ve Sent and are tracking, and Incoming, newly synced calendar events that need a privacy check before teammates see them. Accept, decline, tentative, vote, or set visibility, then it clears. Nothing important hides in a feed.

  • Scheduled · Proposals · Sent by me · Incoming, each badged
  • Accept / tentative / decline flows through to everyone in real time
  • Incoming events land here for a privacy check before they’re shared
  • Actioned items move to the Accepted / Declined history, not back to pending
Review · 3 need a decision
Scheduled 1 Proposals 1 Sent Incoming 2
Design review Thu 15:00 UTC · 4/5 in working hours · Low impact
AcceptTentativeDecline
Weekly standup · vote 4 options · closes in 3h 25m · your weight 1.6×
Vote
2 new synced events From Google Calendar · set visibility before teammates see them
Set visibility

Busy Only by default. Title-visible only when you say so.

Imported calendar events wait in your review inbox with Busy Only pre-selected; once you confirm one, teammates see that you’re busy, not what. Per event you can lift visibility to Shared (full detail to your board) or drop to Private (blocks the slot, no metadata). Sync reads free/busy and titles to detect conflicts; on the Busy Only default the title is dropped and only your busy time is stored, and a title is stored only when you raise an event to Shared. Descriptions, attendees, and attachments are never stored: they are discarded as soon as the conflict check is done, and attachments are never requested at all. The privacy audit lets you review and bulk-update visibility in one pass.

  • Synced events are review-first, with Busy Only pre-selected
  • Per-event override: Private / Busy Only / Shared
  • Board admins can lock a default privacy preset for the whole board
  • Privacy audit tool to review and update all events at once
Privacy controls · This event
Private Hidden from the group
Teammates see nothing Private
Busy Only Default for synced events
Teammates see a “busy” block Default
Shared Full details to the group
Teammates see full details Shared

Each board sets the default via its preset: Privacy First, Standard, or Open Team. Under Standard and Open Team any event can override that default, within what the preset allows. Privacy First is locked: every event stays Private.

Your real meetings, in everyone’s daylight. Nothing stored we don’t need.

Hit Connect to link Google Calendar or Microsoft Outlook (Team+) and your real meetings overlay the timeline as chips in every teammate’s local time, so “Tuesday 14:00 UTC” reads as 9am NY, 2pm London, 11pm Tokyo at a glance. Find Times and the scan window factor those conflicts automatically. Sync reads free/busy and titles to spot conflicts; by default we store only your busy time, and a title only if you raise an event to Shared. Descriptions and attendees from your synced calendar are never stored; for imported events the title is the only field we keep, and only when you say so. Proposals and meetings you create inside FairlyRemote are stored, including what you type into them. See the exact scopes →

  • Google Calendar two-way sync · Microsoft Outlook read-only at launch (Team+)
  • Conflict detection across all your synced events
  • ICS feed import for read-only visibility from any provider
  • New synced events land in the Review inbox for a privacy check
Connect · Integrations

Team+ calendar integrations

Google Calendar ⇆ Two-wayConflict detection · Privacy: Busy Only
Connected
Microsoft Outlook → Read-only BetaTwo-way sync coming after GA · Privacy: Private
Connected
ICS feeds → Read-onlyFrom any provider · token expiry 7d / 30d / 90d / never
Manage

Review inbox: new synced events land here for a privacy check before teammates see them.

Separate boards, an availability heatmap, and honest insights

Team boards

One workspace, many boards: Engineering, Customer Success, Leadership each get their own roster, timezone layout, and fairness history. Switch them from the Overview group picker. The standup rotation and the on-call rotation don’t compete for the same score.

Availability heatmap

The Overlap mode surfaces golden hours as a 24×7 heatmap, so you see where everyone overlaps in working hours at a glance, with the same green / amber / red vocabulary as the timeline.

Insights (when you want them)

Meeting distribution, off-hours contribution, and fairness trends over time, on the Dashboard. The ledger keeps these in the background; the page is there when you want to check the system’s nudges against your own read.

See it in action

5 people, 5 timezones, 30 days of meetings already in place. No signup, no card.

Try the sample team →