Give Remote and Distributed Staff a Route to Raise Concerns, and a Fair Way to Handle Them
Software teams rarely produce formal grievances. Trouble shows up as a team that has stopped working with another, a cluster of exits under one manager, or a quiet withdrawal. We help you design a grievance route that works for remote and distributed staff, a separate conduct procedure, a standard way to investigate, and a central record. GullyHR does not give legal advice; we build the process and you confirm the position with a qualified professional.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsThe starting point
Would a Remote Engineer Know Whom to Approach With a Concern?
When concerns are about a manager, they are hard to raise through that manager. In distributed teams there may be no obvious person to approach at all, and issues turn up later as attrition or disengagement.
We help you build routes people trust and a record that shows patterns.
You may be experiencing:
- No clear person for a remote or client-site employee to approach with a concern.
- Concerns about a manager that can only be raised through that same manager.
- Policies on conduct applied differently across locations and teams.
- Performance concerns treated as conduct matters, and conduct matters as performance.
- Investigations run by whoever is free, with notes kept in personal files.
- Records scattered across chat, email and managers' memory.
- A team that has stopped working with another, with nobody sure whose job it is to look into it.
What we can help with
Our Employee Relations Services for Software Companies
Grievance Route Design
Define how a concern is raised, to whom, through which channels and in what time. The route includes someone outside the line for concerns about a manager, and works across locations, time zones and remote arrangements.
Separate Routes for Complaint and Conduct
Keep the route for a person raising a concern distinct from the route for managing conduct, so each follows its own steps and neither is used as a substitute for the other.
Performance and Conduct Separation
Write a clear line between a performance matter, handled through the appraisal and improvement plan, and a conduct matter, handled through the conduct procedure, with a note on when each applies.
Investigation Standard
Define who investigates, how impartiality is maintained, how evidence is gathered, how the person concerned is heard and how the findings are written, so a case does not depend on the investigator's habits.
Warning and Escalation Steps
Set the steps from informal conversation to written outcomes, who may approve each and how the record is kept. Consistency across teams and locations is checked.
Interpersonal Conflict Support
Offer a route for team conflict, such as facilitated conversations and manager guidance, aimed at settling issues before they harden into formal matters.
Signal Reading
Track exits by manager, tenure and team, patterns in concerns and any quiet withdrawals, and treat concentrated attrition under one manager as a relations signal and not just a market condition.
Central Case Record
Keep a single record of cases, outcomes and timelines, independent of any team, with access limited to those who need it and rules for retention that you confirm with your adviser.
The deliverables
What You Receive
Depending on the agreed scope, you can expect:
- A written grievance route with named receivers, including an independent one.
- A conduct procedure kept separate from the complaint route.
- A note on separating performance and conduct matters.
- An investigation standard and case file template.
- Warning and escalation steps with approvers.
- A conflict support guide for managers.
- A signal review of exits and concerns by manager and team.
- A central case record set up in your system or on GullyHR.
Step by step
How We Work
Understand How Concerns Travel
We speak to HR, managers and a few employees, including remote staff, about whom they would approach and what has happened before.
Design the Routes
We draft the grievance and conduct routes, the investigation standard and the case record, and agree who holds each role.
Brief Managers and Receivers
We brief managers, HR and named receivers on their roles, and on handling a concern raised informally.
Set Up the Record
We configure the case record, reminders and access rules in your system or on GullyHR.
Review the Signals
Before work starts we note where you stand. We then review cases and exit patterns with you and adjust the routes.
The difference
Notice Problems Earlier and Handle Them Consistently
A defined relations process helps your company:
We do not promise outcomes. We record a baseline before work starts, covering the number of concerns raised and where, the time cases take to reach an outcome and the exits clustered under particular managers, and report against it, so you can see what changed and what did not.
- Give every employee a route they can use, wherever they work.
- Raise concerns about a manager without going through that manager.
- Keep complaint and conduct matters on separate tracks.
- Run investigations the same way each time.
- Keep one record of cases and outcomes.
- See patterns that individual cases hide.
Find your fit
Who This Service Is For
Distributed and Remote-first Companies
Give people who rarely meet HR a clear way to raise concerns.
Companies Where Concerns Surface Through Exits
Build a route before the next resignation letter.
IT Services Firms with Client-site Staff
Cover employees who work under a client's supervision.
Founder-led Companies Adding HR
Replace informal handling with a procedure.
Companies with Several Locations
Apply conduct rules consistently across offices.
How it usually shows up in information technology and software
In software companies, employee relations problems usually do not arrive as complaints. They show up as a team that has stopped cooperating with another, as a cluster of exits under one manager, or as a quiet withdrawal. Remote and distributed staff may have no obvious person to approach, and concerns about a manager are difficult to raise through that manager. Policies on conduct, harassment and disciplinary action may exist but are applied differently across locations and teams. Performance concerns are sometimes handled as conduct matters and conduct matters as performance. Investigations are conducted by whoever is available, with notes kept in personal files. Records are scattered across chat, email and managers' memory, and patterns are therefore not visible.
Common challenges
Where it goes wrong in information technology and software
Concerns do not reach HR
People leave instead of complaining, and the cause is never recorded.
The route does not suit remote staff
Distributed employees do not know whom to approach or how.
Performance and conduct are mixed
The wrong procedure is used for the wrong issue.
Records are scattered
Notes sit in chat and personal files, so patterns stay hidden.
A better process
What a working version looks like
- 01
Publish the grievance route
Named receivers outside the line manager, with a way to reach them remotely and a stated response time. The grievance and disciplinary process sets the steps.
- 02
Separate the two routes
Complaints and conduct are handled under a disciplinary procedure, performance under a different one.
- 03
Run investigations in a standard way
Named investigator, written terms, interview notes and a recorded finding, with fair hearing for each side.
- 04
Treat patterns as signals
Review exits and complaints by manager and team each quarter, and look into concentrations.
- 05
Keep a central record
One file system for cases, independent of any team, with limited access and a retention rule.
What to check this week
- Ask a remote employee whom they would approach with a concern.
- List exits under any manager in the last year and look for clusters.
- Check whether performance issues have ever been handled as discipline.
- Look at the file for the most recent case and see what is missing.
- Confirm the legal position with a qualified professional.
Confirm with a qualified professional. What applies depends on your establishment, your state and your sector, and it changes. This page describes a practice; it does not state a legal position.
What this looks like in information technology and software
The parts of employee relations that are specific to this sector, rather than general.
Relations in Knowledge Work
Where issues are interpersonal, remote and often unreported.
What this coversHide
Relations in Knowledge Work
Where issues are interpersonal, remote and often unreported.
What this coversHideSoftware teams rarely produce formal grievances. Issues present instead as attrition, disengagement or a team that has quietly stopped working with another - which makes them harder to see and later to address.
- A route that works for remote and distributed staff
- Manager-related concerns raised without going through that manager
- Interpersonal and team conflict addressed before it hardens
- Harassment and conduct concerns routed formally
- Performance concerns kept separate from relations matters
- Consistency across locations and remote arrangements
- Exit patterns monitored as a relations signal
- Central record independent of any team
Treating concentrated attrition under one manager as a relations signal rather than a market condition is the diagnostic step most often skipped in this sector.
Questions on this, in information technology and software
A small team still benefits from knowing whom to approach and how concerns are handled. We keep the process proportionate. Which obligations apply to you is a legal question, so confirm them with a qualified professional.
Through a route that does not run through that manager, such as a named HR contact or a senior leader outside the line. We help you design the route and explain it so people believe it is safe to use.
A grievance is a concern raised by an employee. A disciplinary matter is the company acting on conduct. We keep the two routes separate, with distinct steps and records, so neither is used to settle the other.
Someone who has no stake in the outcome and has been briefed on the standard. We help you decide who that is for different kinds of case, including when an outside investigator is sensible.
No. GullyHR does not give legal advice. We design the procedure, consistency and record. Employee relations and disciplinary obligations vary by state, sector and establishment, so confirm the position with a qualified professional.
That is for you to decide with your legal adviser. We set up the record with retention and access rules once you confirm them, so that retention is applied consistently and not left to individual managers.
Because people with options leave instead. The lack of complaints is not evidence of the lack of problems, so exits and team patterns should also be watched.
Through a named receiver outside that manager's line, reachable remotely, with a stated process for what happens next.
A grievance is a complaint by an employee about treatment, and a performance issue is the company's concern about work. They need separate routes.
In one central place, independent of the team, with restricted access. Confirm retention periods with a qualified professional.
Build Employee Relations You Can Rely On
If concerns reach HR late, or only as resignations, start with the routes people can use and the record that shows what is happening.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book an Employee Relations Consultation
Tell us about your teams, locations and how concerns are handled today.
The general method — what employee relations covers, the questions it answers and what an engagement produces — is the same whatever the sector, and is set out on the grievance and disciplinary process page. What is above is the part that differs for information technology and software.
To run this in a system rather than on paper, see engagement and employee relations software.
Other HR topics for information technology and software
Where to start
Most engagements begin with a review of how this runs in your business today, then a written process and the sequence to implement it.
See all HR topics for information technology and software, or another industry.