Executive assistant interview scorecard for job-related evidence

Start with the real problem

An interview scorecard prevents a confident conversation from becoming the hiring decision. It translates the actual role into observable evidence and gives every interviewer the same definitions. Start with five to seven outcomes from the job brief, such as a dependable calendar, usable meeting preparation, accurate travel, protected confidential information, and commitments that do not disappear. Avoid personality labels that reviewers cannot define consistently.

Define scope and authority

Build dimensions only from work the person will perform. For each dimension, define strong, mixed, and weak evidence before interviews begin. Include a question or simulation that can elicit the evidence, an interviewer owner, and a place for factual notes. Keep protected personal information and unrelated assumptions out of the score. The hiring owner should resolve contradictory ratings by returning to examples, not averaging away an important concern.

Build the first control

Score prioritization with a realistic collision. Present a leader whose customer call, internal review, and travel change overlap. Strong evidence identifies consequences, gathers missing facts, applies written preferences, proposes options, and escalates by the last useful decision point. Weak evidence relies on guessing what the executive wants or treating the loudest requester as the automatic priority.

Make ownership visible

Score written communication using a short paid or appropriately bounded exercise. Ask the candidate to turn fictional notes into a concise briefing and a separate scheduling message. Review accuracy, audience, decision clarity, tone, and whether assumptions are labeled. Do not reward unnecessary length or an imitation of one interviewer's personal style. Give finalists the same material and reasonable accessibility adjustments.

Test the operating model

Test confidentiality and authority with specific situations. Ask what happens when a senior colleague requests restricted material, a vendor changes payment instructions, or a leader asks the assistant to send a consequential commitment. Strong answers verify identity, consult the approved rule, limit disclosure, preserve the record, and involve the right owner instead of using seniority as permission.

Protect judgment and access

Assess system building by asking how the candidate would learn and document a recurring workflow. Look for triggers, inputs, owners, sources of truth, acceptance, exceptions, and review. Software fluency can help, but a list of tool names is not evidence that the person can make work reliable. Let the candidate explain a comparable system without disclosing a former employer's confidential material.

Create a reviewable decision

Collect independent ratings before the debrief. Interviewers should cite the answer or work sample behind each score and distinguish missing evidence from negative evidence. The hiring manager checks that every required dimension was tested, investigates material gaps, and records the reason for the final choice. Keep records according to applicable policy and qualified guidance.

See the framework in practice

Two candidates receive the same calendar scenario. One immediately moves the internal review and says the executive probably prefers the customer. The other identifies the review's decision deadline, checks the customer's flexibility, preserves travel buffer, and offers two options with an escalation time. The second response earns stronger prioritization evidence even if the first candidate delivered it with more confidence.

Measure the result

Compare scorecard predictions with onboarding evidence after thirty and sixty days. Review correction patterns, escalation timing, accepted briefs, calendar recovery, access questions, and manager time. This is a review of the selection method, not a retroactive excuse to rewrite candidate ratings. Improve unclear prompts and scoring anchors before the next search while preserving a consistent, job-related process for the current one.

Review evidence before adoption

Before adopting this executive assistant hiring framework, review the actual workflow with the accountable executive, the person doing the work, and any qualified owner needed for employment, legal, security, privacy, finance, travel, or governance questions. Separate confirmed facts from assumptions. Record the decision owner, the safe action while information is missing, the last useful decision date, and the evidence that will close the issue. The external reference from EEOC employment tests and selection procedures guidance is a starting point, not a substitute for advice based on the organization's facts and location.

Write the operating brief

Turn the decision into a one-page operating brief. Include the intended outcome, supported leaders, trigger, inputs, source of truth, authority, service window, exception path, completion evidence, backup, and review date. Link the brief to executive assistant support and executive assistant paid work sample so the surrounding service and workflow remain easy to find. Walk through one ordinary case, one ambiguous case, and one failure case. If the team cannot agree on the response, the rule is not yet ready for someone to apply under pressure.

Design for continuity

Keep records in company-approved systems and give people only the access their current work requires. Preserve material changes, approvals, and exceptions instead of rewriting history. A reliable executive support system lets a named backup understand what is open, why it matters, who owns the next decision, and when action becomes too late. That continuity protects the leader without turning the support person into an unreviewable source of truth.

Rehearse the exception path

Run a tabletop review before treating the framework as established. Use a realistic request related to executive assistant hiring, remove one expected input, introduce a priority collision, and make the usual decision owner temporarily unavailable. Ask the team to show where the request enters, how its status becomes visible, which action is permitted without further approval, when escalation begins, and what evidence proves completion. Record confusion as a system defect rather than coaching people to remember an unwritten exception. Repeat the exercise with the named backup and only add access needed for that role. When the test exposes a missing owner or contradictory rule, pause expansion, assign the correction, and rerun the affected step. A short rehearsal is valuable because it tests the handoffs that ordinary documentation often assumes away.

Choose the next operating cycle

HireExecutiveTeam helps founders and leadership teams define and staff practical executive support. Use this guide against the real calendar, inbox, board, travel, meeting, project, and follow-through workload. Keep executive judgment with accountable leaders and specialist decisions with qualified owners. The next step should be a bounded operating cycle with clear acceptance evidence, followed by a review that can preserve, revise, or stop the arrangement.

Related resources

• executive assistant support
• executive assistant paid work sample
• executive assistant reference check questions