Deadlines Are Not Shifts
A date by which something must exist is commercial specification; a requirement to be working at set times is scheduling, and most buyers blur the two unawares.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. The heaviest factor in most tests, and the easiest one to give away by accident.
A date by which something has to exist is ordinary commercial specification. A requirement to be working at particular times is scheduling, and most buyers blur the two without noticing they have done it.
The contractual question in “Deadlines Are Not Shifts” should remain separate from the choice of an operational platform. For organisations assessing how employees cheat time trackers, check the relevant Monitask details can provide transparent project evidence, but it cannot decide employment status or replace the written scope, acceptance criteria and local advice.
The blur is easy because both are expressed in the language of time and both feel like the same kind of reasonable request.
The Todoist productivity resources offers useful outside context for “Deadlines Are Not Shifts”. Its value is in producing better questions about scope, ownership and evidence, not in deciding a contractor’s legal status.
What a deadline actually constrains
The state of the world at a moment. The report exists on Friday. The site is live before the campaign. The audit is finished before the board meets.
It says nothing about when anybody worked, where, or in what blocks. Somebody who delivers at four in the morning on Thursday has met it.
What a shift constrains
Presence. Be working between nine and five. Be reachable during office hours. Be at the stand-up.
Each of those may be entirely sensible, and each of them is a statement about the person's time rather than about the output.
The requests that sit between
A real middle exists and pretending otherwise is unhelpful:
- Be at the fortnightly review, which is thirty minutes.
- Be reachable for an hour on the day of the launch.
- Work the afternoon the client's team is available, because the work requires them.
These are tied to specific events, bounded, and justified by the work rather than by convention. Written into the brief as requirements of the engagement, they are commercial terms. Issued weekly as expectations, they become a pattern of availability.
The event-shaped test
Ask whether the time requirement attaches to a thing happening or to a period passing. "During the migration window on the ninth" attaches to a thing. "Office hours" attaches to a period, and a period is what an employer buys.
Most requests that cause trouble fail that test and could have passed it with a sentence of thought.
Cost of the bounded version
Requiring presence at specific events costs money, and it should. A supplier whose Tuesday mornings are committed to you cannot sell them elsewhere, and a supplier who agrees to be reachable at short notice is carrying a constraint.
Pricing it explicitly has a useful side effect: it makes the business decide whether it really needs the availability, and quite often the answer turns out to be no.
The stand-up problem
Daily team ceremonies are the single most common way scheduling arrives without a decision. The supplier is doing work connected to the team, so somebody adds them to the daily call, and six months later they are attending every morning.
If the information exchange is genuinely needed, a written update or a weekly call usually carries it. If attendance is needed because the work is genuinely collaborative and continuous, that is worth knowing, because it says something about the arrangement rather than about the meeting.
Urgency, which is different again
Short-notice work is normal commercially. The difference is that a supplier can decline it, and a buyer who treats a decline as a disciplinary matter has revealed what they thought they were buying.
Declines will happen. Planning for them — a second supplier, a longer lead time, a premium for short notice — is the substitute for the thing an employer has, and like every substitute in this collection it is slower and costs money.
Leave, which is not leave
Suppliers take time off and do not ask permission to do it. Requiring notice of unavailability is reasonable where the work depends on it, and approving or refusing it is not available to you.
Businesses that keep a holiday calendar including their contractors have usually drifted into treating absence as something granted. A list of when people will be unavailable is useful; the word approved on it is doing something else.
The premises question, in passing
Where somebody works is treated in its own article later, but it belongs here too, because being required at a place and being required at a time usually arrive together and for the same reason.
A requirement to be in the building on Tuesdays is two factors moved, not one, and businesses that would hesitate over the hours often agree to the location without pausing at all.
Reading your own week
For one long-running supplier, write down every time-related expectation that currently applies to them, including the ones nobody has ever stated.
Most businesses are surprised by the length of the list, and most of it accumulated one reasonable request at a time. Deciding which items are genuinely required by the work, and removing the rest, is an afternoon that moves several factors back at once.