Reference. Documentation as Institutional Protection

What to document, when to document it, and how documentation actually protects people and the Mission

1) What this artifact is

A staff-facing operational guide explaining how documentation functions in an embassy as protection, not as bureaucracy, fear-driven CYA, or punishment.

This artifact clarifies:

• what documentation is for,
• what it is not for,
• when documentation is necessary,
• and how to document in a way that protects employees, supervisors, and the institution without creating excess paperwork or mistrust.

This is not a records-management manual or legal guidance. It is a practical reference for daily work.

2) Who it is for

• FSOs and LES who receive verbal guidance or shifting priorities
• Supervisors who give direction, feedback, or accept risk
• PD staff handling sensitive engagement or media issues
• Anyone who has ever heard “that’s not what I meant” after the fact

3) How the work actually functions (process)

A) What documentation actually does in an embassy

Documentation serves four concrete functions:

1. Clarifies direction
   It records what was actually decided, not what people later remember.
2. Protects individuals
   It shows staff acted on guidance they were given.
3. Protects supervisors
   It shows decisions were made consciously, not negligently.
4. Preserves institutional memory
   It allows continuity across rotation and turnover.

Documentation does not:

• replace trust,
• substitute for conversation,
• or guarantee immunity from error.

B) The difference between useful documentation and “CYA”

The test: Would a reasonable supervisor find this helpful six months later?

C) What actually needs to be documented

Documentation is warranted when:

1. Direction is given verbally
2. Risk is accepted or deferred
3. Priorities change
4. Performance is discussed
5. Clearance or escalation decisions are made

Documentation is not required for routine execution where expectations are already clear.

D) Where documentation should live

Effective documentation lives where it can be found:

• a follow-up email,
• a Teams message,
• a shared tracker,
• a supervisor’s notes (for performance matters).

It does not need to be a memo unless policy requires it.

E) Timing matters more than volume

Documentation works best when it is:

• written soon after the event,
• short enough to be read,
• neutral in tone.

Late documentation often looks defensive—even when accurate.

4) Common failure patterns (paired with corrections)

Failure 1: “I didn’t want to bother them”

What happens: staff rely on memory; guidance later disputed.
Correction: Send a brief confirmation message.

Fix language:

“Confirming direction from today: proceed with X; hold Y pending further guidance.”

Failure 2: Documenting only when things go wrong

What happens: documentation appears retaliatory or self-protective.
Correction: Document routinely, not selectively.

Failure 3: Mixing facts with frustration

What happens: emails become emotional; credibility drops.
Correction: Separate facts from feelings. Document facts only.

Failure 4: Over-documenting everything

What happens: important records are buried; people stop reading.
Correction: Document decisions, direction, and risk—not every step.

5) Realistic scenarios (≥3)

Scenario 1: Verbal instruction later denied

A supervisor says verbally, “Go ahead and send it.” After backlash, they say they never approved release.

Documentation response:
Send a same-day confirmation email:

“Per our discussion, proceeding with sending X today. Please let me know if this is incorrect.”

This protects both parties by making guidance explicit.

Scenario 2: Shifting priorities

An urgent task displaces planned work.

Documentation response:

“Confirming that Task A is now priority and Task B will move to next week.”

This prevents later claims of missed deadlines without context.

Scenario 3: Performance counseling

A supervisor gives verbal feedback on missed deadlines.

Documentation response:
Supervisor records:

• date,
• issue discussed,
• expectations going forward.

This avoids surprise at evaluation time.

6) Checklists / templates (≥2)

Checklist 1: Should I Document This?

Document if the answer is “yes” to any:

• Was direction given verbally?
• Was risk accepted or deferred?
• Did priorities change?
• Was performance discussed?
• Would this matter in six months?

Template 2: Neutral Confirmation Email

Subject: Confirming Direction

Confirming today’s guidance:
- Action:
- Owner:
- Deadline:
- Any constraints:

Please advise if this does not reflect your intent.

7) What not to assume / not to do

Do not assume

• memory is shared,
• trust replaces clarity,
• documentation signals mistrust.

Do not do

• write emotionally,
• document selectively to protect yourself only,
• avoid documentation out of fear,
• escalate documentation into formal memos unnecessarily.