Reviewed: 9 October 2026. The rota records, people and correspondence in this guide are original fictional examples. They concern an ordinary information disagreement, not a legal complaint, disciplinary investigation or safety incident.
Good employee relations depend on how an organisation hears concerns, makes decisions and follows up. A polite conversation helps, but it cannot replace clear authority, reliable records or the appropriate process for the issue raised. Employees need to know where a concern can go and what response they can expect.
For managers and HR teams in India, begin with the actual organisational policy and the applicable requirements for the situation. This article provides a practical communication and recordkeeping exercise. It does not certify legal compliance or determine an employee's rights.
Make the route for concerns understandable
Explain which person or channel handles ordinary work questions and which process handles formal or serious concerns. Give an alternative contact where the usual manager is involved in the concern. A route that exists only in a document employees cannot find is difficult to use.
Acas guidance describes listening to concerns, recording discussions and making next steps clear. Its guidance is from the UK; these communication principles are useful here, while its legal rights and procedural duties should not be assumed to apply in India. Acas: dealing with a problem raised by an employee.
Do not require every person to resolve an issue privately before using an appropriate reporting process. Harassment, safety, serious misconduct and formal complaints can require different handling. The fictional rota exercise below is intentionally outside those categories and should not be used as their investigation procedure.
Keep preparing
Continue with Sarkari Resume Templates₹299 — coaching के एक महीने से काफ़ी सस्ता / far cheaper than a month of coachingSeparate the accounts from the decision
Suppose two employees have different versions of a Saturday rota. The supplied records are:
| Record | Supplied information | What remains uncertain |
|---|---|---|
| Version A, dated 5 October | Leena is listed for Saturday morning | Whether this version remains the approved schedule |
| Version B, dated 6 October | Omar is listed for Saturday morning | Whether the manager approved the change |
| Leena's account | She planned around Version A and saw Version B later | Whether the change was communicated before her planning |
| Omar's account | He received Version B and believed it was current | Whether the sender had authority to confirm it |
| Authority record | The team manager approves schedule changes | Which version the manager actually approved |
This record shows an information inconsistency. It does not show that either employee lied, refused work or deliberately ignored instructions. Preserve both accounts without turning an assumption about motive into a fact.
An initial note can say, “Two dated versions name different employees for the same slot; the approved version has not yet been confirmed.” That is more precise than “Leena and Omar are difficult to manage.” The first statement points to evidence that can resolve the practical question.
Hear the practical impact and requested outcome
Ask each person what they received, when they received it and which work arrangement they believed was confirmed. Invite them to identify the practical issue they need addressed. Do not ask them to prove their character or accept blame merely to move the conversation forward.
Leena's supplied request is to know whether her Saturday plan remains valid. Omar's supplied request is to know whether he should attend and who confirms changes. These requests overlap: both need an authoritative schedule and an understandable notification route.
The manager can summarise both accounts before deciding. Acknowledging the concern means it has been received; it does not mean every factual statement has been verified or that the requested solution has been approved.
Assign a source check to the authorised person
The first action is not a vote between the two versions. The manager must check the approval record and confirm the schedule through the proper channel.
Here is the complete original action note for the exercise:
Issue recorded 7 October: Versions A and B name different employees for Saturday morning. Leena says she planned around A; Omar says he received B as current. Neither account has been treated as misconduct. The team manager will check the approval record and send a dated schedule confirmation by 8 October. Until that confirmation, this note does not assign the slot to either person. The manager will also identify the channel for later changes. Both employees may correct this summary if it misstates their account.
The note assigns responsibility and a response date. It does not grant a facilitator authority to approve shifts. Where an unresolved question affects immediate staffing, the authorised manager still needs to make and communicate the necessary operational decision; a meeting note alone cannot fill the gap.
Record the correction and its reason
In the fictional follow-up, the manager checks the approval log. It shows that Version A was approved and Version B was a draft sent before approval. The manager then issues Version C on 8 October, retaining Leena for the slot and marking Version B superseded.
The supplied correction reads:
Version C is the confirmed schedule. The approval record supports the assignment in Version A. Version B was an unapproved draft and should not have been sent as current. Leena remains assigned to Saturday morning. Omar is not assigned to that slot. Future drafts will be labelled as drafts; confirmed changes will come from the manager through the agreed team channel. Please confirm receipt and raise any remaining practical difficulty.
This explains the source and decision without attributing bad intent to either employee. It also identifies a process weakness: an unapproved document was distributed as current. The supplied facts support correcting the label and communication route, not a company-wide claim that conflict has been eliminated.
Check receipt separately from resolution
The next supplied responses are:
- Leena confirms receiving Version C and says the Saturday assignment is now clear. She still wants more notice for future changes.
- Omar confirms receiving Version C and says he understands he is not assigned. He asks where he can find the manager's confirmed version next time.
Both received the correction. Both understand this particular assignment. Two process questions remain. A complete follow-up record should not collapse these statuses into “all concerns resolved.”
| Follow-up question | Evidence now supplied | Status |
|---|---|---|
| Did both receive Version C? | Each confirmed receipt | Confirmed |
| Is the Saturday assignment understood? | Each stated their understanding | Confirmed in this exercise |
| Is a future notice period agreed? | Leena requested one | Pending manager response |
| Is the confirmed-version location clear? | Omar asked where to find it | Pending clarification |
The manager can answer the remaining questions using the actual policy and operational requirements. Do not invent a universal notice period. If the team cannot promise a requested lead time, explain what can be committed to and how exceptional changes will be communicated.
Use records carefully
Keep a factual note of the issue, relevant evidence, decision, reasons and next steps. Share it with people who need it for the process, subject to the applicable policy and requirements. Do not promise absolute confidentiality if information may need to reach an authorised person.
Avoid including unrelated personal details or speculative labels such as “uncooperative.” Give the employee a way to correct an inaccurate summary. A request to correct a record is not itself evidence of resistance.
The rota note contains enough detail to follow the decision. It does not need a person's family arrangements, private messages unrelated to the issue or an informal psychological assessment. Information should serve the actual question being handled.
Build prevention into normal management
Routine practices can reduce avoidable ambiguity: identify the owner of a schedule, distinguish drafts from approved versions, make the current record accessible and explain how changes are confirmed. Review whether employees understand the process rather than assuming that publishing a policy completes the job.
Acas also advises checking relevant policy and using the appropriate route when raising a problem. Again, this is UK guidance supporting the general importance of a clear route, not an Indian legal procedure. Acas: raising a problem at work.
In the example, prevention means addressing the version-control failure and answering the remaining notice and location questions. It does not require employees to avoid all disagreement. A concern raised promptly can reveal missing information that management needs to fix.
Measure the process without rewarding silence
Useful observations include whether concerns were acknowledged, promised checks occurred, decisions had reasons and unresolved questions remained visible. Record the limits of those measures.
A lower complaint count does not by itself prove better employee relations. It could reflect fewer problems, a changed workforce, inaccessible reporting or reluctance to speak. Similarly, a closed ticket does not prove the employee accepted the outcome. Pair counts with specific follow-up evidence and a way to raise continuing concerns.
For this exercise, the supported result is narrow: the authorised manager corrected the rota, and both employees confirmed understanding of that assignment. Future notice and access questions remained pending. No retention, productivity or legal-compliance outcome was measured.
Frequently asked questions
Should every concern begin with an informal conversation?
No universal requirement is stated here. The appropriate route depends on the issue, organisational policy and applicable requirements. Serious or formal concerns should not be forced into this ordinary rota exercise.
Is acknowledging a concern the same as agreeing with it?
No. Acknowledgement records receipt and attention. Verification, decision and follow-up are separate steps.
Does mediation guarantee resolution?
This guide makes no such guarantee. Some disagreements need an authoritative source check or decision; other concerns require a different process entirely.
What should a manager report as completed?
Only the actions and outcomes supported by records. Distinguish sending a correction, confirming receipt, understanding a decision and resolving every remaining question.
For a separate role-and-pay discussion, see the promotion salary guide. For evidence that accurately describes your own work, see personal branding.