A worker complaint intake log with clear role boundaries

A complaint intake log has a narrow purpose: record that a concern was received, capture the minimum facts, and route it to the owner who will handle it. The log is not an investigation file, a performance record, or a place to debate whether the concern is valid. Writing the purpose down helps the team resist the temptation to add opinions and speculation. Keep the purpose statement at the top of the log so every new intake owner reads it before entering a case.

The log should also state what it does not cover. A safety emergency, a suspected crime, or a threat of violence may require an immediate call rather than a log entry. Name those paths in the procedure and make sure the intake owner knows them. A log that becomes the only channel for urgent concerns can delay a response that should have been immediate.

Record the date and time the concern was received, the channel, the person who received it, and the worker who raised it. Capture the concern in the worker's own words when possible, and mark any summary as a summary. Record the people or events named, the location, and the date of the conduct described. Do not add facts the worker did not provide.

Ask only the questions needed to route the concern. A long intake interview can turn an untrained coordinator into an investigator and can create a record that is later hard to correct. If the worker wants to provide more detail, record it as an attachment or a follow-up note. Keep the original entry unchanged and add new information with its date and source.

The person who receives a complaint should not also decide the outcome. Intake is an administrative step; investigation is a separate role with its own training and authority. Record who received the concern and who was assigned to review it. If the same person must do both because of team size, document the conflict and have a second person review the conclusion.

The intake owner can confirm that the concern was received, explain the next step, and give the worker a point of contact. The owner should not promise a particular outcome, a timeline that has not been approved, or confidentiality that the process cannot guarantee. Those promises may be well intentioned, but they can damage trust when the process takes a different path. Use a short script that states what the process can do and who will follow up.

Complaints often contain sensitive personal information, and the log should be restricted to the people who need it. Use the approved system rather than a shared spreadsheet, and limit access by role. Do not discuss the details in a group chat or copy them into an unrelated email thread. Record who accessed the file and why if the system supports it.

Tell the worker what the process can and cannot keep private. An intake owner should not promise absolute secrecy if the employer has a legal or policy obligation to act on the information. Explain that the concern will be shared with the people who need to review it and that retaliation is prohibited. Give the worker the approved channel for follow-up questions.

Every open complaint should have an owner, a next step, and a date. The log should show how long the concern has been open and whether it is waiting on the worker, the reviewer, or another function. An aging report helps the team see whether a concern is stuck without reading every entry. It also gives the owner a reason to update the record.

Do not close a complaint because the worker stopped responding without following the employer's procedure. Record the attempts to contact the worker and the date of the last attempt. The owner decides whether the concern can be closed or must remain open. A closure that is not documented looks like an ignored concern even when the team did the right thing.

Some concerns require an immediate route rather than the standard queue. A threat of violence, a safety hazard, a report of harassment by a manager, or an allegation involving a senior leader may need a different owner. The procedure should name those categories and the contact path for each. The intake owner should not wait for a weekly review.

If the concern involves the intake owner or the owner's manager, route it to the next approved contact. Record only the fact of the routing and the destination, not the details, in the general log. The restricted record should stay with the authorized reviewer. A clear escalation path protects the worker and keeps the process credible.

The log can show patterns that individual cases do not. A cluster of concerns about the same schedule, supervisor, or worksite may point to a process problem rather than a series of isolated events. Review the categories and the locations, not the identities, and look for repeat themes. Share the pattern with the owner who can act on it.

Do not use the pattern review to reopen a closed case without a reason or to label a worker as difficult. The goal is to improve prevention and response. Choose one change based on the most common gap, such as a clearer intake form, a faster route for urgent concerns, or a reminder about retaliation. Record the change and the date it will be reviewed.