How A Modern SharePoint Intranet Improved SharePoint Document Search by 85% For A Landscaping Company

Executive Summary 

The client is a 500-employee landscaping and grounds maintenance company – including 340 field crew members across 12 regional depots. Employees once spent an average of 40 minutes tracking down a single document across a disorganized, shared drive and personal OneDrive folders. After Code Creators audited, restructured, and completed a shared drive to SharePoint migration into a governed intranet, SharePoint document search now returns results in under 6 minutes on average – an 85% reduction. Vehicle inspection compliance, previously tracked on paper with inconsistent follow-through, rose from 61% to 98% completion within the first two months of digitization, backed by automated reminders, escalation workflows, and supervisor notifications built on Power Apps and Power Automate. The engagement also removed 720 GB of duplicate and outdated content before a single file was migrated, giving the client’s 12 depots a single, governed source of truth for the first time. 

Project Snapshot 

1. Industry: Landscaping / grounds services 
2. Company size: 500 employees, including 340 field crew members across 12 regional depots 
3. Main challenge: Disorganized shared drive/OneDrive content, no centralized intranet, inconsistent vehicle inspection compliance 

 Key Metrics 

1. 85% reduction in average document search time 
2. 98% vehicle inspection completion rate (up from 61%) 
3. 720 GB of duplicate/obsolete content removed prior to migration 
4. 31 hours per month saved in supervisor follow-up time 

About the Client 

The client is a regional landscaping and grounds maintenance company operating 12 depots and a fleet of 85 service vehicles. Its workforce splits between office-based administrative staff and field crews who depend on company vehicles and equipment to reach job sites daily, often across multiple counties in a single week. 

Like many landscaping companies that scale quickly through seasonal hiring and depot expansion, the client’s digital footprint had grown organically – and inconsistently. Content was spread across an ungoverned shared network drive, individual employee OneDrive accounts, and a legacy SharePoint site that had never been formally architected. Crew supervisors regularly recreated documents because they couldn’t find the current version, and there was no single, searchable source for vendor equipment suppliers or landscaping material vendors. 

The project mattered because the client was actively shifting toward a more digital, field-friendly operating model – including replacing a manual, clipboard-based vehicle inspection process with a digital one ahead of a new fleet safety compliance requirement. That shift demanded an intranet capable of supporting daily collaboration and structured operational workflows like inspections, not just static file storage. 

The Problem 

Before this engagement, the client’s digital workplace was spread across an unstructured shared drive, individual OneDrive accounts, and a SharePoint environment that had never been properly designed. There was no consistent site hierarchy, no standardized document library structure, and no clear permissions model – so employees often couldn’t tell what they had access to or find what they needed without pinging a colleague on Teams. 

Two operational gaps stood out. First, there was no centralized way to look up vendor or client contact details; that information lived in scattered spreadsheets, with at least three known duplicate versions circulating among depot managers. Second, vehicle inspection tracking – a recurring compliance and safety requirement for a fleet-dependent business – was still handled on paper clipboards, with a completion rate hovering around 61% and no automated way to flag missed inspections or notify supervisors of failed checks. 

Left unaddressed, this created real business risk. Inconsistent, undocumented vehicle inspections increase the odds of a compliance gap surfacing during an audit or, worse, a preventable equipment failure in the field. An unsearchable, unsegmented document environment was costing the equivalent of roughly 265 hours of staff time per month company-wide in document-hunting alone, based on the client’s own time-tracking estimates going into the engagement. And because the shared drive and OneDrive content had never been audited, the client had no clear picture of how much of its roughly 1 TB of stored content was even still relevant. 

SharePoint vs. Shared Drive: Why Search Was the Core Problem? 

At its root, this was a SharePoint vs. shared drive problem. Traditional shared drives have no metadata, no consistent taxonomy, and no governed permission model – so search is limited to file names typed correctly by whoever saved the file. SharePoint document search, by contrast, can index content, metadata, and document libraries together, but only once the underlying structure is actually built for it. Before this engagement, the client’s environment had SharePoint in name only; it inherited all the same searchability problems as an ungoverned shared drive because it had never been architected as one. 

What We Discovered 

Before designing the new intranet architecture, Code Creators ran a structured audit and assessment phase across the client’s existing SharePoint, shared drive, and OneDrive environments. This diagnostic phase was built to surface root causes, not just symptoms, and to make sure the new architecture solved real problems rather than replicating old ones on a new platform. 

The audit process included: 

1. Stakeholder interviews with depot managers, crew supervisors, and office administrators to understand day-to-day pain points and department-specific requirements. 
2. A full content inventory, cataloging 974 GB of existing content across files, folders, sizes, types, and metadata. 
3. Data quality and redundancy analysis, which identified 720 GB (roughly 74% of total content) as duplicate, outdated, or non-essential. 
4. A permissions and access review, uncovering that 40% of shared folders had no documented owner and inconsistent access rules dating back years. 
5. Usability and navigation evaluation, which found that new hires took an average of 9 days to become confident navigating the existing shared drive structure.  

