content

Who Can Help With a Sensitive People Issue?

A fictional employee reference page for choosing a starting point for a sensitive workplace concern. Compare route boundaries, ask about information handling, and identify a next step without assuming confidentiality or policy coverage.

Request pricing See it in MangoApps

Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Professional services · Manufacturing · Technology

9:41

Sites

Overview

Who Can Help With a Sensitive People Issue? is a fictional employee reference page that helps readers choose a starting point without presenting that choice as a policy decision. It opens with a practical orientation, then compares three routes: People Operations, a manager who is not involved in the concern, and an approved conduct or reporting route. Each row pairs a situation where the route may be useful with a boundary employees should consider.

The page is useful in a company or department intranet where employees need a quick, readable way to prepare for a first conversation. Its three scenarios show how to think through a workplace adjustment question, a concern about a manager’s conduct, or uncertainty about policy scope. The ordered steps help an employee describe the concern, ask about information handling, clarify the route, and agree on a next contact or handoff. The FAQ reinforces that the example does not promise confidentiality, eligibility, or a specific outcome.

This is a starting-point guide, not a substitute for an authoritative policy, formal reporting channel, emergency response, or individualized advice. Before publishing, replace the fictional organization’s examples with confirmed local arrangements and link only to verified policy destinations. Do not use the page to decide whether a report qualifies under a policy, or imply that People Operations can handle every concern. Keep the local policy as the authoritative source for scope, process, and available routes.

Standards & compliance context

Treat the page as general orientation, not as a determination of legal rights, policy eligibility, or reporting requirements.
Have the appropriate local policy owner verify route descriptions and confidentiality language before employees rely on them.
Do not imply that any role guarantees confidentiality; state that the employee should ask about applicable information-handling limits.
Use accessible headings, readable table headers, and clear link text, and verify the page against WCAG 2.1 AA expectations.
Keep the approved conduct or reporting policy as the authoritative source and avoid duplicating its rules in a way that could become inconsistent.

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

Start with the route that fits the concern

This introduction makes clear that the page offers a starting point, not a promise about confidentiality or outcomes.

A practical starting point for personal workplace questions At fictional Northstar Works, employees can start with the route that best matches the concern. The right option depends on the issue and the locally applicable arrangements; no route should be assumed to guarantee secrecy or a particular outcome. If you are unsure, you can first ask what a conversation would involve: who may receive the information, how it may be used, and what limits apply before you decide what to share.

Compare the starting points

The table shows when each route may help and the boundary employees should check before choosing it.

Illustrative roles, not a determination of policy coverage or eligibility. Route Useful starting point Boundary People Operations A question about a workplace process, or help identifying an appropriate route. Ask what information is needed and how it may be handled. The role may explain options; do not assume every concern is handled by this team. Manager A work-team conversation when the manager is not involved in the concern and feels appropriate to approach. A manager may help with a team-level conversation. Choose another route if the manager is involved or you do not feel comfortable raising it with them. Approved conduct or reporting route A concern that may fall within the organization’s conduct or reporting policy. Use the locally approved policy to identify the applicable route, scope, and process. Do not infer coverage or confidentiality from this example page.

How the choice might look

These fictional scenarios demonstrate how to apply the route comparison without treating examples as local policy.

These fictional examples show how to think about the first step; local policies determine the actual route. You have a question about requesting a workplace adjustment You could begin by asking People Operations which process applies and what information it needs. Before sharing personal details, ask who may see them and how they may be used. Your concern is about your manager’s conduct A conversation with that manager may not feel suitable. Check the locally approved conduct or reporting policy for an alternative route, or ask People Operations to help identify another option where appropriate. You are unsure whether a reporting policy applies Ask People Operations or the contact named in the local policy which route covers the concern. Describe the issue at the level you are comfortable sharing until you understand the process and its limits.

What happens after you choose a starting point

These steps help employees clarify information handling, process, alternatives, and the next contact before assuming a handoff.

A useful first conversation clarifies the process before assuming what happens next. The receiving role should explain the applicable process and any limits; timing and outcomes depend on local arrangements. Describe the concern Share enough context to explain what help you are seeking. You can begin with a general description while you ask how information will be handled. Ask about information handling Ask who may receive what you share, how it may be used, and what confidentiality limits apply to this route. Clarify the route Ask the receiving role to explain its process, whether the concern fits that route, and what alternatives are available if it does not. Agree on a next contact or handoff Before the conversation ends, confirm who you can contact next and what information, if any, will be passed on. Do not assume a handoff or outcome until it is explained.

If the first route is not suitable

The FAQ addresses common reasons to choose another route and points employees back to approved local policy.

