content

System Go-Live Hub

A five-page intranet hub for a system rollout, with sample pages for what changes, training, cutover dates, and support. Clone it to give employees one clear place to orient themselves and find the next step.

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: Manufacturing · Facilities management · Utilities · Healthcare operations

9:41

Sites

Overview

System Go-Live Hub is a five-page intranet site template for orienting employees during a system change. Its linked pages cover the rollout overview, what changes, training, cutover dates, and getting support. The example follows a fictional Northstar rollout of WorkTrack for recording maintenance requests at Cedar Works and Bay Plant; the system, locations, dates, and process details are sample content, not confirmed facts about a real organization.

Use the hub when employees need one navigable place to understand whether a change applies to their role, find learning information, check the transition plan, and choose a support route. The Go-Live page provides quick links and directs readers to check confirmed scope. What Changes compares the example workflow before and after cutover and distinguishes routine requests from urgent safety concerns. Training explains how to search the Training app without implying that a course is assigned or available. Cutover Dates shows a sample milestone table and tells readers to consult the approved schedule source. Getting Support helps employees prepare useful, non-sensitive details for the Service Desk.

Before publishing, replace fictional details with approved rollout facts, identify the affected roles and locations, name the authoritative source for current dates, and confirm the available app routes. Assign an owner to review the pages when scope, training, or milestones change. This template is not a live schedule, training system, ticketing workflow, emergency procedure, or substitute for an authoritative policy. Do not use it when employees need a formal operating procedure or when the rollout's scope and transition instructions have not been confirmed.

Standards & compliance context

Treat this hub as change communication, not as an authoritative policy, safety procedure, or regulatory determination.
Preserve applicable approved emergency and site procedures; the sample explicitly says not to wait for a system ticket to report an urgent hazard.
Confirm role, location, training, and cutover requirements with the responsible rollout owner before publishing them as instructions.
Use accessible headings, descriptive link labels, readable contrast, and keyboard-operable navigation consistent with WCAG 2.1 AA.

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

Go-Live

A clearer way to record work starts 16 November
For Northstar employees in the fictional sample rollout of the WorkTrack system. This gallery example uses fictional system details and dates. Check the rollout's confirmed scope, training, and schedule before relying on them.
Go straight to what you need
Choose a page for the change, learning, schedule, or help. What Changes See which everyday tasks use WorkTrack in this example. Training Find the learning steps and where to check course availability. Cutover Dates Review sample milestones and what employees do at each stage. Getting Support Prepare useful details before contacting the Service Desk.
Start here
A fictional Northstar example—not a confirmed rollout notice. In this sample, Northstar is replacing a locally maintained spreadsheet with WorkTrack for recording maintenance requests at two fictional sites: Cedar Works and Bay Plant. The example cutover date is 16 November 2026 . A real rollout may affect different systems, tasks, roles, locations, and dates. First, check whether your role and location are included in the confirmed rollout information. Then review the change summary, check the Training app for available learning, and use the approved schedule source for current dates. If a detail is missing or no longer matches your work, raise it through the change's published correction or help route.
Check the Training app
Course availability depends on the setup for each rollout. This template does not enroll employees or confirm that a course is available. Open the Training app and search for the confirmed system or course name. Check the course details for your role, completion expectations, and any listed due date. If the expected learning is not listed, use the published rollout help route to ask what applies to you.

What Changes

What changes in the sample rollout
Fictional Northstar example: WorkTrack maintenance requests at Cedar Works and Bay Plant. Summary: In this example, employees stop adding new maintenance requests to a shared spreadsheet after cutover and enter them in WorkTrack instead. The sample does not establish which tasks or locations a real rollout includes; use confirmed scope information for that. The example change is limited to how a request is recorded and followed. It does not state that emergency response, maintenance priorities, or local safety procedures change. Follow the applicable approved procedures for those matters.
Compare the example workflow
These are illustrative task descriptions, not a statement of Northstar policy. Before the example cutover A maintenance request is added to the shared spreadsheet. Record the equipment or area and describe the issue. Use the current approved route for urgent hazards or immediate risks. After the example cutover A new maintenance request is entered in WorkTrack. Include the equipment or area, what happened, and when it was noticed. Use the current approved route for urgent hazards or immediate risks; do not wait for a system ticket.
Common questions
Confirm scope and access through the published rollout information. Does this change affect every Northstar employee? No such scope is confirmed by this fictional example. The rollout owner should publish the affected roles and locations. If your work is not listed, ask your manager or use the rollout's published help route before assuming the new process applies. What if I still need to use the spreadsheet? Follow the approved transition instructions for your rollout. The example does not set a real shutdown date or exception process. Check the authoritative cutover update before entering new requests. Where can I check whether dates or scope have changed? Use the rollout's designated authoritative update source. A real site owner should name or connect that source after it is confirmed; this example does not create a live update feed. Does this change replace urgent or safety reporting? No. This sample system change is about recording routine maintenance requests. Follow your applicable approved emergency, safety, and site procedures for urgent issues.

