Apple Calendar week view: make it show your real week

Week view is where most calendar work happens. Month view is for orientation and Day view is for a single busy stretch, but the week is the unit people actually plan in, and it is the screen that stays open. It is also the view that arrives with defaults nobody chose and that most people never adjust.

Two complaints turn up again and again. One is that the week looks crushed, with events squeezed into a band too narrow to read. The other is the opposite: acres of empty grid at hours when nothing ever happens, pushing the real day off the bottom of the screen. Both come from the same place, and both are settings rather than limitations.

What the week grid is actually drawing

The week view has three independent dimensions, and confusing them is why adjustments feel like guesswork.

The horizontal axis is a count of days. It is either seven days or five, Monday through Friday, and that choice also affects what a swipe or an arrow key moves past.

The vertical axis is a band of hours. It is not the whole day. The grid shows a window of hours, and everything outside that window exists but requires scrolling. This is the dimension responsible for both the crushed and the empty complaint, because a wide window squeezes each hour and a narrow one hides half the day.

The third dimension is the strip above the grid, where all day and multi-day events live. It has its own height and its own scrolling behaviour, and it is the part of the week most likely to be hiding something.

Apple states the adjustable range plainly:

You can customize Week view to show all 7 days of the week or just Monday through Friday. You can customize Day and Week views so that the Calendar window shows from 6 to 24 hours of events per day, and you can mark when your day starts and ends. Source: support.apple.com

All three live in the same place: Calendar, then Settings, then General.

The four settings that shape the week

Setting	What it changes	When to change it
Days per week	Seven days or Monday to Friday	Weekend work never appears, or weekends are wasted columns
Start week on	Which day sits in the leftmost column	Planning conversations start on Monday
Show hours at a time	How many hours fill the window, from 6 to 24	Events look crushed, or empty hours dominate
Day starts at and Day ends at	Which hours are marked as working hours	The shaded band does not match reality

The one people reach for first is days per week, and it is usually the wrong first move. Dropping to five days makes each column wider and the week easier to read, and it also removes the ability to see a Saturday commitment sitting next to Friday. For anyone whose work spills into weekends, the wider columns are bought at the cost of the exact information that matters most on a Friday afternoon.

The setting worth changing first is the hour window. A default that shows a large slice of the day gives every hour so little height that a thirty minute meeting becomes a sliver with no readable title. Narrowing the window to roughly the span of an actual working day makes each event tall enough to read at a glance, and scrolling reaches the rest.

Why the week looks crushed, and why it looks empty

These are the same problem seen from two sides, and the fix is a pair of settings used together rather than either one alone.

The hour window controls density. The day start and day end markers control where the window sits and which hours are shaded as working time. Setting the window without setting the markers produces a grid that is legible but centred on the wrong part of the day, so a morning person spends every day scrolling up.

A worked example makes the relationship clear. Someone whose meetings run between 9 a.m. and 7 p.m. has a ten hour working span. Setting the window near that span, and the markers to match, produces a week where the whole working day is visible without scrolling and every event is tall enough to read. Widening the window to the full 24 hours halves the height of each event to display hours in which nothing is ever scheduled.

One habit is worth building alongside those settings. The week grid rewards being read at a fixed moment rather than glanced at all day. Opening it once on a Friday afternoon, with the hour window set to a working day and the whole week visible without scrolling, is enough to spot the two or three collisions that would otherwise surface on Tuesday morning. The settings exist to make that single reading reliable, which is a different goal from making the calendar pleasant to look at while other work is happening.

There is a second cause of the crushed impression that no setting fixes. When several events overlap, the app divides the column width between them, so three overlapping meetings each get a third of a day's width. That is information, not a display fault. A column that keeps splitting is showing double booking, and the answer is in the schedule rather than the settings.

The 12 or 24 hour question is not in Calendar

Searching Calendar's settings for a way to switch between 3 p.m. and 15:00 produces nothing, which sends a lot of people to the internet convinced the option was removed. It was never there. Time format follows the system, in Language and Region settings, and Apple points to that pane rather than to any calendar preference.

This matters more than a formatting preference normally would, because the 24 hour clock changes how a week reads. Times without an a.m. or p.m. suffix are shorter, which leaves more room for the event title in a narrow column, and evening events stop being ambiguous at a glance. On a dense week grid, that is a legibility change rather than a cosmetic one.

Week numbers, and starting the week on Monday

Two settings serve people whose organisations plan in weeks rather than dates.

The first is the start of the week, in General, which moves the leftmost column. This is not only a cultural preference. A week that starts on Monday puts the two weekend days together on the right, which makes a working week read as one block instead of two fragments split by a Sunday column.

The second is week number display, which lives in Advanced rather than General. Turning it on adds the week number to the view, which is the difference between translating "week 34" into dates by hand and simply reading it. In any team that schedules by week number, this single checkbox removes a recurring translation step.

Advanced also holds time zone support. Switching it on adds a time zone menu next to the search field, so a week can be viewed in the destination's time before a trip rather than after arriving. Events created while a different zone is selected keep that zone, and events can also be set to Floating so they stay at the same clock time wherever the viewer is.

The strip at the top is where the week hides things

The band above the grid holds all day events, multi-day events, and any scheduled reminders set as all day. It grows to fit a few items and then scrolls, which is where the trouble starts.

A week containing a conference, a holiday, a shipping deadline, and a birthday can have all of them stacked in that strip with only the first two visible. Nothing indicates that the rest are there. This is the most common way a week view is confidently misread, and it is worth deliberately scrolling that band at the start of any week that feels suspiciously empty.

There is a second reason to watch that strip. Multi-day events are drawn as a bar spanning several columns, which is the clearest way to show a trip or a conference, and it is also the reason a single item can consume the width of the whole week. When two of those overlap, the strip grows again, and the grid below gets pushed down. A week can therefore lose vertical space to the strip without anything changing in the schedule itself, which reads as the calendar becoming cramped for no reason.

The related setting is the Holidays calendar, which can be switched off in General. A holiday calendar for a country nobody in the household lives in adds an all day item to the top strip most weeks, competing for the same space with items that matter.

What the week grid cannot show

Three things are invisible in week view no matter how it is configured, and each one is a common cause of a week that looked fine and did not work.

The first is travel. Two meetings in different places show as two blocks with a gap between them, and the grid says nothing about whether the gap is enough. Travel time can be attached to an event, and the Travel time page covers what that does and where it stops working, but a plain week view will not warn anyone.

The second is other people's time. Free and busy information exists on the server, not in the grid. Seeing it requires the availability panel while inviting someone, which is a different surface from the week.

The third is intent. A block of focused work and a block that is genuinely free look identical to everyone else, and to the calendar itself. Nothing in the week view distinguishes a protected hour from an empty one, which is why blocks marked for deep work get booked over by colleagues acting in good faith.

Making the week match the week you have

The pattern behind all of this is that the default week view is drawn for an average that does not exist. Adjusting the four settings takes about two minutes and produces a grid shaped like the actual working day, which changes how much can be judged at a glance without scrolling or clicking.

What remains after that adjustment is the harder part, and it is the same for every calendar: the grid records decisions but does not help make them. Deciding what a week can hold, and getting a new commitment into the right slot quickly, sits outside the view settings entirely. The Features page describes what a calendar looks like when it is built for that second job rather than only the first.

What to change first

Open Calendar settings, set the hour window to roughly the length of a working day, and set the day start and end markers to match. Then scroll the all day strip at the top before trusting any week that looks light, and if the remaining friction is getting events in rather than reading them, Caltimate is aimed at that part.