GullyHR designs and delivers this programme around the writing your business actually sends. We read a redacted sample of your mails, reports and notes, agree the standard you want people writing to, build the exercises from your own situations, facilitate the sessions, mark what participants produce, and hand over the templates and checklists they keep using. You supply the sample writing, nominate and release participants, name the manager who will hold the standard afterwards, and approve the standard itself. It runs as a customised training programme against a scope agreed before we start.
An email is built before it is typed.
A subject line that states the matter and the action, an opening sentence carrying the request, the reason placed after the ask rather than before it, a stated date, and a deliberate decision about who is on To and who is only on Cc.
Business writing puts the point first.
Writing for a reader who is skimming on a phone: purpose at the top, background kept short, one idea to a paragraph, filler removed, and a clear difference between writing to inform, to request and to put something on record.
A report is written to be read from the top down.
Opening with the finding and the recommendation and supporting it afterwards: the summary paragraph, the structure beneath it, what belongs in a table rather than a sentence, and writing for the reader who will only read the first section.
Meeting notes record decisions, not conversation.
Separating discussion from decision, writing each action with an owner and a date, noting what was deferred and why, circulating while people still remember the meeting, and keeping notes short enough that they get read at all.
Etiquette decides who is marked and when you reply.
Salutations and sign-offs that suit the reader, what a reasonable reply looks like when the answer is not ready, when marking a senior is escalation and when it is only habit, forwarding a thread responsibly, and when to stop typing and pick up the phone.
Tone is the part the reader remembers afterwards.
Saying no without giving offence, chasing a delay without accusing anyone, giving bad news early, apologising once and properly, writing while annoyed and then reading it back before sending, and hearing how a sentence lands on someone senior.
Customer writing is your company speaking.
Acknowledging an enquiry, sending a quotation with terms stated plainly, telling a customer about a delay before they ask, replying to a complaint without arguing, and following up without sounding either apologetic or aggressive.
Internal writing has to survive the trip to another department.
Requests a colleague in another function can act on without a call, updates a busy senior can read on a phone between meetings, handover notes someone can work from in your absence, and group mail that does not go to everyone by default.