Training

Find the learning that applies to your role
The Training app is the place to check for available courses and completion records. In this fictional example, employees who enter or follow maintenance requests may need WorkTrack learning. A real rollout owner must confirm which roles need training, which courses are required, and any completion deadlines before publishing those details. Start by checking the rollout's confirmed scope. Then open the Training app and search for the confirmed system or course name. This page does not enroll you, confirm course availability, or set a deadline.
Prepare and complete training
Use the confirmed instructions for your rollout if they differ from this example. Confirm that the rollout applies to you Check the published list of affected roles and locations. Ask through the rollout's help route if your work is not clearly covered. Open the Training app Search for the system or course name provided in the confirmed rollout notice. Review the course description before starting. Complete the applicable learning Follow the course instructions and any confirmed due date. Keep the completion confirmation shown by the Training app. Raise a missing-course question If a required course is not visible or your completion is not recorded, contact the rollout's published support route with the course name and what you see.
Use Training for course status
Course assignments and records depend on the tenant's Training setup. This site does not create training content, assignments, or completion records. Open the Training app to find courses available to you. Check the course page for instructions and any configured completion details. Use the rollout's confirmed support route for access or assignment questions.

Cutover Dates

Example schedule only
Every date and milestone below is fictional and illustrative. Replace it with the approved schedule for the rollout, and identify the authoritative source employees should check when it changes.
Fictional WorkTrack schedule
Northstar sample dates for illustration; not approved rollout dates. Milestone Example date Employee action Scope and access notice 2 November 2026 Check whether your role and location are included; report unclear scope through the published route. Training period begins 9 November 2026 Open Training and check for the confirmed course that applies to your role. Example cutover 16 November 2026 Use WorkTrack for new requests only if the confirmed rollout instructions say it applies to you. Transition check 23 November 2026 Follow the published instructions for open requests and report issues through the Service Desk.
When a date changes
Check the rollout's designated authoritative update source before acting on a date. A real rollout owner should identify that source and keep this page aligned with it; do not treat this fictional table as a live schedule. At cutover, follow the confirmed instructions for work already in progress. Do not copy open items or stop using an existing process unless the approved rollout instructions explain what to do. If the schedule or handoff is unclear, use the published support route and include the milestone you are asking about.

Getting Support

Use the Service Desk app for system help
Describe what you were doing and what happened; this page does not submit a request. For access problems, errors, or questions using the new system, open the Service Desk app and follow its request process. This template does not set a response-time promise or create a support ticket. Before contacting the Service Desk, note the system name, your work location or team, the task you were trying to complete, the time the issue occurred, and the exact error text. Include a screenshot only if it contains no sensitive personal or operational information. For immediate safety concerns or urgent hazards, use the applicable approved emergency or site procedure rather than waiting for a system support request.
Describe the issue clearly
Choose the description that best matches what you need help with, then submit it through the Service Desk app. Access or sign-in You cannot open the system, sign in, or see a task you expect to use. Name the system and the page or task you tried to open. State whether you can sign in and what message appears. Access How-to question You can open the system but are unsure which steps to follow for a task. Describe the task and the step where you are unsure. Include the role or location if it affects the instructions you see. Guidance Error or unexpected result A task fails, information looks incorrect, or the system behaves differently than expected. Write down the time and the exact error text. Explain what you expected and what happened instead. Issue
Submit through Service Desk
Use the Service Desk app's available request options for the rollout or system. If the correct request option is not clear, describe the issue plainly rather than selecting an unrelated category. Open the Service Desk app and choose the request option that best fits your issue. Add the system name, task, location or team, time, and any non-sensitive error details. Use the app to check or respond to your request if it provides those options.

