YMCA (Houston) — Microsoft Office SharePoint Server 2007 implementation (2007)
Work-product evidencedFirst-pass editionYMCA (Houston) · 2007 · Project ID EPC-2007-YMCA-MOSS
Evidence record: YMCA (Houston) 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. YMCA (Houston) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for Microsoft Office SharePoint Server 2007 implementation — EPC Group statement of work dated August 27, 2007 on file. Project ID EPC-2007-YMCA-MOSS. 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 2007, EPC Group completed Microsoft Office SharePoint Server 2007 implementation for YMCA (Houston) on Microsoft Office SharePoint Server 2007, led by EPC Group's senior architects addressing collaboration and document management that needed a platform the organization could run. The work ran through EPC Group's delivery lifecycle as EPC Group describes its engagements: assess, modernize, govern, operate, enable. 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 | YMCA (Houston) | document |
| Industry | Nonprofit association | document / public record |
| Engagement date | August 27, 2007 (SOW date on file) | document |
| Work | Microsoft Office SharePoint Server 2007 implementation | document |
| Microsoft products | Microsoft Office SharePoint Server 2007 | document / scope |
| Scope unit | EPC Group statement of work dated August 27, 2007 on file | document |
| EPC Group role | Consulting and delivery under the instrument named above | document |
| Lead architect | EPC Group senior architects (the published instrument does not name the lead; EPC-reported) | EPC-reported |
| 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-2007-YMCA-MOSS | EPC Group |
What the document states
'YMCA SOW – MOSS 2007' (August 27, 2007) and the 'YMCA SharePoint Initiative' file on record in EPC Group's client archive.
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a nonprofit association's document and collaboration needs on Microsoft Office SharePoint Server 2007. 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)
Collaboration and document management that needed a platform the organization could run.
EPC Group's responsibility
A Microsoft Office SharePoint Server 2007 implementation under the 2007 statement of work.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are farm sizing, site structure and governance basics, document-library design, and training. The decisions actually taken for YMCA will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: planning → build → configuration → training → go-live. 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)
- Right-size the platform to the organization that will run it.
Related service
SharePoint 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.