How should you assess a GEO supplier's team, capacity and key-person risk?

Buy the delivery system, not a slide of biographies

A strong proposal can name impressive people without showing who will actually perform, review and approve the work. GEO delivery may combine technical discovery, source verification, content, structured data, measurement, multilingual review and change control. The buyer therefore needs evidence that the proposed team covers the real scope and has enough time to deliver it.

The UK Government's March 2026 Contract Management Playbook emphasises capability, capacity, accountability and continuity throughout the contract. The Teal Book likewise says resource planning should identify roles, skills, availability and key-person dependencies. For a GEO procurement, convert those principles into one inspectable team record before mobilisation.

Create one six-part team assurance record

Complete the record for the proposed team and keep it current after award. Name an owner, evidence location, review date and status for every row. A generic organisation chart is not enough if it does not identify the people, allocation and controls that apply to this engagement.

Test capability against the real scope

Map each deliverable and control to the person who performs it and the person who reviews it. Ask for bounded evidence: a redacted work sample, an explanation of a comparable technical decision, a bilingual review exercise, or the evidence record the proposed role would maintain. Evaluate the response against the same criteria for every bidder.

Keep role evidence proportionate. A senior title is not proof of hands-on availability, and a long client list is not proof that the named person performed comparable work. Record what was verified, partly verified, unavailable or not relevant, and identify any capability that must be added before work starts.

• Use the statement of work to define the capability needed, rather than adapting the requirement to the supplier's available biographies.
• Separate advisory oversight from the people accountable for day-to-day delivery and review.
• For English and Chinese work, test factual equivalence, terminology governance and local review—not only conversational fluency.
• Confirm who can change production content, code, structured data, monitoring configurations and approved facts.

Run a capacity and absence test

Ask the supplier to map a normal delivery period and one disrupted period. Include planned reviews, urgent factual corrections, buyer approval delays, release dependencies and the absence of one key person. Show who picks up each task, which deadlines move, what is paused, and when the buyer is told. This is more useful than an unqualified promise that the team is fully available.

Compare the plan with the commercial model. If the proposal assumes named specialists, verify their allocation and lead time. If it relies on a shared pool, define the minimum capability, response path and quality gate for whoever is assigned. Capacity should be reviewed when scope, language, cadence, platforms or dependencies change—not only at contract signature.

Control substitutions without creating lock-in

A buyer should not require the same individual forever, but should prevent an unreviewed reduction in capability. Define which roles are key, what notice is practical, what evidence demonstrates equivalence, when buyer approval is required, and how access, conflicts, confidentiality and knowledge transfer are checked. Keep a time-limited exception route for emergencies, followed by a documented review.

Do not let continuity depend on personal inboxes, local files or undocumented judgement. Require shared source records, decision logs, approved fact sheets, change history, runbooks and buyer-controlled access where appropriate. Periodically ask a backup person to reproduce one safe workflow; record defects and retest them before treating cover as proven.

Ask SALIENS for a reviewable delivery team

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery. A scoped engagement can define named responsibilities, English and Simplified Chinese review, source-linked evidence, capacity assumptions, substitution controls, shared records and buyer acceptance checks from the start.

Email info@oxfordintelligence.co.uk with your website, markets and languages, required deliverables and cadence, material systems and access, internal reviewers, procurement timetable and continuity concerns. SALIENS is operated by Oxford Intelligence Limited. Team assurance supports dependable delivery but does not guarantee crawling, indexation, AI mentions, citations, rankings, traffic or enquiries. This guide is a procurement framework, not legal, employment or commercial advice.