Taking an assessment rather than buying one? This page is written for employers. Here is the page for candidates.

Administrative and business support · Mid level

How to assess a Operations Coordinator

This role is hired on tool lists because there is nothing else legible on the CV, and tool fluency is the most trainable input in the job. The actual constraint is influence without authority: a coordinator's entire function is getting things out of people who do not report to them, and the skill is knowing the point at which a polite chase stops working and becomes an escalation with a name and a date attached. No interview observes that, and no Excel test comes near it. The second miss is data hygiene as a judgment call rather than a clerical one. The defining moment of the role is the status report where two source systems disagree and the update is due in twenty minutes; the weak hire picks whichever number makes the report look finished, the strong one reports the discrepancy as the finding. Both produce a document on time, which is why the difference is invisible to every screen currently in use.

An operations coordinator is the connective tissue between systems and people who are each doing their own job correctly and are not talking to one another. The role appears wherever a business has outgrown informal coordination and has not yet built a function: onboarding a customer across sales, finance and delivery; running the weekly cycle of a service desk; keeping a project plan and a purchase ledger and a client's expectations pointing in the same direction. The title is inconsistent across employers, which is exactly why it is hired so badly — a candidate who was a coordinator at one company may have done a scheduling job and at another a light analyst job, and the CV cannot tell you which.

What the role always contains is chasing. A coordinator spends much of the week asking people who do not report to them for things they have not prioritised: the engineer who has not updated a ticket, the account manager who has not returned the signed variation, the supplier whose invoice is blocking a milestone. The interesting skill here is escalation timing, and it is genuinely difficult. Escalate too early and you burn the goodwill you need next week, and you acquire a reputation that makes the next chase less effective. Escalate too late and the deadline has already gone, at which point the escalation is no longer a request for help but a report of a failure. Strong coordinators have an explicit internal rule — two chases and then a named escalation with a date, or whatever the equivalent is in their context — and weak ones either broadcast into a group chat where responsibility diffuses, or carry the delay silently because chasing feels rude.

The second half of the job is the tracker, and the point that hiring managers miss is that maintaining one is a truthfulness problem before it is a spreadsheet problem. Every project tracker in every organisation drifts toward green, because red requires a conversation and green requires nothing. A coordinator is the person best placed to know that a workstream marked on track has not moved in three weeks, and is also the most junior person in the room and the one with the least standing to say so. The single most valuable behaviour in the role is putting the amber in the report before anyone asks, with the reason and the ask stated in one sentence. It is also the behaviour that a friendly competency interview is structurally incapable of detecting, since the interview question — "tell me about a time you raised a risk" — reliably returns a story in which raising it worked out well.

The third component is reconciliation between systems that were never designed to agree. The delivery dates in the project tool were set at kickoff; the finance system holds the dates in the signed contract; the client's own portal holds a third set. A coordinator who reports one of these because it was the one they had open has done the work and produced a false document. A coordinator who notices the disagreement, works out which source is authoritative for which purpose, and states the exposure — "three of eleven milestones are contracted a week earlier than we have them planned" — has converted an administrative task into the most useful thing anyone will read that week.

What a head of operations is trying to predict is therefore quite specific: whether this person will surface bad news early, in writing, without being asked, and whether they can tell the difference between a tracker that is complete and one that is true. Neither is visible in a tool list, and both are visible within twenty minutes of realistic work.

What the job actually needs

• keeping a tracker true
• chasing dependencies without authority
• reconciling systems that disagree
• exception escalation with a name attached
• process documentation

How people fail in this seat

• reports green because nobody said red
• chases by broadcasting to a group where nobody owns the reply
• maintains a tracker that is accurate and unread
• escalates only after the deadline has passed
• patches the same recurring exception every week without naming the cause

What most employers do instead

CV screen against a list of tools (Asana, Jira, Monday, Airtable, advanced Excel), a competency interview, and occasionally a spreadsheet test.

The assessment

About 34 minutes end to end.

The systems it runs in

