AIRE Translator™

You are driven to make the mission's decision make sense to congregation and board people who were not in the room before anyone treats the tool as the problem. In a nonprofit community-translator practice that means you sit between what the board packet or the congregation note actually says and what the program slide promised — a board member, a congregation volunteer, a donor liaison — and you reconcile the two without over-promising the mission. You write the note and turn a program decision into a paragraph that holds when someone who missed the morning meeting asks what the organization decided. You measure success when congregation contacts and board members can each follow the same next step without a second translation — not when the note sounded warmer than what the program and the grant line can stand.

You work by taking one live outward-facing congregation-or-board artifact — a board packet that needs plain language, a congregation note a hurried volunteer will misread, a program-decision recap that has to survive a skeptical board member, or a donor explanation that has to preserve trust without over-promising impact — and rewriting it so each audience hears a decision, not jargon. The locked audiences are congregation and board; the work is making the decision make sense to people who were not in the room. You run the same draft through program, congregation, and board lenses inside an approved tool, then strip anything a board member or a new volunteer would have to call to decode. Decision-making is one clear congregation-and-board narrative with the hard program and grant facts still visible, then a send. Communication sounds like: "Here is what the board actually decided on the program window, and here is what it does not," or "The model can draft the congregation note; it cannot promise a beneficiary outcome the program has not confirmed." You iterate by changing one audience constraint and watching whether the note still decides. You do not invent a commitment nobody verified, and you do not paste unpublished board packets, donor account files, or beneficiary stories into an unapproved tool.

You turn a board-packet clause, congregation-note line, or chaotic-week dump into something a board member or program lead can decide on without a second call. You hear the real objection (Is this program line real? Can you stand behind the grant update?) rather than the one the script says out loud. You reset expectations before they break — before a congregation send, before a board note ships, before a donor explanation treats a confident sentence as a commitment. You surface what program teammates miss: what the congregation must understand, what the board will misread, what a confident sentence will cost the next volunteer window. You preserve trust by leaving the hard limit visible. You keep the mission's decision recognizable to people who were not in the room — congregation and board alike.

Your drive to make everyone feel heard can soften a hard board, congregation, or grant reality to keep the tone comfortable, and small misunderstandings compound into a distrustful reply. You may over-explain, turning a one-line board answer into a story that hides the limit. You can commit other people to promises they were not asked about when you polish the congregation note faster than the program confirms. The skipped detail often becomes the dispute after the board meeting.

When the congregation send just landed, a board packet goes out tonight, or the program slide is still ahead of the room, you polish the note faster. The trigger is any room that wants warm language while the board fact, the congregation limit, or the program owner is still unnamed. In those moments you over-promise: you smooth the conversation, and the smoothing commits the mission to something nobody agreed to. Preserving trust means leaving the hard sentence in the board packet and the congregation note.

Program leads, mission pioneers, and board coordinators hand you the messy board-packet draft, congregation note, or donor explanation because you return something a room can follow without feeling scripted. Teammates say board meetings and congregation sends feel productive only after you have spoken the ask into one honest note. You fill the role of the person who bridges the program and everyone outside it — congregation, board, donor liaisons — without pretending the hard limits disappeared. You treat explanation as the work. You make the mission's decision make sense to people who were not in the room.

You adopt AI the moment it turns a dense board packet into a plain-language note, drafts a congregation explanation three ways until the tone is right, or prepares the donor update that makes the next conversation shorter inside an approved tool — and you still re-read it as the board member and the person who was not in the room. You resist tools that produce a confident paragraph with no verified program citation and no board limit, or that treat a single audience as the whole story when congregation and board both need the decision. Once a prompt survives one live congregation or board touch that did not need a second translation, you lock that pattern. Over-promising on a board packet or congregation note spends trust.

The community translators who turn a program decision into a congregation note a skeptical volunteer recognizes as honest, the board-facing leads who rewrite a packet so a board member can choose without misunderstanding the limit, and the donor liaisons who turn a chaotic week into one page the congregation and the board can both act on.

"Don't push the program slide onto the congregation. Make the next step honest — for the program, the board, and the people who were not in the room."