Project Work Plan Fundamentals

Project Work Plan Fundamentals

Quick Answer: A Project Work Plan (PWP) is the central operational tool an architectural project manager uses to translate contractual obligations into structured deliverables, staff assignments, budgeted labor hours, and milestone schedules. Built upon a hierarchical Work Breakdown Structure (WBS) that adheres strictly to the 100% Rule, the PWP directly aligns production effort with the firm's financial plan. By establishing an initial frozen baseline and conducting weekly variance tracking, the project manager detects scope creep, prevents fee erosion, and ensures timely coordination across multidisciplinary teams.

---

Purpose and Anatomy of a Project Work Plan (PWP)

In professional architectural practice, winning a commission and executing an Owner-Architect agreement (such as AIA Document B101-2017) is merely the preliminary legal step. The operational success of the commission depends on how effectively the firm executes the agreed scope within the stipulated timeframe and allocated fee. The primary management vehicle for achieving this is the Project Work Plan (PWP).

According to The Architect's Handbook of Professional Practice (AHPP 15th Edition), a project work plan is not a static document drafted once and shelved; it is an active, evolving operational instrument. The project manager (PM) creates the initial PWP during contract negotiation and finalizes it immediately upon contract execution before any billable drafting or modeling begins. A comprehensive PWP integrates administrative, technical, and financial parameters into a single operational roadmap.

Essential Components of a PWP

1. Project Directory & Governance Structure: Identifies all key project participants, including the client's designated representative (who possesses legal authority to bind the owner under AIA B101 § 5.3), the architect's project team (Principal-in-Charge, Project Manager, Project Architect, Job Captain, and design staff), engineering and specialty consultants, code officials having jurisdiction (AHJ), and construction entities.
2. Project Scope Narrative: Outlines the architectural boundaries of the project, summarizing project program requirements, square footages, site constraints, and specific sustainability or code benchmarks. Crucially, the scope narrative explicitly itemizes both inclusions (basic services) and exclusions (services that constitute additional services if requested by the owner, per AIA B101 Article 4).
3. Deliverables Checklist by Phase: Itemizes every discrete drawing sheet, 3D model milestone, specification section, outline report, and presentation rendering required across all traditional design phases: Schematic Design (SD), Design Development (DD), Construction Documents (CD), Procurement/Bidding, and Construction Administration (CA).
4. Task Assignments & Resource Allocation: Assigns specific team members to each deliverable based on required technical skill levels, staff availability, and individual billing rates.
5. Budgeted Staff Hours (Labor Budget): Translates the architectural net service fee into an exact pool of billable hours per team member for each phase.
6. Master Milestone Schedule: Defines key client presentations, phase completion gates, owner approval intervals, AHJ permit application dates, bid package releases, and construction deadlines.
7. Consultant Coordination Dates & Protocols: Details the scheduling of multidisciplinary backgrounds, BIM coordination file exchanges, clash-detection workshops, and cross-check review cycles with structural, MEP/FP, civil, and landscape consultants.

---

The Work Breakdown Structure (WBS)

The foundational structural framework of any rigorous PWP is the Work Breakdown Structure (WBS). A WBS is a hierarchical decomposition of the total scope of work to be carried out by the architectural team to accomplish project objectives and create the required deliverables.

Level 1: Project (e.g., Regional Health Center)
   └── Level 2: Phase (e.g., Construction Documents - 40% of Fee)
        └── Level 3: Deliverable / Major Task (e.g., Exterior Envelope Assemblies)
             └── Level 4: Work Package (e.g., Wall Sections & Window Head Details)

The Four Levels of Architectural WBS

• Level 1: The Total Project: The overarching project identity, contract number, and total professional fee.
• Level 2: Project Phase: The primary contractual milestones, traditionally organized around standard AIA phases: Schematic Design (15%), Design Development (20%), Construction Documents (40%), Bidding & Negotiation (5%), and Construction Administration (20%).
• Level 3: Deliverable / Major Task: Major discipline-specific deliverables required within that phase. In Construction Documents, Level 3 deliverables include the Life-Safety Plan Package, Core and Shell Architectural Drawings, Interior Partition Schedule, Structural Framing Documents, and MasterFormat Project Manual.
• Level 4: Work Package: The lowest, most granular level of the WBS. A work package represents a discrete, manageable unit of work that can be realistically assigned to a single staff member or sub-team and tracked over a defined timeframe (typically 8 to 80 labor hours). Examples include drafting stair and elevator core enlarged sections, editing MasterFormat Division 08 door hardware specifications, or conducting a clash-detection run on above-ceiling mechanical ductwork.

The 100% Rule

The fundamental integrity rule of the WBS is the 100% Rule. It states that the WBS must capture 100% of the work defined by the project scope and contract, including internal management, QA/QC peer reviews, and consultant coordination. The WBS should exclude unauthorized scope additions, but omitting an existing contractual duty from the WBS does not excuse that duty. Correct planning omissions and separately assess changes to the agreed baseline. Adherence to the 100% Rule prevents two widespread professional practice hazards: omitting critical contract deliverables from the schedule, and tacitly absorbing unauthorized scope additions ("scope creep") without securing an additional service agreement.

---

Integrating the PWP with Financial Management

