Examples Section D E Personal Maintenance

## Section D — Optional personal content

#### D1. Optional personal note

- **Tier:** Supporting
- **Last updated:** [YYYY-MM-DD]
- **Tags:**
  - Role families: All (use only when explicitly requested)
  - Capability: People, culture and workforce
  - Sector: All
  - Anchor org: Personal
- **Primary example:** Cross-personal background
- **Secondary example:** N/A
- **See also:** [Related A-block IDs — typically motivation and leadership-approach blocks]
- **Best used for:** Only where a recruiter explicitly asks for personal background or outside-of-work context

**Core response**

[200–300 words. The candidate's personal note — interests, family, hobbies, what shapes them outside work. Use sparingly: only when explicitly invited. Should connect to professional themes without forcing the link — what does the candidate do that mirrors the way they lead? What sustains them? What signals values, character, perspective without performing them?]

[Setup guidance: this section is optional during initial setup. Skip it unless the candidate has a clear sense of how they want personal context to land if asked. Many candidates prefer to write D1 the first time a recruiter actually asks for personal background, rather than pre-writing it.]

**Proof points**

- Useful only when an application explicitly asks for personal content or a more rounded introduction.

**Cautions**

- Do not use in formal statements of claims unless the application expressly invites personal background.
- Do not contrive parallels between personal interests and professional capabilities. The connection should be honest or absent.

---

## Section E — Maintenance and retrieval notes

#### E1. How to keep this document useful

The day-to-day maintenance protocol is embedded in the companion file `Evidence_Bank_Changelog.md`. In short:

- After each application draft, record any new evidence, sharper framings or retired claims in the changelog.
- Add new entries into the correct capability section (A, B1–B6, C, or D), never as a free-standing addendum.
- Keep the core response polished and under 200 words; move deep detail into proof points.
- Keep the master index (Section 4 of `Examples_Master.md`) and role-family recipes (Section 5) in sync with new or retired entries.
- Review the watch-outs register (Section 7) whenever an example is strengthened by new evidence.

#### E2. Additional note for specialist-domain roles

For specialist-domain applications, use direct domain evidence where it exists. Where the fit is adjacent rather than exact, say so clearly and bridge through comparable scale, complexity, client delivery, data and platform leadership, operating-model change, and commercial outcomes. Do not create constructed equivalence with specialist technical or regulatory domains unless the evidence genuinely supports it. This preserves credibility and usually produces a stronger application than overstating direct subject-matter depth.

#### E3. Changelog and version control

The authoritative change history for this evidence bank lives in a separate file in this project:

- **File:** `Evidence_Bank_Changelog.md`
- **Owner:** [Candidate First Name] (edits accepted from Claude when changes are made during an application)
- **Format:** Reverse-chronological. Each entry records date, section touched, nature of change (add / amend / retire), reason, and a one-line source note.

Every time this evidence bank is updated during an application, the changelog must be updated in the same session. If the changelog is not updated, the change is considered draft only.

---