Finding Time Suggested slots, the team availability view, and exactly how much anybody can see about your day.

The slowest part of arranging anything internal is finding the hour. Two features exist for it, and they work on the same underlying data.

Suggest a time

Inside the create form, once you have added attendees and chosen a length, a button finds slots where everybody is free.

It reads every attendee's real commitments and yours on the day you have chosen, then walks your hub's working hours in half-hour steps looking for gaps long enough for the meeting you are actually creating.

The result is a short list of real times. Pick one and the form fills in.

It uses your hub's hours

Not nine to five as a universal assumption. Your hub's configured business hours, which is what makes it correct in an organisation working across several places. Where a hub has no hours set, it falls back to 9am to 6pm.

This matters more than it sounds in a distributed team. A suggestion engine that assumes one working day produces confident nonsense for everybody outside it, and people stop using it within a week.

What it can and cannot see

It reads busy or free, and nothing else. Not titles, not attendees, not whether the conflict is a client call or a dental appointment.

That is a firm boundary rather than a current limitation. The query behind this returns time ranges only, and there is no view anywhere in the product, for anybody at any permission level, that turns availability into a window on somebody's day.

The practical consequence is that free-busy is safe to share widely, which is what makes it useful at all.

Where it will find nothing

Two common cases, both worth recognising rather than fighting.

A genuinely full day. The answer is a different day, and the empty result is telling you so rather than failing.

Attendees in very different zones. Two hubs with a small working overlap will produce few slots or none, and the honest answer is that somebody is going to take a call outside their hours. Much better to know that while creating the meeting than to discover it from a decline at eight in the evening.

The team view

Press 5, or pick Team from the view switcher.

It shows your team across one day as availability rather than as events: who is free, who is not, at a glance, in one grid.

Clicking a free slot starts a new event at that time, which makes it a scheduling surface rather than only a reporting one.

What it is for

Finding a slot for a group that is too large for the suggestion list to solve cleanly. Past about five people, the suggestion list starts returning nothing and the grid starts being the better tool, because you can see where the near-misses are.

Deciding whether to interrupt somebody. Not to inspect their day: to see whether right now is a reasonable moment for the thing you were going to send anyway.

Understanding load. A team where one person's row is solid and everybody else's has gaps is a team with a problem, and it is visible here in a way that a list of meetings never makes visible.

What it will not show

The same boundary as everywhere else. Busy is busy. A day reads as occupied blocks, not as a schedule, and no amount of permission changes that.

Responses

Every attendee can accept, decline, or answer tentatively, and their answer shows on the event. Yours shows to them.

Responding is not politeness, it is data. A meeting where nobody has responded is a meeting nobody can plan around, and the declines that arrive an hour beforehand are the reason a simple rule of thumb is worth adopting: answer invitations when you read them, not when you get around to them.

A tentative response is a real answer and an underused one. It says you intend to be there and something might intervene, which is frequently the truth and considerably more useful to the organiser than silence.

Making yourself findable

Two habits do most of the work.

Block focus time as an event. An afternoon you have mentally reserved and not put on the calendar will be booked over, entirely correctly, because nothing said otherwise. Blocked time shows as busy in the suggestion list, in the team grid, and to every colleague who checks before inviting you.

Keep your hub details right. Working hours and time zone drive the suggestions, the working-days grid, the weekend shading and the auto-scheduler in Plan. Wrong hub details make every scheduling tool in the platform quietly wrong for you, and quietly is the problem: nothing errors, the answers are just subtly bad.

Scheduling across hubs

An organisation working from more than one place hits the same three problems, and all three have an answer here.

The overlap is smaller than people think. Two hubs four hours apart have perhaps three shared working hours, and half of those are somebody's lunch. The suggestion list will show you exactly how few slots exist, which is more useful than discovering it through three rounds of declines.

Somebody always pays. When the overlap will not hold a meeting, the honest move is to decide who takes it outside their hours and to rotate that deliberately rather than defaulting to whoever is most junior or most agreeable.

The dual time-zone column is not decoration. Booking a slot that looks like a civilised four in the afternoon to you and half past nine at night to somebody else is the single most common scheduling mistake in a distributed team, and it is entirely preventable by glancing left before saving.

Recurring meetings deserve more thought, not less

A one-off meeting at an awkward time is an inconvenience. A recurring meeting at an awkward time is a standing tax on somebody's evening, and nobody ever revisits it.

Two habits are worth the effort. Set an end date on anything recurring, so it has to be renewed deliberately rather than surviving by inertia. And check the availability of every attendee before making it recurring, not just for the first occurrence, because the person who is free this Tuesday may be permanently busy on the following forty.

When to ignore all of this

For two people who talk constantly, the fastest way to find twenty minutes is still to ask. These tools earn their place at four or more attendees, across hubs, or when you do not know the person well enough to interrupt them.

Using the full apparatus to book a chat with the colleague sitting next to you is the sort of thing that makes people dislike scheduling tools.