A missed deadline, repeated customer complaint or ongoing quality issue may look straightforward at first. It rarely stays that way. Knowing how to document employee performance concerns gives managers a clear record of what occurred, what support was offered and what is expected next. It also helps protect the business if a concern develops into a formal performance process, disciplinary matter or employment dispute.
For Australian SMEs, the goal is not to create a paper trail for its own sake. It is to address issues early, fairly and consistently while giving the employee a genuine opportunity to improve.
Why performance documentation matters
Performance concerns are often handled informally at the beginning. A manager has a quick chat, provides a reminder or agrees on a changed approach. That can be appropriate, particularly for a one-off minor issue. The problem arises when the concern continues and there is no reliable record of what was discussed.
Without notes, managers can struggle to explain the history of an issue. Different managers may take different approaches, expectations can become unclear, and an employee may reasonably say they were not told there was a problem. This creates operational frustration and can increase risk if the business later needs to issue a warning, place someone on a performance improvement plan or consider termination.
Good documentation supports better management as well as better compliance. It helps you identify patterns, test whether expectations are realistic and confirm whether the employee has been given the tools, training and time needed to perform their role.
When to document employee performance concerns
Document concerns from the point they become more than a passing observation. You do not need a formal letter every time someone makes a minor error, but managers should keep a factual file note after a meaningful conversation about performance.
Examples include repeated lateness, failure to meet agreed targets, errors that affect customers or safety, incomplete work, poor quality outcomes, complaints about service, or an ongoing failure to follow a reasonable work process. Record the issue sooner where it has financial, safety, client or team impacts.
The level of formality should match the seriousness and history of the concern. An initial coaching conversation may only need a manager file note. Repeated concerns may require a documented meeting and written expectations. Serious issues may need specialist HR advice before the manager acts, especially where the facts are unclear or misconduct may also be involved.
Performance and conduct are not always the same thing. A worker who lacks the capability to complete a task may need training, supervision or a reasonable period to improve. A worker who deliberately refuses a lawful and reasonable direction may raise a conduct issue. Do not label the matter too quickly. The right process depends on the facts.
Start with facts, not conclusions
The most useful records are specific, objective and written close to the event. Avoid language that is emotional, speculative or personal. Saying an employee is lazy, difficult or not a team player does not explain what happened and may create unnecessary risk.
Instead, describe the observable behaviour and its effect. For example, rather than writing that Sam has a poor attitude, record that Sam interrupted two customers during a service call on 14 May, did not complete the agreed follow-up, and the customer lodged a complaint the next day.
A strong file note answers the practical questions a business owner, HR adviser or external decision-maker would ask: what happened, when did it happen, what standard applied, what evidence is available, and what was the impact?
Use documents that already exist where relevant, such as rosters, sales reports, quality checks, customer correspondence, timesheets, work orders or emails. Keep copies secure and only collect information that is relevant to the concern.
Record the conversation as well as the issue
Documentation should show that the employee had a fair chance to understand and respond to the concern. Before reaching a conclusion, meet with them privately, explain the issue clearly and ask for their perspective.
There may be information you do not know. The employee may have been given conflicting instructions, lacked access to a system, been covering additional work, or be dealing with a health issue that affects their capacity. You do not need to accept every explanation, but you do need to genuinely consider it.
After the discussion, record the employee’s response in neutral terms. Note any explanation, relevant evidence they identify and whether they accept or dispute the concern. If they raise a medical condition, injury, workplace adjustment or other sensitive issue, pause before taking further action and obtain appropriate HR advice.
Your notes should also confirm what support was offered. This may include refresher training, clearer instructions, a buddy shift, regular check-ins, adjusted priorities or access to a required system. A fair process is not simply about identifying what went wrong. It is about setting the employee up to meet a clear standard.
Use a consistent file note structure
A simple, repeatable format makes it easier for managers to keep records that are useful later. Each note should include:
- the date, time and location of the incident or meeting
- the people involved and anyone who witnessed the event
- the specific behaviour, work outcome or missed expectation
- the relevant role requirement, policy, procedure or agreed target
- the impact on customers, safety, quality, cost or the team
- the employee’s response and any explanation provided
- the support, direction and improvement actions agreed
- the review date and the consequences of failing to improve, where appropriate.
Write the note as soon as practical, while details are fresh. If you send the employee a follow-up email, make it concise and accurate. It should confirm the key expectations and next steps, not introduce new allegations or use threatening language.
Set clear expectations and realistic review points
A record of a concern is only useful if the employee knows what improvement looks like. Vague directions such as improve your communication or be more proactive are difficult to manage and difficult to measure.
Be specific. For a retail team member, that may mean completing the closing checklist before leaving each shift for the next four weeks. For a project coordinator, it may mean providing an accurate project update by 3 pm each Friday and escalating delays within one business day. For a trades business, it may mean submitting completed job records by the end of each working day.
The appropriate review period depends on the role and issue. A simple attendance or process concern may be reviewed quickly. A capability issue involving complex technical work may require more time, training and scheduled support. Set a date to review progress, then hold the review even if the employee has improved. Consistency matters.
If the concern continues, document the further discussion and explain the next step. That could be additional coaching, a formal warning or a structured performance improvement plan. Avoid making outcomes up as you go. Your approach should align with the employee’s contract, workplace policies and the circumstances of the case.
Keep records confidential and separate from assumptions
Performance records contain personal information and should only be accessed by people who need it for a legitimate management or HR purpose. Keep notes in a secure personnel file rather than in a manager’s personal notebook, open inbox or informal team chat.
Do not include gossip, unrelated personal observations or unsupported claims. If another employee raises a concern, record what they said, when they said it and what steps you took to verify it. Do not present an allegation as fact before you have properly considered it.
Managers should also avoid changing historical notes without a clear explanation. If new information becomes available, create a dated follow-up note rather than rewriting the original record. Accurate records are more credible than records that appear polished after the fact.
Common documentation mistakes to avoid
The most common mistake is waiting until the business has had enough. By then, the employee may have had months of mixed messages and no clear opportunity to improve. Address concerns early and document the important conversations.
Another mistake is relying on generic statements. A warning that says performance is unsatisfactory, without examples, expectations or support, gives little guidance to the employee and little protection to the business. Equally, do not over-document every minor interaction in a way that feels punitive. The record should be proportionate and relevant.
Finally, do not assume that a written warning automatically makes a later dismissal safe. Fair Work obligations, procedural fairness, the employee’s length of service, the seriousness of the issue and any mitigating circumstances can all matter. A technically neat file is not a substitute for a fair and considered process.
A practical example
A hospitality manager notices that a supervisor has submitted incorrect stock orders three times in six weeks, resulting in shortages during busy services. Rather than writing that the supervisor is careless, the manager records each order date, the items affected, the resulting shortages and the expected ordering process.
At a private meeting, the manager explains the pattern and asks for the supervisor’s response. The supervisor says the ordering platform was changed and they did not receive training on the new approval screen. The manager documents this explanation, arranges training, provides a checklist and sets a two-week review period. The follow-up email confirms that future orders must be checked against stock levels and submitted by the agreed deadline.
If the errors stop, the business has managed the issue constructively. If they continue after appropriate support, the business has a clear foundation for a more formal process. In either case, the manager has acted fairly and has evidence of the steps taken.
When performance concerns become repeated, sensitive or high-risk, getting advice before issuing formal documentation can prevent a manageable issue from becoming an expensive one. The HR Department Consulting Group can help SMEs put clear, practical processes in place so managers can act with confidence when it matters.