Hours You Can Ask For and Hours You Cannot
Asking somebody to work at particular times is scheduling whoever they are, and the useful question is what each kind of request is actually tied to.
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. A deadline is not a shift, and the difference is visible from outside.
A requirement to be working at particular times is scheduling, whoever the person is. The useful question is not whether you are allowed to but what each request is tied to, because requests tied to the work behave quite differently from requests tied to the calendar.
The boundary discussed in “Hours You Can Ask For and Hours You Cannot” should be explicit before any workforce data is collected. A company evaluating read the associated Monitask overview for tips to increase productivity can use agreed time and project context, provided contractors know the purpose, can correct records and are not judged against employee-style attendance rules by default.
Every business ends up making some of them. Very few make them deliberately.
Teams documenting “Hours You Can Ask For and Hours You Cannot” can also review Airwallex business-payment articles. Record which ideas fit the engagement and which still need confirmation from the contract owner or local adviser.
Tied to an event
The migration runs on the ninth, so somebody has to be working on the ninth. The client's team is only available Thursday afternoons. The building is accessible between seven and six.
These are properties of the work. They belong in the engagement, they can be priced, and a supplier can decline the engagement if the constraint does not suit them.
Tied to the calendar
Office hours. Weekdays. Monday mornings. Available during the working day.
These are properties of your organisation rather than of the job, and they are what an employer buys. A supplier who has agreed to office hours for two years has agreed to something nobody would have described as part of a piece of work.
The honest middle
Some requests are genuinely both. A business that needs somebody reachable while its own staff are working, because the work is interdependent, is asking for something the job requires in a form that looks like a schedule.
The way to keep it defensible is to say which it is and bound it: reachable for an hour a day during the integration phase, rather than available during office hours indefinitely.
Pricing availability properly
Time held open for you cannot be sold elsewhere. If you want it, it costs something, and the price is a useful discipline because it makes the business ask whether it is actually needed.
Businesses that have never priced availability usually discover, when they do, that most of what they thought they needed was habit. The remainder is real, and paying for it is cheaper than the alternative.
What you cannot do with hours
Three things that belong to an employer and are not available regardless of how the request is phrased:
- Require attendance as a condition rather than as a term you paid for and they accepted.
- Treat a failure to be available as misconduct.
- Approve or refuse time off.
Each of those will be reached for at some point, usually by somebody who has managed employees for a long time and is not thinking about it at all.
Notice of unavailability
Entirely reasonable to agree, and quite different from approval. A supplier saying they are away for two weeks in August is giving notice. A supplier asking whether they may be away for two weeks in August has, somewhere along the way, been taught to ask.
That teaching is almost always accidental and it is usually visible in a message thread if anybody goes looking.
When the pattern is the evidence
A single week of agreed hours is a commercial term. Two years of weekdays nine to five, with nobody having decided it, is a pattern, and patterns are what people look at.
This is the general shape of everything in this collection: no single instance is decisive, and the accumulation of instances is what somebody reads.
Overtime, which does not exist here
A supplier working late to hit a date they committed to is managing their own business. There is no entitlement being accrued and nothing to approve.
Where a buyer starts thinking in terms of extra hours — recording them, authorising them, resenting them — the mental model has shifted, and the language usually shifts with it in ways that are visible later.
Writing it down at the start
Any time requirement that is genuinely needed can go in the engagement, with its reason and its boundary. That takes one sentence and converts something that would look like a schedule into something that looks like a term.
The requirements that cannot be written down that way are generally the ones that were not actually about the work, and finding that out before the engagement starts is considerably cheaper than finding it out in year three.
What this leaves available
A date, an event, a bounded commitment you paid for, and the right to stop buying if none of it is being honoured. Thinner than a rota and sufficient for most work.
Where it is not sufficient — where the business genuinely needs somebody whose week it can arrange — that is worth saying out loud, because it is a statement about what the business needs rather than a problem with the supplier.