Spell it out the first time

A rule — across professional, academic, legal and scientific writing, and the people in these conversations who work in those fields say so from experience rather than taste. Several separate conversations describe the convention the same way: write the full term the first time it appears, put the short form in brackets straight after it, and use the short form from then on. The major style guides require it; scientific journals often demand a separate list of every abbreviation used; in legal and government writing, stating a defined term on first use is the standard convention even when it seems obvious; and two conversations describe work being sent back — by a client, a supervisor, a reviewer — for nothing more than undefined initials. So the answer to 'am I being fussy?' is no. Two refinements the accounts add. First, only introduce the short form if you're going to use it again: if a term appears once or twice, one conversation's advice is to write it out every time and never abbreviate at all, because the bracket buys you nothing. Second, the order matters — full term first, short form second. Defining it afterward, one person notes, makes the reader carry an unknown until you get round to explaining it. A smaller stylistic point several people make: don't repeat the word the abbreviation already contains — an 'ATM machine' is a machine machine. And on the argument about words: technically an acronym is an abbreviation you say as a word and an initialism is one you spell out letter by letter, a distinction two conversations raise and a larger number find pedantic. Use whichever word you like; the rule applies to both.

It does depend, and the conversations say so plainly — this is the one place where the rule bends. If you're writing for specialists who share the vocabulary, spelling out every term is unnecessary and can read as condescending; one account calls it code-switching, and the test is whether the term is widely known within the specific group you're writing for, not whether it's known to you. The trouble, the accounts say, is that writers are poor judges of that. Across these conversations the same mistakes recur: internal company abbreviations that confused new employees for months; engineering and corporate shorthand that meant nothing to the client; a two-letter code that means one thing in a hospital, another in psychiatry, and a third in a bedroom; state and country codes that collide across borders; a fan community's terms landing in front of the general public. The pattern is that the writer knew the audience they imagined, not the one they had. So the honest version of the rule is: spell it out unless you're certain every reader shares the term — and when you're writing anywhere public or cross-disciplinary, assume you aren't certain. One more refinement from the accounts: sometimes the expansion is useless on its own. Spelling out a technical name in full can leave a general reader exactly as lost as the letters did, and one conversation's better move is a short functional definition — what the thing does — rather than the words the letters stand for. Some terms have become words in their own right and nobody needs the expansion; you know which those are because you've never had to look them up. And one fair defence of abbreviations from a dissenting account: they're how language stays efficient, and plenty of ordinary words began as shortenings. True — the rule isn't against short forms. It's against making the reader guess.

Two things, from the accounts who've been there. First, a search trick two separate people recommend: put the letters in quotes with a bracket — the abbreviation as it would appear right after being defined — and the search engine will often find a document where somebody spelled it out. Second, ask, out loud, early. The accounts describe whole fields where the jargon is dense enough that teams keep translation files just to onboard people, where a new member spends weeks decoding, and where — in one medical account — a department will reprimand staff for using shorthand while the department next door reprimands them for not using enough. In that environment nobody will think less of you for asking what the letters mean, and the person who explains them is usually relieved someone asked. One quiet observation from the conversations is worth carrying as a writer too: people tend to remember an abbreviation and forget what it stood for, so even the fluent insiders in your audience may be using terms they couldn't expand. The bracket costs you eight words. It saves someone else a search, a wrong guess, or the decision to stop reading — which, more than one account admits, is what they do when the third undefined abbreviation arrives.