Google Calendar for time management: deciding what the week holds

Most advice about Google Calendar for time management assumes the problem is that the calendar is not being used enough. For anyone whose week is already full, the opposite is true. The calendar is used constantly, it is accurate about meetings, and it is still a poor description of where the week goes. Colour coding a schedule that is already overbooked does not change what the week holds. Deciding what the week holds, and then making the calendar reflect that decision, is a different piece of work.

A calendar is a record of accepted requests

Google Calendar fills up through invitations. Someone sends a meeting, it lands on the default calendar, and the week gets shorter. Nothing in that flow asks whether the week had room. The result is a calendar that is an accurate record of every request that was accepted and a silent record of everything that was displaced to make space.

This matters because the two things look identical on screen. A Tuesday with five meetings and a Tuesday with five meetings and a report due both render as five coloured blocks. The report is not on the calendar, so as far as the calendar is concerned, Tuesday afternoon was free and giving it away cost nothing.

The practical consequence is that the calendar cannot be consulted for a scheduling decision, because it is missing the side of the ledger that the decision depends on. Anyone who has agreed to a Thursday call while looking at an empty Thursday, and then remembered the deadline, has hit this directly. The fix is not a new view or a new colour. The fix is putting the unbooked work into the same surface as the meetings, so that accepting a request has a visible cost.

That is a decision about what goes in the calendar, not a feature. It is worth making before touching any settings, because every setting below only helps once the calendar contains the whole week rather than the negotiated part of it.

What Google Calendar decides on its own

A few defaults do real damage before any tip list gets involved, and they are worth knowing precisely rather than approximately.

Working hours are not available on every account

Working hours is the setting that tells other people when a meeting request falls outside the day. Google's documentation is explicit about who can use it: working hours and availability are available if the account is through a work or school organisation, the option can be turned off by an administrator, and it can only be turned on from a computer.

You can use working hours and availability if your account is through your work or school organization. If you don't see the working hours or location option, your admin could have turned it off for your organization. Source: support.google.com

For a personal Gmail account, the advice to "set your working hours so people stop booking your evenings" is not advice that can be followed. Any article that presents it as a universal first step was written without checking. On a personal account the equivalent has to be done by hand, by keeping a recurring block over the hours that are not open and letting that block do the refusing.

The default event length shapes the day

New events get a default duration, and that default becomes the unit the week is measured in. A calendar whose default is sixty minutes produces sixty minute conversations, because the person booking accepts whatever the form offers. Changing the default to a shorter length, and using speedy meetings so that events end before the next slot begins, changes the shape of every future request rather than fixing one.

The default calendar collects everything

Events land on the default calendar unless changed at the moment of creation. Over a year that means work, personal appointments and anything subscribed sit in one stream, and the option to hide one of them to read the others disappears. Deciding on the split is cheap. Undoing a year of events on the wrong calendar is not.

The three kinds of time that never get booked

A full calendar usually has three categories of missing time, and they are missing for different reasons.

Travel is the one that breaks the day. A meeting at one address followed by a meeting at another address has a gap between them that exists in the world and not in the calendar. Google Calendar records the location as text. It does not reserve the minutes needed to cross the city, and it does not object when the next event starts the moment the previous one ends. Anyone whose day runs late from the second appointment onward is usually looking at this, not at poor discipline.

Preparation is the one that gets sacrificed. An hour of review before a client meeting is real work with a deadline attached, but it arrives as a personal intention rather than an invitation, so it never becomes a block. When the week tightens, the unbooked hour is the first thing to go, and the meeting happens without it.

Recovery is the one nobody admits to. Four consecutive calls with no gap is not four hours of work. It is four hours of work plus the cost of never writing anything down between them. The follow-up actions from each call accumulate and land somewhere later in the week, unscheduled.

