Open almost any job listing for an executive assistant and you will find the same word, usually in the first paragraph: gatekeeper. It sounds sharp and protective, which is why nobody stops to ask what it is doing there. Gatekeeping itself is not the problem, it is one of the more valuable things a good assistant does every day. The real problem is that nobody has properly described what good gatekeeping looks like, so the word ends up underselling the judgement behind it while quietly excusing the moments that same protective instinct shuts down things that were never noise to begin with.
What gatekeeping actually protects
It is worth saying plainly what good gatekeeping does, because it is a real skill and any organisation that loses it notices fast. A strong gatekeeper protects an executive’s attention from the small distractions that would otherwise fill a day, filters requests so only the ones that genuinely need a decision reach the top, and absorbs the friction of saying no to things that do not deserve a leader’s time, quietly enough that the leader never has to. None of that is administrative, it is a constant, high judgement filtering process, and any assistant who has done it well knows exactly how much thought sits behind a decision that looks, from the outside, like nothing happened at all.
That is the case for gatekeeping, and it is a genuinely strong one. It is also only half the job.
What the word conveniently leaves out
Think about everything else that fills an EA’s week beyond the filtering: reading a difficult message and knowing how to soften it before it reaches a client, sensing that two people are about to disagree in a meeting and quietly restructuring the agenda so it never becomes a problem, holding years of context about a relationship that exists nowhere in writing because it was never anyone’s job to document it. None of that is gatekeeping, all of it is judgement, and judgement does not fit neatly into a bullet point, so it tends to get left off the list entirely.
Gatekeeper survives in job descriptions because it is easy to picture and easy to write, a tidy shorthand for “controls access to my time” that requires nobody to articulate the far harder to define skill underneath it: making consistently good calls on someone else’s behalf, often with incomplete information and no time to ask for clarification.
The gate that has to open, too
Somewhere in the middle of doing this well, a different failure tends to creep in, and it is worth naming honestly because it is common and rarely discussed. Protecting someone’s time is not the same as deciding, quietly and without asking, that whatever is on the other side of the door is not worth their time at all. “They won’t be interested.” “That’s not a priority right now.” “I’ll just handle it myself.” Each of those judgements might occasionally be right. None of them are actually the assistant’s call to make alone, and making that call alone, as a default, is not gatekeeping, it is editorialising with somebody else’s opportunities.
The authority that comes with this role is the authority to filter out noise. It was never the authority to decide in advance what was worth mentioning. A door only opens and closes. A gate can also let something extraordinary through, and the difference separates an assistant who protects a calendar from one who helps grow the business behind it.
None of this requires a different personality, only a different reflex: curiosity instead of assumption. Before deciding an opportunity is not worth raising, ask the two second question instead of skipping it. That single habit, staying open rather than pre-deciding on somebody else’s behalf, is one of the more reliable ways an EA becomes known as someone who brings value to the table, not only someone who manages what is already on it.
Why the word matters more than it sounds
Language in a job description is never neutral, since it decides who applies, how the role gets paid, and how much authority the person in it is eventually given. Describe someone as a gatekeeper and you are describing a role built around restriction, easy to manage, easy to measure, and easy to underpay, because on paper it looks like support rather than strategy. A chief of staff “manages competing priorities.” A strategic advisor “filters signal from noise.” Somehow, when it happens from a seat closer to the boardroom, it is strategy; from a desk outside the office, it is gatekeeping. The skill has not changed, only the word describing it has, and that word decides how the role is valued, promoted, and paid.
This is how a highly skilled profession ends up chronically underused: not through one dramatic decision, but through decades of job specs and internal language that quietly cast the role as smaller than it is, and quietly teach good assistants to say no by default rather than to ask. Nobody sits down and decides to undervalue assistants; it happens one lazily worded job description, and one over-cautious “they won’t be interested,” at a time, until it looks like an industry standard rather than a mistake.
What better language actually looks like
None of this means the protective function of the role should disappear, only that it should be framed as what it really is: judgement applied under pressure, on behalf of someone who has entrusted an enormous amount of their time, reputation, and information to another person,exercised with enough curiosity to recognise an opportunity as often as it filters one out. That is closer to risk management, and to growth, than to standing at a door.
Companies that get the most value from their assistants describe the role differently from the start, talking about strategic support, operational judgement, and trusted decision making, because it is more accurate, and accurate language produces accurate pay and trust in return.
A posting that opens with “this role exercises independent decision making, often under time pressure and with incomplete information” attracts a different pool of candidates, and justifies a different salary, than one that opens with “manages the calendar and controls access to their time.” A handful of forward thinking companies have already started rewriting postings this way,and the difference in who applies is noticeable within a single hiring cycle.
The word is a symptom, not the disease
None of this is really about a single word, since gatekeeper is simply the most visible symptom of a much older habit: describing the EA role by what it filters out rather than what it makes possible. Fix the word without fixing the thinking behind it and nothing changes; fix the thinking, stay curious instead of cautious by default, and the language tends to follow on its own.
The next time a job description for an assistant lands on your desk, it is worth reading past the first paragraph and asking what the language is really conveying. If the word doing the heaviest lifting is still gatekeeper, with nothing said about judgement, curiosity, or the opportunities a good assistant is trusted to bring through the door rather than keep out of it, that is not a description of the job, it is a description of how little the person writing it has actually understood about what the role requires.
