Baseworks Voice Guide — Patrick

Created 2026-02-28

Updated 2026-02-28

Status active

Tags voicewritingbrandreferencepatrick

This guide documents Patrick’s personal writing voice for use in messages, emails, program copy, and any communication written in his name. It builds on VOICE-GUIDE-UNIFIED.md — read that first. This guide covers what is specific or distinctive about Patrick’s voice.

Patrick’s Voice in a Sentence

Direct. Warm. Precise. Short sentences for emphasis. No hedging. No performative enthusiasm.

Core Characteristics

Tone

Direct without being cold. Warm without being soft.
Conviction throughout — no apologies for the method’s requirements.
Respectful of the reader’s intelligence. Does not over-explain.

Sentence Structure

Prefers short, standalone sentences to make a point land.
Does not string ideas together when they deserve their own space.
Longer sentences are used for context or sequencing — not for emphasis.

Example:

The in-person sessions will start connecting. But only if the preparation is in place.

Not:

The in-person sessions will only start connecting if the preparation is in place, so it’s important to do the work beforehand.

Warmth

Warm when appropriate — but specific, not generic.
Does not say “wonderful” or “fantastic” indiscriminately.
Warmth appears through specificity: naming what was notable, not just saying something was good.

Acceptable warmth:

“That’s a rare observation — and it says a lot about how you’re engaging with the practice.”
“We’re genuinely glad you reached out.”
“That’s striking.”

Not acceptable:

“That’s amazing!”
“Wonderful to hear from you!”
“So excited about this!”

Team Language

When writing as Patrick, acknowledge the team where appropriate — even when signing personally. Baseworks is a shared effort.

“We’re really glad you’re joining us.” (not “I’m really glad”)
“We’ll be in touch before the session.” (not “I’ll be in touch”)
Signing with “Patrick” does not mean the voice shifts entirely to first person singular.

Exception: Personal reflections, teaching observations, or first-person accounts of Patrick’s own experience can use “I” naturally.

Qualifiers — Intentional Use

Patrick uses qualifiers not as hedges but as precision tools. They make the writing more honest, not less confident.

Use:

“Often”
“In most cases”
“Many practitioners find”
“A certain quality of attention”
“Typically”

These are not weakeners. They signal that Patrick is being accurate about what varies, rather than overstating outcomes.

Avoid accidental hedging:

“Maybe,” “possibly,” “it seems like,” “I think,” “kind of,” “sort of” — these hedge without adding precision.

Preferred Terminology

Use	Avoid
”Shifts"	"Changes” (in a Baseworks method context)
“Practitioners"	"Students” (in public-facing copy)
“Guided practice"	"Class” or “workout"
"Structured study"	"Course” (in method-specific contexts)
“The method"	"The system” (in casual copy)
“In-person"	"Live” or “IRL”

Email and Participant Communication Voice

Opening

No apologetic openers: “Sorry to bother you,” “Just a quick note,” “Hope this finds you well.”
Address the point directly. Context follows if needed.

Good opening:

Good evening Manon,

Completing Segment 5 is the last assignment for this cohort.

Not:

Hi Manon, hope you’re doing well! Just wanted to quickly reach out about your assignment question.

Closing

Clear, complete, no lingering open threads.
Signing with just “Patrick” is standard. No sign-off phrases unless the context calls for it.

Tone Escalation

When following up on missed assignments or policy matters, the tone escalates in specificity and directness — but never in coldness.

Light:

Just checking in — I noticed you haven’t started the first assignment yet. Wanted to make sure you received access okay.

Direct:

I’m reaching out because we’re just a few days out from Saturday’s session and the assignment isn’t started yet. The program relies on everyone completing these before we meet in person.

Firm:

Quick check-in before Saturday. I see you haven’t started the first assignment. I wanted to reach out directly rather than wait until we’re all together. The hybrid format depends on this preparation being in place.

What to Always Avoid in Email

Exclamation marks in professional or policy-adjacent contexts
Apologetic language for program requirements
Framing that suggests the participant might opt out of methodology requirements
Generic warmth without substance (“So great to see you there!”, “Incredible session!”)
Singling out one modality (e.g., yoga) as the reference point when the person has a diverse background — refer to “your background” broadly, or list comprehensively. See unified guide: “Referencing specific modalities.”

Session Summary Voice

Session summaries are written in Patrick’s voice — methodologically precise, grounded in what actually happened.

Principles

Extract, don’t invent. Base content on what was said and practiced. Do not add language that sounds like it fits but wasn’t present.
Name specific participants when they ask questions or make observations — this anchors the summary in what actually happened.
Include actual cues and quotes from the session where possible.
Connect to Primer content by lesson number where relevant.
Supplement from form documentation when the transcript is sparse — not to invent, but to describe the physical reality that the verbal instruction assumes.

Tone in Summaries

Methodological and precise — not clinical.
Explanatory — written so that someone who missed the session can follow what was practiced and why.
No generic wellness framing: “relax,” “release tension,” “body awareness.”
Correct Baseworks framing throughout (see _session-summary-guidelines.md for full terminology reference).

Example of Voice in Summaries

Good:

We reviewed signals to watch for when deciding whether to back off: pain or compression in any joint, body temperature increasing, difficulty maintaining conversational breathing. These are not failure signals — they are calibration information.

Not:

We talked about listening to your body and knowing when to rest — important for everyone’s wellness journey.

Copy Voice (Program Pages, Website)

When writing program copy in Patrick’s voice:

Lead with what the program is and what it does — format, structure, who it’s for.
Do not open with positioning statements or competitive framing.
No urgency language unless factually accurate and necessary.
The two-version principle applies (see VOICE-GUIDE-UNIFIED.md): produce accessible and formal versions.

Patrick’s copy style:

Short paragraphs. Short sentences where they count.
Conviction in the description — no hedging about what the method does.
Specific over general: “Practitioners often notice the awareness skills developed here become useful in how they learn, concentrate, and sustain effort” — not “a transformative experience.”

What to Avoid — Patrick’s Specific Avoids

Beyond the unified guide’s list, these are specifically inconsistent with Patrick’s voice:

“Graciousness” — too soft, not his register
“Wonderful” (as generic warmth) — no substance
“Amazing,” “incredible,” “unbelievable” — performative
“Journey,” “path,” “process” in a wellness framing
“Mindset” — too self-help adjacent
“Show up for yourself” — not Baseworks language
Opening a sentence with “So…” — too casual, signals hedging
“Just” as a softener (“just wanted to check in”) — undermines directness

Version History

Version	Date	Change	Confirmed by
1.0	2026-02-28	Initial creation — synthesized from communications guide, session summary guidelines, participant communications log, and copy feedback from Patrick (2026-02-28 session)	Patrick
1.1	2026-03-16	Added to email avoids: do not single out one modality as reference point when person has diverse background. Cross-references unified guide. From Millie Tresierra inquiry response review.	Patrick