Put an awkward conversation in writing

Most awkward requests start out spoken. You mention the leak to the building manager in the lobby. You tell your manager in the corridor that you're stretched. You knock on a neighbor's door and say the music is a bit loud. Everyone nods, and two weeks later nothing has changed.

The next step is to put it in writing, and that is where people get stuck. A written message feels formal, maybe hostile, and it's permanent. So you draft three versions, delete them, and decide to wait one more week.

This guide is about that second message: the one that turns a conversation people forgot into a short note they can't misread. You get three prompts from the book, one each for work, home repairs and neighbors, plus how to fill them in, what a good draft looks like, and where you still need to use your own judgment.

Why the spoken version didn't stick

A spoken request has no date, no detail and nothing that holds anyone to it. The other person remembers the gist, if anything, and remembers it in the version that suits them best. Your manager remembers you were fine with it. The landlord remembers a small drip. The neighbor remembers a friendly chat, not a request.

Writing fixes three things at once. It pins down what you asked for and when. It gives the other person something concrete to answer. And it leaves a record you can point to if this becomes a bigger problem later.

The danger is that writing also magnifies tone. If you sound annoyed, the annoyance is in writing too. If you apologize three times, your request reads as optional. That's why a vague prompt like "write an email to my landlord about the sink" tends to give you either a limp, over-polite note or a stiff letter that sounds like a lawsuit. The prompts below fix both problems by telling the chatbot the tone, the length and what the message has to achieve.

At work: you said you were busy, now say it properly

Here's the usual pattern. Someone drops a new task on you in a meeting or a passing chat. You say something like "I'll try" or "I'm pretty full right now." They hear yes. A day later the task shows up in your inbox as if it had been agreed.

The written reply has a job to do. It shouldn't refuse and it shouldn't complain. It should hand the decision back to the person who has the authority to make it: if this new thing matters more, something else slips. This prompt is built around exactly that framing.

Draft a concise, professional email responding to a work request that exceeds my current capacity.
Context:
- Sender: [Manager's Name / Colleague's Name]
- Incoming Request: [Briefly describe the requested task, e.g., Take over the quarterly client audit report]
- Current Priority: [Describe your existing primary deliverables, e.g., Completing the Q3 software migration rollout by Friday]
- Boundary: [Cannot take this on without delaying primary deliverables / Do not monitor emails after 6:00 PM]

Constraints:
- Tone: Professional, collaborative, calm, and firm.
- No unnecessary apologies (do not use "I'm sorry" or "Unfortunately").
- Frame the situation as a priority trade-off decision for the sender rather than personal unwillingness.
- Keep the length under 100 words.

Fill Incoming Request with the task in their words, not yours, so they recognise it. Put one deliverable in Current Priority, with its deadline. A list of five things reads as a grievance, and one dated commitment reads as a fact. For Boundary, choose the line you will actually hold. If you'd take the work as long as the deadline moves, say so.

A good draft is short, names the trade-off in plain numbers ("this would push the migration back about three days") and ends with a choice for them. Take out any estimate you can't defend. Chatbots like to invent a precise delay, so swap in your real one. If the draft still slips in an apology, delete it. The prompt forbids that, but check anyway.

At home: the repair you reported once already

Repair requests are where the spoken-then-written gap costs the most. If you told the building manager in person, or sent a quick text, there may be no clear record of when they first knew. If the damage spreads, or you later need to show you reported it promptly, that date matters.

So the escalation email has two jobs: get a technician scheduled, and put the earlier report on record in the same message. The prompt below asks for both, and it asks for written confirmation of the appointment, which is the detail most people forget.

Draft a formal, polite maintenance escalation email to a property manager or landlord.
Details:
- Recipient: [Landlord / Property Management Company Name]
- Property Address: [Unit Number and Street Address]
- Maintenance Issue: [Describe issue, e.g., Water leaking under the kitchen sink]
- First Reported Date: [Date of initial report, e.g., October 12th via text]
- Impact: [Describe functional or safety impact, e.g., Unable to use kitchen sink; risk of cabinet wood rot]
- Required Action: [Request scheduled repair technician within 48 hours]

