Haskell (The Haskell Company) — myHaskell.com intranet implementation and upgrade on SharePoint Online (2019)
Contracted — countersignedFirst-pass editionHaskell (The Haskell Company) · 2019 · Project ID EPC-2019-HASKELL-SPO
Evidence record: Haskell (The Haskell Company) evidence record with redacted documents and SHA-256 hashes
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
EPC-reported — statement of work on file; evidence record pending. Haskell (The Haskell Company) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for myHaskell.com intranet implementation and upgrade on SharePoint Online — 165-hour block per EPC Group statement of work dated January 21, 2019 (document on file; countersignature to be confirmed). Project ID EPC-2019-HASKELL-SPO. The engagement was completed and paid in full (EPC Group accounts-receivable record).
First-pass edition. The facts in the verification line and the project-facts table come from the documents named there. The engagement narrative below is written by EPC Group from the engagement type and the documented scope, is marked EPC-reported, and is pending review by Errin O'Connor. Delivery status comes from EPC Group's accounts-receivable record as stated by Errin O'Connor on 2026-10-15; no other result is claimed that the documents or project records do not support.
Summary
In 2019, EPC Group completed myHaskell.com intranet implementation and upgrade on SharePoint Online for Haskell (The Haskell Company) on SharePoint Online, Office 365, Yammer / Microsoft Teams, Delve, Outlook, led by Errin O'Connor, EPC Group's founder and the architect named in the engagement documents (the statement of work is prepared by Errin O'Connor), addressing a legacy intranet whose structure, search and integrations no longer served a construction and professional-services workforce. The work ran through the phases the documents define: Initiate, Design, Deploy, and Post-Deployment (Support and Training). The client accepted the deliverables and paid in full, per EPC Group's accounts-receivable record; EPC Group reports that its objectives for the engagement were met. Verification: EPC-reported — statement of work on file; evidence record pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported). What the documents establish, and what they do not, is stated in Evidence and limitations below.
Project facts
| Field | Value | Source |
|---|---|---|
| Client | Haskell (The Haskell Company) | document |
| Industry | Architecture, engineering and construction | document / public record |
| Engagement date | January 21, 2019 | document |
| Work | myHaskell.com intranet implementation and upgrade on SharePoint Online (165-hour initiative) | document |
| Microsoft products | SharePoint Online; Office 365; Yammer / Microsoft Teams; Delve; Outlook | document / scope |
| Scope unit | 165-hour block per EPC Group statement of work dated January 21, 2019 (document on file; countersignature to be confirmed) | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | Errin O'Connor — the statement of work is prepared by Errin O'Connor | document |
| Delivery status | Completed; invoiced and paid in full. Source: EPC Group's accounts-receivable record (paid invoices on file, not published because they carry commercial terms), stated by Errin O'Connor on 2026-10-15. EPC Group treats payment as acceptance; no client acceptance record is published for this engagement. | EPC AR record (EPC-reported) |
| Verification class | EPC-reported — statement of work on file; evidence record pending; Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) | Evidence Center convention |
| Evidence record | evidence record pending (CC builds it from the document on file) | — |
| External source | none published yet | — |
| Project ID | EPC-2019-HASKELL-SPO | EPC Group |
What the document states
EPC Group Statement of Work (January 21, 2019): a new SharePoint Online intranet covering the existing myHaskell.com departments (Administration Services, General Accounting, HR, IT, Marketing, Risk Management, AE Core, C Core, Procedures, Project Forms, Haskell Applications); clean UI/UX, consistent look and feel, custom navigation, responsive design; integration with Yammer/Teams for news commenting, Haskell's Twitter and LinkedIn feeds, Outlook calendar and tasks, and Delve for the employee directory and profiles; search; custom department and news templates; a central third-party application launch point. Phases: Initiate, Design, Deploy, Post-Deployment (Support and Training).
Starting environment (EPC-reported, first pass)
An engagement of this type begins with an existing Office 365 platform and a legacy intranet (myHaskell.com) with departmental areas — administration services, general accounting, HR, IT, marketing, risk management, core engineering and construction groups, procedures, project forms and applications — to be rebuilt on SharePoint Online. The specific inventory for this engagement is held in EPC Group's project records and will replace this paragraph when published.
Business problem (EPC-reported, first pass)
A legacy intranet whose structure, search and integrations no longer served a construction and professional-services workforce.
EPC Group's responsibility
Design, development and implementation of myHaskell.com on SharePoint Online: requirements and use cases by department, technical evaluation, custom templates for department and news sites, custom navigation and responsive design, integration with Yammer/Teams, public social feeds, Outlook and Delve, search, and a central application launch point — as the statement of work describes.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are site and hub architecture for the departmental areas, template design, navigation and responsive UX, integration approach for social, calendar and profile data, and the search configuration. The decisions actually taken for Haskell will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: initiate (discovery and planning) → design → deploy → post-deployment support and training. Dates and acceptance for this engagement will be stated from the project record.
Results
| Metric | Baseline | Observed result | Period | Source | Verification class |
|---|---|---|---|---|---|
| Scope delivered against the instrument | as contracted | Completed; invoiced and paid in full | engagement period | EPC AR record (paid invoices on file; not published) | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Client acceptance | — | Deliverables accepted; EPC Group's objectives met | close-out | payment in full + EPC-reported | Delivered — paid in full (EPC Group accounts-receivable record; EPC-reported) |
| Primary technical outcome (migration completeness, platform live, deliverable detail) | pending | pending project record | — | project record | pending |
| Service interruption during cutover (where applicable) | planned window | pending | cutover | cutover log | pending |
Completion, acceptance and payment are stated from EPC Group's records; the technical rows stay pending until the project record is published. No figure is invented.
Client perspective
The client accepted the deliverables and paid every invoice in full. No client quotation is published on this page; where a client has given a written statement or a review, it is linked from the evidence record.
Evidence and limitations
The source document is on file with EPC Group; CC builds the evidence record (redacted images, SHA-256, transcript) before this page leaves first-pass status. The instrument establishes the client, the supplier, the service and the date as stated above. It does not by itself establish delivery dates, volumes, acceptance or outcomes; those require the project records referenced in the Results table. Completion and payment in full are established by EPC Group's accounts-receivable record (paid invoices on file; not published because they carry commercial terms).
Lessons for similar organizations (EPC-reported)
- An intranet is a set of department templates and a search box; everything else is decoration.
- Integrations (social, calendar, profiles) are what make people come back.
Related service
SharePoint Online intranet implementation ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.