Skip to main content
Loading...
landing

Manager Essentials at a Glance

A one-page manager guide to onboarding, time and attendance, check-ins, employee development, and workplace concerns, with pointers to the MangoApps apps and company guidance managers may need.

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: Retail and frontline operations · Healthcare administration · Manufacturing · Professional services

Overview

Manager Essentials at a Glance is a service-oriented intranet landing page for people managers. Its fictional Northstar example groups five recurring responsibilities: welcoming and onboarding employees, reviewing time and attendance, holding check-ins, supporting development, and responding appropriately to workplace concerns. Two scenario cards illustrate how to make a next step and owner clear in a first-week conversation or a schedule concern, without presenting either scenario as company policy.

The page also points managers toward the MangoApps apps and sources they may need: Forms for configured HR submissions, Policy Hub for published guidance, Calendar for manager dates, and Communications for updates. A policy-links section is intended to connect to the authoritative policy source, while the calendar-events block depends on a connected calendar source. These are setup-dependent destinations, not integrations or workflows guaranteed by the template. The page explicitly asks its owner to verify app availability, connections, the correction route, and the reporting route before publishing.

Use this template as a starting point when managers need one findable guide to common people tasks and the next place to look. Adapt the examples and scope to your policies, locations, and employee groups, and retain the authoritative policy as the home for decisions. Do not use the page as a replacement for required policy, local instructions, formal HR procedures, or an operational escalation directory. Review it when a referenced process, policy, or app connection changes; keep sensitive employee details out of general team updates.

Standards & compliance context

  • Treat the Northstar scenarios as fictional illustrations, not evidence of approved policy, legal requirements, or a required manager schedule.
  • Direct managers to current authoritative guidance for decisions that depend on location, employee group, or company policy; the landing page does not establish local applicability.
  • For serious concerns or immediate safety risks, verify and publish the actual company reporting route rather than relying on this template as an escalation contact.
  • Limit sensitive employee information to appropriate company systems and roles, as the page advises; do not place case details in general team updates.
  • Review page structure, headings, link labels, and contrast for WCAG 2.1 AA accessibility, particularly after customization.

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

The people work managers own

This introduction defines the guide as a starting point and reminds managers to use current processes for policy- or location-dependent decisions.

  • A practical starting point for Northstar office and frontline managers. Managers help employees succeed by keeping people information current, supporting accurate time and attendance, making time for regular check-ins, and acting promptly when a workplace concern is raised. Use the current company process for decisions that depend on policy, location, or employee group. About this example: Northstar and all company-specific situations on this page are fictional. This page is a guide to where to start, not a substitute for current policies or local requirements.

Your recurring responsibilities

These five responsibility cards give managers observable actions for common people-management tasks.

  • Use the relevant company process when a decision depends on policy or location. Welcome and onboard Before a new employee's first shift or workday, confirm that the required onboarding tasks have an owner and that the employee knows where to get help. Agree on first-week priorities and who will show the employee the essential tasks. Check that required onboarding steps are recorded in the company's designated process. People Review time and attendance Review submitted time and attendance information on the schedule set by your company, and follow the established process when an entry needs correction. Check for missing or inconsistent entries before the applicable approval deadline. Ask the employee to clarify a discrepancy rather than guessing or changing information without following process. Routine Hold regular check-ins Make space for employees to raise workload, schedule, support, and progress questions. Agree on the next action and who owns it before the conversation ends. Keep sensitive details in the appropriate company system, not in a general team update. Connect Support growth Discuss skills employees want to build and identify practical opportunities that fit the role and available work. Record agreed development actions through the process your company uses. Check back on the agreed action at a later conversation. Develop Respond to workplace concerns Listen, avoid promising an outcome, and use Northstar's established reporting and support route for the type of concern raised. For an immediate safety risk or serious concern, use the verified company reporting route promptly. Do not investigate beyond your role or share sensitive details with people who do not need them. Respond