How to use this template

Clone the site and verify that the horizontal navigation points to the Go-Live, What Changes, Training, Cutover Dates, and Getting Support pages.
Replace the fictional system, company, locations, tasks, dates, and scope statements with rollout information approved for the intended audience.
Assign a rollout owner to confirm affected roles and locations, identify the authoritative schedule and correction route, and validate the published help path.
Update the Training page with confirmed course names and expectations, then verify that employees can find the relevant courses in the Training app.
Publish the approved cutover milestones and employee actions, including clear instructions for open work and any transition exceptions.
Review the hub at each rollout milestone, correct outdated information, and direct access or system-use issues to the confirmed Service Desk route.

Best practices

Mark illustrative sample details clearly until an owner replaces them with approved rollout facts.
State affected roles and locations explicitly instead of implying that a change applies to every employee.
Keep one authoritative source for changing dates and identify it on the Cutover Dates page.
Describe only confirmed training requirements, and tell employees how to check course availability in the Training app.
Preserve the distinction between routine system requests and urgent safety or emergency reporting.
Ask employees to include the system, task, location or team, time, and exact non-sensitive error details when seeking support.
Review every page link and app route after cloning; a visible link is useful only if the destination is available to its audience.
Give a role clear responsibility for correcting scope, schedule, or support details when rollout information changes.

What this template typically catches

Issues teams running this template most often surface in practice:

Fictional sample dates or system details remain visible and are mistaken for an approved rollout notice.

Affected roles and locations are not stated, leaving employees unsure whether the change applies to their work.

A schedule is copied into the hub without identifying the authoritative source that employees should check for updates.

Training is described as required or available even though the course assignment and tenant setup have not been confirmed.

Employees assume a routine system ticket replaces an urgent hazard or emergency reporting route.

Support requests omit the task, time, location, or exact error, making the issue difficult to understand.

Pages are published with broken internal links or app routes that employees cannot access.

No rollout owner reviews the pages when scope, milestones, or transition instructions change.

Common use cases

Manufacturing systems rollout

A rollout owner adapting the fictional WorkTrack example can explain how maintenance requests move from a shared spreadsheet to a new system. The What Changes and Cutover Dates pages help employees distinguish the routine workflow from existing urgent safety procedures.

Facilities operations change

A facilities team can use the five-page structure to orient staff across locations, direct them to role-appropriate learning, and explain where to report access or task errors. Replace the sample locations and process only after the operational scope is approved.

Healthcare operations software launch

An implementation team can adapt the hub to guide affected operational roles to confirmed learning, transition instructions, and support. Keep clinical, privacy, safety, and emergency procedures in their authoritative homes rather than treating this communication hub as a replacement.

Multi-site utility platform transition

A change owner can use the landing page and five-item navigation to separate employee orientation from scope, training, dates, and support details. Confirm which locations and roles are included and provide one authoritative source for schedule changes.

Frequently asked questions

What does the System Go-Live Hub template include?

It includes five linked pages: Go-Live, What Changes, Training, Cutover Dates, and Getting Support. The sample follows a fictional WorkTrack rollout for maintenance requests at two fictional sites, with clear reminders that its scope and dates are illustrative. The pages guide employees from orientation to learning, transition information, and help.

Who should use this hub, and who owns its updates?

Employees use it to check whether a system change applies to them and to find the relevant next step. The rollout owner should confirm scope, training expectations, schedule, and the authoritative update source before publishing. Assign a named role to maintain the pages and route corrections or unresolved questions through the rollout's published help path.

How often should the pages be reviewed?

Review the hub before launch, whenever scope or milestones change, and at each transition point that affects employee actions. The Cutover Dates page explicitly directs readers to an authoritative source when dates change, so its sample table should not be treated as a live schedule. After the transition, confirm whether the hub should be updated, archived, or linked to ongoing support information.

Does this template establish regulatory or safety requirements?

No. It is a communication and orientation hub, not a compliance policy or operational procedure. The sample distinguishes routine system support from urgent hazards and tells employees to follow applicable approved emergency and site procedures. Confirm local requirements and preserve existing authoritative procedures when adapting the pages.

What should employees do if they still need the old process at cutover?

