USPS OIG Multi-Agency Drupal Distribution | Wilkes & Liberty Case Study

Inspector General offices occupy a structurally distinctive position in the federal web landscape. They are oversight bodies — their mandate is accountability and transparency — and that mandate creates simultaneous, competing requirements for their digital infrastructure.

On the public-facing side, IG offices must publish findings, reports, audits, and investigative outcomes in accessible, searchable, standards-compliant formats. The public's ability to access and understand oversight work is a core function of the institution, not a secondary communications goal. On the internal side, IG offices manage sensitive investigative workflows, document handling, and case records that require strict access controls and data segregation from public-facing systems.

Managing this complexity across multiple affiliated oversight entities compounds the challenge. When each entity maintains its own independently customized Drupal installation, configuration diverges over time. Security patches must be applied separately to each instance. Accessibility improvements made for one entity do not automatically propagate to others. Editorial experience varies across teams working on what is nominally the same platform. The operational overhead grows with each additional entity, while the benefits of a shared platform are not realized.

Solution

Wilkes & Liberty's principal engineer designed and built a shared Drupal distribution for the USPS Office of Inspector General and affiliated oversight entities. [VERIFY: prime/sub arrangement for this engagement]

A Drupal distribution is a pre-configured installation profile — a packaged, deployable version of Drupal that encodes a defined set of content types, configurations, modules, access controls, and editorial workflows. When a new entity needs to stand up a platform, they deploy the distribution rather than configuring Drupal from scratch. The configuration is consistent from the first deployment.

The distribution built for the USPS OIG was purpose-built for Inspector General office requirements. It encoded IG-specific content types — reports, findings, investigations, and public disclosures — with the editorial workflows and access controls appropriate to each. Federal accessibility standards were built into the distribution foundation, not applied after deployment. Shared configuration management meant that improvements, security updates, and new capabilities could be applied to all deployed instances simultaneously rather than requiring per-instance maintenance work. [VERIFY: specific content types, modules, and access control architecture implemented]

Results

The distribution model delivered a reusable platform that reduced the per-agency deployment overhead and created a maintainable, consistent foundation across affiliated oversight entities. Because the platform encodes configuration rather than documenting it, the institutional knowledge of how the platform should work is portable and durable. [VERIFY: specific deployment count — number of entities on the distribution]

Configuration improvements and security patches applied to the distribution propagate to all deployed instances simultaneously, reducing the total maintenance burden across the portfolio of oversight entity deployments. [VERIFY: maintenance time savings — hours per month or per release cycle compared to per-instance maintenance]

Key Metrics

[VERIFY: number of affiliated oversight entities deployed on the distribution]
[VERIFY: per-agency deployment time reduction compared to custom Drupal build]
[VERIFY: maintenance time savings across the portfolio per release cycle]
[VERIFY: Section 508 compliance status across deployed instances]

Technologies: Drupal, Drupal Distribution / Installation Profile, [VERIFY: specific modules and hosting infrastructure] Sectors: Federal Oversight, Government, Inspector General Related platforms/services: Keel CMS Platform, Headless CMS Implementation, Gazette