Make the next step clear

The fictional handoff scenarios show how a manager and employee can leave a conversation with an owner and follow-up.

  • These fictional examples show a useful manager-employee handoff; they are not Northstar policy or a required schedule. First-week priorities Illustrative example: a manager and a new office employee agree on two priorities for the first week and identify a colleague who can answer day-to-day process questions. Manager: confirm the priorities and the support owner. Employee: raise access or task questions early. Together: revisit what is still unclear at the next check-in. Schedule concern Illustrative example: a frontline employee flags a recurring schedule conflict. The manager listens, checks the applicable process in Policy Hub, and explains the next step without promising an exception. Manager: check the current applicable guidance. Employee: share the dates and work impact needed to understand the request. Together: agree who will follow up and when.

Choose the right MangoApps app

These app descriptions help managers identify where to look while making clear that availability and connections depend on company setup.

  • App setup App access and connections depend on your company's MangoApps configuration. Confirm the relevant app is available and connected after this page is installed. Forms Use Forms for HR requests or submissions when your company has configured the relevant form. Policy Hub Check the current published policy for the topic and employee group before making a policy-based decision. Calendar Check Calendar for manager training dates and review-cycle milestones once the relevant calendar source is connected. Communications Read company updates in Communications; use the current post or notice for details that may change.

Check the current policy

This section is intended to surface the authoritative published policy source and its applicability qualifications.

Upcoming manager dates

This connected calendar section can surface manager dates after the relevant calendar source is configured.

When a concern needs prompt attention

This guidance emphasizes prompt use of a verified reporting route, appropriate information sharing, and a clear handoff.

  • For an immediate safety risk or serious employee concern, follow Northstar's established reporting route. Verify and configure that route and the appropriate support contacts before publishing this page; this template does not provide an operational escalation contact. Page owner and correction route: assign these during setup. Review this page when a related policy, manager process, or app connection changes. Use the verified company reporting process for the concern. Share only the information needed with the appropriate company role. Record or hand off the matter through the designated company process.

How to use this template

  1. Assign a page owner and confirm which manager roles, locations, and employee groups the guide is meant to serve.
  2. Replace the fictional Northstar scenarios with approved examples and verify the company processes for onboarding, time review, check-ins, development, and concerns.
  3. Connect Policy Links to the authoritative published policy source and confirm the relevant Forms, Policy Hub, Calendar, and Communications apps are available.
  4. Configure the Calendar Events source and verify the real reporting and correction routes before making the page visible to managers.
  5. Publish the page in the manager-facing navigation and explain that policy-dependent decisions must be checked against current applicable guidance.
  6. Review the page when a related policy, manager process, or app connection changes, and correct stale guidance through the assigned owner.

Best practices

  • Keep the fictional Northstar framing visible until every sample situation has been reviewed and replaced or deliberately retained as an example.
  • State which manager roles and employee groups the guidance covers instead of assuming one process applies everywhere.
  • Link to one authoritative published policy source rather than copying changeable policy text into the landing page.
  • Set the time-review reminder against your company's actual approval schedule rather than inventing a universal deadline.
  • For check-ins and development conversations, record agreed actions in the designated company process and keep sensitive details out of general team updates.
  • Verify the serious-concern reporting route and appropriate support roles before publishing; do not leave the page's setup warning as the only operational direction.
  • Connect the Calendar Events block to a current source and describe it as a date listing, not an approval or reminder workflow.
  • Give the page a named owner and correction route, then review it when its linked policy, process, or app connection changes.

What this template typically catches

Issues teams running this template most often surface in practice:

Managers cannot tell which locations or employee groups a generic instruction applies to.
A time-entry reminder implies a universal approval deadline that the company has not confirmed.
A sample scenario is mistaken for an approved schedule exception or onboarding requirement.
Policy links point to copied or outdated guidance instead of an authoritative published source.
A Calendar Events section appears empty because its source was not connected.
A serious-concern section names no verified reporting route or appropriate support role.
Sensitive employee details are repeated in general team updates instead of the designated company system.
The page has no assigned owner or correction route, so changed processes and app connections remain stale.

