A write-up is not a place to vent. It is a contemporaneous record of a specific workplace event, the rule that applied, the employee’s response, and the action the company chose. For a cleaning, security, landscaping, pest, or HVAC company, the document may later be read by an unemployment agency, a lawyer, a regulator, or a jury that does not know the supervisor’s shorthand.
Good documentation is fair to the employer and the employee. It distinguishes a missed checkpoint from a missed punch, an unsafe act from a language misunderstanding, and a customer complaint from a proven performance failure. The National Labor Relations Board’s Section 7 framework also matters: an employer cannot use discipline to punish protected concerted activity simply because the complaint was inconvenient.
Start with the event, not the label
Write what happened, when, where, and how the company learned it. “Bad attitude” is a conclusion; “the employee left Building 4 at 10:18 p.m. before the assigned restroom checklist was complete, according to the supervisor’s inspection and the client’s photo log” is an event that can be investigated. Identify the building, shift, assignment, witnesses, system record, and any safety or customer impact.
Avoid exaggeration and borrowed conclusions. If a worker was late, record the scheduled start, actual arrival, notice given, and whether the site was accessible. If a guard missed a patrol, distinguish a missing checkpoint from a device failure. StockPoint’s photo, PIN, and GPS-with-honest-accuracy record can help establish a field event, but the write-up should say what the record shows and what it cannot prove.
What a defensible write-up contains
A useful document normally states the date of the incident, the policy or expectation, the factual description, the employee’s explanation, prior related coaching if relevant, the corrective action, the support or training offered, and the next step if the conduct repeats. Include the investigator or supervisor and the date written. If a policy was not provided to the employee, say so and correct the onboarding process rather than pretending the employee had notice.
The employee should have a meaningful opportunity to respond. Provide a language-accessible explanation for a worker who prefers Spanish, allow a reasonable response period, and attach the response without editing it to make it sound more favorable. An employee signature acknowledges receipt, not necessarily agreement. If the employee refuses to sign, document the refusal with a witness; do not forge a signature or treat refusal alone as insubordination.
Consistency is evidence
A company that disciplines one cleaner for a missed punch but ignores the same conduct by a favored supervisor creates avoidable risk. Review comparable cases by role, location, seriousness, prior notice, and actual harm. Consistency does not require identical outcomes when facts differ, but the difference should be explainable. Keep the decision-maker’s reasoning in the file.
The same principle applies to bilingual teams. Do not translate discipline for Spanish-speaking workers while leaving English-speaking workers with informal coaching that never enters a file, or use language proficiency as a proxy for reliability. The EEOC’s national-origin guidance is relevant when discipline, assignments, or advancement differ because of national origin or language. A bilingual workflow should make expectations clearer, not create a second standard.
Separate performance from protected complaints
A worker who reports unpaid time, a missed break, discrimination, unsafe chemicals, or a suspected violation may be protected by federal or state law. The FLSA’s anti-retaliation provision, EEOC retaliation principles, OSHA protections, and NLRB Section 7 rights can overlap depending on the complaint and the worker’s conduct. Discipline may still be appropriate for unrelated misconduct, but timing and decision-maker knowledge will be examined.
Before issuing a write-up soon after a complaint, require a second-level review. Compare the proposed reason with prior practice and the underlying records. Ask whether the same conduct would have been documented absent the complaint. Do not label a group complaint “insubordination” merely because several workers raised the same pay or safety concern; NLRB guidance on protected concerted activity should be part of the review.
A field-service example
Suppose a supervisor reports that a cleaner left a building 20 minutes early. The first question is not whether to write “abandonment.” Check the assigned scope, the building access log, the punch, the checkpoint list, client messages, whether the area was inaccessible, and whether a manager released the employee. Ask the employee what happened and preserve the answer.
If the records show the employee left after completing the assigned work and the supervisor had changed the scope by text, coaching about change communication may be appropriate. If the employee left because a chemical spill made the area unsafe and reported it, the response should address hazard handling, not punish the report. If the employee simply left without authorization after prior notice, a documented step in the policy may be justified. The write-up should reflect the evidence rather than the supervisor’s first assumption.
StockPoint can connect the assignment, building proof, correction, and supervisor review so the manager is not drafting from memory. Its audit log should preserve edits and approvals. That does not make the conclusion correct automatically; it makes the path to the conclusion visible.
Progressive discipline is a process, not a staircase
Progressive discipline commonly moves from coaching to written warning to final warning or termination, but a serious safety, violence, fraud, or harassment matter may justify a different response under the policy and law. State the range accurately and reserve discretion for serious cases. Do not promise “three strikes” if the handbook does not say that.
Each step should identify the improvement required, who will support it, and when the company will review progress. “Be better” is not a measurable expectation. “Use the assigned per-building punch before beginning work, report an inaccessible room through the app, and meet with the supervisor at the next two shifts” is clearer. If the worker lacks a phone, training, transportation, or safe equipment, address that barrier before treating the failure as willful.
Retention and access controls
Retain write-ups according to the company’s schedule, applicable law, contract obligations, and any litigation hold. Keep the personnel record separate from a complaint investigation when that separation protects confidentiality or reduces unnecessary disclosure. Limit access to people with a business need, and record when a correction is made.
A late correction should never erase the earlier version. Keep the original, the revised text, the reason, the approver, and the date. StockPoint’s audit log and per-worker payroll lock can support this approach for field events and payroll records, but HR should use a dedicated personnel-record policy and secure access. Bank-feed reconciliation is on the roadmap, not shipped, and is unrelated to the disciplinary record.
Build the evidence before the meeting
Before meeting with the employee, gather the assignment, schedule, punch, checkpoint or inspection record, client message, prior coaching, and applicable policy. A supervisor should be able to explain why each item matters and should remove material that is only rumor. If a system record is incomplete, say that it is incomplete and ask questions; do not turn a missing field into proof of misconduct.
For a worker who prefers Spanish, arrange an interpreter or bilingual reviewer who understands the policy and the limits of interpretation. Record the language used, the people present, the documents provided, and the employee’s response. A translated meeting is not a concession and an English-only meeting is not automatically fair because the worker signed an English handbook. The company should be able to show that the expectation and the response opportunity were usable.
If the incident involves time, compare the proposed discipline with payroll. A worker should not be disciplined for a “late” arrival when the company required an earlier unpaid equipment check, and a supervisor should not edit a punch to make an attendance problem disappear. StockPoint’s shared punch source and audit history can show the event and correction path, while per-worker payroll locking prevents a closed period from being paid again during a dispute. Keep the HR conclusion separate from the payroll calculation.
Close the loop after discipline
After the meeting, give the employee a copy and state the next review date. A write-up that sits in a file without follow-up teaches supervisors that documentation is ceremonial. At the review, compare the defined expectation with actual work, provide coaching or equipment support, and record whether the issue improved. If the company changes the expectation, issue the change clearly instead of judging the employee against a moving target.
Keep client pressure out of the personnel conclusion. A facility manager’s complaint can be an important lead, but the employer should verify what was observed, whether the scope was clear, and whether the worker had time and tools to perform it. StockPoint’s client portal can provide checkpoint status and proof-of-work photos, while the employer’s HR process determines whether coaching or discipline is fair. The two records should be connected but not confused.
The final review before delivery
Before giving a write-up to the employee, ask whether a neutral reader could identify the event, rule, evidence, response, corrective action, and next step. Remove adjectives that do no work. Check dates, names, building IDs, and attachments. Confirm the employee can understand the document and has a channel to respond.
Then ask a second reviewer whether the action is consistent and free of retaliation or discrimination concerns. A manager should not be the only person judging an incident in which the manager is a witness or subject of the complaint. Document the review without turning it into a vote about the employee’s character.
A complete file should also show what the employee was told about future expectations and how to request a correction. That is especially important when the issue involves a building access failure, a client-directed change, or a pay-related complaint. Clear next steps give the employee a fair path to improve and give the company a record that its process was not merely punitive.
Owners can pair this process with StockPoint’s features and the guide to employee complaint logs. StockPoint can keep field evidence, bilingual instructions, payroll corrections, and audit history together so a write-up is based on a verifiable event. To give supervisors that record and a clearer response workflow, sign up at getstockpoint.com.