Inbox Triage: what the reviewer is actually looking for.

When I was recruiting, the question I could never answer at interview was the one that mattered most: what does this person do at 8:45 when there are forty emails, the diary has already moved twice and the principal is on a plane? Everyone describes it well. Very few people can be watched doing it. Inbox Triage is the module that lets a reviewer watch.

It is the first of the six core modules in every Core Standard assessment, whether an employer commissioned it or you sat TCS Certified yourself, and it runs at every level. The inbox gets harder as the level rises. The rubric does not change. This piece is for the EA about to sit it. I am not going to show you the inbox, because seeing it would not help you and would make your result mean less. I am going to show you how it is marked.

What the module is

You arrive at a point in a fictional principal’s day. The inbox is live, the principal is unreachable for a stretch, and the messages are the ordinary mix of a real morning: things that look urgent and are not, things that look routine and are not, something personal, something from someone senior, something with a date in it that is wrong. You are asked what you would do, in what order, and why. At the higher levels the mix carries more weight: stakeholders whose relationship with the principal you have to read, a commercial or reputational risk buried in a polite email, and less certainty about what the principal would want.

Two things are true about the module that people often do not expect. There is no answer key with a single correct order. Two strong EAs will sequence the same inbox differently and both score well, because the reviewer is marking the reasoning, not the ranking. The second is that everything you write is read. The line of reasoning next to each item is where most of the marks live.

The four things a reviewer reads for

A principle you can name

The first thing I look for is whether the candidate is working from a principle or from the order things arrived. Strong triage almost always comes back to three questions: who is blocked until I act, what becomes irreversible if it waits, and what can only the principal decide. You do not have to use those words. You do have to show that some rule is driving the sequence, and that it survives contact with the awkward items. The Developing band on Prioritisation is, roughly, worked top to bottom or marked everything urgent. Distinctive is re-sequenced without prompting when a new input arrived, held the principal’s agenda in mind when the obvious path would have solved the smaller problem, and named the trade-off in writing rather than just picking one.

The quiet risk

Every inbox in the assessment has at least one item that is not marked urgent and would hurt most if missed. The wrong dates on a booking. A calm email whose subject line does not match its body. A meeting invitation with the wrong people on it. This is Judgement, and it is the pillar that most often separates a good result from a very good one. The reviewer is looking for whether you read each message twice, once for what it says and once for what it means. The candidates I have seen score highest here are rarely the fastest. They are the ones who paused on the item everyone else skimmed.

The line between you and the principal

Somewhere in your answer the reviewer will look for a line: this I closed myself, this I held until the principal was free, this I took to her the moment she landed. Where you draw it is scored under Partnership, and both extremes lose marks. Escalating everything reads as a pair of hands. Deciding things that were never yours to decide reads as a risk. The strong middle is the EA who acts within sensible limits and says so, in writing, so the principal knows what was done in her name and why.

The handover

Most candidates treat the summary at the end as admin. Reviewers treat it as Communication and Execution evidence. Is it short? Is it in a register the principal could read on a phone between meetings? Does it say what is done, what is waiting on him, and what is still open, in that order? A handover that lists everything you did is weaker than one that tells the principal the three things he now needs to know.

How it is scored

Every module is scored against the five pillars on a published, behaviourally anchored rubric with five bands: Developing, Proficient, Strong, Distinctive and Exemplary. Each band is a description of behaviour, not an adjective, which is why two reviewers looking at the same triage land in the same place. AI generates a first pass. An expert reviewer reads your work, adjusts, and signs the report. Name, age and education are stripped before the reviewer sees it. Prose quality is not scored: a clear bullet list that makes the right call beats a beautiful paragraph that misses it.

A serious misjudgement in a module, the kind that would have cost the principal something real, is logged as a red flag and caps that pillar for the module. A standout move is logged too, and carries through to the reviewer’s narrative and, if you sat Certified, to your Recruiter Summary. The full rubric is public on the methodology page.

What changes by level

The module has the same name at every level and is recalibrated at each. At Operational EA, the reviewer wants accuracy and calm: nothing slips, the obvious calls are right, the handover is clean. At EA to Senior Leadership, the inbox contains people, and the marks move towards anticipation and stakeholder reading: you noticed the chair’s office was being polite about something that was not optional, you protected the principal’s time without being asked. At Executive Business Partner, there is usually a commercial or reputational thread running through the messages that nobody has labelled, and the reviewer is looking for whether you found it and what you did about it.

If you sit TCS Certified, you sit one assessment and your work is scored against every level, so your result is the level your triage demonstrated. That is why the reasoning matters more than the ranking.

Three habits that cost a band

Treating the sender’s seniority as the priority. The email from the most senior person is not automatically first. It is first if it is blocking, irreversible or only theirs to decide. The scariest title in the inbox is a trap the module sets deliberately.

Flagging everything to the principal to be safe. Safe for you, expensive for her. The reviewer reads a wall of escalations as an EA who has not yet earned, or does not want, the trust the role runs on.

Writing to impress the reviewer. The reviewer is not the audience. The principal is. Answers that explain what a good EA would do, in the abstract, score below answers that simply do it.

Can you use AI?

Yes. We do not ban it, because the job does not. We tested submissions that leaned heavily on AI and they did not come out on top, because the module turns on decisions AI cannot make for you: which of three competing demands this principal cares about today, what to protect him from, when to check before acting. Use it the way a strong EA uses it in the seat, as a capable assistant, and then apply your own judgement on top. That is what the rubric rewards.

How to prepare, and how not to

Do not go looking for practice inboxes. The rubric does not reward people who have seen a similar prompt, and rehearsed triage reads as rehearsed. What helps is ten minutes the night before, writing down the three hardest calls you have made in your current seat and why you made them. That is the muscle the module uses. On the day, read every message twice, write how you would speak, and decide. The practical guide to the day itself, from setting up your space to what happens if your laptop dies, is on the how to prepare page.

Common questions

---