Common use cases

Frontline manager onboarding
A frontline manager uses the onboarding and first-week sections to agree on priorities, identify a day-to-day support owner, and check that required tasks are recorded through the company's designated process. The example stays illustrative until it is aligned with local onboarding guidance.
Office manager time review
An office manager checks for missing or inconsistent time entries before the company's applicable approval deadline and asks the employee to clarify a discrepancy. The template points the manager to the established correction process rather than instructing them to guess or edit records outside it.
Retail manager schedule concern
A retail manager listens when an employee raises a recurring schedule conflict, checks the applicable published guidance, and agrees who will follow up and when. The fictional scenario helps make the handoff clear without promising an exception.
People leader responding to a serious concern
A people leader uses the page's prompt-attention guidance to avoid promising an outcome, limit information sharing, and follow the verified company reporting route. Before rollout, the organization must supply and validate that route because the template does not include an operational contact.

Frequently asked questions

Who is this manager guide designed for?

The example is written for office and frontline managers, with fictional Northstar scenarios to show how the guidance can work across different roles. It covers common people-management tasks rather than every responsibility of a manager. Tailor the scope to the roles, locations, and employee groups your published policies support.

How often should managers use or review this page?

Managers can return to it when onboarding an employee, reviewing time entries, preparing for a check-in, or responding to a concern. The page does not set approval deadlines or a check-in cadence; follow the schedules established by your company. Assign a page owner and review the content when a related policy, process, or app connection changes.

Who should own this page and its app connections?

Assign a page owner during setup, typically the role responsible for keeping manager guidance current. That owner should verify the Policy Hub source, available Forms, Communications guidance, and Calendar connection before publishing. The page also calls for a correction route and verified reporting guidance, but does not supply operational contacts.

Does this template provide HR or legal advice?

No. It directs managers to current company processes and published policies when decisions depend on policy, location, or employee group. The Northstar situations are explicitly fictional examples, not policy or legal guidance. Have the appropriate company policy owner confirm the linked sources and applicability before rollout.

What should a manager do when an employee raises a serious concern?

Listen, avoid promising a particular outcome, and use the verified company reporting route promptly for an immediate safety risk or serious concern. Share only information needed with the appropriate company role, then record or hand off the matter through the designated process. Configure and verify the actual route and support contacts before publishing; this template does not provide an operational escalation contact.

Can we customize the examples and responsibilities?

Yes. Replace the fictional Northstar examples with guidance that matches your own processes, role scope, and applicable employee groups. Keep the first-week and schedule-concern cards clearly framed as examples unless they reflect approved company requirements. Preserve the distinction between a general manager starting point and authoritative policy.

What needs to be connected or configured in MangoApps?

The page describes Forms for configured HR submissions, Policy Hub for current published policies, Calendar for manager dates, and Communications for updates. Its Calendar Events section needs the relevant calendar source connected, and the Policy Links section needs an authoritative policy source. Confirm app availability and connections in your company’s MangoApps setup; the page itself does not create an approval workflow or guarantee access.

How should we roll this guide out to managers?

First assign an owner and confirm the policy source, reporting route, correction route, and app connections. Then review the sample copy with the people responsible for the relevant company processes and make the audience and scope explicit. Publish it in the manager-facing site navigation and tell managers where to find the authoritative policy when a decision requires one.

How is this different from sending managers ad-hoc reminders?

The page groups recurring responsibilities, employee handoff examples, app pointers, policy access, and upcoming dates in one place. That gives managers a consistent starting point instead of relying only on scattered messages. Changing policies and deadlines still need to be maintained in their authoritative sources and reflected here when relevant.

Go deeper on the topic

Related concepts
  • 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 Manager Essentials at a Glance 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.