Neurodiversity at Work: A Practical Employer Guide

Neurodiversity at work is not an abstract debate for most Indian SMBs. They already employ neurodivergent people; they just do not know it. Somewhere in your team is an engineer who does the deepest debugging work in the company but freezes in a whiteboard interview, a designer whose spelling is unreliable but whose spatial reasoning is exceptional, an operations executive who spots the one broken row in a 4,000-line reconciliation file and cannot sit through a 90-minute all-hands. Neurodiversity at work is not a future policy problem. It is a present, unmanaged reality, and the question is only whether your hiring and performance systems are quietly filtering that talent out or letting it do its best work.

This guide is written for founders, HR leads and managers at Indian small and mid-sized businesses — the 20-to-500 person companies that do not have a dedicated DEI function, a disability affairs officer, or a budget for external consultants. It covers what neurodiversity in the workplace actually means, where standard hiring and appraisal processes go wrong, accommodations that cost almost nothing, how to handle disclosure and health data responsibly, what managers should actually say, and how to tell whether any of it is working.

A note on what this article is not. It is not medical guidance. It contains no diagnostic criteria, no advice on identifying conditions, and no suggestion that managers should ever attempt to assess anyone. It also avoids the two failure modes that make most corporate neurodiversity content unusable: treating neurodivergent employees as a charitable cause, and treating them as a set of superpowers to be extracted. Neither is respectful and neither is accurate.

What Neurodiversity Means — And What It Does Not

Neurodiversity is a description of a population, not a description of a person. It is the simple observation that human brains vary in how they process information, regulate attention, handle sensory input, and communicate — and that this variation is normal, in the same way that variation in height or handedness is normal.

The words that follow from that:

• Neurodivergent describes an individual whose cognitive functioning differs from what is socially expected or designed for. It commonly includes people who are autistic, have ADHD, dyslexia, dyspraxia, dyscalculia, Tourette syndrome, or other differences in processing. It is a self-descriptive term, not a clinical label you apply to someone else.
• Neurotypical describes someone whose processing broadly matches what workplaces are designed around. It is not a compliment or an insult.
• Neurodiverse describes a group or a team, never an individual. A team can be neurodiverse; a person cannot. This is a small distinction that signals to neurodivergent employees whether you have actually read anything.

Just as important is what you should not say. Avoid "suffers from", "afflicted with", "high-functioning" or "low-functioning", and "special needs" in an adult employment context. Avoid describing someone as "a bit OCD" or "so ADHD" as shorthand for tidy or distractible — these are casual phrases that tell any neurodivergent person in the room exactly how their disclosure will be received. Avoid framing colleagues as inspirational for doing their jobs.

Also worth retiring: the idea that every neurodivergent person has a hidden savant talent. Some neurodivergent employees are outstanding at pattern recognition. Some are outstanding at empathy. Some are outstanding at neither and are simply good at their jobs, which is all any employer should require. The "superpower" framing sets an unfair bar and quietly implies that ordinary competence is not enough to justify accommodating someone.

The Social Model, In Plain Terms

The most useful frame for an employer is this: much of what looks like an individual limitation is actually a mismatch between a person and an environment that was designed without them in mind.

An employee who cannot concentrate in an open-plan office with a sales floor ten feet away does not have a concentration problem. They have an acoustics problem. An applicant who performs badly in a rapid-fire panel interview but excellently in a take-home task does not have a competence problem. They have a format problem. A team member who misses instructions given verbally in a corridor but never misses a written one does not have a reliability problem. They have a channel problem.

This is not semantics. It changes where you look for the fix. If the problem is the person, your only lever is to ask them to try harder — which they have almost certainly already been doing for years, at considerable cost. If the problem is the environment, you have dozens of cheap levers, and most of them improve conditions for everyone.

The Indian Context, In General Terms

India has a statutory framework for disability inclusion in employment, and it recognises that certain neurodevelopmental and learning differences fall within the scope of disability protections. In broad terms, the law contemplates non-discrimination in recruitment and employment, the provision of reasonable accommodation, and workplace policies and grievance mechanisms for covered employees. Obligations differ between government and private establishments, and different requirements apply at different organisational sizes.

Two practical points for an SMB.

First, the details matter and they change. Definitions of covered conditions, documentation and certification processes, establishment thresholds, and record-keeping requirements are all specific, and they interact with your state's rules. Do not treat this article as legal advice. Have your employment counsel confirm what applies to your entity, headcount and locations before you write policy.

Second, and more importantly: compliance is a floor, not a strategy. Most of what makes a workplace genuinely neuro-inclusive is not legally mandated. It is a set of design choices about how you interview, how you write job descriptions, how you run meetings and how you evaluate performance. None of it requires a legal trigger and none of it requires anyone to disclose anything.

Where Standard HR Systems Quietly Screen People Out

Almost no Indian SMB has a policy that discriminates against neurodivergent candidates. Almost every one has processes that do. The exclusion is structural, not intentional, which is exactly what makes it hard to see.

Here is where it happens.

1. Job Descriptions That Test For Personality

Look at your last five job posts. Count the requirements that describe how someone should be rather than what they should deliver: "excellent communication skills", "high-energy team player", "thrives in a fast-paced environment", "strong presence", "cultural fit".

Some of these are genuine requirements. If the role is enterprise sales, verbal fluency under pressure is the job. But most of the time these phrases are copied forward without thought, and they function as filters on social style rather than capability. A candidate who reads "excellent communication skills" and knows they process spoken instructions slowly will often self-select out of a role they would excel at.

2. Interviews That Measure Interview Skill

The unstructured conversational interview is the single largest source of unintentional exclusion in SMB hiring. It rewards fast verbal processing, comfortable eye contact, confident improvisation, socially fluent small talk, and the ability to construct a polished narrative on demand.

Very few jobs actually require those five things simultaneously and under time pressure. But almost every interview does.

Whiteboard coding rounds, "walk me through your thinking out loud" exercises, rapid-fire case studies, and group discussion rounds all compound the problem. They add a real-time verbal performance layer on top of a task that, in the actual job, would be done alone, with notes, and with time to think.

3. Assessments With Hidden Time Pressure

Timed aptitude tests, especially ones with tight per-question limits, measure processing speed alongside the skill they claim to measure. If the job does not require snap decisions, the clock is testing something irrelevant. Reading-heavy assessments with dense, unformatted text add another layer for dyslexic candidates who may read more slowly while comprehending perfectly well.

4. Onboarding By Osmosis

Most SMB onboarding is verbal, informal and social: someone walks you around, you pick things up, you learn who to ask. This works reasonably well for people who read social context fluently and terribly for people who do not. Unwritten norms — when it is acceptable to interrupt, how direct feedback is expected to be, whether a 6 pm message expects a reply — are invisible to everyone but punishing only for some.

5. Performance Reviews That Rate Style

This is where the damage compounds. Look at the language in your last appraisal cycle. Phrases like "needs to be more proactive in meetings", "should build stronger relationships across teams", "presence could be stronger", "not visible enough to leadership" appear constantly in Indian SMB reviews.

Each of these rates communication style, not output. A neurodivergent employee who consistently delivers strong work but speaks little in meetings will be rated as a solid-but-not-exceptional performer year after year, with real consequences for increments and promotion — even in a company where nobody intends any such thing.

6. Promotion Criteria Built Around Visibility

Related, and worse: many SMBs promote based on who is visible to leadership. Visibility is a function of being in the right conversations, speaking up, networking at offsites and being socially memorable. It is only loosely correlated with contribution, and the correlation is weakest exactly for people whose social energy budget is spent elsewhere.

Redesigning Hiring: Before and After

The good news is that everything above is fixable with process changes that cost nothing and improve your hiring signal for all candidates, not only neurodivergent ones. Structured, task-based hiring is simply better hiring.

Sharing Questions In Advance Does Not Weaken The Signal

This is the objection every hiring manager raises, so it is worth addressing directly.

If you send behavioural questions ahead of time, you are not making the interview easier. You are removing recall speed and improvisation from what you are measuring, and leaving the quality of the candidate's actual experience. A candidate with nothing to say will still have nothing to say, only more fluently phrased. A candidate with five years of relevant work will bring a better example than the one they happened to remember under pressure.

The same is true for take-home tasks. The common worry is that someone else does the work. Fix that by keeping the task short — under two or three hours, and paid or at least time-capped out of respect — and following it with a discussion of the submission. Someone who did not do the work cannot discuss the choices in it. Someone who did can, even if they are nervous.

Practical Interview Adjustments Worth Offering Everyone

Rather than waiting for a candidate to request adjustments — which requires them to disclose something and risk being judged for it — offer a standard menu to every applicant. One line in your interview invitation email does most of the work:

"If there is anything that would help you do your best in this interview — questions in advance, extra time, a written task instead of a verbal one, breaks, a quieter room, or joining online — just reply and let us know. You do not need to give a reason."

Note the last sentence. It is the most important one. It removes the disclosure tax entirely.

Rewriting Your Job Descriptions

A quick before-and-after on a real pattern you will recognise:

Before: "We are looking for a highly motivated, energetic self-starter with excellent communication and interpersonal skills who thrives in a fast-paced, dynamic environment and can juggle multiple priorities while being a strong team player."

That sentence contains zero information about the job.

After: "In this role you will: own the monthly GST filing calendar for 14 entities; reconcile vendor payments and flag discrepancies over Rs 5,000; prepare the month-end pack for the finance head by the 5th working day; respond to vendor queries within one business day. You will work with two colleagues in finance and coordinate mainly over email and our ticketing tool."

The second version tells a candidate exactly what success looks like, what the communication load is, and what channels are used. It attracts people who can do the job and repels people who cannot — which is the entire purpose of a job description.

A Reasonable Accommodation Menu That Costs Almost Nothing

The word "accommodation" makes finance teams nervous because it sounds like construction. In practice, the overwhelming majority of workplace accommodations for neurodivergent employees are process changes, scheduling changes, or a piece of equipment costing less than a mid-range office chair.

The table below is a working menu. It is organised by the underlying need rather than by condition, deliberately — because needs are what you manage, and because organising by diagnosis would push managers toward guessing at diagnoses, which they must never do.

Read down the cost column. Almost every row is nil or one-time-low. The real cost of accommodation in an SMB is not money. It is managerial attention — someone has to remember to send the written summary, protect the focus block, and not schedule the strategy review at 6 pm.

The Universal Design Shortcut

Notice how many of those accommodations are things you would happily give the whole team.

Written summaries after verbal instructions. Agendas in advance. Clear priority order instead of a flat list of twelve urgent things. Camera-optional calls. Recap emails. Meeting-free focus blocks. Predictable notice of change. None of these harm anyone.

This is the single highest-leverage move for a small company: make the common accommodations into default practice. Do that and you remove most of the need for individual requests, most of the need for disclosure, and most of the awkwardness for managers who are not sure what they are allowed to ask.

Consider an illustrative example. A 60-person logistics services firm moves to a simple rule — every verbal instruction from a manager gets a two-line follow-up in the team channel. It is introduced for one employee who kept missing corridor instructions. Within a quarter, handover errors across the whole team have dropped and the rule stays. Nobody thinks of it as an accommodation anymore. It is just how they work.

Disclosure, Privacy and Health Data

This is the area where well-meaning SMBs most often create real harm, and it is worth being precise.

Nobody Owes You A Diagnosis

An employee may tell you they are autistic. They may tell you they have ADHD. They may tell you only that they find open-plan offices unworkable and would like to sit near the window. They may tell you nothing at all and simply ask for written instructions.

All four are legitimate. Accommodations should not be gated behind a diagnosis. If an employee asks for noise-cancelling headphones and a quieter seat, the correct response is to work out whether it is operationally feasible, not to ask what is wrong with them.

There is a narrow exception. If an employee is seeking a formal protection or benefit under statutory disability provisions, there may be a documentation or certification process involved. That is a specific legal pathway with its own rules, and it should be handled by HR with legal input — not by a line manager asking questions in a one-on-one. For everything else, which is the vast majority of day-to-day adjustments, keep it simple: what would help, and can we do it?

Managers Must Never Diagnose Or Speculate

Say this explicitly in your manager training, because it happens constantly:

• Do not tell an employee you think they "might be on the spectrum" or "sound quite ADHD".
• Do not raise a suspected condition in a performance discussion, a calibration meeting, or a note in the HR system.
• Do not discuss your theory with other managers, with the team, or over lunch.
• Do not suggest someone "get tested" or "see someone about it".

Even where the intent is kind, this is speculation about a person's health, shared without consent, often in a setting that affects their livelihood. It is the fastest way to guarantee that nobody in your company ever discloses anything.

What a manager should do instead is stay entirely in the territory of work: what is happening, what would help, what can we change. You do not need to know why an accommodation helps in order to provide it.

Handling The Data Itself

If an employee does disclose, you are now holding sensitive personal information about health. Treat it accordingly.

1. Ask consent before sharing anything, and be specific. "Are you comfortable if I tell the team that you have a focus block from 10 to 12 and shouldn't be pinged then?" is a specific ask. "Is it okay if I mention this?" is not.
2. Share the accommodation, not the reason. The team needs to know that Priya does not take calls before 11. They do not need to know why. If a colleague asks why, the answer is "that is her working arrangement" — full stop, no apologetic elaboration.
3. Store it separately and minimally. Disclosures and accommodation records should not sit in an open shared drive, in a WhatsApp group, in an email thread with twelve people on it, or in free-text notes on a performance record. Keep access limited to named HR roles, with a record of who can see what.
4. Keep it out of performance documentation. An accommodation is not a performance issue and must not appear in a rating rationale, a PIP, or a promotion note.
5. Have a retention rule. Decide how long you keep this information, where, and what happens when someone leaves. Write it down.
6. Have a defined intake path. Employees should know exactly who to approach — a named HR person, a form, or an email alias — rather than having to guess whether telling their manager is safe.

Given the evolving data protection landscape in India for personal and sensitive personal data, this is another place to have counsel review your policy language and your consent flows. The principle to hold to regardless of the specific rules: collect the minimum, share on a need-to-know basis with consent, store it securely, and delete it when there is no longer a reason to keep it.

Why People Do Not Disclose

If your disclosure rate is zero, the explanation is almost never that you have no neurodivergent employees. The usual reasons:

• Fear of being seen as a liability at appraisal or restructuring time.
• Previous experience of disclosure being met with pity, doubt, or gossip.
• Uncertainty about who will see the information and where it goes.
• Not wanting the label to become their defining characteristic at work.
• Simply not needing anything from you — which is a perfectly good reason.

You cannot demand trust. You can only build the conditions and let people decide. The most persuasive evidence an employee has is not your policy document; it is how they saw the last person's request handled.

Manager Conversation Scripts

Managers freeze because they are afraid of saying something offensive or legally unwise. Give them words. These are starting points to adapt, not lines to read out.

Script 1: An Employee Discloses

They say: "I wanted to mention that I'm autistic. I don't tell many people at work."

A good response: "Thank you for telling me — I know that isn't a small thing to share. Two questions and then we can move on. First, is there anything about how we work that you'd like to change or try? And second, who else, if anyone, would you like this shared with? The default is that it stays with me unless you tell me otherwise."

What not to say: "I would never have guessed." / "You seem so normal." / "My cousin's son has that." / "Is that why you...?" / "Don't worry, we're all a bit like that."

Script 2: Offering Adjustments Without Anyone Disclosing

Manager opens: "I want to check something with everyone on the team, not just you. Is there anything about how we work — meeting formats, how I give instructions, seating, hours, notice periods on changes — that makes your work harder than it needs to be? You don't have to explain why. I'd just like to fix what's fixable."

Asking the whole team removes the spotlight and usually produces useful answers from everyone.

Script 3: Raising A Genuine Performance Concern

The rule: describe the work, never the person, and never speculate about a cause.

Say: "The last three vendor reports came in two days after the deadline. That pushes the finance close back. I want to understand what's getting in the way and what we can change so the dates hold. Is it the volume, the timing, the way the inputs reach you, or something else?"

Do not say: "You seem disorganised." / "You need to focus more." / "Is something going on with you?" / "Have you thought about seeing someone?"

The first version is a solvable work problem. The second is a character judgement, and it is also the version that ends up in a rating rationale where it does the most damage.

Script 4: When Communication Style Is Being Read As Rudeness

Direct communication is frequently misread as blunt or arrogant, particularly in Indian workplaces where hierarchy and indirectness are strong norms. This deserves a real conversation, not a "needs to work on soft skills" note.

Say: "I want to give you some context that might be useful. Your messages are very direct and clear, which I find efficient. A couple of people have read them as abrupt. I don't think that's your intent, and I'm not asking you to change who you are. Would it help if we agreed on a couple of small conventions — a greeting line at the top, or a sentence of context before a request — that would remove the misread without you having to guess each time?"

The other half of that conversation is with the team: direct is not rude, and interpreting a colleague's typing style as an insult is also a communication problem.

Script 5: When A Colleague Complains

A colleague says: "Why does he get to work from home two days and I don't?"

Say: "Working arrangements are agreed individually and I'm not going to discuss anyone else's. If your current arrangement isn't working for you, let's talk about yours."

Short, non-defensive, no detail. Every additional word is a leak.

Script 6: Accommodation Check-In

Six to eight weeks after any adjustment is made:

Say: "We changed a few things a couple of months ago — the written summaries, the Tuesday focus block. I wanted to check whether they're actually helping, whether anything needs adjusting, and whether there's something else we should try. Also fine to say it made no difference; I'd rather know."

Accommodations are experiments. Some fail. Reviewing them keeps them useful and signals that the offer was genuine.

Redesigning Performance Reviews Around Outcomes And Evidence

Hiring gets most of the attention in neurodiversity discussions, but performance management is where careers are actually made or stalled. A neuro-inclusive company that still runs style-based appraisals will hire well and then under-promote the people it hired.

The Core Principle

Rate what the person produced and how it affected the business. Rate behaviour only where the behaviour is genuinely part of the job, defined in advance, and evidenced with specific examples.

Three tests for any line in a review:

1. Is it observable? "Delivered the migration two weeks early" is observable. "Lacks executive presence" is not.
2. Is it job-relevant? If the role does not require leading meetings, "doesn't lead meetings" is not a development area. It is an observation about personality.
3. Is it evidenced? If you cannot cite two specific instances with dates, do not write it.

Most vague, style-based review language fails all three at once.

Review Language: Do And Don't

Structural Changes To The Review Process

Beyond language, six process changes make appraisals substantially fairer for everyone:

1. Share the questions and the form in advance. Give people at least a week with the self-assessment. This removes recall-under-pressure from what you are measuring.
2. Allow written responses before or instead of live discussion. Some employees will articulate their year far better in writing. Let them, then discuss.
3. Collect evidence continuously, not in a two-week scramble. A running log of shipped work, incidents handled and feedback received prevents recency bias, which disproportionately penalises people who do steady, invisible, unglamorous work.
4. Define ratings against outcomes, with examples, before the cycle starts. Ambiguity in criteria is where bias lives.
5. Run calibration with a bias check. In every calibration meeting, someone should be empowered to ask: "Is this rating about output, or about style?" and "What is the evidence?" Ban "fit", "presence", "energy" and "attitude" from calibration discussion unless backed by a specific incident.
6. Audit the outcomes. Look at ratings, increments and promotions across the company each cycle and ask whether quiet, heads-down contributors are systematically landing a band lower than visible ones. If they are, the problem is your process, not them.

A good HRMS makes points 3, 4 and 6 much easier — continuous check-in notes, a documented rating framework, and reporting that lets you actually see the distribution instead of guessing at it.

Goal-Setting That Works Better For Everyone

• Write goals as outcomes with dates, not as activities. "Reduce invoice disputes to under 5 per month by Q3" beats "be more careful with invoicing".
• Break large goals into visible checkpoints. Ambiguous long-horizon goals stall for many people, not only neurodivergent ones.
• Put priority order in writing. When everything is priority one, the person who takes instructions literally is set up to fail.
• Distinguish "must", "should" and "nice to have" explicitly.
• Confirm changes in writing. If priorities shift mid-quarter, update the goal document rather than leaving it as a verbal aside that later becomes an appraisal problem.

Onboarding: The First Ninety Days

Onboarding by osmosis fails a lot of people. Making it explicit takes a few hours of one-time work.

Week zero, before day one. Send a written note covering: what time to arrive and where exactly to go, who will meet them, what the first day looks like hour by hour, dress code in plain terms, whether lunch is provided, and the names and photographs of the five people they will interact with most. Uncertainty is the expensive part of a first day.

Day one. Give them the map, not the tour. A written document listing: what the team does, who does what, which tools are used for what, and how to get help. Include a named buddy — not their manager — whose explicit job is to answer questions that feel too basic to ask a manager.

Week one. Write down the unwritten rules. This single document is the highest-value inclusion artefact most SMBs can produce:

• Which channel is for what, and what response time is expected on each.
• Whether messages after 7 pm expect a reply.
• How direct feedback is expected to be here.
• Whether it is acceptable to decline a meeting, and how.
• Whether cameras are expected on calls.
• Whether interrupting in meetings is normal or rude.
• Who to ask about salary, leave, reimbursements and IT.
• What "urgent" actually means in this company.

Weeks two to four. Define success at 30, 60 and 90 days in writing, with specific deliverables. Ambiguity in a new job is where good hires quietly drown.

Throughout. Offer the adjustment menu at the start, in the same neutral language used at interview: here are things people commonly find helpful, tell us if any would help you, no reason required.

Three Anonymised Scenarios

The following are illustrative composites, not accounts of specific individuals.

Scenario 1: The Analyst Who Was Never "Ready For The Next Level"

A financial analyst at a 120-person services firm had four years of strong output — accurate models, zero missed closes, the person other teams quietly consulted. Every appraisal placed her at "meets expectations". The recurring comment was that she needed to be "more visible" and "more assertive in senior forums".

When a new HR lead audited the previous two cycles, the pattern was obvious. Every colleague rated above her had roughly equivalent delivery and much higher meeting participation. The company had been rating airtime.

The fix was not to send her for an assertiveness workshop. It was to change the process: the leadership pack began citing named contributors, rating rationales required two documented examples of impact, and the words "visible" and "presence" were struck from the form. Her next rating moved on the same body of work, because the work had always been there.

Scenario 2: The Engineer Who Failed The Interview And Passed The Job

A product company kept rejecting a candidate profile it badly needed — deep systems engineers — because its final round was a live whiteboard exercise with three observers.

One candidate, rejected on "poor communication, could not explain approach", had shipped a well-regarded open-source tool that the interviewing team itself used. The hiring manager, curious, re-ran the loop as a take-home problem with a follow-up discussion. The written solution was the strongest they had received that year, and the discussion was articulate the moment it was about the code on the screen rather than performance in front of an audience.

The company replaced the whiteboard round entirely. Offer-accept rates went up across the board, because the format had been penalising nervous candidates of every description, not only neurodivergent ones.

Scenario 3: The Accommodation That Cost Two Thousand Rupees

A customer support executive at a 40-person SaaS company was making errors in the last two hours of every shift. His manager's initial instinct was a performance conversation about attention to detail.

Instead, she asked a better question: when in the day does this work go best, and what makes it harder? The answer was that his desk was directly beside the sales team's calling floor and the cumulative noise was exhausting by 4 pm.

He got noise-cancelling headphones and a seat two rows away, next to a wall. Error rates normalised within three weeks. Total cost: one pair of headphones and a seating change. Nobody disclosed anything, and the manager never needed to know why noise affected him more than it affected her.

That is what most accommodation actually looks like. Not a policy. A question, asked in good faith, followed by a small change.

Manager Training: What Actually Needs Teaching

You do not need a certified programme. You need a 90-minute session, repeated for every new people manager, covering six things:

1. Language. Neurodivergent, not "suffering from". Neurodiverse describes teams, not people. Retire "a bit OCD" and "so ADHD" as casual descriptors.
2. The hard boundary. Never diagnose, never speculate, never repeat a theory about someone's brain. Stay in the territory of work.
3. How to respond to disclosure. Thank them, ask what would help, ask who else may know, then get back to work as normal.
4. How to give feedback on outcomes. Describe the work, cite examples, agree a change. Nothing about the person.
5. Accommodations they can approve themselves. Give managers a standing authority — seating, headphones, hours within a core window, meeting format, written follow-ups — without needing HR sign-off. Friction kills adoption.
6. Confidentiality in practice. Including what to say when a colleague asks why someone gets something they do not.

Run it as scenarios, not slides. Give managers the scripts above and have them practise the awkward ones out loud.

Measuring Whether Any Of This Is Working

Do not measure this by counting disclosures. Disclosure rates are a measure of trust and privacy preference, not of inclusion, and chasing the number creates pressure to disclose — the opposite of what you want.

Measure the system instead.

Those last three survey items are the most useful single instrument here, because every employee can answer them and no one has to identify themselves as anything.

A reasonable cadence for an SMB: audit hiring loops once a year, sample review language every cycle, check rating and promotion distributions every cycle, and run the three engagement items twice a year. If your HRMS holds recruitment, performance and engagement data in one place, most of this becomes a report rather than a project.

A 90-Day Rollout Plan

If you are starting from nothing, do it in this order. Steps one to four cost nothing and deliver most of the value.

1. Days 1-15 — Fix the language. Rewrite your five most-used job descriptions around outcomes. Strike "culture fit", "high energy" and "excellent communication skills" unless genuinely essential. Add the adjustments line to every interview invitation.
2. Days 15-30 — Fix the interview. Standardise questions per role, share them in advance, name interviewers in the invite, replace or redesign live whiteboards and GD rounds, and introduce a scorecard tied to the job outcomes.
3. Days 30-45 — Set the defaults. Written follow-ups after verbal instructions. Agendas in advance. Camera-optional calls. Meeting-free focus blocks. Notice before change. Publish them as team norms, not as accommodations.
4. Days 45-60 — Write the unwritten rules. Produce the norms document and fold it into onboarding, along with 30/60/90-day written expectations and a named buddy for every joiner.
5. Days 60-75 — Train managers and set the accommodation path. Run the 90-minute session. Publish a named intake route, a simple request-to-decision workflow with a target turnaround, and the list of adjustments managers can approve on the spot.
6. Days 75-90 — Fix performance. Update the review form and rating criteria, ban style-only language, brief calibration on the evidence test, and set up the first rating-distribution audit.

Then get the policy language and data handling reviewed by counsel, and revisit the whole thing annually.

Frequently Asked Questions

Do we have to provide an accommodation if someone asks for one? Treat every request seriously and assess it properly rather than reflexively. Legal obligations around reasonable accommodation vary with your entity type, size and location, and the specific facts matter, so confirm your position with employment counsel. Practically, most requests in an SMB are cheap and easy, and the sensible default is to say yes unless there is a genuine operational reason not to. If you must decline, explain why in writing and offer an alternative that addresses the underlying need.

Can we ask a candidate whether they are neurodivergent? No. Do not ask candidates about health, disability or diagnosis during hiring. Ask instead whether they need any adjustments to the process, make clear no reason is required, and focus your assessment on whether they can do the job.

An employee's work is genuinely not meeting the standard. Can we still manage performance? Yes. Neuro-inclusion is not immunity from performance management. What changes is method, not standard. Be specific about the gap, make sure expectations were communicated clearly and in writing, check whether an adjustment would remove the obstacle, give a real opportunity to improve, and document the work — not the person. Where a disability may be relevant, take HR and legal advice before formal action.

What if we cannot afford accommodations? Look again at the cost column in the menu above. The most common accommodations — written instructions, agendas in advance, flexible hours, seating changes, meeting-format changes, notice of change, clear priority order — cost nothing but attention. Headphones, a desk lamp and a screen filter are one-time purchases smaller than a single recruitment fee. Compare against the cost of replacing a capable employee who left because a fixable environment problem was never fixed.

Somebody told their manager in confidence. Who else can know? Only who the employee agrees to, and only what they agree to. Share the arrangement, not the reason. Keep records limited, access-controlled and out of performance documentation. If a colleague asks why someone has a different arrangement, the answer is that working arrangements are individual and not discussed.

Should we run a special hiring programme for neurodivergent candidates? Fix your main process first. Segregated programmes without inclusive core systems tend to produce a small cohort in a token track while the ordinary pipeline continues to filter people out. Once your standard hiring is structured, task-based and adjustment-friendly, a targeted partnership with disability employment organisations can widen your reach usefully.

Our team is fully in-office and open-plan. What can we realistically do? More than you think. Create one bookable quiet room, even a small one. Allow headphones with a clear do-not-disturb norm. Move desks away from calling floors and pantries. Offer staggered start times to dodge peak commute crowding. Add meeting-free focus windows. Swap one bank of overhead tubes for desk lamps in the worst-lit corner. None of these require a new office.

How do we handle a colleague who says the accommodation is unfair? Do not defend it by disclosing anything. State that arrangements are individual, then take the complaint seriously as a signal about your defaults — if several people want quieter space or written instructions, the answer is usually to make those available to everyone rather than to withdraw them from one person.

The Bottom Line

Building a neuro-inclusive workplace is not a values exercise that costs money. It is an accuracy exercise that saves it.

Every process described here — structured interviews, task-based assessments, outcome-based goals, evidence-based ratings, written expectations, clear priorities, predictable notice of change — is simply better management. They exist because unstructured, style-based, verbal-by-default systems produce noisy signals about everybody. Neurodivergent employees just feel the noise first and hardest.

Start with the free things. Fix your job descriptions this month. Add one line about adjustments to every interview invite. Follow verbal instructions with written ones. Strike "culture fit" from your review form. Write down the unwritten rules for your next joiner. Those five changes cost nothing, require no disclosure from anyone, and will improve your hiring and retention regardless of who is on your team.

Then build the plumbing that makes it stick — structured interview scorecards, documented goals and continuous check-ins, evidence-backed reviews, controlled access to sensitive employee records, and reporting that shows you whether your quiet high performers are being rated fairly.

That is exactly the kind of thing an HRMS should carry for you. CozyHR brings recruitment, onboarding checklists, goals and continuous performance check-ins, role-based access to employee records, and payroll into a single system built for the way Indian SMBs actually run. If your current setup is a mix of spreadsheets, WhatsApp and memory, it is worth seeing what the alternative looks like — start a free trial of CozyHR and set up your first structured hiring loop and review cycle this quarter.

This article is general guidance for employers, not legal or medical advice. Verify your statutory obligations around disability inclusion, reasonable accommodation and personal data with qualified counsel for your jurisdiction and entity.