Voice Registers
Five relationships. One voice, held differently.
YMF writes across at least five distinct relationships — and each one asks something slightly different from the voice. The five rules on the Voice page hold in all of them: no jargon, no big-noting, problem before vision, mentor not friend. What changes is which of those rules comes forward, and which recedes.
The register matrix below is a working tool, not a permission slip. It names where the voice flexes so that writers can flex deliberately, not accidentally.
Donor
Fundraising letters, year-end appeals, partnership pitches, gratitude correspondence to financial supporters. Any writing where the explicit ask — or the implicit ask — is money, time, or formal backing.
- Problem-first structure.
- A number in the first paragraph.
- Mentor-not-friend register.
- No big-noting. No jargon.
- The emotional register can extend slightly further than in recruit copy. Donors are deciding whether the work is worth their attachment, not just their investment.
- A sentence of genuine conviction is appropriate — feeling is permitted to land.
- Sentences can be longer and more periodic.
- The closing posture move has more room to breathe.
- Charity-brochure voice: "Together, we can make a difference." Delete on sight.
- Gratitude as currency: opening with "your generosity has meant so much" before the substance.
- Urgency theatre: "this is our most critical moment yet."
- Progress-reporting as performance: listing activity as proof of worth rather than naming what the activity produces.
Thirty-six youth ministers came to the Residential in 2025. That number is not incidental — it represents every leader we could responsibly form in that setting, with the time and faculty ratio the model requires. We did not take more because the point is not headcount.
International faculty in 2026 adds complexity we have been working toward for three years. None of that cost lands on participants: the church cannot afford to pay them properly, and it is not reasonable to charge them to be formed.
If you give this year, that is what it pays for. Not administration. Not growth. The formation of people the church will rely on.
Opens with the confirmed figure (36), not "dozens" or "a cohort of." Buries conviction inside logistics rather than leading with feeling. "The point is not headcount" is the anti-vanity-metric move in donor register. The ask is in the third paragraph, framed as allocation.
Does the reader know exactly what their money does, before they're asked for it? Would a thoughtful donor forward this to a friend without embarrassment?
Recruit
Pipeline applications, Cohort invitations, role descriptions, Residential prospectus, any writing where the reader is being asked to consider joining something. The relationship has not started yet.
- Problem-first.
- Mentor register.
- No exclamation marks, no emoji.
- No jargon. The offer is described, not decorated.
- More direct address ("you").
- The "data" move may be about the program itself — what it contains, who is in it, what the time commitment is — rather than macro statistics.
- The problem being named is often the reader's professional situation, not the sector's aggregate figures.
- "Amazing opportunity": the register collapses the moment this phrase appears.
- Community-first framing: "join a community of…" before the reader knows what they would actually be doing.
- Requirements dressed as benefits: describing how competitive selection is, as proof of value.
- Vague transformation language: "grow as a leader," "deepen your practice," without naming the mechanism.
Your name came to us from [name], who has been watching your work with care. That is how we find people.
The Leaders' Cohorts run over twelve months: monthly peer supervision groups, a four-day residential in January, and one-to-one check-ins with a faculty member twice a year. You would be one of eight ministers in your group. The work is examining what it costs to stay — and what it produces when you do.
There is no application form. There is a conversation, and then a decision. If this is a year you have capacity for that, reply here.
Opens on their situation (someone vouched for them — concrete and specific). States the structure of the Cohort precisely before any claim about its value. "The work is examining what it costs to stay" is the offer in one line — honest, not glossy. The close is low-friction and respects their time.
Does the reader know exactly what they're being asked to do and how long it will take, before any claim about its value?
Internal admin
Committee agendas, reference panel communications, board reports, internal policy documents, operational emails between YMF staff and advisers. The reader already knows the mission; efficiency is the primary value here.
- No jargon.
- Mentor register (not peer-casual).
- No big-noting.
- Problem-first is often replaced by decision-first or action-first — the reader knows the context, they need the resolution.
- Sentences are shorter.
- Passive voice is acceptable when the actor genuinely does not matter.
- Lists are appropriate and expected.
- Ministry-speak leaking into operational copy: "as we continue to seek God's leading on this…" before a budget line.
- Excessive preamble: restating context the reader already holds.
- Hedging a decision: "we might consider…" when a decision has been made.
- Warmth performance: sign-offs warmer than the relationship actually is, compensating for directness.
Reference Panel — Cohort 2 intake update, September 2025
Twelve applications received. Eight proceeded to conversation. Six accepted.
Two declining decisions were sent this week. Neither involved the reference panel. Both were capacity-based; neither applicant was flagged as unsuitable for a future cohort.
Cohort 2 begins October 14. The panel will receive the group overview — names, contexts, presenting questions — by 7 October.
Subject line is a reference, not an announcement. Opens on the number, not a thank-you. "Neither involved the reference panel" tells readers what they need to know about their role without a separate paragraph. Timeline at the end is the close — no warmth-performance because the relationship does not need it here.
Has every sentence moved someone closer to a decision or an action? Is there anything here the reader already knew?
Pastoral
Direct correspondence with ministers in the Cohorts, prayer letters, notes of condolence, encouragement after a hard supervision session. The relationship is already established; the writing is doing relational work rather than persuasive or administrative work.
- Mentor register (not counselling-speak).
- No jargon.
- No big-noting.
- Problem-first gives way to presence-first. The opening can acknowledge the person's situation before moving anywhere else.
- Warmth is not just permitted — it is the point.
- Sentences can be shorter, paused, more personal.
- Data is rarely appropriate here; this is the register where the human situation is the subject.
- Counselling-speak: "I hear that you're feeling…", "it sounds like…", "that must be really hard."
- Ministry platitude: "God is in this," "trust the process," without weight behind it.
- Performance of busyness: referencing how much YMF has on, before acknowledging the person's situation.
- Unsolicited next steps: framing pastoral concern as a list of actions.
What you said on Tuesday stays with me. Not because it was a problem to solve — it isn't — but because it took something to say it in the room.
You have been doing this for eight years in a church that has not made it easy. That is not a small thing. Whatever you decide about next year, you should know that you did not fail it.
There is no action required from you before our next session. I will be in touch.
Opens on the specific moment (Tuesday), not a generalisation. "Not because it was a problem to solve — it isn't" names and refuses the counselling-speak move before the reader could apply it. "You did not fail it" is a direct pastoral statement, not hedged. The close is logistically clear without warmth-performance.
Does this sound like it was written to this specific person, about this specific situation? Could it be mistaken for a form letter?
Academic-adjacent
Long-form essays, methodology notes, research summaries, the bryanjhickey.com register, formal submissions, thought leadership writing intended for theological or ministry-sector audiences.
- Problem-first.
- No vanity metrics.
- Mentor register — meaning authoritative without condescension.
- Longer sentences are not just permitted — they are expected.
- Citation and footnote are appropriate.
- The paragraph can build an argument across multiple steps rather than delivering the point in the first sentence.
- The "data" move may be a footnote reference rather than an inline statistic.
- Turgid abstract-voice: "This paper seeks to interrogate the paradigmatic assumptions underlying…"
- Excessive qualification: three hedges before a claim that could stand on its own.
- Borrowed jargon: "liminal," "praxis," "hermeneutical circle" without definition.
- Switching from "I" to "one" to sound more scholarly.
The operating assumption behind the Leaders' Cohorts is simple, and it is not original: people stay in ministry when they are known. Not managed, not supported in the programmatic sense, but known by someone with enough experience to name what they are carrying. The literature on pastoral retention is thin, which is itself significant — the church has not studied exit in the way it has studied entry, and the asymmetry has costs. What follows is a description of the model we built in response to that gap, and an honest account of what we do not yet know about whether it works.
Opens with the thesis, not a preamble. "Simple, and it is not original" performs the anti-big-noting move while establishing credibility. The second sentence brackets the literature before the reader can ask about it. "An honest account of what we do not yet know" is the voice rule working in academic register — early-stage, treated honestly.
Has anything been stated that the author does not actually believe? Has any hedge been added that would not survive a reader asking "why qualified?"