Afh 33 337 Tongue And Quill

Working with the Air Force Writing Handbook in Practice

Most people who tell you they have to follow Afh 33 337 Tongue And Quill have never actually read it cover to cover. They reference it when someone on the chain of command complains about formatting, then go back to doing whatever they were doing. That is a problem because the handbook is not just a formatting checklist. It is the operating procedure for how the entire Air Force communicates, and missing the underlying logic in it will cause you to make the same mistakes repeatedly. The document was originally based on the book "Tongue and Quill" by Lt. Col. Richard E. Simcox, which went through many editions starting in the 1940s. The current Air Force Handbook version consolidates that legacy material with newer guidance on electronic communication, briefing standards, and the transition from paper-based correspondence to digital workflows. The official download lives on the AF Publications and Digital Publishing website at afpc.af.mil or through the e-Publishing portal. You do not need a .mil login to access the PDF, but your unit's webfilter may block it depending on how your network is configured.

Afh 33 337 Tongue And Quill Practical Application

Here is the thing that trips people up most: the handbook assumes you are writing for a reader who is busy and potentially hostile to whatever you are telling them. That shapes every single rule in the document. The emphasis on BLUF (Bottom Line Up Front) is not just bureaucratic preference. It comes from the reality that a colonel or senior enlisted leader will read the first two paragraphs and decide whether to keep reading. If the purpose is buried in paragraph three, you have already lost. I learned this the hard way when I drafted a 14-page policy implementation memo that opened with a historical overview of the program. My reviewer marked it up with a single note that said "where is this going?" and sent it back. The rewrite took forty minutes because I already knew the answer. Just put the request or decision point in the first paragraph and move the background to an enclosure. The formatting rules themselves are fairly straightforward if you approach them systematically. Letter templates have prescribed margins, font sizes, and block structure. For standard correspondence you are looking at one-inch margins, Times New Roman or Arial at 12-point, and single spacing within paragraphs with a blank line between them. Memo format follows the same basic structure but with a different header block. The tricky part is getting the subject line right. It should be specific enough that someone filing it can find it three years later. A subject like "Request for coordination on FY26 training budget" is useless. A subject like "FY26 ANG Training Budget Allocation – Action Required by 15 March" tells the reader exactly what the document is about and what you need from them. One edge case that the handbook does not really address head-on is the intersection between official correspondence and instant messaging or chat-based communication platforms. When I was working a staff section that used Teams alongside formal memos, we ran into a situation where a commander gave verbal direction through chat that conflicted with an already-drafted policy memo. The chat message was technically not an official record, but everybody in the building treated it as binding. I ended up having to draft a clarification memo that referenced the original guidance without directly contradicting the commander's chat comment. The workaround was to frame it as a correction of a clerical error rather than a policy reversal, which kept the chain of command intact while still getting the record straight. It is not a satisfying solution, but it is the kind of thing that comes up when you are actually doing the work.

Briefing slides have their own set of rules that most people ignore until someone with a red pen shows up. The handbook specifies maximum points per slide, font size minimums, and color contrast requirements. The counter-intuitive part is that less information on a slide often communicates more effectively. A slide with three bullet points at 24-point font will land better than a slide with eight bullets at 14-point font, even if the eight-bullet version contains more detail. The detail belongs in your speaker notes, not on the screen. I have seen briefers try to put entire paragraphs on slides and then stand there reading them verbatim. That is not a briefing. That is someone reading aloud while other people sit in a room wondering why they were called in. Technical reports and evaluations follow a different structure entirely. The handbook has specific templates for inspection reports, after-action reviews, and capability assessments. Each one has prescribed sections that cannot be arbitrarily rearranged without getting your document sent back. The inspection report format, for example, requires an executive summary, findings organized by area, recommendations with priority ratings, and management concurrence responses. You cannot skip the concurrence section even if you think the unit leadership will agree with everything. The concurrence block is where they formally accept or reject each recommendation, and that formal acceptance is what makes the document valid for tracking purposes. Without it, the inspection report is just someone's opinion with a fancy cover page. The biggest limitation of the handbook as a standalone resource is that it covers the ideal case. It does not address what happens when your organization has its own supplementary guidance that conflicts with the handbook, which happens more often than you would think. Some major commands issue command-specific supplements that modify or add to AFH 33-337 requirements. If you are deploying to a unit that operates under a different command, their supplement may override certain handbook provisions. The hierarchy is generally: statute, regulation, directive, handbook, and then command supplement. But in practice, people cite the handbook as if it is the final authority when it is actually near the bottom of that chain. Always check whether your gaining command has issued a supplement before you assume the base-level handbook version applies to you.

Another practical limitation is that the handbook does not keep pace with how people actually communicate anymore. The guidance on email is adequate but thin compared to what you would need for a modern workplace. Chat, video conferencing, shared documents, and project management tools are barely addressed. If your unit relies heavily on collaborative platforms, you will need to supplement the handbook with your command's social media and electronic communication policies. Those are usually found in separate publications that cross-reference AFH 33-337 but operate independently. The most useful section for day-to-day work is the correspondence and memo writing guidance, followed closely by the briefing preparation rules. Everything else is either niche-specific or overlaps with other publications. If you are going to keep a copy somewhere, bookmark the correspondence chapter and the appendix with the template examples. The templates save more time than any amount of reading about formatting theory, and that is the main value of this document. It is not a novel you read for enjoyment. It is a reference manual you open when you need to produce something that will not get sent back for corrections. The download link for the current version remains on the official AF e-Publishing site. Search for AFH 33-337 and you will find the PDF listed with the effective date. Make sure you are downloading the latest revision, because older versions circulate widely through unit websites and intranets and some of them contain superseded guidance. The revision history at the front of the document will tell you what changed, and the changes are usually material enough that using an outdated version will cause real problems.