Use the locally approved conduct and reporting policies as the authoritative source for their scope and routes. What if the concern involves the person I was going to approach? You do not have to start with someone involved in the concern. Check the locally approved conduct or reporting policy for another route. Where appropriate, People Operations can help identify an alternative; ask about information handling before sharing details. What if I am not comfortable with the first option? Ask the receiving role to explain its remit, who may receive your information, and what alternatives exist. If the route still does not feel suitable, use another option named in the applicable local policy or ask People Operations to help identify one where appropriate. Does speaking to a particular role guarantee confidentiality? No. This example page cannot establish confidentiality terms. Ask the relevant role to explain the actual limits and information-handling process before deciding what to share. What if I do not know whether a policy applies? Ask People Operations or the contact identified in the locally approved policy which route may apply. The policy, not this example, determines its scope and process.

How to use this template

Replace the fictional organization and route descriptions with roles and policies confirmed for the intended employee audience.
Ask the relevant policy owner to verify the scope, information-handling boundaries, available alternatives, and any local terminology.
Add verified links to the authoritative policy or approved reporting route using the site’s supported link setup, and omit destinations that are not confirmed.
Publish the page in the employee-facing intranet location where people can find sensitive-issue guidance without searching through unrelated team resources.
Assign a content owner to review the page when routes or policies change and to correct any outdated description promptly.

Best practices

Keep the opening focused on choosing a starting point and state plainly that local arrangements determine the applicable route.
Preserve a boundary beside every route so employees can see when an option may not be suitable.
Use role names rather than individual employee names so the page remains maintainable when personnel change.
Keep the approved policy as the authoritative home for scope and process, and link to it only after confirming the destination.
Retain the prompts to ask who may receive information, how it may be used, and what confidentiality limits apply.
Use examples to illustrate decision-making without implying that a particular route guarantees a result or protects information in a specific way.
Identify a local page owner and correction route only after the organization confirms who is responsible.

What this template typically catches

Issues teams running this template most often surface in practice:

Employees may assume that People Operations handles every type of concern unless its role boundary is stated clearly.

A manager may be an unsuitable first contact when the concern involves that manager or the employee does not feel comfortable approaching them.

Employees may mistake an illustrative reporting route for a confirmed local process or eligibility determination.

Confidentiality may be assumed without asking who can receive information or how it may be used.

A policy link may become stale or point to the wrong version if no page owner checks it after policy changes.

A dense explanation of reporting options can bury the immediate task of choosing a safe and appropriate starting point.

Unverified contact details or invented handoff promises can make a reference page misleading.

Common use cases

People Operations: workplace adjustment question

An employee wants to ask which process applies before sharing personal details. The page prompts them to ask what information is needed, who may receive it, and how it may be used.

Employee with a concern about a manager

An employee is considering raising a concern about their manager and does not view that manager as a suitable contact. The page directs them to check the locally approved policy for an alternative route rather than presuming a particular outcome.

Department policy owner: clarify reporting routes

A policy owner uses the comparison table and FAQ to explain that local policy determines scope and process. They replace the fictional examples with confirmed routes and maintain the policy as the authoritative reference.

Company intranet editor: improve issue navigation

An editor places the page where employees can find sensitive-issue guidance and verifies any policy destinations before publication. A named content owner can then review the page when routes or policies change.

Frequently asked questions

Who is this page for, and what kinds of concerns does it cover?

It is a starting-point reference for employees deciding where to raise a sensitive workplace question or concern. The examples include a workplace adjustment question, a concern about a manager, and uncertainty about a reporting policy. It does not determine eligibility, policy coverage, or the right route for a particular case.

How often should an organization review this page?

Review it whenever the relevant People Operations roles, approved conduct or reporting policies, or employee support routes change. A named content owner should also set a review cadence under the organization’s normal content governance process. Update the page promptly when a listed route or its boundaries are no longer accurate.

Who should own and maintain this template?

A People Operations content owner can coordinate updates, with the policy owner confirming the approved routes and their scope. The page should identify a local help or correction route once the organization has confirmed one. Do not publish illustrative role descriptions as confirmed policy or contact information.

Does this page establish confidentiality or legal protections?

No. It explicitly tells employees not to assume secrecy, a particular outcome, or policy coverage from the example. The applicable local policy and the receiving role’s explanation determine how information may be handled. Have qualified local policy or legal reviewers check any organization-specific claims before publication.

What should an employee do if the concern involves their manager?

The example advises that the manager may not be a suitable starting point when they are involved or do not feel appropriate to approach. Employees can check the locally approved conduct or reporting policy for another route. People Operations may help identify an alternative where appropriate, but employees should ask how information will be handled before sharing details.

Can we customize the route names and examples?

Yes. Replace the fictional Northstar Works examples with confirmed local roles, policies, and routes, while preserving the distinction between a starting point and a guaranteed process. Keep the boundary column, information-handling questions, and alternative-route guidance. Remove any option that does not exist or is not approved for the intended audience.

Does this page connect to a reporting tool or case-management system?

