How to read a TOR like a hiring manager

Most TORs attach a scoring grid or evaluation criteria, even if it is buried in an annex. Read those criteria before you skim the narrative: they tell you what the client will actually defend in debriefs and shortlisting.

Highlight mandatory requirements (years of experience, language level, registration, geography) in one colour and desirable criteria in another. If you cannot evidence a mandatory criterion, do not burn time on a generic proposal.

Look for who signs off on deliverables, who chairs the steering group, and who owns budget revisions. Misaligned expectations between programme, finance, and MEAL teams are a common source of scope creep.

If the TOR references a host government partner or cluster coordination, note how often formal approvals are required. That rhythm affects staffing intensity and travel.

Strong TORs still use vague phrases like “strengthen capacity” or “improve resilience.” Rewrite those into measurable indicators you can track in your workplan: numbers of staff trained, tools adopted, or response times improved.

When you respond, mirror the TOR’s language in headings but tighten definitions in your methodology so evaluators see alignment without ambiguity.