How to coordinate timetables with your friend group

The core problem is combinatorial. Even with two people, the number of possible schedule combinations gets large fast. Four subjects each with three or four class options means hundreds of combinations per person before you start looking for overlap.

Multiply that by three or four friends, all with different subjects and constraints, and you are looking at thousands of possible group combinations. No amount of good intentions in a group chat can manually evaluate those combinations. What ends up happening instead is a negotiation that optimises for whoever speaks loudest rather than for the actual best group outcome.

The other problem is iteration. One person changes a tutorial - reasonable enough on its own - and the group schedule that took an hour to agree on needs to be rebuilt from scratch. This happens multiple times before the semester even starts.

Beyond the raw combinatorial size, group scheduling is hard because everyone's constraints interact in non-obvious ways. Person A's preference for no early starts means they want 10am at the earliest. Person B works Wednesday afternoons. Person C has a compulsory lab that only runs on Tuesday mornings. Finding a configuration that respects all three simultaneously - while also maximising shared lunch windows - is not something you can eyeball from a shared Google spreadsheet.

The constraints also compound across subjects. What works for subject overlap between two people might break the third person's individual timetable. Optimising the group result requires evaluating all subjects and all constraints for all people simultaneously. That is exactly the kind of computation that tools handle better than humans.

Doing that manually with a shared spreadsheet works until someone changes a class, at which point the whole thing needs to be rebuilt. With four or five friends, it's effectively impossible without tooling.

SmoovSync is Smoov's group coordination feature. The flow is straightforward:

The results rank group schedule combinations by how well they maximise shared free time - including shared lunch windows, matching days off, and overlapping free blocks suitable for group study.

The group matcher scores combinations across five dimensions: shared free blocks, shared lunch windows, matching campus days, shared days off, and shared class times. This gives you a nuanced ranking rather than a single pass/fail. A combination that scores well on shared lunches but not on study blocks looks different from one that does the opposite - and you can choose based on what your group actually values.

Upload more options.Each person can upload up to four schedule options. The group matcher works across all of them - so if someone only uploads one option, there's less for the matcher to work with. Encourage everyone to generate and upload at least three options before syncing.

Think about location.A shared Tuesday lunch is useful if you all live nearby. If two people commute from opposite ends of the city, a shared 12pm slot might not translate into actual time together. Factor in whether the shared blocks are usable for your group's actual geography.

Decide on priorities before you sync.Does your group care most about shared lunch breaks, shared study days, or maximising each person's individual schedule quality? Having that conversation before you look at results means you are choosing between real options rather than debating values in the moment.

Not everyone in a friend group is doing the same number of subjects or the same workload. Some people might be taking five subjects; others might be down to three in their final semester. That imbalance affects what overlap is even possible.

The person with the heavier load has fewer flexible class options - they are constrained by more compulsory activities. The person with lighter load has more flexibility to adjust. In practice, that means the person with more subjects should set their individual timetable first and treat it as the anchor, with the people who have more flexibility adjusting around them.

For groups across different degrees or different universities, shared time is typically about lunch and study blocks rather than shared classes. Focus the sync on those goals rather than trying to manufacture class overlap that genuinely does not exist.

SmoovSync finds the best overlap across the schedules you give it - it can't force everyone into the same class groups if you're at different universities or enrolled in different subjects.

This is the correct order of operations for groups that want to share specific classes as well as free time: agree on the shared classes first, lock them in each person's individual timetable, then sync to find the best group configuration for the remaining flexible choices.

Stop trying to coordinate timetables in a group chat. The combinatorial problem is too large for back-and-forth messages to solve well, and the result is always a compromise that nobody is fully happy with rather than an actual optimum.

The better approach is to have everyone build their best individual schedule first, then pool those schedules into a sync session. Five minutes of matcher output replaces days of group negotiation and produces a measurably better result. If you want to try it, start by building your own timetable in Smoov and then create a sync room when you're ready.