PCL Construction: How One of North America's Largest Builders Manages Document Risk at Scale
PCL Construction: How One of North America's Largest Builders Manages Document Risk at Scale
PCL Construction is one of the most recognized names in North American construction, with a project portfolio that spans hospitals, stadiums, data centers, and infrastructure at a scale most GCs never reach. For project managers, preconstruction leads, and VDC coordinators, understanding how PCL Construction operates is both a competitive benchmark and a case study in managing complexity. That complexity starts with documents.
What Is PCL Construction?
Company History and Employee-Owned Structure
PCL was founded in 1906 in Portage la Prairie, Manitoba. It transitioned to 100% employee ownership in 1977, a structure it maintains today. That ownership model shapes how the company operates: employee-owners have a direct stake in project outcomes, which drives a culture of process discipline and risk management that filters into how preconstruction teams handle documentation.
With roughly 5,000 employee-owners across North America and annual revenues exceeding $6 billion, PCL consistently ranks among the top general contractors on Engineering News-Record's Top 400 list.
PCL's Key Markets and Project Types
PCL organizes its work into several core market sectors:
- Civil infrastructure: highways, bridges, marine structures
- Industrial: oil sands, power generation, processing facilities
- Buildings: healthcare, education, sports and entertainment, government
- Retail and commercial: mixed-use, office, and tenant improvement
Each sector carries distinct documentation requirements. An industrial project in Fort McMurray generates different spec section volumes and submittal workflows than a hospital in Denver. The common thread is document volume and the risk that comes with it.
How PCL Construction Delivers Large-Scale Projects
PCL's Preconstruction Process
PCL invests heavily in preconstruction, treating it as the primary risk-mitigation phase. Their preconstruction teams review constructability, coordinate with design teams, and develop detailed cost models before mobilization. The goal is to surface conflicts and scope questions before they become field problems.
This is standard practice for top-tier GCs, but execution is where the gap appears. Manual document review, no matter how experienced the team, has a ceiling on what it catches.
Design-Build vs. Design-Bid-Build at PCL
PCL pursues both delivery methods. On design-build projects, they carry more responsibility for design coordination, which increases the importance of internal document QA. On design-bid-build projects, the drawing set and spec sections arrive from the owner's architect, and the GC's job is to identify conflicts before pricing and before breaking ground.
In both cases, contradictions between drawings and specifications create change order exposure. The delivery method changes who holds the liability, not whether the risk exists.
Technology and Innovation Initiatives at PCL
PCL has invested in BIM, VDC workflows, and prefabrication. Their internal technology teams have piloted tools across project lifecycle phases. Like most large GCs, they operate with a mix of enterprise platforms (Procore, Autodesk Construction Cloud) and specialized tools for specific workflows.
Document review at the preconstruction phase is one area where purpose-built AI tools have begun to outperform general-purpose document management platforms, particularly for contradiction detection across large drawing sets and specification divisions.
The Document Complexity Challenge on PCL-Scale Projects
How Many Documents Does a Major Commercial Project Generate?
A mid-size commercial project generates thousands of individual document files: architectural and structural drawing sheets, MEP coordination drawings, 20 to 30 CSI spec sections, addenda, RFIs, submittals, and schedules. On a hospital or data center project, that number scales significantly.
The average large commercial project generates approximately 800 RFIs. Many of those RFIs trace back to something that existed in the document set before the first shovel hit the ground.
Common Causes of RFIs and Change Orders on Large Projects
The most common sources of RFIs and change orders on large projects are not surprises to experienced project teams. They include:
- Spec-to-drawing contradictions: a material specified in 09 91 23 that conflicts with the finish schedule on the drawings
- Scope gaps: work that is implied but not explicitly assigned to any trade in the bid documents
- Missing details: referenced details that do not appear in the drawing set
- Coordination failures: MEP conflicts that were not resolved during design
- Code compliance gaps: requirements in the applicable building code that are not addressed in the drawings or specs
Each of these can be detected before construction begins with a systematic review process. The problem is time: preconstruction teams rarely have enough of it to read every page of a 10,000-page document set.
Spec vs. Drawing Contradictions: A Silent Budget Killer
Contradictions between spec sections and drawings are particularly costly because they often go undetected until a subcontractor prices work one way, installs it, and then gets told the spec says something different. At that point, the project has a change order, a delay, or both.
Lintel analysis of commercial construction document sets finds that projects over 50,000 sq ft average 23 detectable spec-to-drawing contradictions before preconstruction review - each one a potential RFI or change order event.
Undetected contradictions on a typical commercial project carry an average cost of $340,000. Across a portfolio of projects, that number compounds quickly.
How AI-Powered Document Review Works on Projects Like PCL's
Detecting Scope Gaps Before the First Shovel Hits the Ground
An AI construction document review platform reads the entire document set, cross-references scope assignments across drawings and spec sections, and flags work that is referenced but not explicitly scoped. This is the kind of review a senior estimator or project engineer would do if they had 40 hours and a photographic memory.
Scope gaps are most common at the interfaces between trades: the area where mechanical ends and structural begins, or where civil and building sit side by side on a site plan.
Compliance Risk Flagging Across Drawings, Specs, and Schedules
Compliance violations caught in the field result in 3 to 6 months of average delay per violation. An AI review tool can flag potential compliance gaps against applicable code references before the documents go to bid, giving the design team time to address them without schedule impact.
This is particularly relevant on PCL-scale projects where the jurisdictional complexity is high: a multi-state infrastructure program or a federally-funded healthcare facility carries code requirements that span multiple bodies of authority.
Reducing RFIs with Automated Contradiction Detection
When contradiction detection runs automatically across the full drawing set and all spec sections, the output is a prioritized list of issues with document references. The preconstruction team can resolve, escalate, or log each item before the project bids. RFIs that would have generated field delays become pre-bid clarifications.
The math on this is straightforward: the earlier a contradiction is caught, the cheaper it is to fix.
What Project Teams at Top GCs Can Do Right Now
Checklist: Preconstruction Document Review Best Practices
Before any project goes to bid, a preconstruction team should be able to confirm:
- [ ] All referenced spec sections exist in the project manual
- [ ] All referenced drawing details are present in the drawing set
- [ ] No material or product contradictions exist between the finish schedule and the applicable spec sections (09 series)
- [ ] Scope boundaries between trades are explicitly documented
- [ ] All applicable code references are addressed in the drawings or specs
- [ ] RFI log from the last comparable project has been reviewed for recurring issue types
- [ ] Submittal schedule aligns with the construction schedule
Most preconstruction teams can confirm some of these items. Few can confirm all of them under a real-world bid timeline without automated support.
How Lintel Fits Into a GC's Existing Workflow
Lintel does not replace Procore, Autodesk Construction Cloud, or a GC's existing VDC process. It runs at the preconstruction phase, reads the document set, and returns a structured report of contradictions, scope gaps, and compliance flags before the project goes to bid or breaks ground.
The output feeds directly into the preconstruction team's existing RFI and issue log process. There is no new platform to onboard, no new workflow to train. The review happens once; the findings integrate into what the team is already doing.
FAQ
Is PCL Construction employee-owned?
Yes. PCL has been 100% employee-owned since 1977. There are no outside shareholders. This structure means employee-owners have a direct financial stake in project performance, which influences how the company approaches risk management, including during the preconstruction and document review phases of a project.
What types of projects does PCL Construction specialize in?
PCL works across civil infrastructure, industrial, healthcare, education, sports and entertainment, and commercial buildings. They operate throughout Canada, the United States, Australia, and the Caribbean. Project sizes range from mid-market to multi-billion-dollar programs, with particularly deep experience in healthcare and heavy civil work.
How do large general contractors like PCL handle RFIs and change orders on complex projects?
Large GCs manage RFIs through formal logs tracked in platforms like Procore. Prevention, however, happens in preconstruction. Teams review drawing sets and spec sections for contradictions and scope gaps before bid. AI-powered tools now automate parts of that review, catching issues that manual review misses under tight timelines.
See what Lintel finds in your document set - Book a demo