From there, the team proposed a target SharePoint information architecture with departmental segmentation and produced a migration mapping document defining exactly how existing content would transition into the new structure. The output was a detailed audit report with findings, recommendations, and next steps – the foundation everything else in the project was built on. This audit-first methodology reflects Code Creators’ standing as a Microsoft Solutions Partner, applying the same governance and information-architecture practices Microsoft recommends for enterprise SharePoint deployments to a mid-market landscaping business. 

This diagnosis-first approach mattered because migrations that skip straight to “build the new site” tend to just move disorganization onto a new platform. By auditing first, the team identified what actually needed a home in the new architecture (active department content, vendor/client data, inspection records) versus what needed to be archived or deleted – directly shaping the hub-and-spoke site design and the role-based permission model applied during migration. 

The Solution 

Based on the audit findings, Code Creators designed a modern SharePoint solution built around a hub-and-spoke site architecture, a governed migration process, and two purpose-built tools: a Power Apps vehicle inspection system and custom SPFx search pages functioning as a lightweight SharePoint vendor management tool for vendor and client contacts. 

Site Architecture 

1. The Home Site was designed as the organization’s central hub – combining a dynamic menu bar, news and announcements, a consolidated calendar, quick links, an employee birthday/anniversary feed, and a document library, all built with editable, admin-managed content blocks rather than static pages. 
2. Department Sites extend that hub with department-specific document libraries, FAQs, policies and procedures, key contacts, an organization chart, and a video gallery – giving each team (Operations, Fleet Maintenance, HR, Business Development) a self-contained workspace that still inherits the hub’s navigation and branding. 
3. The Learning & Development Site adds employee polls/surveys and a “Shoutouts” recognition feature on top of the same core building blocks, supporting seasonal-crew onboarding and training alongside document access – a priority given the client’s seasonal hiring spikes. 

For the technology stack, the team chose SharePoint Online as the content backbone for native Microsoft 365 integration and governance, Power Apps and Power Automate for the vehicle inspection workflow, and custom SPFx web parts for the vendor and client search pages – built to query the client’s existing Excel-based vendor/client data directly, so a fast, filterable search experience could go live without waiting on a full data migration. 

Vendor and Client Search: Technical Design 

The vendor and client search experience is built as a custom SPFx web part deployed on the relevant Department Sites, rather than as a full database-backed application. It queries a single master Excel workbook stored in a governed SharePoint document library, using the Microsoft Graph workbook API to read named ranges and table data directly – so the search page always reflects the current state of the workbook without a separate sync or ETL step. 

1. Data source and ownership: The workbook has one designated owner – the Business Development coordinator – who is responsible for adding new vendor and client records and approving edits submitted by depot managers. Depot managers do not edit the workbook directly; they submit updates through a simple SharePoint list form, which routes to the coordinator for review before being applied to the master file. This keeps a single source of truth instead of the three duplicate spreadsheets the audit uncovered. 
2. Governance and version control: The workbook is stored in a version-controlled document library with check-in/check-out enabled, so every change is time-stamped and attributable, and prior versions can be restored if a bad edit is applied. A recurring quarterly review reminder, built with Power Automate, prompts the coordinator to confirm the workbook is current. 
3. Handling incomplete records: The SPFx web part includes normalization and validation logic at query time. Records missing required fields (such as a phone number or region) are still returned in search results but are visually flagged as “incomplete,” and the coordinator receives a monthly digest listing flagged records so gaps get closed over time rather than blocking search from working in the interim.

Vehicle Inspection Automation: How It Works 

One of the most operationally significant pieces of this project was the shift from a manual, clipboard-based vehicle inspection process to a digital, auditable workflow: 

1. Automated reminder emails prompt assigned crew leads to complete an inspection after a defined period. 
2. The employee accesses the Vehicle Inspection Form via a quick link on the Home Site. 
3. They complete the form on a mobile device from the depot, record the inspection outcome (pass/fail), and submit it. 
4. Submission triggers a Power Automate flow that emails the fleet supervisor, confirming completion and including the pass/fail status. 
5. The SharePoint List backing the form updates automatically, maintaining a timestamped inspection and compliance history for every vehicle in the fleet. 

What happens when an inspection is overdue or fails: 

