← Back to Hub Lockwood Advisory
19 · Format Spec
Brand System · 19 · Lockwood Advisory · MMXXVI
Capability
Statement
Visual preview · spec 19
19 · Opportunity Doc · Format Spec

Capability Statement

The artefact that introduces the practice when an introduction is what's needed.

Standardisation in progress

When to use it

  • Initial introduction to a senior recipient.
  • Board chair or minister outreach with no pre-existing brief.
  • Executive search response at the qualification stage.
  • Pre-pitch context before a more detailed Proposal.

When NOT to use it

  • Pricing or scope discussion · use the Proposal (14) or Engagement Scope (17).
  • Personal application for a role · use the Cover Letter (18) + Executive CV (23).

When this format is right

One page. Sent to a senior recipient. Says who LA is, what it does, where it sits in the system, what kinds of engagement are possible. No price. No specific ask. The door that gets opened.

Canonical reference

Feb 2025 archived reference · LA + NL share the spec, tailored per role · standardisation pending.

Tooling

Built with the docx skill. Single page A4. Output as PDF.

Structure

  • Header band (LA navy + gold + globe-wordmark)
  • Practice positioning paragraph (1-2 sentences)
  • Three to four capability areas with brief descriptions
  • Indicative engagement types
  • Footer with contact and ABN
The DNA

Same as LA letterhead docs but condensed to a single page. Three to four capability areas in a grid or stack. Gold meta labels. Cormorant headings.

Variations

Same spec for LA and NL. Tailored per role · the positioning paragraph changes, capability areas adjust, sign-off varies (LA studio vs NL personal).

Voice rules

  1. One page. The constraint is the spec.
  2. No price. No specific ask.
  3. Positioning over claims. Show what's specific, not generic.
  4. Door-opener voice. Warm enough for the next conversation.

Production checklist

  1. Single page
  2. Positioning paragraph specific
  3. Capability areas distinct (not overlapping)
  4. Recipient context reflected (board vs minister vs search)
  5. Filename: LockwoodAdvisory_CapabilityStatement_[Context]_[YYYYMMDD].pdf
Prompt-ready brief · copy into any AI 
You are writing a Capability Statement for Lockwood Advisory (or Nicole Lockwood as her personal practice).

CONTEXT
One-page introduction sent to a senior recipient. No price, no specific ask.

STRUCTURE
- Header band (navy + gold + globe-wordmark)
- Practice positioning paragraph (1-2 sentences)
- 3-4 capability areas with brief descriptions
- Indicative engagement types
- Footer (contact + ABN)

VOICE
- One page. The constraint is the spec.
- Positioning over claims. Show what's specific.
- Door-opener tone. Warm enough for the next conversation.

FORBIDDEN SYMBOLS (NEVER USE)
- No em dashes (—)
- No en dashes (–)
- No section symbol (§) — use plain numbers (01, 02) instead
- No curly quotes (“ ” ‘ ’) — use straight quotes (")
- No ellipsis character (…) — use three dots (...)
- Use middle dot . only as separator (the . shown here is U+00B7)

OUTPUT
Write a Capability Statement for [LA or NL] tailored to [recipient context: board / minister / executive search / pre-pitch].

What this block does

Drop this into Claude, GPT, Gemini, or any LLM to produce a Capability Statement in the Lockwood Advisory format and voice without re-explaining each time.