Facilities & Workplace Hub
The Facilities & Workplace Hub puts office locations, access, rooms, food, shipping, and facilities help in one task-first employee starting point.
Trusted by frontline teams 15 years of frontline software
Built for: Corporate Offices · Higher Education Campuses · Healthcare Administration · Financial Services Workplaces · Technology Companies
Overview
The Facilities & Workplace Hub is a task-first intranet landing page for everyday office and workplace services. Its hero establishes one starting point for employees, contractors, and visitors, while the primary CTA sends people directly to a facilities request form and the secondary CTA helps them find an office. The quick-links section surfaces high-intent actions including meeting-room booking, cafeteria hours, lost-badge replacement, package shipping, and reporting something broken.
Use this site_type as the front door to a facilities service library, not as the place to store every policy or location detail. Link the hub to focused pages such as Locations & Access, Rooms & Meetings, Amenities & Mail, and Facilities Requests. Each service page can use the appropriate page_type, section archetypes, owner, review date, contact route, and escalation guidance. This hub-and-spoke pattern follows employee-experience conventions used in Atlassian and Microsoft Viva environments and supports the Gartner digital-workplace goals to find, do, know, and connect.
Do not use the landing page as a substitute for emergency instructions, a full building directory, a ticketing system, or a location-specific safety manual. Put urgent exceptions and formal policies on maintained destination pages, then make them easy to reach. Before publishing, replace sample links, confirm permissions, add navigation, and test the experience with people using keyboard navigation and assistive technology where the site is audience-restricted.
Standards & compliance context
- Treat access, emergency, safety, food-allergen, and accessibility instructions as location-specific operational content that requires review by the responsible policy owner.
- For an audience-restricted page, apply WCAG 2.1 AA practices including keyboard access, logical heading structure, descriptive links, text alternatives, and readable contrast.
- Do not place sensitive security details such as exploitable badge-system procedures or restricted building information on broadly visible pages; link to appropriately permissioned guidance.
- Keep formal emergency and workplace safety procedures authoritative on their approved policy pages, with clear links from the relevant facilities service page.
- Record ownership and review cadence for operational content so outdated hours, access rules, and escalation instructions can be identified and corrected.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Clone the site and replace the sample CTA and quick-link URLs with your approved facilities request form, location pages, room-booking tool, cafeteria information, badge process, and shipping portal.
- Create or connect destination pages for Locations & Access, Rooms & Meetings, Amenities & Mail, and Facilities Requests, assigning an owner and review cadence to each page.
- Configure the site navigation tree so the Workplace Hub is the landing page and service pages are reachable from both the sidebar and the task links.
- Ask facilities, security, reception, food service, mailroom, and IT reviewers to validate their instructions, hours, forms, permissions, and after-hours escalation paths.
- Publish the hub and test each task from an employee, contractor, and visitor perspective, including mobile, keyboard-only, and restricted-audience access where applicable.
- Review analytics and feedback for failed searches, dead links, repeated questions, and stale service details, then update the responsible destination page rather than adding more text to the hub.
Best practices
- Keep the hero focused on immediate workplace tasks and reserve detailed rules, maps, and exceptions for linked service pages.
- Use quick-link labels that describe an observable action, such as “Replace a lost badge” or “Report something broken,” instead of department names.
- Show the response owner, expected handling path, and after-hours escalation route on the facilities request page.
- Maintain separate location pages when parking, entrances, access hours, room technology, or accessibility routes differ by office.
- Add a last-reviewed date and accountable role to every page containing hours, menus, access rules, or shipping cutoffs.
- Link to official room-booking, maps, ticketing, and cafeteria systems rather than duplicating data that changes outside the intranet.
- Use progressive disclosure so the landing page or table of contents orients visitors before they reach deeper policy and process content.
- Test the page with keyboard navigation, visible focus, meaningful link text, sufficient contrast, and accessible labels before making it available to a restricted audience.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who is this Facilities & Workplace Hub for?
Use it for employees, contractors, and visitors who need practical workplace information. The hub supports common tasks such as finding an office, replacing a badge, booking a room, checking cafeteria hours, sending a package, or reporting a fault. Keep audience-specific instructions on linked service pages when access rules differ by location.
How often should the hub be reviewed?
Review high-change content such as cafeteria hours, room policies, access instructions, and shipping cutoffs whenever operations change. Assign a facilities content owner to check every linked page on a regular cadence and confirm that locations, contacts, forms, and escalation routes still work. Put a visible review date and owner on detailed service pages rather than relying on the landing page alone.
Who should own and run this site?
Facilities or workplace operations should own the site, with security, reception, food service, mailroom, and IT contributing to their sections. A named service owner should approve changes to each page type and coordinate urgent updates during closures or access incidents. Employees should report broken links and outdated instructions through the facilities request path.
Does this template address workplace compliance requirements?
The template helps publish operational guidance, but it does not replace local safety, accessibility, security, fire, food-allergen, or employment requirements. Link to approved emergency procedures and formal policies from the relevant service pages. Review location-specific rules with your legal, security, safety, and accessibility owners before launch.
What is the most common mistake when launching this hub?
The common pitfall is linking to a form or service page without explaining what happens next, who responds, or what to do after hours. Add response expectations, escalation instructions, and emergency exceptions to each operational page. Also test every quick link from an employee perspective so the hub does not recreate the buried-navigation problem it is meant to solve.
Can we customize the hub for multiple offices?
Yes. Keep the landing page focused on universal tasks, then create location pages for maps, entrances, parking, badge rules, accessibility information, and local contacts. Use role-based or location-based landing pages when employees need different instructions, while preserving a consistent hub-and-spoke navigation pattern.
Can this connect to booking, forms, maps, or service systems?
The CTA and quick-link structure can point to room-booking tools, facilities forms, maps, shipping portals, cafeteria menus, and ticketing systems. Replace the sample URLs with approved destinations and verify that audience permissions work for employees, contractors, and visitors. If a system requires authentication, state that clearly before the link is opened.
How should we roll this out without overwhelming employees?
Start with the highest-frequency tasks: report an issue, find an office, book a room, replace a badge, check food hours, and send a package. Test the page with employees from several locations and roles, then publish short launch guidance that points to the specific task links. Add deeper policy and service detail progressively instead of turning the landing page into a wall of text.
Why use this template instead of an ad hoc facilities page?
This template gives the site a predictable starting point with a hero, quick links, and task-specific service destinations. An ad hoc page often buries urgent actions among announcements, repeats content, and leaves ownership unclear. The structured approach makes it easier to apply Nielsen Norman Group usability principles, review stale content, and expand into location and service pages without losing orientation.
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...
Ready to use this template?
Get started with MangoApps and use Facilities & Workplace Hub with your team — pricing built for small business.
