Worker Grievance Handling: A Factory Case Log with Clear Follow-Up

A complaint needs an owner and a checked outcome

A worker reports that a locker will not close. The welfare officer tells maintenance, which orders a latch. The weekly report then says the matter is complete. Yet the worker still cannot store belongings safely. Each person has acted, but no one has checked whether the problem is solved.

That gap is a useful starting point for garment factory grievance handling. A message arrives, someone makes a decision, and a team acts on it. These are separate events. A case record should link them without drawing unwanted attention to the worker.

The welfare officer can help people use the process and keep follow-up moving. They should not have to make every decision or conduct every inquiry. Managers need clear duties. Workers also need a usable route when their concern involves a manager.

This guide develops a practical case log through an invented facilities complaint. The people, figures and response times are teaching examples. The actual procedure must follow local law and collective agreements. It must also meet any customer or financing terms that apply.

Decide what the process receives

The ILO explanation of grievance handling draws a useful distinction. A claimed breach of rights differs from a request for a new benefit. Rights may arise from law, contracts, collective agreements or workplace rules. That helps the team choose the right way to handle a concern.

For example, a question about an agreed wage payment differs from a request for a higher future wage. Both deserve a clear route, but they do not have the same basis. A welfare request, suggestion and grievance need not share every decision step.

Workers should not have to identify a legal clause before someone listens. The receiver can help record the facts and explain the process. They can then direct the concern to the right person. Workers should be able to challenge the label given to their concern. Staff must not use a label to discard a report they would rather not address.

In the fictional factory below, a written policy promises workers usable assigned lockers. Its complaint concerns that existing promise. The example does not suggest that every factory has the same legal duty to provide lockers.

Make the route usable before advertising it

A poster is of little use when no one can reach the contact. A day-shift office may be closed when the night shift ends. A phone-only channel may exclude someone without a private device. A written form may be difficult for a worker who reads another language.

Ask workers and their freely chosen representatives to test the route. Give them a fictional concern to raise. Can they find the contact, explain the problem and understand what happens next? Include different shifts and employment arrangements in this test.

Better Work's garment-sector guidance draws on work in Bangladesh and Cambodia. It stresses that workers should help design the process and improve it. Those discussions can reveal which channels people will use. An app's modern look cannot answer that question.

A factory might combine private conversations, a written channel and a phone service. Each needs a person who receives the reports and someone to cover their absence. Records must also pass between handlers securely. Explain which channels are monitored outside office hours. An unattended box should never be presented as an emergency service.

Workers need another contact if their concern involves the usual handler. Workers should be able to find this other contact without asking the usual handler for permission.

Separate urgent action from ordinary case timing

When a report arrives, find out whether someone needs urgent help or protection. A report of an exposed live wire cannot wait for the next grievance meeting. Follow the site's emergency and safety procedures. Bring in people with the right skills and retain the case record.

A report of violence, serious harassment or another threat to a person needs the same care. A routine facilities log cannot guide every kind of inquiry.

The ILO guide on violence and harassment calls for trained handlers who act without bias. Affected people need support and protection from retaliation. The guide also explains limits to confidentiality. Some facts may need to be shared to investigate, correct a problem or meet the law.

Set up those specialist routes before a difficult report arrives. Find out who can provide skilled support and what reporting duties apply. Explain what information may need to be shared and with whom. Do not promise absolute secrecy that the procedure cannot deliver.

A report should receive care even when the available facts are incomplete. The team can take steps to protect people and seek the facts fairly. It need not declare the claim proved before doing so. Do not require a worker to confront an alleged harasser as a condition of being heard.

ApparelDiary's risk assessment guide explains how to assess hazards. A grievance can trigger that work; a case number does not perform the assessment.

Design a small record with controlled access

The working log should show the concern and who must act next. It should also give the date of the next update. It does not need every personal detail in one widely shared spreadsheet.

Keep a private case file and a separate action register with fewer details. The case file holds necessary statements, contact details and sensitive evidence. The action register contains only what the assigned team needs to complete its task.

For the locker example, maintenance needs to know where the faulty lockers are and what to repair. The team does not need the worker's home address, pay record or other complaints.

Keep changes traceable. If someone entered the wrong location, correct it and record why it changed. Do not silently replace a worker's account with the manager's conclusion.

The UK Information Commissioner's employment-record guidance covers limited collection, accuracy, security and retention. This UK guidance is under review after changes in the law. Factories elsewhere need to check which rules apply to them.

Receive the locker complaint without deciding it in advance

Imagine a worker reports four faulty latches in a bank of twelve assigned lockers on Monday. They say the doors will not remain closed when used. The receiver records the worker's account. No one yet knows the cause. Writing “maintenance failure” would assign blame too soon.

