Asking, or Telling
The habit of requesting permission arrives without anybody imposing it, and it changes both how the arrangement feels and how it reads to anybody looking.
Is any time off paid, or do I just not earn?
The law where you areDo I have to ask, or only tell them?
What you signedWhat happens in a month with no work in it?
Only what happensDoes turning something down count against me?
Four questions a person in this position actually asks. One of them has no answer anybody can give in advance, and nothing here fills a blank with a guess. Two of these have findable answers and two depend entirely on the people involved.
The habit of requesting permission arrives without anybody imposing it. Nobody tells you to start asking; you simply do, because that is what the last ten years of working taught you, and six months later every message about your own time is phrased as a request.
The practical question in “Asking, or Telling” is easier to handle when expectations and evidence are visible to both sides. For teams assessing time tracking with screenshots, open the workforce-management overview can provide time and project context, but the purpose should be disclosed, access limited and every consequential interpretation reviewed by a person.
Noticing it is most of the correction.
For broader context around “Asking, or Telling”, see SimplyHired career resources. Compare its general guidance with the worker category, jurisdiction and day-to-day facts in this case.
Where the habit comes from
Years of employment, mostly. People who have always had a manager reach for the same wording automatically, and the wording is polite and feels safer.
It is also occasionally encouraged from the other side, by somebody who has only ever managed staff and does not notice the difference either.
The two sentences
They carry the same information and sit differently:
Would it be all right if I took the 14th off?
I am not working on the 14th; everything for that week will be done by the 13th.
The second is not rude. It is a supplier telling a client about availability, with the planning attached, which is what the arrangement actually is.
Why it matters beyond feeling
Permission over working time is one of the recognisable features of employment in most systems, and a trail of requests and approvals is exactly the kind of ordinary traffic anybody examining the arrangement would read.
Nothing turns on a single message. The pattern across two years is a different matter, and the pattern is made of messages like these.
Where asking is correct
Plenty of places. Anything that is genuinely theirs to decide: access to a system, a change to a deadline that affects them, whether a piece of work should be done at all, spending their money.
Those are not permission about your time. Confusing the two produces the opposite error, which is refusing to ask about things that obviously require their agreement.
The test
Whose resource is being committed. Your own hours and your own calendar are yours; their budget, their systems and their deadlines are theirs.
Applied honestly, that settles most cases in a second, and it explains why "can I take Friday off" and "can we move the deadline to Friday" are completely different messages.
Rewriting one message a week
The practical way to change a habit without a project. Before sending anything about your own time, read it once and check whether it asks for something that is yours.
Most people find three or four a month. Changing them takes seconds and the cumulative effect over a year is substantial.
When they respond as though approving
Common and usually meaningless. "Yes that's fine" is how people talk, and reading it as an assertion of authority is overthinking.
Where it goes further — a request logged in a leave system, a refusal, a requirement to find cover before going — that is worth noticing, because those are mechanisms built for employees and you are in one.
Being put on their leave system
Happens through the same provisioning process that creates accounts and directory entries. Nobody decided it.
Asking to be taken off is a reasonable administrative request: "could you take me off the leave calendar — I will just tell you my dates directly." Most organisations do it without comment.
The reverse problem
Over-correcting into brusqueness. A supplier who announces absences with no notice and no regard for the client's planning is not asserting independence; they are being difficult to work with.
The goal is a client who always knows where they stand, told rather than asked. That is both better practice and better business.
What this looks like after a year
Your calendar is yours and theirs is theirs, nobody uses the word approve, and the client plans around your stated dates without friction.
That is not a legal position and it does not settle anything by itself. It is simply an arrangement that is being run as the thing it says it is, which is worth something in every direction.
Where it has already gone wrong
If you have been requesting permission for two years, changing the wording tomorrow will not undo it and will look odd.
The realistic version is to stop adding to it: say dates rather than ask from now on, and let the change be gradual. Nobody announces this and nobody needs to.
The thing that cannot be read from here
Whether a particular client would react badly to being told rather than asked. Some would, most would not notice, and nothing published anywhere predicts which.
What is knowable is that the version with planning attached — the dates plus what will be done before them — rarely causes trouble in any arrangement, which makes it the safe form of the correction.