Changing Your Personal Details
Changing Your Personal Details is an employee reference for identifying which workplace records may need an update, contacting each system owner privately, and confirming every change took effect.
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 · Technology · Manufacturing · Healthcare
Overview
Changing Your Personal Details is a content page that helps employees identify which workplace records may be affected by a personal change, find the relevant system owners, and confirm that each record was updated. The fictional Northstar Works example covers contact details, home or mailing address, legal name, and emergency contacts. A system-owner table maps these changes to illustrative systems and gives a check to perform afterward. A worked address-change example shows why updating a People Hub profile may not update payroll or benefits automatically.
Use this reference when an employee needs to update a personal detail and is unsure which records or owners are involved. The sequence is practical: identify what changed, ask each owner about its update route and any evidence requirements, make the update privately, and inspect the result in each system. Supporting-information guidance warns against sharing personal details in team chats, shared mailboxes, or visible ticket comments. The confirmation checklist turns an apparently submitted request into a verified record change.
This page is not a data-collection form, a connected HR workflow, or a source of local legal requirements. The example names and owners are illustrative; replace them with confirmed organization-specific information before publishing. Do not use it to request or store employee details, determine legal eligibility, or resolve sensitive legal or safety matters without the appropriate private support route. Local evidence, timing, and system behavior must be confirmed with each actual owner.
Standards & compliance context
- The page supports data minimization by advising employees to send only requested evidence through an owner's approved private route.
- Its warning against sharing personal details in chats, shared mailboxes, or visible ticket comments reinforces careful handling, but does not replace organizational privacy and security policies.
- Evidence requirements, eligibility, and processing timing vary by country and site; confirm applicable rules with the relevant system owner rather than treating the fictional example as policy.
- Keep the page accessible under WCAG 2.1 AA expectations, including a clear heading structure, readable table headers, and keyboard-accessible navigation.
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
Changing your personal details
Start by identifying the change, confirming each system's route, and keeping personal values out of shared spaces.
-
Identify the affected records, confirm which systems share data, and check the result. Northstar Works is a fictional organization used in this example. Different systems may hold or share your details. Do not assume one update reaches every system: ask which records share data, then check the result. Work through it in this order: identify what changed , confirm the update route with each system owner , then check the result . Keep your new details off this page, out of team chats and out of ticket comments that other people can read. The system names and owners below are illustrative. Evidence requirements, eligibility and timing differ by country and site, so ask the owner of each system.
On this page
Use these contents links to jump directly to the relevant change category, owner mapping, or confirmation guidance.
Which detail changed
Match the type of change to the records that may need review before contacting their owners.
-
Find your change, then use the next table to see who owns each record. Contact details Personal phone number Personal email address Preferred name in the directory Home or mailing address Home address Address for payslips and tax papers Remote work location, if named Legal name Payroll and tax records Benefits enrolment Email name and ID badge Emergency contacts Contact name and number Relationship to you A second contact
System owners
Use this illustrative mapping to identify likely record owners and what to check after an update.
-
Illustrative mapping for Northstar Works. Evidence, eligibility and timing vary by country and site, so ask each owner what applies to you. What changed Systems that may hold it Owner Check afterwards Phone or personal email People Hub profile; emergency contact record People Operations Profile shows the new number or address Home or mailing address People Hub profile; payroll and tax records; benefits enrolment People Operations; Payroll; Benefits Each system shows the new address. Ask Payroll where it reads the address from. Legal name People Hub; payroll and tax; benefits; email display name; ID badge People Operations; Payroll; Benefits; IT Service Desk; Workplace Services Name matches in every system you use. Name changes often need supporting evidence, so ask first. Emergency contact People Hub emergency contacts Name, number and relationship display correctly
Worked example: after a move
Follow the address-change example to see why a profile update may not reach payroll or benefits.
-
A customer-support analyst moves house within the same country. Only the home address changes. Name, phone and emergency contact stay the same. Name what changed Only the home address. That means the profile, payroll and tax records and benefits enrolment may all hold the old one. Update the People Hub profile Use the self-service profile page. The analyst does not assume the change reaches Payroll or Benefits. Ask Payroll how its record is updated Payroll says whether it reads the profile address or needs its own update. The analyst uses Payroll's private route, not a team chat. Ask Benefits whether the address matters Some plan options depend on where you live. Benefits tells the analyst whether the new address affects theirs. Check each system separately The analyst reopens the profile, the payroll record and the benefits summary and compares each with what was submitted. Any mismatch goes back to that system's owner.
Supporting information
Confirm evidence requirements with the owner and submit documents only through an approved private route.
-
Some changes need evidence. The system owner decides what, and how to send it. Before you send a document Ask the owner whether evidence is needed for this change and which kind. Use the owner's approved private route, such as a secure upload inside the system. Send only the pages the owner asks for. Keep it out of shared spaces Team chats, shared mailboxes and distribution-list emails. Ticket titles and comments that other people can see. This page. It never stores or collects your details.
Confirmation checks
Verify each updated record directly and send any mismatch back to that system's owner.
-
Finish each update by checking it, because a submitted request is not the same as a changed record. Open each system you updated, one at a time. Compare what it displays with what you submitted. Look where the detail shows up in daily work: the directory, a payslip preview, the benefits summary, your badge or your email display name. If a system still shows old details, contact that system's owner by its own route. Name the field that is wrong without repeating the sensitive value in a public place. Keep a private note of which owners you have contacted and which updates are still open.
Common questions
Find practical answers about separate systems, mismatches, sensitive changes, and manager involvement.
-
If I update my profile, does that change every system? Not necessarily. Each system has its own record and owner. Some read from the profile and some do not. Ask each owner whether your change carries over, and check the result yourself. Two systems show different details. What do I do? Decide which is correct, then contact the owner of the system that is wrong through its usual route. Say which field differs, and avoid pasting the detail into a public ticket or chat. My change is sensitive or involves a legal or safety matter. Who should I talk to? Contact People Operations first and ask for a private conversation. They will point you to the trained owner. Local rules apply to these cases, and this page does not replace them. Can my manager update my details for me? Usually you update your own records through each owner's route. Ask People Operations what your manager can and cannot do in your location. Avoid sending personal details through your manager's email or chat. I cannot tell which owner to contact. Start with People Operations. Tell them what changed, not the new details, and they can point you to the right system owners.
How to use this template
- Replace the fictional Northstar Works system names and owner roles with routes and responsibilities confirmed by People Operations and each system owner.
- Review the change categories and system-owner table, then identify which records may hold the detail that changed.
- Ask each owner whether the record needs a separate update, whether evidence is required, and which private submission route to use.
- Submit the change through each confirmed route without putting the sensitive value in shared chats, public ticket comments, or this page.
- Open every affected system and compare its displayed record with what you submitted, including relevant directory, payslip, benefits, badge, or email views.
- Contact the owner of any record that remains incorrect, keep a private note of open updates, and confirm the correction.
Best practices
- Check with each system owner whether records share data instead of assuming a profile update propagates everywhere.
- Name the field and affected system when asking for help, but do not repeat the sensitive value in a shared channel.
- Ask whether evidence is required and use only the owner's approved private submission route.
- Verify the saved result in each affected system rather than treating a submitted request as a completed change.
- For an address change, check payroll and benefits separately because they may hold their own records or have different requirements.
- Keep the system-owner mapping and self-service instructions current, and identify an owner responsible for correcting outdated routes.
- Use the page as a routing reference, not as a place to collect, store, or discuss employee personal details.
- For sensitive legal or safety matters, use a private conversation with the appropriate People Operations contact instead of following a routine update path blindly.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Which personal changes does this page cover?
The example covers phone or personal email, home or mailing address, legal name, and emergency contact changes. Its Northstar Works system names and owners are fictional, so replace them with confirmed routes for your organization. Ask the relevant owner about country- or site-specific requirements.
Does changing my profile update every workplace system?
Not necessarily. Payroll, benefits, email, badges, and emergency contacts may use separate records or update routes. Ask each owner whether records share data, then check each system directly.
Who should run this process, and how often?
The employee identifies the change, contacts the owners of affected records, and verifies the results. People Operations can help identify the right owners when the route is unclear. Use the reference whenever a personal detail changes; it is not a recurring inspection.
What if two systems show different details or an update is delayed?
Contact the owner of the system showing the incorrect record through that system's usual route. State which field is wrong without repeating the sensitive value in a shared chat or public ticket. Keep a private note of the outstanding update and check again with the owner.
Does this page explain legal or regulatory requirements?
No. It is a practical routing and confirmation reference, not legal advice or a statement of local requirements. Evidence, eligibility, and timing can vary by country and site, so ask each system owner what applies. For a sensitive legal or safety matter, the example directs employees to People Operations for a private conversation.
What should I do before sending supporting documents?
Ask the system owner whether evidence is needed and what kind they accept. Use the owner's approved private route and send only the requested pages. Do not put personal details or documents in team chats, shared mailboxes, visible ticket comments, or this page.
Can a manager submit a personal-details change for me?
The example expects employees to use each system owner's route and advises asking People Operations what a manager may do in the employee's location. Do not assume a manager can change every record. Avoid sending personal details through a manager's email or chat.
How should our organization customize this template?
Replace the fictional system names, owners, and self-service references with verified local information. Confirm which records each system holds, the approved private submission routes, and what employees should inspect after an update. Keep the worked example clearly illustrative and do not publish actual employee details.
Does this template connect to HR or payroll systems?
No connected system or live data source is specified. The system-owner table is static reference content, and the employee checks records in the relevant systems themselves. Add or link to verified routes only if your intranet supports them and your organization has confirmed the destinations.
Why use this reference instead of asking around in chat?
The page maps common changes to likely record owners and gives employees a consistent sequence: identify, ask, update, and verify. Ad-hoc chat can expose sensitive details and leave employees unsure which systems were checked. Keep the mapping current so the page remains a useful starting point rather than an unverified directory.
Related templates
Go deeper on the topic
-
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) — increasingly called people operations, people ops, or simply "people" — is the organizational function responsible for the systems and...
-
Compare clinical communication platforms and workforce apps for hospitals. Learn how to reach frontline healthcare staff without EHR logins in 2026.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Clinical Staff Engagement with MangoApps: unify schedules, training, and HR self-service in one mobile app for frontline healthcare teams.
-
Healthcare employee engagement ideas to reduce burnout, boost retention, and improve patient outcomes in your health system.
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Changing Your Personal Details 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.