National Archives and Records Administration (NARA) — SharePoint records management and Center of Excellence advisory and implementation support (2010)
Work-product evidenced — presentation on file; evidence record pendingFirst-pass editionNational Archives and Records Administration (NARA) · 2010 · Project ID EPC-2010-NARA-RM
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Work-product evidenced — presentation on file; evidence record pending. National Archives and Records Administration (NARA) engaged EPC Group (O'Connor Enterprise Group, Inc., doing business as EPC Group) for SharePoint records management and Center of Excellence advisory and implementation support — EPC Group presentation to NARA on file (April 12 and August 19, 2010 dates); contracting instrument to be published. Project ID EPC-2010-NARA-RM. 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 2010, EPC Group completed SharePoint records management and Center of Excellence advisory and implementation support for National Archives and Records Administration (NARA) on SharePoint Server 2010 (records management), led by EPC Group's senior architects addressing records management requirements that SharePoint had to meet in a disciplined way, with a roadmap and governance behind it. 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: Work-product evidenced — presentation 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 | National Archives and Records Administration (NARA) | document |
| Industry | Federal records agency | document / public record |
| Engagement date | April–August 2010 (presentation dates on file) | document |
| Work | SharePoint records management and Center of Excellence advisory and implementation support | document |
| Microsoft products | SharePoint Server 2010 (records management) | document / scope |
| Scope unit | EPC Group presentation to NARA on file (April 12 and August 19, 2010 dates); contracting instrument to be published | 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 | Work-product evidenced — presentation 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-2010-NARA-RM | EPC Group |
What the document states
EPC Group presentation to NARA (2010) on file: 'Understand and Define — current process for document and record storage, content volume, business requirements, government regulations, current use and state of SharePoint at NARA, internal plans, timeline'; the SharePoint Center of Excellence pillars (roadmap 3–36 months, governance strategy and operational governance, platform architecture, gallery approach) and EPC Group's ATLAS delivery methodology. EPC Group's public pages already state 'National Archives and Records Administration (SharePoint records management implementation)'.
Starting environment (EPC-reported, first pass)
An engagement of this type begins with a federal records agency's own use of SharePoint for document and records storage, its content volume, the regulations it enforces on others and must meet itself, and the state of its existing SharePoint deployment. 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)
Records management requirements that SharePoint had to meet in a disciplined way, with a roadmap and governance behind it.
EPC Group's responsibility
Records-management and Center of Excellence advisory for SharePoint: understanding current process and content, business requirements and government regulations, the current state of SharePoint, and a roadmap and governance strategy.
Technical decisions (EPC-reported, first pass)
The decisions this kind of engagement turns on are records architecture (record centers, retention, file plans), governance enforcement, and the platform roadmap horizon. The decisions actually taken for National Archives will be stated here from the project record.
Delivery sequence (EPC-reported, first pass)
Typical sequence for this engagement type: understand and define → roadmap and governance → architecture → implementation guidance. 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)
- Records management is a governance program with software attached, not the reverse.
- Start from the file plan, not the site structure.
Related service
SharePoint records management and governance ·Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-15 · Substantively updated: 2026-10-15.