No connected system or live workflow is specified in this page structure. The routes are explanatory text, and the examples do not create a case, submit a report, or notify a contact. Add links only after the organization confirms the correct destinations and the page’s supported link setup.

How is this better than an informal list of contacts?

The comparison table explains when each starting point may be useful and what its boundary is, rather than presenting contacts as interchangeable. The examples and ordered steps prompt employees to ask about remit, information handling, alternatives, and handoff. This reduces the risk of implying that a particular person guarantees confidentiality or a specific outcome.

Related templates

Sites

Performance Review Preparation

Prepare for a performance-review conversation with prompts for agreed outcomes, observable eviden...

Sites

Permit-to-Work Navigation

Permit-to-Work Navigation helps authorized employees and contractors identify whom to ask about a...

Sites

Customer Reference Request

A single-page guide for selecting an approved customer reference, checking permission and contact...

Sites

Find the Right Employee Service

Find the employee service that matches a workplace need, with practical details to prepare before...

Sites

Sort Workplace Waste Correctly

A workplace waste-sorting reference with clear material examples, a worked case for an unlisted p...

Forms

Employee Onboarding Form

Employee Onboarding Form for collecting new hire details, tax references, direct deposit, emergen...

Inspections

Forklift Daily Pre-Shift Inspection

Forklift Daily Pre-Shift Inspection template for recording pre-use checks, defects, and out-of-se...

Sop

Fire Evacuation Procedure

A fire evacuation procedure that tells each role exactly what to do from alarm to accountability....

Go deeper on the topic

Related concepts

Digital Workplace vs Modern Intranet

A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Human Resources (HR)

Human resources (HR) — increasingly called people operations, people ops, or simply "people" — is the organizational function responsible for the systems and...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Who Can Help With a Sensitive People Issue? ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Start with the route that fits the concern A practical starting point for personal workplace questions At fictional Northstar Works, employees can start with the route that best matches the concern. The right option depends on the issue and the locally applicable arrangements; no route should be assumed to guarantee secrecy or a particular outcome. If you are unsure, you can first ask what a conversation would involve: who may receive the information, how it may be used, and what limits apply before you decide what to share. Compare the starting points Illustrative roles, not a determination of policy coverage or eligibility. Route Useful starting point Boundary People Operations A question about a workplace process, or help identifying an appropriate route. Ask what information is needed and how it may be handled. The role may explain options; do not assume every concern is handled by this team. Manager A work-team conversation when the manager is not involved in the concern and feels appropriate to approach. A manager may help with a team-level conversation. Choose another route if the manager is involved or you do not feel comfortable raising it with them. Approved conduct or reporting route A concern that may fall within the organization’s conduct or reporting policy. Use the locally approved policy to identify the applicable route, scope, and process. Do not infer coverage or confidentiality from this example page. How the choice might look These fictional examples show how to think about the first step; local policies determine the actual route. You have a question about requesting a workplace adjustment You could begin by asking People Operations which process applies and what information it needs. Before sharing personal details, ask who may see them and how they may be used. Your concern is about your manager’s conduct A conversation with that manager may not feel suitable. Check the locally approved conduct or reporting policy for an alternative route, or ask People Operations to help identify another option where appropriate. You are unsure whether a reporting policy applies Ask People Operations or the contact named in the local policy which route covers the concern. Describe the issue at the level you are comfortable sharing until you understand the process and its limits. What happens after you choose a starting point A useful first conversation clarifies the process before assuming what happens next. The receiving role should explain the applicable process and any limits; timing and outcomes depend on local arrangements. Describe the concern Share enough context to explain what help you are seeking. You can begin with a general description while you ask how information will be handled. Ask about information handling Ask who may receive what you share, how it may be used, and what confidentiality limits apply to this route. Clarify the route Ask the receiving role to explain its process, whether the concern fits that route, and what alternatives are available if it does not. Agree on a next contact or handoff Before the conversation ends, confirm who you can contact next and what information, if any, will be passed on. Do not assume a handoff or outcome until it is explained. If the first route is not suitable Use the locally approved conduct and reporting policies as the authoritative source for their scope and routes. What if the concern involves the person I was going to approach? You do not have to start with someone involved in the concern. Check the locally approved conduct or reporting policy for another route. Where appropriate, People Operations can help identify an alternative; ask about information handling before sharing details. What if I am not comfortable with the first option? Ask the receiving role to explain its remit, who may receive your information, and what alternatives exist. If the route still does not feel suitable, use another option named in the applicable local policy or ask People Operations to help identify one where appropriate. Does speaking to a particular role guarantee confidentiality? No. This example page cannot establish confidentiality terms. Ask the relevant role to explain the actual limits and information-handling process before deciding what to share. What if I do not know whether a policy applies? Ask People Operations or the contact identified in the locally approved policy which route may apply. The policy, not this example, determines its scope and process.