Why the warning needs to be in writing
Inside a company with an HR department, a performance problem triggers a process automatically: a documented conversation, a formal warning on file, a defined escalation path. When you hire a remote assistant directly, none of that machinery exists, and so most direct employers handle problems the informal way: a slightly tense message, a hopeful wait, another tense message a month later. Nothing is written down, and so six months later nobody can say what was actually asked for, when, or how many times.
A written warning fixes that in one page. It records what the concern is, what evidence it rests on, what standard is expected, and what happens next, which is exactly the set of facts a later disagreement would be about. It protects your assistant as much as you: a person can only fix a problem that has been stated precisely, and a warning with dates and examples is something they can measure themselves against, where "I need you to step it up" is not. And if the engagement does eventually end over performance, the fair sequence is on record: the problem was named, the standard was clear, and time was given.
There is a discipline benefit for you too. Writing the letter forces you to check whether you actually have specifics, or just a mood. If you sit down to fill in the examples box and find you cannot name one incident with a date, that is worth knowing before you send anything, because it usually means the real problem is vaguer than a warning can carry: a mismatch of expectations that a conversation, or a clearer written process, would fix better.
Before you write: is a warning the right step?
The warning letter is the second tool, not the first. The first is an honest conversation, ideally inside the regular one on one rhythm where problems surface while they are still small. Most performance issues die in that conversation: the brief was unclear, the workload was silently impossible, something at home went wrong for a month. A formal warning about something you have never actually said out loud reads as an ambush, and it burns trust you will want later. The letter this tool writes assumes the conversation happened, and says so in its opening line.
It is also worth being honest about which tool the situation needs. If the problem is one specific, recent, fixable thing, missed deadlines, a quality slip, unanswered messages, a written warning is proportionate. If performance has slipped across the whole role, or a warning has already come and gone without change, the performance improvement plan is the better instrument: a structured 30 to 90 days with milestones, check-ins, and support commitments. And if you already know, honestly, that the engagement is over, a warning you do not mean is worse than none; the termination letter handled cleanly is fairer than a paper trail built for appearances.
One classification note worth taking seriously: most directly hired South African assistants work as independent contractors, and a contractor relationship is governed mainly by the written agreement rather than by employment law and its disciplinary procedures. That cuts both ways. You are usually not legally required to run a warning process before ending a contractor agreement with notice; you are choosing to, because fixing a known-good person is cheaper and kinder than replacing them. But the label on the agreement is not the whole story in any country, and a long-running, exclusive, closely directed arrangement can carry employment obligations in substance. This page is a writing tool, not a legal opinion; if your situation is contested or unusual, spend an hour with someone qualified.
The anatomy of a fair written warning
Open with what the letter is, stated without hedging: a formal first, second, or final written warning, following the conversation you had. The level should be honest. A first warning that arrives styled as final reads as a threat; a fifth incident still being called a first warning teaches that the warnings mean nothing. If there was a previous warning, name its date, so the sequence is on the record.
Then the concern, in one sentence, and the specifics, in a list. This list is the whole difference between a fair warning and a vague one. "The client report due Friday 10 July arrived on Tuesday 14 July with no heads-up" is something a person can accept, dispute, or fix. "Your work has been sloppy lately" is an accusation with no handle on it. Dates, deliverables, and impact; adjectives left out. If you find the list hard to write, that difficulty is information.
The second half of the letter looks forward, and it is where the warning earns its keep. Set out the standard the role needs in observable terms: the generator seeds a standard for eight common assistant roles, and the items specific to your setup, the Friday report, the response time, belong in the box above. Give a review window, so improvement has a timeline instead of a vibe. State next steps with both outcomes: what resolves the warning, and what follows if nothing changes, whether that is a further warning, a structured plan, or, at final level, the end of the agreement under its notice terms. Then invite their side in writing, ask about blockers on your side of the fence, unclear briefs, workload, overlap hours, connectivity, and close by asking them to confirm receipt, with the explicit note that receiving is not agreeing. Every one of those elements is fairness you will be glad of later.
Delivering it, and what happens after
A warning letter should never arrive cold. The decent sequence is a short call where you say the concern plainly and hear their side, then the letter the same day as the written record of what was discussed. Time zones make the call easier than most employers expect: South Africa sits at UTC+2 with no daylight saving, so a morning call from the US or an early-afternoon call from Europe lands inside their working day. Fifteen undistracted minutes, the concern in the first minute, and no talking over the silence that follows it.
Then manage the aftermath like it matters, because it does. Watch the review window you named, and use your regular check-ins to track it; a warning followed by managerial silence tells the person you either did not mean it or were building a file. If the standard is met, say so, in writing, with the same formality the warning had: "I consider the warning resolved" is one sentence, and it converts a bad month into a story about a problem that got fixed. People do their best work for employers who close loops.
If the standard is not met, follow the path the letter promised: a further or final warning, or the structured improvement plan with its milestones and support commitments. And if that fails too, the engagement ends the way the documents always said it would: the termination letter citing an honest reason, the offboarding checklist run properly, and nothing in any of it a surprise. That is what fair looks like in practice: not the absence of hard outcomes, but the absence of ambushes.
Where the warning letter fits in your toolkit
This letter sits in the middle of the difficult-documents chain this toolkit builds. Upstream of it, the one on one agenda catches problems while they are still conversation-sized, and the performance review measures the whole role on a schedule. Downstream, the improvement plan is the structured escalation, and the termination letter is the end of the line. The warning is the hinge between the informal and the formal: the first document, and, when it works, the last.
It works best when the standards it points to already exist in writing. A warning about process is only fair if the process is documented, which is what the SOP generator is for; a warning about availability is only fair if the remote work policy actually says what hours and response times were agreed. Half the value of writing the warning is discovering which of those documents you skipped, and fixing that at the same time.
And remember that the chain has a happy branch. Most warnings, delivered early and fairly, get resolved, and an assistant who worked through a rough patch with an employer who was straight with them tends to become a loyal one. When the review after the turnaround goes well, the salary increase letter documents the other kind of outcome. An employer with both letters in their toolkit, and the judgment to know which one the moment needs, is the kind worth working for.
Written warning letter FAQs
How do I write a written warning letter to an employee or contractor?
Keep it factual and fair. Open by saying plainly that the letter is a formal written warning following a conversation you have already had. Name the concern in one sentence, list the specific examples with dates, set out the standard you need going forward, give a review window, and state honestly what happens if nothing changes and what resolves the warning. Close by inviting their written response and asking them to confirm receipt. The generator on this page assembles exactly that structure; your job is to supply the true specifics.
What is the difference between a written warning and a performance improvement plan?
Scope and weight. A written warning is a short letter that documents one concern, the standard required, and the consequences of no change; it is the right tool when the problem is specific and recent. A performance improvement plan is a structured 30 to 90 day program with milestones, scheduled check-ins, and support commitments; it is the right tool when performance has slipped across the board or a warning has not worked. A common fair sequence is conversation, then written warning, then improvement plan, then, only if all of that fails, ending the engagement.
Do I need to give a verbal warning before a written warning?
It is almost always fairer, and it usually works better. Most performance problems are fixed by one honest conversation, which costs nothing and preserves the relationship. The written warning exists for the cases where the conversation did not fix it: it turns what was said into a record both sides can check. Sending a formal warning about something you have never actually raised face to face tends to feel like an ambush, and the letter this tool writes assumes the conversation happened first.
Can I give a written warning to an independent contractor?
Yes, and for a directly hired remote assistant it is often the fairest tool you have, but the legal frame differs from employment. An employee warning usually lives inside a formal disciplinary process regulated by employment law. A contractor relationship is governed mainly by the written agreement, which typically lets either side end it with notice; the warning letter is you choosing to fix the problem rather than exercising that clause. Note that the label on the agreement is not the whole story in law, so if your arrangement looks like employment in substance, take proper advice.
What happens after a written warning?
One of two things, and the letter should say both in advance. Either the standard is met and sustained, in which case tell the person clearly that the warning is resolved; leaving it hanging forever is its own kind of unfairness. Or the problem continues, in which case the next step is a further or final warning, a structured performance improvement plan, or ending the agreement in line with its notice terms. The whole point of putting the sequence in writing is that nothing that happens afterwards is a surprise.
Is this warning letter generator free, and is anything stored?
Completely free, no signup, no watermark, and nothing you type is stored or sent anywhere; the whole tool runs in your browser. Pick the warning level and the concern, add your specific examples with dates, choose the sections you need, and copy the finished letter into a document to sign. Pair it with the one on one meeting agenda generator for the conversation and the performance improvement plan generator if the warning needs to escalate.