The worker chooses a private conversation for updates. The welfare officer reads back the short note and checks that it captures the concern. The worker wants usable storage and a clear answer on when it will be restored.

The site provides temporary storage while a competent person checks the lockers. In this fictional case, the check finds no immediate physical danger. A real assessment could reach a different conclusion and require a faster response.

The officer provides a reference and explains who will check the lockers. The first update is promised for Tuesday. This is the factory's chosen update time. It is neither a legal deadline nor a promise to settle the whole matter that day.

The first reply should explain how to report a problem with the case handling. If the record seems wrong, the worker needs a way to correct it. Otherwise, an error may shape later findings.

Follow the evidence through the repair

On Tuesday, maintenance confirms that four latches fail during normal use. The team identifies the parts required and records the affected locker numbers. Photographs show the faults without including people or personal belongings.

The case owner checks that the temporary storage arrangement is usable. An offered locker may still be locked or assigned to someone else. The worker must be able to use it during their shift.

On Wednesday, the replacement parts are delayed. The officer explains the delay and gives the next update time. The record retains the original promised update time. Erasing it would hide a missed commitment.

The repair takes place on Thursday. A technician tests the empty lockers and marks the work order complete. The grievance record moves to “action completed; outcome check pending.” It does not jump straight to “resolved.”

During normal use, two doors still fail to latch. The workers report this through the same case reference. Maintenance adjusts the fittings on Friday and repeats the checks. The case file now explains why the first repair did not work.

That history matters. A later reader might otherwise think the second repair concerns a new complaint. They might also blame the worker for raising a supposedly solved problem.

Distinguish repair completion from case closure

In the example, the case owner checks the four affected lockers after the second repair. The workers confirm that the first reported problem is now fixed. The record identifies the checks, the date and the agreed follow-up.

A further check takes place after five working days of normal use. This period was chosen for the example. No standard is being claimed for it. Its purpose is to see whether the repair lasts through ordinary use.

The file needs a clear reason for closure. Here, the repair is done and its result has been checked. Other cases may end with a reasoned decision that the worker disputes. Keep that disagreement in the record. A closed case does not always mean a satisfied worker.

Acas guidance on grievance outcomes provides a useful UK example. Decisions should reflect the evidence. Workers should receive the outcome and have a route to appeal. The exact procedure elsewhere depends on local requirements and agreements.

An internal closing date must not hide a pending appeal. It must not block another route open to the worker.

Give decisions to people with the right authority

A welfare officer may coordinate the locker case. Maintenance approves the repair, while management authorises spending. The outcome reviewer needs to know what was promised and see the evidence.

A more difficult case may require a different decision-maker. If the complaint concerns the usual case owner, choose someone without that conflict. Naming the same person in a new column does not create an independent review.

The EBRD guidance on worker grievances describes other routes besides the immediate manager. It covers senior oversight and an appeal stage. It warns that a suggestion box or open-door policy is not enough on its own.

That document is guidance for the EBRD context, not a universal factory law. Its practical lesson is that a channel needs a functioning process behind it.

In a small factory, one person may handle several office tasks. The procedure still needs cover for absence and conflicts. It must explain who takes matters beyond that person's skills. A small workforce does not make every complaint simple.

Preserve other routes and worker representation

The factory process needs clear links to worker organisations and external bodies. Explain how it fits with collective agreements. It should not tell workers that management's internal route replaces all others.

IFC Performance Standard 2 covers access to grievance systems in paragraph 20. This includes reports from workers who do not give their names. The system should not block available remedies through courts or administrative bodies. Nor should it replace routes under collective agreements. These rules apply within the standard's scope. They do not describe every country's law.

In practice, a worker may ask a representative to help explain the concern. The case owner should check that person's role and what they may be told. A representative's title alone does not grant access to a private case file.

Keep outside contact details current. Check which issues and places each body covers. Some programmes cover particular factories or types of complaint. A logo on a poster does not establish that a worker's case is eligible.

Explain relevant time limits through competent local advice. An internal reply may take time. Do not mislead workers into missing an external deadline while they wait.

Handle anonymous reports without inventing agreement

Anonymous and confidential are different. With a confidential report, authorised handlers may know the person's identity. An anonymous report may provide no identity or safe way to contact the sender.

The absence of a name does not make a reported fault imaginary. An anonymous note naming a locker bank can still lead to an inspection and repair. The record should show the information available and the checks performed.

Without contact, the factory cannot claim that the anonymous sender accepted the result. It can record that someone checked the agreed action. It should also state that there was no feedback from the person who complained. Those are different facts.

