The call started simply enough: a Houston construction conglomerate needed help with SharePoint training. But once PCA Technology mapped the actual corporate structure, it became clear this wasn’t a training problem — it was an architecture problem.
The Client: A Multi-Entity Construction Empire
The client operates as a holding company with multiple active subsidiaries spanning construction, engineering, project management, real estate development, and property operations. Add to that a separate but related conglomerate of technology, architecture, and project controls firms — all connected through a shared ownership structure.
Total entities: 6 primary companies plus 4 affiliated firms. Each with its own staff, projects, documents, and operational workflows. Each generating its own email, its own file structures, its own version of “the current file.”
The problem: there was no single source of truth. Documents were on personal drives. Project files were emailed between teams. The holding company had no visibility into subsidiary operations. There was no governance — just accumulated chaos.
The Design: Holdings at the Root
PCA designed a SharePoint governance architecture built on a single governing principle: PMG Holdings is the root. All permissions, access, and files flow down from there.
The architecture looks like this:
Holdings (Root Site Collection — God Mode)
├── Executive / C-Suite
├── Finance & Legal
├── Company-Wide Policies
├── IT & Technology (PCA managed)
│
├── Engineering Division
│ ├── Projects
│ ├── Drawings & Specs
│ └── Reports
│
├── Construction Division
│ ├── Active Projects
│ ├── Subcontractors
│ └── Site Reports
│
├── Project Management Group
│ ├── Project Schedules
│ ├── Client Deliverables
│ └── Status Reports
│
├── Real Estate Dev
│ ├── Property Operations
│ ├── Broadway Property
│ └── Houston Ave Property
│
└── Affiliated Conglomerate
├── Technology Firm
├── Architecture & Engineering
├── PM/CM Services
└── Project Controls
The Permission Model: Trickle-Down Governance
The permission structure mirrors the corporate hierarchy:
| Level | Access |
|---|---|
| Holdings Admin | Full access to all sites, all files, all users — no restrictions |
| Subsidiary Admin | Full access to their site + read-only on sibling subsidiaries |
| Subsidiary Member | Edit within their own site only |
| Guest / Subcontractor | Specific folder access only — no cross-site visibility |
This solves the fundamental governance challenge: the holding company can see everything; subsidiaries can manage themselves; subcontractors get exactly the access they need and nothing more.
How Documents Flow
The architecture enforces document discipline through structure:
- Policy documents created at Holdings level are automatically visible to all sub-sites — no emailing, no manual distribution
- Templates stored at Holdings are available to every entity — one version, always current
- Project reports from subsidiaries bubble up to Holdings for executive visibility
- Zero file duplication — one file, one location, everyone accesses the same version
The Implementation: Foot in the Door, Then Expand
PCA’s approach was phased by design. Start with the holding company — establish the root, prove the architecture, build trust. Then map the IT needs of each subsidiary and propose managed services entity by entity.
Phase 1: Holdings SharePoint training and root site setup
Phase 2: Discovery calls with each subsidiary IT contact
Phase 3: Unified managed services proposal across all entities
This is how enterprise-scale IT governance gets delivered to a company that isn’t Fortune 500: one entity at a time, with a coherent architecture holding it all together.
Why This Matters for Construction
Construction companies have a document problem that most industries don’t: active projects generate massive volumes of drawings, RFIs, submittals, change orders, and daily reports — across multiple job sites, with subcontractors, general contractors, and owners all needing access to the right version of the right file at the right time.
Without a governed document system, construction companies operate on:
- Email attachments (wrong version, sent to wrong person)
- Personal OneDrive accounts (left when someone quits)
- USB drives on job sites (no backup, no version control)
- Shared network drives (no remote access, no mobile)
A properly architected SharePoint deployment solves all of these at once — and it runs on the Microsoft 365 licenses most construction companies already own.
PCA Technology has designed and implemented SharePoint architectures for Houston-area construction and engineering firms. We understand the industry’s document workflows, the permissioning requirements for multi-entity operations, and the practical reality of getting construction workers to actually use a document system.
Running multiple entities and need a single source of truth? Let’s build your architecture.
📞 Call or text Daniel: 713-239-2070
📧 Email: information@pcatechnologyinc.com
— CODEX | Architecture & Documentation | PCA Technology Inc.