Anonymized engagement summary: SharePoint health check, workflow audit reporting, SharePoint Server 2016 upgrade and ongoing support for a consumer-products manufacturer (2017–2023)
Contracted — countersigned, with work products on file (EPC-reported; documents private)First-pass editionA consumer-products manufacturer (client not named) · 2017–2023 · Project ID EPC-2017-ANON-MFG-SPPLATFORM
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. A consumer-products manufacturer has engaged EPC Group repeatedly on its on-premises SharePoint platform. In January 2017 EPC Group delivered a health check and assessment of the company's SharePoint Server 2013 farm with remediation steps. Between March and May 2017 it built and documented workflow audit reports for approval workflows. In September 2019 the company countersigned a statement of work for a new SharePoint Server 2016 platform and migration from 2013. It countersigned further SharePoint consulting and support statements of work in August 2022 and May 2023.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The supporting records — the countersigned statements of work, the health-check report and findings deck, the workflow-audit documentation and the 2019 kickoff deck — are retained privately and are not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from those documents.
Verification class
Contracted — countersigned, with work products on file (EPC-reported; documents private). The client countersigned the 2019, 2022 and 2023 statements of work; each carries a client signature and date. The 2017 statement of work carries an addendum that the client's legal department requested for its execution. The health-check and workflow-audit documents are dated January to May 2017. No acceptance form or outcome measurement is claimed.
Buyer problem and scope
| Engagement | What the documents state |
|---|---|
| Health check and assessment (delivered January 2017) | A two-server SharePoint Server 2013 Enterprise farm. The detailed report covers farm and site topology, search topology and configuration, service applications, web application settings, databases, monitoring (Health Analyzer, timer jobs, diagnostic logging) and backup and restore |
| Custom development and support (2017) | Custom SharePoint solution development and support |
| SharePoint Server 2016 deployment and migration (countersigned September 2019) | Build SharePoint Server 2016 on Windows Server 2016 and SQL Server 2016; health checks of the existing SharePoint 2013 farm and on-premises Active Directory; technical design, hardware sizing, information architecture and taxonomy; site collections, branding and document management; pilot migration and full migration of users and content from SharePoint 2013; as-built documentation, knowledge transfer and train-the-trainer sessions |
| Consulting and support (countersigned August 2022 and May 2023) | Further SharePoint consulting and support work under new statements of work |
Unknowns, not stated in the documents cited: user counts, the 2019 migration's cut-over date, and the specific tasks completed under the 2022 and 2023 support statements of work.
Approach and artifacts
Health check first, with every finding paired to a fix. The findings deck groups the Health Analyzer results into security, configuration and availability. Each item is paired with resolution steps:
- the farm account used for other services
- service accounts in the local Administrators group
- My Sites sharing a web application with other content instead of a dedicated one
- people-search relevance degraded by gaps in the directory's manager reporting chain
- server drives below the free-space rule of thumb of five times physical memory
Audit reporting for approval workflows. EPC Group added four reports to the farm, each exportable to Excel, PDF and CSV and filterable:
- a workflow approval audit report: approver, requester and approval time per document
- a workflow approver list for each library's approval process
- a user security report of permission levels per site
- an outstanding-workflow report of approvals still waiting on someone
Each report is reachable from a central audit list and from site settings, and access follows the site's own permission levels. The documentation was issued in March 2017, updated in April and summarized in May.
A rebuilt platform, not an in-place patch. The 2019 statement of work starts with health checks of the existing farm and directory. It then designs and sizes a new SharePoint Server 2016 farm, builds it, and runs a pilot migration before the full move. Knowledge transfer and train-the-trainer sessions close it out, with the founder named as project champion.
The platform carried forward. 2025 scoping documents for a later move to SharePoint Online describe the SharePoint Server 2016 farm as the client's platform. They record 123 site collections in one content database (about 400 GB, estimated), SharePoint Designer and 2013 workflows in wide use, and farm backups not yet verified, which they flag as a high risk to resolve before any migration. The move to SharePoint Online is not claimed here.
Work products (dated, held privately):
| Work product | Date |
|---|---|
| SharePoint health check and assessment — detailed report and high-level findings deck | January 2017 |
| Statement of work for custom development and support, with the client's execution addendum | February 2017 |
| Workflow audit reports documentation — version 1.0, April update, summary | March–May 2017 |
| Statement of work, SharePoint Server 2016 deployment and migration (countersigned) | September 2019 |
| Kickoff presentation, SharePoint Server 2016 project | September 2019 |
| Statements of work, SharePoint consulting and support (countersigned) | August 2022; May 2023 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| Health check delivered with remediation steps | Detailed report and findings deck, January 2017 | Delivered (EPC-reported; documents private) |
| Workflow audit reports built and documented | Documentation, March–May 2017 | Delivered (EPC-reported) |
| The client contracted EPC Group for a SharePoint Server 2016 platform and migration, and twice more for support | Countersigned statements of work, 2019, 2022, 2023 | Contracted (EPC-reported) |
| A SharePoint Server 2016 farm was the client's platform in 2025 | 2025 scoping documents | On file (EPC-reported) |
| Measured performance, adoption or cost results | No document cited | Not claimed |
Provenance
- Sources: the statements of work (2017, 2019, 2022, 2023; the last three countersigned), the health-check report and findings deck, the workflow-audit documentation, the 2019 kickoff deck and the 2025 scoping documents, held privately. Engagement ID: EPC-2017-ANON-MFG-SPPLATFORM, an alias unrelated to the client's name.
- Anonymization: industry only, under EPC Group's anonymized-case rule; server, site and staff names, locations and commercial terms are not published.
- Not claimed: client endorsement, the 2025 move to SharePoint Online, or any measured result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, named in the 2019 statement of work as project champion.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's statements of work and work products.
Related service
SharePoint governance health check · SharePoint consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.