Haskell — myHaskell.com SharePoint Online Implementation and Upgrade (2019): Evidence Record
Claim level: Contracted — countersigned
Verified against the 1 primary source document and 2 redacted page images published on this page. Every published file carries a SHA-256.
On January 21, 2019 EPC Group issued Haskell a statement of work for a 165-hour SharePoint Online implementation and upgrade of the myHaskell.com intranet. Haskell's VP Information Technology & CIO countersigned it on January 30, 2019. The cover and execution page are published here as redacted images with SHA-256 hashes.
Engagement fact, as the document states it
Statement of Work "SOW for myHaskell.com Upgrade Initiative to SharePoint Online Implementation and Upgrade" dated January 21, 2019: a 165-hour block of SharePoint Online implementation and upgrade services, executed for EPC Group on January 21, 2019 and countersigned for Haskell on January 30, 2019 by its VP Information Technology & CIO.
Delivery status: completed and paid in full per EPC Group’s accounts-receivable record (EPC-reported, 2026-10-15). EPC Group treats payment as acceptance; no client acceptance record is published for this engagement.
- Move and upgrade the existing myHaskell.com intranet into SharePoint Online on Haskell's Office 365 tenant, built from Office 365-compatible templates (SOW-stated scope)
- Cover the existing myHaskell.com areas: Administration Services, General Accounting, HR, IT, Marketing, Risk Management, AE Core, C Core, Procedures, Project Forms and Haskell Applications (SOW-stated scope)
- Custom SharePoint Online user experience: consistent look and feel, custom navigation, responsive design, and integration with Haskell's existing systems (SOW-stated scope)
- Phases: initiate, design, build and migrate, post-deployment support and training; 165-hour block purchase (SOW-stated scope)
165 hours or units as stated on the document. Period on the paper: 2019-01 (no end date is stated on the published documents).
O'Connor Enterprise Group, Inc., doing business as EPC Group, is the legal contracting entity for the engagements documented here.
Verification summary
| Verification vector | Validated value |
|---|---|
| Client entity | Haskell (as printed on the statement of work) |
| EPC contracting entity | EPC Group — O'Connor Enterprise Group, Inc., doing business as EPC Group |
| Document type | Statement of Work, countersigned by both parties |
| Effective date | January 21, 2019 (EPC Group signed); countersigned January 30, 2019 |
| Engagement | myHaskell.com intranet implementation and upgrade into SharePoint Online |
| Block purchased | 165 hours |
| Client signatory | VP Information Technology & CIO (name redacted) |
Source documents
SOW for myHaskell.com Upgrade Initiative to SharePoint Online Implementation and Upgrade — 165-hour initiative
- Document type:
- Statement of Work (countersigned)
- Date:
- January 21, 2019 (countersigned January 30, 2019)
- Issuer:
- EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group), countersigned by Haskell
- Published:
- Cover (page 1) and execution page (printed page 13) of 13, redacted
What this document establishes
- EPC Group issued a statement of work to Haskell on January 21, 2019 for a 165-hour SharePoint Online implementation and upgrade initiative covering the myHaskell.com intranet.
- An authorized Haskell signatory (title: VP Information Technology & CIO) countersigned it on January 30, 2019; both parties' execution blocks are on the published page.
What it does not establish
- That the 165 hours were consumed, that the intranet went live, or that Haskell accepted any deliverable.
- Any amount invoiced or paid.
- Any outcome or adoption figure.
Redactions applied
- The preparer line on the cover (name, direct telephone, main office number and e-mail)
- Both handwritten signatures and the client signatory's printed name on the execution page
- The pricing and hourly-rate pages, and the Microsoft credit line, are not published at all
No client name, EPC Group identity, project description or date has been altered.
What this page does not claim
- Delivered: no acceptance form, closeout letter or client sign-off is published; the public documents do not establish that the contracted work was completed or accepted — both are EPC-reported from EPC Group's own delivery and accounts-receivable records (see the delivery status line).
- Paid: no client remittance or payment record is published; the public documents do not establish payment — payment in full is EPC-reported from EPC Group's own delivery and accounts-receivable records (see the delivery status line).
- Outcome: no business result, adoption figure or satisfaction measure is claimed; the page states what the instrument says and nothing more.
Document provenance
Source: EPC Group historical corporate records.
Public version: privacy-redacted reproduction of the pages listed above.
Material alterations: none, other than the redactions disclosed against each document.
Original retained: yes, by EPC Group.
Redaction method: Each published excerpt is rebuilt from a rasterised image of the page, with redaction boxes burned into the pixels before the file is reassembled. The derivative carries no text layer, no annotations, no form fields and no metadata, so nothing beneath a redaction box can be recovered by text extraction. Every derivative was additionally reviewed by eye at high magnification.
What a hash proves: The SHA-256 confirms the downloaded file matches the published file; it does not independently authenticate the underlying agreement.
Basis for publication: written consent of the client. The owner's written instruction of 2026-10-15 (checkpoint word HASKELL keep; Addendum 10 item 140), not a client letter. No confidentiality or publicity clause appears in the statement of work (full-text search of the OCR text on 2026-10-15).
Text transcripts: 01 · 02 — generated by optical character recognition from the published, redacted images, never from the originals; where an image is boxed the transcript reads [REDACTED].
Review cycle: this record is reviewed every 90 days.
Questions about this record
Has EPC Group worked with Haskell?
Haskell contracted EPC Group for SharePoint Online implementation and upgrade of the myHaskell.com intranet in 2019; this record publishes 1 primary-source document at claim level "Contracted — countersigned". EPC Group publishes historical contracting records supporting this engagement; the published material does not establish every claimed delivery outcome.
Is the client's signature on the published page?
The execution page is published with both parties' blocks. The handwritten signatures and the client signatory's printed name are removed; the signatory's title and the handwritten execution date are retained, because those establish that an authorized officer executed the document.
Why are the pricing pages not published?
EPC Group does not publish rates, totals or credit amounts on any evidence record. The cover and execution page establish the engagement, the hours and the parties; the commercial terms stay in the project record.
Case study for this record
Haskell: myHaskell Intranet on SharePoint Online (2019) — project ID EPC-2019-HASKELL-SPO · service: SharePoint intranet Consulting
Related evidence records
- Haskell — Contracted — countersigned
Service pages this record supports
Client names, trademarks and documents are displayed for factual verification of historical business relationships only. Their inclusion does not imply a current commercial relationship, sponsorship or endorsement.
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group