Where practical, let a person use a case reference to seek updates without giving their name. Test whether the arrangement actually protects privacy. A public list of case details may reveal the sender through the shift, job or event described.

An anonymous report with too little information may remain difficult to investigate. Record that limit and any reasonable action taken. Avoid treating a lack of proof as proof that a worker lied.

Reconcile the monthly case figures

A monthly review can reveal missed follow-up, but only when it counts consistent units. A phone call, a concern and an open case count different things.

Consider a separate invented month. The factory begins with six open cases. It receives eighteen new cases and five additional messages about those cases. The five follow-ups retain the existing case references. They do not become five new cases.

Twelve cases meet the example's closure criteria during the month. This example has no reopened or merged cases. No cases leave the reporting boundary.

Closing open cases = opening open cases + new cases − closed cases.

6 + 18 − 12 = 12 open cases.

Sending a referral does not remove the three cases from this example's open balance. The factory retains a defined follow-up duty. The register should state the factory's role while the other body handles the matter.

Real cases may reopen or merge. The reporting scope may also change, so the register needs entries for those events. Show those movements explicitly. Do not make the balance work by deleting cases.

Measure response time without rewarding premature closure

Suppose fifteen of the eighteen new cases have a safe contact route. Fourteen receive an acknowledgement within the factory's chosen two-working-day target. Three anonymous cases have no contact route and are reported separately.

Acknowledgement performance = 14 ÷ 15 × 100 = 93.3%, rounded to one decimal place.

This measures timely acknowledgement among contactable cases. It does not mean that 93.3% of complaints were solved. Show the fifteen-case base, the three cases left out and the local target beside the result.

The remaining contactable case requires review. Was the receiver absent? Did a shift handover fail? Was the agreed method unsafe to use? The answer should guide the response, rather than automatically assigning blame.

Also review the oldest open cases and the reason for delay. An average can look acceptable while one important case waits far too long. Use each case's urgency and promised dates. One standard duration may not suit every concern.

ApparelDiary's factory KPI dashboard guide explains how to define measures and assign owners. For grievance work, use these methods in a private report for managers. Keep case details that could identify workers off the production board.

Look for retaliation and unresolved effects

Even after a sound repair, the worker may worry about having spoken up. They may fear losing overtime or facing an unfair move. Others might label them difficult.

The factory's non-retaliation commitment needs a safe way to report such concerns. The case owner should explain that route. They should also check whether their own follow-up draws unwanted attention. Questions asked in front of a supervisor may defeat that purpose.

A changed assignment after a complaint needs a closer look. Timing alone does not prove retaliation. Review the documented reason, who decided it and whether the process was fair. Keep that review separate from routine production scoring.

The same care applies to witnesses and other people involved. A general instruction to “keep quiet” can prevent someone from seeking support. Privacy rules should explain when sharing is allowed. They should not cut people off from representatives or qualified help.

For sensitive cases, use the specialist procedure and trained people established earlier. The routine locker example should never become a script for investigating abuse.

Learn from patterns without exposing people

The locker case raises a practical question: who was meant to check these facilities? A clearer inspection task may help prevent further faults. The team may also need a parts request route and a test of repairs in normal use.

That is different from merely reminding workers to complain sooner. Learning should examine the process that allowed the problem to persist.

A general update can explain what changed and how to report a remaining problem. Remove details that could identify people unnecessarily. In a small department, removing a name may not be enough.

Do not rank supervisors by the lowest complaint count. A low count could reflect few problems, but it could also reflect poor access or fear. A rise after training may mean that workers understand the route better. The figures need context and worker feedback.

Review the mechanism itself as well as the individual cases. Are contacts current? Do different shifts receive updates? Can workers find an alternative handler? Have promised actions actually happened?

Keep the next step clear

Before the process goes live, test a routine fictional case. Follow it from the first report through the final checks. Do this again when making major changes. Test a second scenario that requires a specialist referral. The aim is to expose missing ownership before a real person depends on the system.

Use the findings to help workers reach the right people and keep records safe. A complex form cannot replace a skilled person who follows through.

For each live case, the authorised team should be able to identify the next step, its owner and the next update. The worker should understand the process and available review routes. Those checks help the team keep the worker's concern at the centre of its work.

References

• ILO: grievance handling, rights and access to remedy.

• Better Work: guidance on grievance mechanisms in the garment sector.

• ILO: Violence and Harassment at Work, a practical guide for employers.

• UK ICO: collecting and keeping employment records.

• Acas: deciding and communicating grievance outcomes.

• EBRD: employee grievance mechanism guidance, March 2023.

• IFC: Performance Standard 2, Labor and Working Conditions.