The sample does not define a real exception, shutdown, or transition process. Replace it with the approved instructions for open work and any permitted continued use before launch. Until those instructions are confirmed, employees should check the authoritative rollout update and ask through the published help route rather than assume.

What should be customized before publishing?

Replace the fictional company, system, task, locations, dates, and rollout details with confirmed information. Identify affected roles and locations, the actual course names and completion expectations, the authoritative schedule source, and the correct help route. Remove or rewrite sample claims that do not apply, and check every internal page link after cloning.

Does the hub integrate with the Training or Service Desk apps?

The pages direct employees to the Training and Service Desk apps, but the template does not enroll learners, create tickets, or verify course status. Any connected callout content depends on the tenant's configured setup and does not itself create a workflow. Confirm the apps and their request or course options are available to the intended audience.

How is this different from sending a launch email or sharing a schedule?

A one-time message can become hard to find and may separate training, scope, dates, and support across different sources. This hub gives those related topics distinct pages under one navigation menu, while directing employees to the authoritative source for changing details. It still needs an owner and accurate links; publishing the template alone does not keep information current.

Related templates

Sites

Jury Duty and Public Service Leave

A practical jury duty and public service leave reference for employees and managers: notify the r...

Sites

Code of Conduct at a Glance

A one-page employee guide to ten illustrative conduct expectations, with a connection to the auth...

Sites

Policy Change Explainer

A single-page guide that explains a sample policy change, its effective date, possible scope, and...

Sites

Access Request Preparation

Prepare a system-access request with a clear work need, narrowly scoped role, approver, and durat...

Sites

Data Quality Issue Guide

The Data Quality Issue Guide helps data consumers document a suspected discrepancy, compare it wi...

Forms

Employee Onboarding Form

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

Inspections

Fall Protection Equipment Inspection

Inspect PFAS gear before use or on an annual competent-person schedule with a clear checklist for...

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...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with System Go-Live Hub 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.

5 pages Go-Live What Changes Training Cutover Dates Getting Support