Three named systems that disagree, which is the whole fixture. A work tracking tool holds the plan set at kickoff — Asana, Jira, Smartsheet or monday.com, and demonstrated proficiency in one of them is the near-universal line in published postings for this seat. A finance or contract system holds the dates in the signed contract. The customer's own portal holds the third set, exported last week, alongside the two previous weekly exports. All three are supplied as exports rather than as live instances, which is deliberate: the competency is reconciling sources that do not agree, and it is measured identically whichever product produced them. The spreadsheet is where the reconciliation is actually done and it is worth being exact about what it requires. Eleven milestones across three sheets, where no two sheets share a key: the project tool exports task names, the finance system exports contract line references, and the portal exports the customer's own milestone labels. Joining them requires the candidate to decide what the key is before anything can be compared, and there is no column that supplies it. Column order differs between the three exports and between sitting variants, so a lookup written positionally quietly returns a date from the wrong milestone rather than failing visibly. The stalled workstream is not visible in any single sheet at all — it is visible only by laying this week's export beside the two prior weeks and noticing that a percent-complete figure has not moved, which is a comparison across time rather than a lookup. And the completed milestone is recorded as complete in one system and not the other two, so a candidate who picks a single authoritative source will report it wrong whichever source they pick. Fast and correct here means establishing the join key first and then working once; slow and correct means comparing the sheets pairwise three times and arriving at the same answer with no minutes left for the report; fast and wrong is reporting from the project tool, which is already open, internally consistent, complete, and false.

• Asana
• Jira
• Smartsheet
• monday.com
• Microsoft Excel
• Google Sheets
• Oracle NetSuite
• Salesforce

Any work tracking tool with dated milestones and a percent-complete or status field, any system of record holding contracted dates, and any customer-facing export. Where the buyer provides their own three sources the fixture is rebuilt from them, and it is worth doing, because which of a buyer's systems is authoritative for which purpose is the specific thing a new coordinator has to learn. Where they do not, the generic exports are used and nothing in the rubric changes. No criterion rewards tool fluency and no criterion mentions a platform; naming them fixes what the fixture looks like, not what earns a score.

What the candidate actually does

The mark scheme

Each criterion is scored 1 to 5 against written anchors, and every score is reported with the excerpt that earned it. A criterion marked floored is reported as a finding rather than averaged into the total. The first is open; open any other to read its anchors in full.

How it is scored

Weighted mean of the five criteria, each scored 1 to 5 against the anchors and reported with the milestone line, transcript line or sentence that earned it. Two facts are reported beside the score and annotated explicitly as not positive signals: whether the report was delivered inside the time box, and the overall status the candidate assigned. Both are things a buyer will look for and neither is a result — in this fixture the honest status is not green, and a report delivered on time from a single system is the failure the role exists to prevent. The call is scored from the transcript, which is the reviewer's default and only view; audio is retained for dispute and is not a scoring surface, and no criterion is named clarity, professionalism or assertiveness.

Integrity

• one unbroken monitored sitting in the order t1, t2, t3, with the reconciliation committed before the call opens
• the status report is graded against the candidate's own reconciliation and against a call transcript they cannot re-read, so a prepared status template cannot be made to fit a programme that went somewhere unplanned
• fixture variants rotated between sittings so the identity of the stalled workstream and the direction of the contract discrepancy differ
• one live follow-up question at the mid band, which invalidates an assumption rather than adding work: the candidate is told the customer has just confirmed they are planning against the contracted dates, and asked what changes in their report and what they would do first
• session log records file-open order across the three source systems, time distribution and paste-versus-typed provenance; no automated integrity verdict is produced from it

The log describes what happened. It does not produce a cheating verdict — the follow-up conversation is the control, because a statistical accusation is not something we would ask a reviewer to defend.

What you receive

• the reconciled milestone position with the source used for each
• full call transcript with the deferral offer time-marked
• the status report as it would have gone out, and anything the candidate chose to escalate, with its addressee
• per-criterion score with the milestone line, transcript line or excerpt that earned it
• delivery inside the time box and assigned overall status, annotated as not positive signals

Who decides

Recommended. The reviewer's specific job is the escalation threshold, because it is a property of the buyer's organisation rather than of the candidate: two chases and then a named escalation is right in a business where escalation is routine and wrong in one where it is a significant act, and a candidate who escalates on the third slip is correct in the first and abrasive in the second. The reviewer states the buyer's own norm before scoring and overrides the fourth criterion in writing where it differs. The ranking entitles a buyer to conclude that this candidate will surface bad news early and in writing without being asked, can tell a tracker that is complete from one that is true, and can get a commitment out of somebody who does not report to them. It does not establish familiarity with any particular project or finance tool, which is the thing the CV screen for this role currently measures and the most trainable input in the job.

What this does not measure