Constraints:
- Tone: Civil, objective, fact-focused, and legally clear.
- Explicitly establish a written record of previous notifications.
- Request written confirmation of the repair appointment date and time.
- Keep under 120 words.

Be exact in First Reported Date: the date and the channel, such as "told the on-site manager in person on the 12th" or "texted on the 12th." If you reported it several times, list each one briefly. Describe Impact as function and risk, not frustration: what you can't use and what might get damaged. For Required Action, set a deadline that's reasonable for the problem. Forty-eight hours fits a leak. Next week fits a sticking cupboard door.

Expect a short, neutral email that restates the facts, asks for a confirmed date and arrival window, and stops there. Check every date and detail against your own notes before you send it, because the chatbot only knows what you typed. Send it through whatever channel your lease or building names for maintenance requests, and keep a copy.

Next door: the knock that didn't change anything

With neighbors, the spoken version often failed because it was too gentle. "No worries, just thought I'd mention it" doesn't sound like a request. Or you never said anything at all, and now the note feels like a big step.

A written note works best when it reads as information, not a complaint. Most people honestly don't know how much sound gets through a wall or a floor. The prompt assumes they don't, which keeps the note friendly while still asking for something specific.

Draft a polite, friendly, but direct written note to a neighbor regarding recurring noise.
Details:
- Specific Issue: [Describe noise, e.g., Loud television bass / dog barking late at night]
- Timing: [Specify hours, e.g., Between 11:00 PM and 2:00 AM on weeknights]
- Impact: [Brief neutral impact, e.g., Wakes up family members / disrupts sleep before workdays]
- Goal: [Request volume reduction during designated quiet hours]

Constraints:
- Tone: Neighborly, empathetic, calm, and non-accusatory.
- Assume good intentions (assume they are likely unaware of sound transfer between units).
- Provide a polite closing that leaves room for open communication.
- Length: 60 to 90 words.

Put real hours and days in Timing. "Late at night" invites argument, while "between 11 and 2 on weeknights" doesn't. Keep Impact to one neutral clause about sleep or work. In Goal, name a concrete ask, such as a time after which the volume goes down, or headphones, or moving the speaker off the shared wall.

The draft should be short enough to fit on a card, mention how sound carries, make one request and leave a way to reply. Decide whether you want to include contact details before the chatbot adds a placeholder for them. A note under the door is fine to send as is. If you've already knocked once, add one line saying so, kept light: "Following up on my knock last week."

Before you hit send

Read the draft out loud once. If any sentence would be awkward to say to the person's face, soften the wording but keep the request. If any sentence makes the request sound optional ("only if it's no trouble"), cut it.

Check that the message has one clear ask and, where it fits, one date. The person reading it should know what you want and by when without reading it twice.

Keep a copy. For work and repairs, sent email does this for you. For a paper note to a neighbor, take a photo before you deliver it. You'll probably never need it, but if you do, you'll be glad you have it.

Finally, plan the next step before you send, not after. If the landlord doesn't confirm by your deadline, or the noise carries on for another week, decide now whether you'll follow up again, call, or go to the building manager or your tenancy agreement. You don't have to say this in the message. It just helps you stay calm when nothing happens straight away.

What this cannot do

• It doesn't give legal advice. The repair email creates a tidy record, but it won't tell you what your landlord is required to do, how fast, or what you can do if they don't. Those rules depend on where you live and on your lease. Check your local tenant resources before you withhold rent or arrange repairs yourself.
• It only knows what you tell it. Dates, deadlines and how long things will take come from you. If you guess, the email will state your guess as fact, so check every number.
• It can't read the relationship. A firm note that suits a property company might be too blunt for a small landlord you get on well with. A note to a neighbor you've already argued with might need a different approach entirely. Adjust the tone yourself.
• It won't make anyone respond. A clear written request makes a reply more likely and makes it harder to ignore you without consequences. It doesn't guarantee either.
• It isn't for real danger. Gas smells, electrical faults, flooding or threats from a neighbor call for the relevant emergency line or authority, not a polite email.

Related reading

• Stop Typing, Start Asking — full first chapter, free, no email required
• Full contents and what is included
• Three put-off emails, each under 120 words
• Turn dense paperwork into a checked action list
• All Avalon Store products