Go-Live A clearer way to record work starts 16 November For Northstar employees in the fictional sample rollout of the WorkTrack system. This gallery example uses fictional system details and dates. Check the rollout's confirmed scope, training, and schedule before relying on them. Go straight to what you need Choose a page for the change, learning, schedule, or help. What Changes See which everyday tasks use WorkTrack in this example. Training Find the learning steps and where to check course availability. Cutover Dates Review sample milestones and what employees do at each stage. Getting Support Prepare useful details before contacting the Service Desk. Start here A fictional Northstar example—not a confirmed rollout notice. In this sample, Northstar is replacing a locally maintained spreadsheet with WorkTrack for recording maintenance requests at two fictional sites: Cedar Works and Bay Plant. The example cutover date is 16 November 2026 . A real rollout may affect different systems, tasks, roles, locations, and dates. First, check whether your role and location are included in the confirmed rollout information. Then review the change summary, check the Training app for available learning, and use the approved schedule source for current dates. If a detail is missing or no longer matches your work, raise it through the change's published correction or help route. Check the Training app Course availability depends on the setup for each rollout. This template does not enroll employees or confirm that a course is available. Open the Training app and search for the confirmed system or course name. Check the course details for your role, completion expectations, and any listed due date. If the expected learning is not listed, use the published rollout help route to ask what applies to you. What Changes What changes in the sample rollout Fictional Northstar example: WorkTrack maintenance requests at Cedar Works and Bay Plant. Summary: In this example, employees stop adding new maintenance requests to a shared spreadsheet after cutover and enter them in WorkTrack instead. The sample does not establish which tasks or locations a real rollout includes; use confirmed scope information for that. The example change is limited to how a request is recorded and followed. It does not state that emergency response, maintenance priorities, or local safety procedures change. Follow the applicable approved procedures for those matters. Compare the example workflow These are illustrative task descriptions, not a statement of Northstar policy. Before the example cutover A maintenance request is added to the shared spreadsheet. Record the equipment or area and describe the issue. Use the current approved route for urgent hazards or immediate risks. After the example cutover A new maintenance request is entered in WorkTrack. Include the equipment or area, what happened, and when it was noticed. Use the current approved route for urgent hazards or immediate risks; do not wait for a system ticket. Common questions Confirm scope and access through the published rollout information. Does this change affect every Northstar employee? No such scope is confirmed by this fictional example. The rollout owner should publish the affected roles and locations. If your work is not listed, ask your manager or use the rollout's published help route before assuming the new process applies. What if I still need to use the spreadsheet? Follow the approved transition instructions for your rollout. The example does not set a real shutdown date or exception process. Check the authoritative cutover update before entering new requests. Where can I check whether dates or scope have changed? Use the rollout's designated authoritative update source. A real site owner should name or connect that source after it is confirmed; this example does not create a live update feed. Does this change replace urgent or safety reporting? No. This sample system change is about recording routine maintenance requests. Follow your applicable approved emergency, safety, and site procedures for urgent issues. Training Find the learning that applies to your role The Training app is the place to check for available courses and completion records. In this fictional example, employees who enter or follow maintenance requests may need WorkTrack learning. A real rollout owner must confirm which roles need training, which courses are required, and any completion deadlines before publishing those details. Start by checking the rollout's confirmed scope. Then open the Training app and search for the confirmed system or course name. This page does not enroll you, confirm course availability, or set a deadline. Prepare and complete training Use the confirmed instructions for your rollout if they differ from this example. Confirm that the rollout applies to you Check the published list of affected roles and locations. Ask through the rollout's help route if your work is not clearly covered. Open the Training app Search for the system or course name provided in the confirmed rollout notice. Review the course description before starting. Complete the applicable learning Follow the course instructions and any confirmed due date. Keep the completion confirmation shown by the Training app. Raise a missing-course question If a required course is not visible or your completion is not recorded, contact the rollout's published support route with the course name and what you see. Use Training for course status Course assignments and records depend on the tenant's Training setup. This site does not create training content, assignments, or completion records. Open the Training app to find courses available to you. Check the course page for instructions and any configured completion details. Use the rollout's confirmed support route for access or assignment questions. Cutover Dates Example schedule only Every date and milestone below is fictional and illustrative. Replace it with the approved schedule for the rollout, and identify the authoritative source employees should check when it changes. Fictional WorkTrack schedule Northstar sample dates for illustration; not approved rollout dates. Milestone Example date Employee action Scope and access notice 2 November 2026 Check whether your role and location are included; report unclear scope through the published route. Training period begins 9 November 2026 Open Training and check for the confirmed course that applies to your role. Example cutover 16 November 2026 Use WorkTrack for new requests only if the confirmed rollout instructions say it applies to you. Transition check 23 November 2026 Follow the published instructions for open requests and report issues through the Service Desk. When a date changes Check the rollout's designated authoritative update source before acting on a date. A real rollout owner should identify that source and keep this page aligned with it; do not treat this fictional table as a live schedule. At cutover, follow the confirmed instructions for work already in progress. Do not copy open items or stop using an existing process unless the approved rollout instructions explain what to do. If the schedule or handoff is unclear, use the published support route and include the milestone you are asking about. Getting Support Use the Service Desk app for system help Describe what you were doing and what happened; this page does not submit a request. For access problems, errors, or questions using the new system, open the Service Desk app and follow its request process. This template does not set a response-time promise or create a support ticket. Before contacting the Service Desk, note the system name, your work location or team, the task you were trying to complete, the time the issue occurred, and the exact error text. Include a screenshot only if it contains no sensitive personal or operational information. For immediate safety concerns or urgent hazards, use the applicable approved emergency or site procedure rather than waiting for a system support request. Describe the issue clearly Choose the description that best matches what you need help with, then submit it through the Service Desk app. Access or sign-in You cannot open the system, sign in, or see a task you expect to use. Name the system and the page or task you tried to open. State whether you can sign in and what message appears. Access How-to question You can open the system but are unsure which steps to follow for a task. Describe the task and the step where you are unsure. Include the role or location if it affects the instructions you see. Guidance Error or unexpected result A task fails, information looks incorrect, or the system behaves differently than expected. Write down the time and the exact error text. Explain what you expected and what happened instead. Issue Submit through Service Desk Use the Service Desk app's available request options for the rollout or system. If the correct request option is not clear, describe the issue plainly rather than selecting an unrelated category. Open the Service Desk app and choose the request option that best fits your issue. Add the system name, task, location or team, time, and any non-sensitive error details. Use the app to check or respond to your request if it provides those options.