Case Studies/Phillips International

From Binders to Runbooks: How Phillips International Caught $400K in Scope Creep

ADL replaced Phillips International's scattered binders, PDFs, and regional handbooks with a single indexed playbook workspace — catching $400K in scope creep and halving new-manager onboarding time across a national real estate portfolio.

Phillips International

Snapshot

Client
Phillips International
Domain
Real estate & property management operations
Timeline
8 months
Team
2 Design Engineers, 1 Operations Lead
Services
Knowledge Architecture Runbook Design Governance & Change Management
Environment
SharePoint, regional handbooks, PDFs; migrated to single playbook workspace

Results

$400K

in scope creep caught and recovered

50%

faster time to independent shifts for new managers

1

indexed playbook workspace across all regions

About Phillips International

Phillips International is a U.S.-based real estate and property management company overseeing a national portfolio of retail, office, multifamily, and hotel assets.

With teams spread across regions and a constant stream of regulatory and safety updates, the operations group depends on clear procedures, current guidance, and fast communication between corporate, properties, and vendors.

The Problem

For years, Phillips International ran on a mix of binders, regional handbooks, SharePoint folders, and the memories of a few long-tenured managers.

Standard operating procedures (SOPs) lived in PDFs, email attachments, and local drives; each region maintained its own version, and no one could say with confidence which document was current when an incident hit.

New site managers spent months shadowing their predecessors just to learn “how things really work here,” and corporate leaders had no consistent view into whether required checks, trainings, and inspections were actually happening.

What We Built

A single playbook workspace that replaced scattered binders and folders with searchable, tagged, versioned procedures — owned by the right people and visible to everyone who needs them.

  • Knowledge architecture — mapped SOPs, runbooks, and regional variations into one global structure with local notes where variation is required
  • Indexed playbook with search, tags, and clear ownership so incident commanders can pull the right runbook in seconds
  • Governance board and change log — every procedure shows what changed, when, and why; policy updates no longer get lost in email
  • Guided runbooks for new managers so they reach independent shifts in half the time instead of months of shadowing
  • Structured metadata and event logs — ready for automation, analytics, and future AI assistance without a rebuild

The Shift

Before
After
SOPs scattered across binders, PDFs, and email threads
Single indexed playbook workspace with search, tags, and ownership
Each region maintained its own version of “how we do things”
One global standard with local notes where variation is truly required
Incident response relied on calling whoever “knew the drill”
Incident commanders can pull up a clear, versioned runbook in seconds
New managers spent months shadowing to piece together workflows
New managers reach independent shifts in half the time with guided runbooks
Policy changes announced by email and slowly absorbed (or forgotten)
Governance board, change log, and visible “what changed” notes on every procedure
No realistic path to automation or AI assistance
Structured metadata and event logs ready for automation, analytics, and future copilots

“Before this, every region solved the same problem in parallel — binders, SharePoint, and a lot of ‘just ask Maria.’ Now if something happens in Miami, Minneapolis can learn from it the next morning in the same system.”

Diana MarroneSenior Vice President

Ready to scope your project? We'll map, design, and build the right solution.