Administrative Support
Calendar Management for roofing contractors
Four people can move the same block and none of them will know the other three did. A calendar has no way to object.
The week you actually get
A week that will actually happen. Every commitment on it was confirmed with the person who has to keep it, rather than entered on the assumption that they saw the invitation. Every fixed point — the dates that belong to an inspector, a supplier or a homeowner and are not yours to move — is marked as fixed rather than sitting there looking like everything else.
And when something moves, which it will, the move happens in one place and everybody it touches hears about it, including the people outside your company. That last part is the one that goes wrong quietly, because a person who was not told is not complaining yet.
Everybody can write and nothing can object
A calendar looks like a record and behaves like a shared document that several people edit at once without a track-changes feature. That is the whole difficulty, and it is a property of the artifact rather than of the people using it.
Consider what happens when somebody drags a meeting an hour later to make room for a site visit. The tool accepts it instantly. It does not ask whether the original time had been agreed with anybody. It does not know that a homeowner was told that time on the phone last week, or that the block being covered was left deliberately empty because a delivery is due. It has no concept of a commitment being harder or softer than another. Every entry is a rectangle, and rectangles all move the same way.
So the calendar drifts away from reality through a series of individually sensible edits, and — this is the part that makes it expensive — it drifts silently. A wrong ledger eventually fails to reconcile. A wrong estimate eventually meets a roof. A wrong calendar keeps displaying with total confidence right up until somebody is standing outside a house at a time nobody expected them.
What fixes it is not a better tool. It is that somebody is accountable for the difference between what the calendar says and what is true, that changes go through one place rather than being made by whoever noticed the problem, and that a commitment made to somebody outside the company is treated as a different kind of thing from a block of your own time.
What makes a week hold together
Entries have to say who agreed to them. An entry recording only a time and a title cannot be defended when it collides with something, because nobody can tell whether it represents a promise or an intention. An entry that names the person on the other end, and records that they confirmed, is a fact with a weight attached — and weights are what let a conflict be resolved rather than merely noticed.
Moving something is a two-part act. The change and the telling are one operation, not a change followed by an intention to tell. Almost every calendar failure worth caring about is a completed first half and an abandoned second, and it is abandoned because it happens after the urgent thing was solved and the pressure came off.
Fixed points have to look different from soft ones. In this trade a surprising amount of the week belongs to somebody else — an inspection window, a crane, a delivery, a permit office’s opening hours. Those cannot be moved, only missed, and a calendar that renders them identically to an internal catch-up invites exactly the sensible-looking edit that breaks the week.
Last, and the one people resist: the calendar has to be the same object for everybody. Two views of the week that are mostly the same are worse than one view that is inconvenient, because the disagreements between them are invisible and are discovered by the person least able to do anything about it, usually while standing on somebody’s driveway.
Three scheduling desks this is not
Calendar work is one desk inside Administrative Support, and the limits that govern the whole department are set out there rather than repeated here. Scheduling crews against work, sequencing the stages of a job, and agreeing a time with a homeowner are three separate functions handled elsewhere in the back office; this page is about the shared artifact all three of them write to.
What owners ask about a shared week
Whose calendar are we talking about?
The company’s commitments in time, wherever they are kept — an owner’s day, a shared office calendar, the meetings and site visits and inspection windows that several people need to see. The distinctive property is that more than one person can write to it. A calendar only one person ever touches has a different and much smaller set of problems.
Is this the same as booking appointments with homeowners?
No, and the difference is worth being precise about because the vocabulary overlaps. Booking a homeowner is a negotiation between two parties about one time, and it is handled elsewhere. This is what happens to that agreement afterwards, once it is an entry that four people can move and nobody owns. The booking is a conversation; the calendar is an object.
What actually goes wrong most often?
A silent overwrite. Somebody moves a meeting to make room for something urgent, entirely reasonably, and the person who originally arranged it finds out when the other party turns up or does not. Nothing warned anybody, because nothing was watching. The damage is rarely the clash itself — it is that a commitment was made to somebody outside the company and then quietly changed without them being told.
We use shared calendars already. Is that not enough?
Shared is what creates the problem rather than what solves it. Sharing gives more people the ability to write; it does not give the calendar the ability to notice that two of those writes contradict each other, or that one of them broke a promise made to somebody who is not in your company. Visibility is necessary and it is not sufficient.
Do you decide what gets cancelled when two things collide?
No. Ranking two genuine commitments against each other is a commercial judgement about your business and it stays with you. What the desk does is make sure the collision is seen before it is felt, that the trade-off arrives with the information needed to make it, and that whatever you decide actually reaches everybody the change touches — including the people outside the company, who are the ones most likely to be forgotten.
How far ahead does this usefully work?
Far enough that inspection windows, supplier dates and anything with somebody else’s clock on it are visible before they become urgent, which in this trade is the part that pays. Weather makes the near term genuinely unpredictable and there is no administrative fix for that. What is fixable is that the fixed points — the dates that are not yours to move — never get overwritten by the moveable ones.
A week is not a filing
Where a page on this site argues from a published rule, it links to the rule. There is no rule to link to here, and saying so plainly is more useful than reaching for an adjacent one. A calendar is an internal artifact. Nothing published governs how a contractor arranges their own week, and a page implying otherwise would be reaching.
What it is held to instead: Every commitment on the calendar was agreed by the person who has to keep it, and the calendar matches what is actually happening.
Open this week and ask who confirmed each thing
If the answer for most entries is that somebody put it there and assumed, the calendar is a set of intentions being displayed as commitments.