1. Overdue inspections: If a scheduled inspection isn’t submitted within the defined window, Power Automate sends a first reminder to the assigned crew lead. If it remains incomplete 24 hours past that reminder, the flow escalates automatically to the depot’s fleet supervisor, and the vehicle’s status in the SharePoint List is updated to “Inspection Overdue” so it’s visible on the fleet dashboard. 
2. Failed inspections: A “fail” outcome on any submitted form triggers a second Power Automate flow that creates a linked record in a separate Maintenance Requests list, assigned to the Fleet Maintenance team, and notifies both the fleet supervisor and the maintenance lead. The vehicle’s status is set to “Out of Service – Pending Maintenance,” and depot managers see that status flagged on the Home Site so the vehicle isn’t dispatched until it’s cleared. 
3. Tracking unresolved exceptions: Both overdue inspections and open maintenance requests remain visible on a status dashboard until resolved. A maintenance record can only be closed, and a vehicle’s status reset to “In Service,” once the Fleet Maintenance lead confirms the issue was addressed – creating a closed-loop record rather than a self-reported checkbox. 

It’s worth noting what this system is and isn’t: it’s a governed inspection and compliance tracking workflow tied to each vehicle. It does not yet manage full asset lifecycle data – vehicle ownership records, depot assignment history, or scheduled maintenance beyond what’s triggered by a failed inspection. Extending it into a complete SharePoint asset tracking system would mean layering in vehicle master records (purchase date, assigned depot, current custodian) and a preventive maintenance schedule, which was scoped as a potential phase-two enhancement rather than part of this engagement. 

Within the first two months of post-launch, inspection completion rates rose from 61% to 98%, and the average time between a scheduled inspection and its completion dropped from just over 4 days to same day in most cases. 

Challenges Overcome 

Two implementation challenges stood out during the build. 

First, the client’s vendor and client contact data lived in an Excel file with inconsistent formatting across regional depots – some entries used full names; others used abbreviations, and phone number formats varied. Rather than forcing a full data cleanup before development could start, the team built the SPFx search web part with normalization logic that handled these inconsistencies at query time, allowing search to go live without a multi-week data-cleaning delay. 

Second, folder path length limits became a real constraint during migration planning. The client’s full legal entity name, when combined with nested department and job-site folder structures, regularly pushed file paths close to SharePoint’s character limits. The team worked with the client to adopt a shortened internal naming convention for folder paths – using a brand-style abbreviation rather than the full legal entity name – resolving the issue without requiring a broader systems rename. 

Lessons Learned 

The biggest takeaway from this engagement: don’t let data cleanup become a blocker for delivering value. Waiting for the client’s vendor data to be perfectly standardized before building search would have added weeks to the timeline for a problem that normalization logic could solve at query time instead. The teams that get the most out of a SharePoint modernization project tend to sequence “govern as you go” ahead of “govern everything up front.” 

Results & Business Impact 

The new SharePoint environment delivered measurable improvements across search efficiency, compliance, and content governance within the first quarter post-launch. 

1. 85% reduction in average document search time – from roughly 40 minutes to under 6 minutes, based on a post-launch survey of 62 employees across office and depot roles. 
2. 98% vehicle inspection completion rate, up from 61% under the manual process, with same-day completion becoming the norm rather than the exception. 
3. 720 GB of duplicate and obsolete content removed prior to migration, reducing the final migrated footprint by roughly 74% and simplifying ongoing governance. 
4. 31 hours per month saved in supervisor follow-up time, based on the client’s internal estimate of time previously spent chasing incomplete inspections and locating misplaced documents. 
5. New-hire onboarding time to intranet proficiency dropped from 9 days to under 3, according to feedback collected from the Learning & Development team during the first seasonal hiring wave after launch. 

The faster search experience translated differently for each part of the organization. Depot managers, who previously fielded most of the “where’s the file” questions from their crews, now point people to the department site’s search bar instead of digging through folders themselves – freeing up time that used to go into being the unofficial document librarian. Field crews, working from mobile devices at job sites, can pull up safety procedures, equipment manuals, or the vendor directory on the spot instead of waiting until they’re back at the depot or calling the office. Office staff no longer maintain informal, personal copies of “the real version” of a document out of self-defense against a disorganized shared drive – the governed library structure and metadata mean there’s one current version, and everyone is searching against the same source. 

Results KPI Snapshot 

1. 85% Faster Document Search 
2. 98% Vehicle Inspection Completion Rate 
3. 720 GB Duplicate Content Removed 
4. 31 Hours/Month Saved in Supervisor Follow-Up

Client Testimonial 

Before this project, finding the right document meant asking three different people and hoping one of them remembered where it was saved. Now our crews can pull up what they need from their phones at the depot, and our fleet supervisors get real-time visibility into inspection status instead of chasing paper. The vehicle inspection piece alone has changed how accountable our crew leads feel day to day – nobody wants to be the depot with the lowest completion rate on the dashboard. It’s changed how our whole operation runs, from the office down to the trucks in the field. I wish we’d done this two seasons ago. 

– Director of Operations