How SharePoint Intranet for Construction Delivers 80% Faster Safety Search For A 300 Employee Firm

A case study on replacing email threads and shared drives with a structured SharePoint intranet for construction built around a Home Hub Site, a Relationship Building and Business Development Site, a dedicated Safety Site, an Admin Site, and a Project Management Framework Site, all built on a clear SharePoint site structure spanning 62 web parts in total. 

Executive Summary 

A mid-size construction and project services company with approximately 300 employees was running internal communication almost entirely through email and shared drives, with no central place for safety documentation, business development resources, or project management standards. SPDW designed and built a 5 site SharePoint intranet for construction, following a consistent SharePoint site structure across 62 web parts and including a calendar integration that keeps company events visible in the tool employees already use daily. Safety document retrieval time dropped from an estimated 15 minutes searching for shared drives and email to about 3 minutes through the new Safety Document Library, an 80% reduction. The project ran on a 5-week agile sprint timeline, within the 4-to-6-week window scoped at the outset and included admin and user training backed by a dedicated user manual and admin manual. 

About the Client 

The client is a mid size construction and project services company with approximately 300 employees working across field operations, business development, safety and compliance, project delivery, and administration. Construction firms at this size typically run lean on internal IT, which meant the company had never had a real intranet: company news, safety bulletins, project resources, and HR information were split across email chains, a shared drive with an inconsistent folder structure, and whatever a given project manager happened to post on a physical bulletin board at a site office. 

Safety carries particular weight in this industry. Documentation, policies, and team information related to safety carry real compliance and liability weight, which meant a scattered approach to safety content was a genuine business risk. Business development and client relationship continuity mattered just as much: with employees turning over and projects starting and ending on their own timelines, the firm had no consistent home for referral programs, new hire visibility, or the organizational knowledge that keeps client relationships intact when a team member moves on. 

The Problem 

Without a central intranet, information at the company lived wherever the last person to touch it decided to put it. Safety policies, procedures, and team contacts were split across email attachments and a shared drive folder that different site offices organized differently, so an employee looking for a specific safety document had no reliable starting point and, by the company’s own estimate, spent around 15 minutes on a typical search across email and shared drives before finding what they needed. 

Business development content was similarly fragmented. Referral program details, internal job postings, and the organization’s reporting structure existed in scattered documents or lived only in people’s heads, which made it harder for staff to refer candidates, understand who did what across departments, or find current information about company policies without asking around. Project teams had no standardized project management resources site to work from, so consistency in how projects were run depended heavily on which project manager was leading a given job. 

Scheduling added its own friction. Company-wide events, from safety trainings to internal celebrations, were communicated through Outlook invites that only reached people already on a distribution list, with no single company calendar anyone could check to see what was coming up across the whole organization. 

What We Discovered 

Before building a single site, SPDW worked through requirement gathering sessions with stakeholders across safety, business development, project management, and administration to understand what each function actually needed from an intranet, well beyond what a generic SharePoint template would offer. 

SharePoint Site Structure and Architecture Planning  

We mapped the company’s structure to a hub and site collection model: one Home Site configured as the SharePoint hub, with four associated SharePoint sites, each its own separate site collection: Relationship Building and Business Development, Safety, Admin, and Project Management Framework. Being associated with the hub gives each site shared navigation and branding only, with permissions handled entirely separately, so associating the Safety Site with the hub didn’t open its content to the rest of the company. Permissions for each site, and for specific libraries within it, stayed independently managed, with only the necessary groups granted access, which meant safety content could carry tighter access controls where needed, such as incident investigation records restricted to safety managers alone, while the general safety policies every employee needed stayed freely accessible, all without fragmenting the overall intranet experience. 

Web Part and Content Requirements by Site  

Each site’s requirements were gathered separately and independently for every function. The Safety Site needed a document library, a way to introduce the safety team by name and photo, and an employee poll mechanism for safety culture feedback. The Relationship Building site needed an organization chart, new hire visibility, a referral program section, and a discussion forum. The Admin site needed FAQs, an admin-managed document library, and a recently accessed documents view. This site-by-site requirement gathering is what produced the eventual 62 web parts spread across all five sites, each tied to a real function identified during discovery. 

Calendar Integration Requirements  

Because Outlook was already the tool employees checked daily, we confirmed early that the SharePoint calendar needed to reflect the existing Outlook shared calendar automatically, with Outlook staying the single source of truth for scheduling, so the SharePoint calendar would never become a second, separate calendar staff had to remember to update themselves. 

Building the SharePoint Intranet for Construction 

The objective was a genuinely unified intranet, five sites sharing one consistent experience, built on an agile sprint timeline that delivered working sites for stakeholder feedback throughout the project. 

The Home Site was built as the SharePoint hub, carrying a dynamic menu bar linking to all four associated sites, a high resolution banner reflecting the company’s vision and values, a news and announcements section, quick links, a world clock and weather display for multi region awareness, an upcoming events list, a “who do I call for” contact directory, a document library, an image gallery, a recently accessed documents view, and the synced SharePoint calendar, 13 web parts in total anchoring the hub experience. 

The four associated sites were each built around their function, following the same SharePoint site structure established during discovery. The Relationship Building and Business Development Site, the largest at 15 web parts, included an organization chart, new hire visibility, a referral program, internal job postings, a relationship building document library, a video gallery, a discussion forum, and a company policies and procedures section.  