A work plan is fundamentally flawed if it is created in isolation from the firm's financial accounting model. The Project Manager must bridge the gap between contractual revenue and staff labor expenditure by converting the gross fee into an actionable labor hour budget.

Step-by-Step Fee-to-Hours Conversion

1. Determine the Gross Architectural Fee: The total compensation stipulated in the Owner-Architect agreement (e.g., a stipulated lump-sum fee of $300,000).
2. Deduct Non-Architectural Line Items: Subtract consultant pass-through fees (assumed 20% to 35% for structural, MEP, and civil engineering), reimbursable expense allowances, and a firm project contingency (assumed 5% to 10% reserved for internal rework or unforeseen technical hurdles). The remaining balance is the Internal Production Allowance (the remaining planning allocation for labor, overhead recovery, and profit; an internal reserve is not a reduction of earned net revenue).
3. Allocate Net Fee to Project Phases: Distribute the net fee across phases according to standard office benchmarks or project-specific delivery requirements.
4. Derive Phase Planned Hours: Divide the phase fee allocation by the blended hourly billing rate of the project team assigned to that phase:

$$\text{Planned Labor Hours} = \frac{\text{Phase Labor Budget}}{\text{Blended Hourly Billing Rate}}$$

Practical Worked Example: Construction Documents Phase

Assume an architectural firm secures a contract with a gross fee of $300,000 for a commercial medical office building:

For the Construction Documents (CD) phase, the firm allocates 40% of its Internal Production Allowance:

$$\text{CD Labor Budget} = \text{\textdollar}210,000 \times 0.40 = \text{\textdollar}84,000$$

If the architectural CD team consists of a Project Architect (billing rate: $160/hr), a Job Captain ($120/hr), and an Architectural Intern/Drafter ($100/hr), the planned weighted blend is $120/hr using 14 PA hours, 28 Job Captain hours, and 28 drafter hours weekly. The Project Manager calculates the total planned labor hours available for the CD phase:

$$\text{Total CD Planned Hours} = \frac{\text{\textdollar}84,000}{\text{\textdollar}120/\text{hr}} = 700\text{ hours}$$

If the CD phase is scheduled across a 10-week calendar window, the PM can allocate an average of 70 total staff hours per week across the three team members (e.g., 14 hrs/week PA, 28 hrs/week Job Captain, 28 hrs/week Intern). If actual timesheets reveal the team is burning 95 hours per week during week 3, the PM immediately detects a 35.7% increase in hours compared with plan and must intervene before the fee is exhausted.

---

Deliverables Checklist & Phase Gate Reviews

A deliverables checklist ensures that every technical item required for contractual compliance and agency approval is systematically produced, verified, and cross-referenced. Architectural deliverables do not merely accumulate; they must pass through structured Phase Gate Reviews.

A phase gate review is a formal project milestone occurring at the conclusion of each design phase before advancing to the next. For example, before concluding Schematic Design, the team conducts:

• An Internal Peer Review: An uninvested senior architect or QA/QC director evaluates the drawings for spatial clarity, building code egress compliance, and structural grid coordination.
• A Client Sign-off Review: Under AIA B101 § 3.2.7, the architect must submit the Schematic Design documents to the owner, along with an updated estimate of the Cost of the Work. The architect must obtain the owner's written approval before commencing the Design Development phase.

Advancing into subsequent design phases without formal, written client approval of the preceding phase deliverables is one of the most frequent causes of catastrophic fee loss. If an architect initiates Construction Documents while the owner is still modifying schematic space planning, the firm will inevitably be forced to discard and redraw thousands of dollars worth of technical details.

---

Baseline Tracking, Scope Creep & Plan Maintenance

Once the initial PWP is approved by firm leadership and aligned with the client's schedule, it is officially frozen as the Project Baseline. The baseline represents the standard against which all future progress, time expenditures, and budget variances are measured.

Monitoring Project Performance

The Project Manager tracks performance weekly using time-tracking software and project reporting metrics:

• Planned Hours vs. Actual Hours: Comparing budgeted staff hours to actual timesheet entries per task.
• Earned Percent Complete: Quantifying the actual progress of deliverables (e.g., exterior elevations are 60% complete) rather than assuming progress equals the percentage of fee spent.
• Estimate to Complete (ETC): Forecasting the remaining labor hours required to bring each deliverable to 100% completion.

Managing Scope Creep vs. Additional Services

Scope creep is the gradual, unacknowledged expansion of project scope without a corresponding increase in fee or schedule duration. It typically occurs when a client makes "small" verbal requests during design meetings—such as requesting alternate entrance canopy studies, evaluating an unprogrammed rooftop terrace, or asking for photorealistic marketing renderings.

When a client request falls outside the PWP scope narrative, the PM must reference AIA B101 Section 4.2. Under Section 4.2, the architect is obligated to notify the owner promptly in writing with reasonable promptness, explaining that the requested work constitutes an Additional Service. The architect must outline the required fee adjustment and schedule extension, and receive written authorization from the owner before executing the additional work. The PM then formally updates the PWP, establishes an amended baseline, and allocates the newly approved hours and deadlines to the team.

---

Comprehensive Architectural Work Breakdown Matrix

The following table illustrates a standardized architectural Work Breakdown Structure integrating phase fee allocations, typical deliverables, assigned roles, and quality review gates: