Pronoun and Name Use Policy
A Pronoun and Name Use Policy template for setting expectations on chosen names, pronouns, records, and respectful workplace communication. Use it to standardize day-to-day practice and document the interactive process where needed.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Healthcare · Retail · Technology · Education · Professional Services
Overview
This Pronoun and Name Use Policy template sets a clear standard for how employees, managers, HR, and systems should use chosen names and pronouns at work. It covers the policy statement, request and update procedure, roles and responsibilities, exceptions, and discipline so the organization can respond consistently when someone asks to be addressed differently from their legal record.
Use it when you need a written rule for respectful communication, onboarding, directory and badge updates, and handling repeated misuse after notice. It is especially useful where HRIS, payroll, email, and facility systems do not all use the same name field. The template also helps document the interactive process when a name or pronoun issue overlaps with a disability-related accommodation or another protected concern.
Do not use this as a substitute for legal advice or as a one-size-fits-all global policy. It should be customized for the jurisdictions where you operate, the systems you use, and the roles that need access to legal names for payroll, tax, benefits, safety, or compliance reasons. It is also not the right tool for unrelated identity, conduct, or harassment issues unless those issues are tied to workplace name and pronoun use. The strongest version of this template makes the operational steps explicit, including who receives requests, how quickly changes are made, what records remain legal-name only, and what happens if someone intentionally ignores the policy.
Standards & compliance context
- The policy should be written consistently with Title VII and EEOC anti-harassment principles, including protection from sex-based harassment and retaliation.
- If a request overlaps with a disability-related need, the policy should support the ADA interactive process and avoid rigid rules that block reasonable accommodation.
- Where employee conduct or concerted activity is involved, the policy should not be used to chill NLRA Section 7 rights or protected workplace discussions.
- Legal-name use may still be required for payroll, tax, benefits, immigration, or other records governed by FLSA-related administration and state recordkeeping rules.
- State and local protections can be broader than federal law, so California, New York, Illinois, Washington, and local human rights rules should be checked before rollout.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Purpose
Explains why the policy exists and what workplace problem it is meant to solve.
-
This policy establishes the company's expectations for respectful use of employees' chosen names and pronouns in workplace interactions, records, and systems. The policy is intended to support a respectful workplace, reduce miscommunication, and help the company comply with applicable anti-discrimination laws, including **Title VII of the Civil Rights Act of 1964** and related **EEOC** guidance. The company will address name and pronoun requests in a consistent, confidential, and good-faith manner.
Scope
Defines who and what systems the policy applies to so there is no confusion about coverage.
-
This policy applies to all employees, interns, temporary workers, contractors, managers, supervisors, recruiters, HR personnel, and IT administrators when acting on behalf of the company. It applies to workplace interactions, written communications, meeting settings, email signatures, directories, badges, HR records, learning systems, collaboration tools, and other company-controlled systems. **California employees:** This policy must be applied consistently with the **California Fair Employment and Housing Act (FEHA)** and any applicable local ordinances. **New York employees:** This policy must be applied consistently with the **New York State Human Rights Law** and any applicable local ordinances.
Definitions
Clarifies key terms like chosen name, legal name, pronouns, and interactive process before the rules begin.
-
For purposes of this policy: - **Chosen name** means the name an employee asks others to use in the workplace. - **Pronouns** means the words an employee asks others to use when referring to them. - **Legal name** means the name required for payroll, tax, benefits, background checks, or other legally required records. - **Deadnaming** means using a person's former name when they have asked to be called by a different name. - **Misgendering** means referring to a person with pronouns or gendered language that are inconsistent with their stated identity. - **Interactive process** means a good-faith, individualized discussion to determine whether a workplace adjustment or system change is needed to support the employee while meeting business and legal requirements.
Policy Statement
States the organization’s rule for respectful name and pronoun use in plain, enforceable language.
-
Employees are expected to use coworkers' chosen names and pronouns in good faith and without unnecessary questioning, delay, or disclosure. The company prohibits intentional or repeated deadnaming or misgendering, including in meetings, emails, chat messages, documents, and verbal communication, when the employee's chosen name or pronouns have been communicated. Managers and supervisors must model respectful use of names and pronouns and must correct mistakes promptly and professionally. Repeated refusal to use a coworker's chosen name or pronouns may result in corrective action, up to and including termination, consistent with applicable law and company policy. Employees are not required to provide medical documentation, legal documentation, or a court order to request use of a chosen name or pronouns, unless a specific legal or system requirement applies to a particular record or process.
Procedure
Shows the exact steps for requesting updates, making corrections, and escalating issues.
-
1. **Employee request:** Employees may inform HR, their manager, or another designated contact of their chosen name and pronouns verbally or in writing. 2. **Record update review:** HR and People Operations will review which systems can be updated to reflect the chosen name and pronouns and which records must retain the legal name for legal, payroll, tax, benefits, or security reasons. 3. **System changes:** Where feasible, the company will update email display names, directories, badges, org charts, collaboration tools, and internal profiles promptly after the request is received. 4. **Confidential handling:** HR will limit disclosure of legal name or prior name information to personnel with a legitimate business need. 5. **Corrections:** If an employee is misnamed or misgendered, the listener should correct the mistake promptly, apologize briefly, and continue the conversation without unnecessary attention. 6. **Escalation:** Employees who experience repeated misuse, harassment, or retaliation should report the issue to HR, Ethics, Compliance, or their manager. HR will review the concern and, where appropriate, use the company's complaint and investigation process. 7. **Interactive process:** If a requested change affects a system, essential function, security control, or legal record, HR, IT, and the employee will use the interactive process to identify a workable solution.
Roles & Responsibilities
Assigns ownership so employees, managers, HR, IT, and payroll know their part.
-
- **Employees:** Use coworkers' chosen names and pronouns in good faith; report concerns promptly. - **Managers and supervisors:** Model compliant behavior, correct misuse, support updates, and avoid retaliation. - **HR / People Operations:** Receive requests, coordinate record updates, maintain confidentiality, and document exceptions. - **IT administrators:** Implement approved display-name, directory, badge, and system changes where technically feasible. - **Recruiters:** Use the candidate's stated name and pronouns during recruiting and onboarding, subject to legal record requirements. - **Policy holder:** Owns the policy, approves exceptions, and ensures periodic review.
Compliance, Exceptions, and Discipline
Explains lawful exceptions, how violations are handled, and what discipline can follow repeated misuse.
-
Failure to follow this policy may result in corrective action, up to and including termination, depending on the severity, frequency, intent, and impact of the conduct. The company may make limited exceptions when a legal, payroll, tax, benefits, immigration, security, or technical requirement requires use of a legal name or a specific identifier. Exceptions must be handled narrowly and confidentially. This policy does not restrict employees' rights under the **NLRA Section 7** to engage in protected concerted activity, or any rights under applicable whistleblower, leave, accommodation, or anti-retaliation laws. Nothing in this policy limits the company's obligations under the **ADA** to engage in the interactive process for a reasonable accommodation, or under the **FMLA** to administer qualifying leave requests, or under the **FLSA** to maintain accurate wage-and-hour records.
Review & Revision
Sets the cadence for updates so the policy stays aligned with law, systems, and practice.
-
This policy will be reviewed at least annually and updated as needed to reflect changes in law, system capabilities, or company practices. The policy holder is responsible for approving revisions, coordinating legal review where appropriate, and communicating material changes to affected employees and managers. Jurisdiction-specific updates must be documented explicitly, including any state or local requirements that affect name, pronoun, recordkeeping, privacy, or anti-discrimination obligations.
How to use this template
- 1. Fill in the effective_date, version, review_frequency, applicable_jurisdictions, and applicable_roles fields before publishing the policy.
- 2. Define which systems use legal names and which can display chosen names, including HRIS, payroll, email, badges, directories, and learning platforms.
- 3. Assign the intake owner, approval path, and update timeline so employees know exactly where to submit a request and who completes the change.
- 4. Train managers and HR on how to correct mistakes, document repeated misuse, and escalate conduct concerns without arguing about identity.
- 5. Roll out the policy with a short employee notice, then review exceptions, complaints, and system gaps after the first implementation cycle.
Best practices
- State plainly that intentional, repeated misuse after notice may lead to documented warning, PIP, or other discipline under the conduct policy.
- Separate legal-name requirements from chosen-name usage so payroll, tax, benefits, and background-check records stay accurate while daily-use systems can be updated.
- Use a simple request path with a named HR contact, because employees should not have to explain their situation to multiple managers.
- Document the interactive process when a name or pronoun issue overlaps with an ADA accommodation request or another protected workplace concern.
- Train managers to correct themselves briefly and move on, rather than debating the request in front of coworkers.
- Add a clear escalation path for retaliation, harassment, or refusal to update records after approval.
- Audit badges, directories, and email signatures after onboarding and role changes so the policy works in practice, not just on paper.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this policy template actually cover?
It covers how employees, managers, HR, and systems should use chosen names and pronouns in workplace communication, records, directories, badges, and email display names where feasible. It also includes a procedure for updating records, handling mistakes, and escalating repeated misuse. The template is designed to be adapted to your HRIS, payroll, badge, and directory systems. It is not a general diversity statement; it is a working policy with steps and accountability.
Who should own and enforce a pronoun and name use policy?
HR usually owns the policy holder role, with managers responsible for day-to-day enforcement and correction of misuse. IT, payroll, and facilities often need to support record changes and display-name updates. The policy should also name a reporting path for employees who experience repeated misuse or retaliation. Clear ownership matters because these issues often span conduct, records, and system administration.
How often should this policy be reviewed?
Review it at least annually, and sooner if state law, EEOC guidance, or internal systems change. It should also be revisited after a complaint, a transition in HR software, or a broader policy update affecting anti-harassment or records management. Annual review helps keep the procedure aligned with actual workflows. The review_frequency and effective_date fields should be filled in before rollout.
Does this policy create legal obligations under Title VII or the ADA?
The policy should be written to support compliance with Title VII, EEOC anti-harassment principles, and the ADA interactive process where a name or pronoun issue intersects with a disability-related accommodation. It should not promise outcomes that conflict with legal or operational constraints, such as changing legal records without a lawful basis. The policy should also avoid retaliation and harassment. State and local protections may be broader than federal law, so carve-outs should be added where required.
What are the most common mistakes when implementing this policy?
The biggest mistake is treating it as a values statement without a procedure for updates, corrections, and escalation. Another common gap is failing to distinguish legal name requirements from chosen-name usage in email, badges, rosters, and internal systems. Employers also miss training managers on how to respond to mistakes without escalating conflict. Finally, policies often omit discipline for repeated, intentional misuse after notice.
Can this template be customized for different jurisdictions or employee groups?
Yes. You can add jurisdiction-specific language for California, New York, Illinois, Washington, or local ordinances, and you can tailor the procedure for employees, contractors, applicants, and interns. If your organization operates across multiple states, the policy should identify where legal name use is required and where chosen-name use is preferred or permitted. You can also add role-based instructions for front-line managers, recruiters, and customer-facing teams. Keep the core policy consistent and use carve-outs for local differences.
How does this policy fit with HRIS, payroll, and badge systems?
The policy should specify which systems use the legal name and which can display the chosen name, such as email, badges, and internal directories. It should also define who approves changes and how quickly updates should be made after a request. Integrations matter because inconsistent records are a common source of errors and complaints. The template can be adapted to match your HRIS workflow and data privacy controls.
How should managers roll this out without creating confusion?
Managers should receive a short briefing on what to do when an employee shares a chosen name or pronouns, how to correct mistakes, and when to escalate to HR. Rollout should include the policy, a simple request form or intake path, and a reminder that repeated intentional misuse can lead to discipline. It helps to pair the policy with training on respectful communication and anti-harassment expectations. A clear rollout reduces ad-hoc handling and inconsistent responses.
Related templates
Ready to use this template?
Get started with MangoApps and use Pronoun and Name Use Policy with your team — pricing built for small business.