The reason these three stay missing is that putting them in is manual, and manual entry is slow enough that it loses to the alternative of remembering. This is where the entry method stops being a detail. A calendar that takes a whole sentence, including the place and the attendee, in one pass is a calendar where a preparation block costs a few seconds to create. Details of how that kind of entry works are in the Entering events notes. Travel is the same argument in a stronger form, because the number of minutes has to be looked up before it can be blocked, and a calendar that calculates it from the two addresses removes the step that causes the block to be skipped. That approach is described under Travel time.

Reading one week instead of four accounts

Time management advice tends to assume a single calendar. Most working weeks are spread across a work account, a personal account and at least one subscription, and the count of accounts is exactly the number of places a conflict can hide.

Google Calendar can be brought into another application in two distinct ways, and the difference decides whether the result is usable. Signing in with the Google account gives a connection where events can be added and edited from either side. Using the iCal link gives a read-only copy.

With some calendar applications, you can sync your calendar using your Google Account. This means you can add and edit events from either Google Calendar or your other application. Source: support.google.com

The read-only route is the source of a specific and common frustration. A week assembled from iCal links looks complete, so it gets trusted for decisions, and then an event created in the aggregating application never reaches the account that other people are looking at. For anything other than a calendar that is only ever read, the account connection is the one to use.

Deciding the week before other people do

The order of operations decides the outcome. A week that is looked at on Monday morning has already been shaped by whatever arrived over the weekend, and the only remaining moves are defensive. A week that is looked at before the requests arrive can still be shaped.

The practical version of this is short and does not need a system. Before the week starts, list the things that have to be finished in it, and give each one a block at the time it will actually be done rather than the time that happens to be empty. Two or three blocks is enough. The purpose is not to plan the week in detail, because the detail will not survive. The purpose is to make the week's real commitments visible on the surface that other people's requests will be measured against.

What follows from that is the part that pays. When a request arrives for Thursday afternoon and Thursday afternoon already has a block on it, the answer is a decision between two known things instead of a reflex. Some of those decisions will go in favour of the meeting, and that is fine. The difference is that the displaced work is then known to be displaced, and can be moved somewhere rather than quietly lost.

Two habits make this hold up. Put the blocks on a calendar that other people can see as busy, because a private note has no effect on anyone else's scheduling. And keep the blocks honest about length, since a ninety minute task written as a thirty minute block produces a week that looks feasible and is not. Neither habit requires a tool. Both require that adding a block is fast enough to do without hesitating, which is the recurring theme.

Choosing where to spend the effort

The changes available are not equal in cost or in effect, and it helps to see them side by side before committing to any of them.

Change	Effort	What it actually fixes
Colour coding by calendar	Low	Reading a full week faster. Does not change what is in it
Shorter default duration and speedy meetings	Low, once	The length of every future meeting request
Separate work and personal calendars	Low now, high later	The ability to hide one context to read another
Working hours	Low, work and school accounts only	Other people booking outside the day
Blocking travel between locations	Repeated, per event	Days that run late from the second appointment
Blocking preparation and follow-up	Repeated, per event	The gap between meetings held and work done
Moving to a desktop calendar app	One time setup	The cost of every entry, which decides whether blocking happens at all

The pattern in the table is worth naming. The cheap changes are settings, they are made once, and their effect is limited to how the week is displayed or how long meetings default to. The changes that alter what the week holds are the repeated ones, and repeated changes only survive if each instance is fast. That is why entry speed, which sounds like a minor preference, ends up determining whether travel and preparation ever make it into the calendar at all.

A desktop calendar that keeps every connected account in one window is the lever under the repeated work rather than another tip to apply on top of it. The full list of what that kind of application handles is on the Features page, and a straight comparison of the Mac options on price and capability is on the Compared with other calendars page.

What to change first

Pick one thing that is currently invisible and put it in the calendar for the next two weeks. Travel between locations is the usual best choice, because the effect shows up the same day and needs no agreement from anyone else. If the entry cost is what stops that from lasting, a native Mac calendar that takes a plain sentence and calculates the travel block is Caltimate.