Email as the default record, and its norms

The default written channel

Email is where most workplace writing happens: the request, the confirmation, the forwarded file, the reply that becomes the record of what was agreed. Smith's channel table lists its strengths — instant, to one or many, attachments, a thread archived for years — and its one disadvantage that matters more than the rest: the illusion of privacy. An email can be forwarded to anyone, monitored by the firm, retrieved under a warrant, or hacked — even if both sender and receiver have deleted it. So two facts sit under every rule in this module. Email represents you and the firm in your absence: the reader forms a view of your competence from the message alone. And email is permanent: assume every message will be forwarded and read by someone it was not addressed to.

Worked example — the message that came back

A junior analyst at a Kitchener advisory firm, three weeks into a stock-count engagement, emails a colleague: honestly the client's warehouse records are a MESS, I'd guess half of what they told us is made up, going to be a long month lol. The colleague forwards it to the engagement manager with a question about scope; the manager, replying to a query from the client's controller, forwards the thread without reading to the bottom. Three weeks later the client disputes the fee, and the analyst's sentence is quoted back in a meeting. Notice what went wrong: not the forwarding — that is normal — but the writing. "Made up" is an unsupported claim about a client's honesty in writing; "a MESS" in capitals reads as shouting; "lol" and "I'd guess" belong in a text to a friend. The professional version was available in the same number of words: The warehouse records have gaps — about half the bin counts we sampled could not be traced to a source document. I will need an extra week; can we discuss scope on Monday? That sentence can be forwarded to anyone.

The 24-hour norm

Reply within 24 hours — Smith's table says so, and adds "or sooner if company policy requires it"; some workplaces expect a reply within about two hours in business hours, and Olds gives the same 24-hour rule with a promise within 48 hours. The rubric-safe form: if you cannot answer in that window, acknowledge and promise a time — I have your three questions on the lease and will reply with the figures by Thursday noon. Silence past a day is read as a decision.

Netiquette and the legal facts

Smith adopts Virginia Shea's rules of netiquette, which reduce to one — be as kind online as you should be in person — and the practical forms of it: no ALL CAPS (shouting), no text abbreviations (u, b4, thx, lol), no emoji to a manager or client, no email written angry (L8.4's cool-down rule). The legal facts: your writing can commit the firm; an exaggeration, a false claim about a competitor's product, or a statement that defames a person or a company carries liability; and, deleted or not, a message is discoverable in a dispute. The test for any sentence: would you be content to have a third party — the client, a lawyer, your manager — read it? If not, it does not go in an email.

Judge five behaviours

Replying to a client's Tuesday question on Friday — breaks the norm; acknowledge Tuesday, answer by a promised time. Deleting an email that criticised a supplier — it is still on the supplier's server, the firm's backup and the thread; assume permanent. Writing "URGENT!!!" in capitals in the body — shouting; state the deadline instead. "Can u send the file b4 3?" to a partner — text register; L8.4. Forwarding a client's email to a colleague who needs it — fine, and normal; that is why you write every email as though it will be.

State the norms cold

Reply in 24 hours, or acknowledge and promise a time. Email is permanent and discoverable — write nothing you would not want a third party to read. No capitals, no abbreviations, no anger; it represents you and the firm when you are not in the room.