The Safety Site, at 13 web parts, centered on a dedicated Safety Document Library alongside a “meet the safety team” section, an employee poll for safety culture feedback, and its own policies and procedures and discussion forum, forming the backbone of the firm’s new SharePoint safety management approach.  

The Admin Site, at 11 web parts, gave administrators a document library, FAQs, an admin-managed poll, and a recently accessed view. The Project Management Framework Site, at 10 web parts, served as the firm’s SharePoint project management site, centralizing a project management document library, policies and procedures, forms, and a “meet our team” section for project staff. 

Development ran across parallel agile sprints, with weekly review meetings where stakeholders saw working sites and gave feedback on content mapping before the next sprint began. A Power Automate flow keeps the SharePoint calendar current with the Outlook shared calendar: whenever an event is created or updated in Outlook, the flow copies it into the SharePoint calendar list, matching on the event’s Outlook identifier so an edit updates the same SharePoint item without creating a duplicate. Outlook remains the source of truth throughout, since staff already had the habit of scheduling there, and the SharePoint calendar functions as a continuously refreshed, read only mirror for anyone browsing the intranet. 

Challenges Overcome 

Delivering SharePoint Safety Management Without Fragmenting the Intranet

Some safety content, like incident investigation records, needed more restricted access than the general safety policies every employee had to see freely, but building the whole Safety Site as a fully separate, disconnected system would have defeated the purpose of a unified intranet. SPDW addressed this by structuring the Safety Site as its own site collection associated with the shared hub, giving it consistent navigation and branding from the Home Site while keeping its own independent permissions, with only the Safety team and relevant managers granted access to the site itself, and specific document libraries within it, such as incident investigation records, carrying even tighter access rules restricted to safety managers alone. 

Keeping five sites visually and structurally consistent while gathering requirements independently  

Gathering requirements independently for each site risked producing five sites that felt like five different products. SPDW addressed this by locking a shared menu bar, banner treatment, and hover arrow navigation pattern across every site early in the project, so each site’s unique web parts, a safety poll here, an organization chart there, sat inside the same consistent shell every time. 

Delivering a 5-week timeline without sacrificing stakeholder input  

A 4-to-6-week window left little room for a slow requirement process or late-stage rework. SPDW addressed this with weekly review meetings built into the sprint structure from day one, so stakeholders saw and reacted to working sites throughout the project. Feedback surfaced and got resolved sprint by sprint, which is what kept the project inside its 5-week timeline without a scramble at the end. 

Results & Business Impact 

The company now runs its internal communication and documentation through a 5 site SharePoint intranet spanning 62 web parts, with safety document retrieval time down from an estimated 15 minutes to about 3, an 80% reduction, thanks to the dedicated Safety Document Library replacing scattered shared drive folders and email attachments. 

The day-to-day impact varied by function. Field and project staff now check one Home Site for company news, upcoming events, and key contacts, no longer dependent on whichever email thread happened to reach them.

Safety personnel have a dedicated home for documentation, team introductions, and culture feedback through the employee poll, giving safety a visible presence in the intranet that matches its importance to the business. Business development and HR-adjacent functions gained a structured home for the organization chart, referral program, and new hire announcements, making it easier for staff to understand who does what and refer candidates with confidence.

Administrators manage company-wide FAQs, forms, and documents through a dedicated Admin Site, cutting down on the same questions arriving repeatedly by email, and the calendar integration means a company event scheduled in Outlook now reaches everyone who checks the SharePoint calendar too, without anyone maintaining two calendars by hand. 

Over time, the new structure has also changed how the firm maintains consistency, well beyond just how it communicates day to day. Document version control now lives in one place per site, replacing scattered copies that used to sit across old shared drive folders.

New hires start from the same organized set of onboarding resources on the Relationship Building Site regardless of who is training them, and project teams increasingly reference the same Project Management Framework Site materials from one job to the next, no longer rebuilding project documentation from scratch each time. 

Lessons Learned 

A few things from this project are worth carrying into any multi-site SharePoint intranet build: 

1. Gathering requirements site by site produces a better intranet than one template applied five times. A Safety Site and a Business Development site serve genuinely different purposes, and treating them identically would have meant either over-building the Admin Site or under-building the Safety Site. The extra time spent scoping each site’s web parts individually is what made the final 62 web parts feel deliberate. 
2. A shared navigation shell is what makes five sites feel like one intranet. Locking the menu bar, banner treatment, and navigation pattern early, before the sprint-by-sprint content work began, is what kept five independently scoped sites from feeling like five separate products glued together at the end. 
3. Weekly reviews are what make an aggressive timeline survivable. A 5 week build across five sites leaves very little room to discover a misunderstanding late. Catching a content or layout misalignment in week 2 costs a conversation. Catching the same misalignment in week 5 costs a rebuild. 

Client Testimonial 

“Before this, if you wanted to find a safety policy you either remembered which email it was buried in or you called someone and hoped they remembered. Now it’s just there, organized, in a site built specifically for safety. Our field teams have picked it up faster than I expected, and the fact that our Outlook calendar and the SharePoint calendar actually talk to each other now has stopped so many double bookings.” 

Director of Operations