No criterion here rewards tool fluency and no fixture requires a specific platform: the three sources are supplied as plain exports, any method of comparing them is accepted, and no spreadsheet formula use is scored. That is the deliberate inversion of the usual screen, which is a list of product names on a CV. The call is scored from the transcript rather than the audio, which is the structural control on accent, dialect and speech variation, and the third criterion is written so that it cannot be satisfied by sounding forceful — the anchors ask for a named deliverable, a date and a consequence, all of which are facts a reviewer can point at in a transcript, and a quietly spoken candidate who obtains them scores 5 while a confident one who leaves with an assurance scores 3. The counterpart applies social pressure through friendliness and apology rather than through hostility, and never through anything a candidate could experience as personal. What the design does not reach is the week. A coordinator's real difficulty is that this is the eleventh chase of a Thursday and the relationship with the engineering lead has to survive until December, and a single call samples the judgment without observing what it costs to repeat. Nor can it observe the opposite failure over time: the coordinator who escalates correctly in month one and has spent all their credit by month four. A buyer should put both to a reference. Deployers should monitor the data task separately by group; extended time and assistive technology should be available on request, and the time box exists to control cost rather than to create difficulty.

This role is hired on a tool list because there is nothing else legible on the CV, and the tool list measures the most trainable input in the job. What the job actually consists of is two things that no interview reaches: getting work out of people who do not report to you, and keeping a document true when everybody involved would prefer it to be complete. The design spends its thirty-four minutes on exactly those, in that order, and then makes the second depend on the first.

The reconciliation comes first because it is the fixture that makes the status report meaningful. Three systems hold three sets of dates, all of them plausible, none of them flagged as wrong. The project tool is the one already open and the one the previous coordinator used. Reporting from it is fast, internally consistent and false, and — this is the part that makes it a genuine fork rather than a comprehension test — nobody will query it today. The exposure surfaces at a contractual date months away, by which time it belongs to somebody else. The candidate who instead states that three of eleven milestones are contracted earlier than the plan has them has converted an administrative task into the most useful sentence anyone on that distribution will read this week.

The stalled workstream is planted differently, and deliberately. It is not visible in this week's export at all; it is visible only by comparing three weekly exports supplied in the pack, none of which the brief draws attention to. That is what makes it a test of whether the candidate reads a tracker or merely updates one. The same design logic governs the dependency that has slipped three times for the same reason: the pack contains the two prior weeks, nothing points at the pattern, and noticing it is the difference between a coordinator who patches the same exception every week and one who names its cause.

The call is where the role's other half sits. Escalation timing is genuinely difficult and it is the thing coordinators are most often either too early or too late on. Escalate early and you burn goodwill you need next week, and the next chase lands weaker. Escalate late and the escalation is no longer a request for help but a report of a failure. So the counterpart is built to be likeable and busy rather than obstructive: they apologise, their reason is real, and halfway through they offer to take it away and look at it this week. Accepting that is pleasant, preserves the relationship, and produces an update that reads fine. It is also the third time, which the candidate can know only from the pack. If they press for escalation, the counterpart pushes back once, reasonably, which is where a candidate who was performing assertiveness rather than exercising judgment usually retreats.

The written segment is graded against both the candidate's own reconciliation and a transcript they cannot re-read. That combination is the strongest anti-coaching control available in a written task, because a prepared status template cannot describe a programme it has never seen or a call that went somewhere unplanned. It also measures the thing the job requires, which is an accurate record rather than good prose.

The truthfulness criterion is floored, and it is the only floor here. Every tracker in every organisation drifts toward green, because red requires a conversation and green requires nothing, and in this fixture the conversation is expensive: the account manager has already told the customer the programme is on track, the customer is on the distribution, and the coordinator is the most junior person on it. A candidate who assigns green when their own reconciliation does not support it has produced a document that will cause other people to make decisions on a false basis, and no strength elsewhere should offset that. A score of 1 there is printed as a finding rather than folded into an average.

Nothing in the brief asks for an escalation. The segment offers a blank field with no addressee rather than an escalation template, because a brief that instructs the candidate to escalate would measure compliance with an instruction, and every candidate would comply. Whether an escalation gets written at all, and to whom, is the observation.

Thirty-four minutes is affordable for a seat hired in ones and twos by a head of operations, and the allocation is deliberate: fourteen minutes for the fixture that gives the report something to be true or false about, eight for the only segment that can observe escalation timing at all, and twelve — the second largest — for the two documents, because the artefact is the job. Two facts are reported beside the score and marked as not results: whether the report went out on time, and what status was assigned. A buyer who reads either as a positive has misread the whole design.

Sources

Every figure on this page is traceable. Where a claim could not be sourced it is stated qualitatively instead.

1. US Bureau of Labor Statistics, Occupational Outlook Handbook, Office and Administrative Support Occupations, 2025-35 projections, about 1.7 million projected annual openings across the group, https://www.bls.gov/ooh/office-and-administrative-support/home.htm