14.3 Contract Administration Planning & Performance Monitoring

Contract Administration Planning & Performance Monitoring

Foundations of Post-Award Contract Administration

The award of a public contract marks the conclusion of the sourcing process, but it represents only the beginning of contract execution. Deficient administration can undermine even a well-drafted solicitation; planning and post-award controls both matter. Once the contract is executed, the public entity must actively manage vendor performance, maintain rigorous compliance documentation, verify invoices against actual deliverables, and ensure strict adherence to statutory and ethical standards.

Division of Authority: The Procurement Officer vs. The Project Manager

A foundational principle of public contract administration is the strict legal separation between contractual authority and technical oversight:

• Contracting Officer / Public Buyer: Possesses express legal authority delegated by statute, ordinance, or administrative rule to legally bind the public agency. Only the contracting officer or authorized buyer has the legal power to issue contract modifications, approve change orders, negotiate price adjustments, waive contractual requirements, issue formal warning notices (Cure Notices or Show Cause Notices), or terminate a contract. No representation by any other public official can modify a written contract.
• Project Manager (PM) / Contracting Officer's Representative (COR): Possesses technical and operational authority to monitor day-to-day work, review deliverables, perform inspections, track milestone schedules, and verify that services meet technical specifications. The PM or COR acts as the technical eyes and ears of the procurement officer. Crucially, the PM has no legal authority to alter contract scope, increase prices, waive specifications, extend completion dates, or direct the contractor to perform out-of-scope work.

When project managers or field engineers inadvertently instruct contractors to perform additional or altered tasks without the buyer's written authorization, they create severe legal complications known as constructive changes, exposing the agency to unauthorized liabilities and unbudgeted financial claims.

The Post-Award Orientation Conference (Kickoff Meeting)

The post-award orientation conference, commonly known as the contract kickoff meeting, is the primary administrative mechanism used to establish a shared understanding of contractual duties, operational protocols, and performance expectations before work commences.

Primary Objectives of the Orientation Conference

1. Establish Mutual Understanding: Ensure that both public agency personnel and contractor leadership share an identical interpretation of the statement of work, delivery timelines, quality standards, and contractual constraints.
2. Clarify Communication Protocols: Designate official single points of contact (SPOC), delineate the exact boundaries of field personnel authority, and establish formal channels for written correspondence, technical submittals, and change requests.
3. Review Compliance and Administrative Procedures: Walk through mandatory administrative processes, including security badging, site access rules, prevailing wage certified payroll reporting, environmental compliance, safety plans, and DBE/MWBE participation tracking.
4. Align Invoicing and Payment Workflows: Define the required invoice format, necessary supporting documentation, billing cycles, prompt payment review workflows, and retainage terms to prevent billing disputes.
5. Identify Potential Risks Early: Conduct an initial review of critical project dependencies, long-lead procurement items, and potential operational bottlenecks.

Mandatory Attendees and Stakeholder Roles

To ensure complete organizational alignment, the orientation conference must include key decision-makers from both the public agency and the commercial contractor:

• Public Procurement Officer / Buyer (Chair): Presides over the conference, establishes contractual boundaries, explains modification procedures, and enforces the rule that only the procurement office can authorize contract changes.
• Public Project Manager / COR / Lead Engineer: Explains technical workflows, submittal review processes, inspection standards, testing procedures, and day-to-day site coordination.
• Fiscal / Accounts Payable Representative: Clarifies billing requirements, invoice routing, electronic fund transfers, prompt payment statutory timelines, and tax-exempt documentation.
• Contractor Executive / Contracts Administrator: Represents commercial management, verifies corporate commitment, and executes administrative protocols.
• Contractor Project Manager / Field Superintendent: Oversees on-site labor, coordinates daily logistics, manages subcontractors, and submits technical submittals.
• Key Subcontractors: Major specialty trade subcontractors (e.g., electrical, mechanical, or software architecture leads) whose work directly affects the project's critical path.

Official Meeting Minutes and Contract Record

The public buyer is responsible for taking detailed, formal minutes during the orientation conference. These minutes must document all discussions, clarifications, agreements, and action items. The buyer distributes the draft minutes to all attendees, secures written concurrence or corrections from the contractor, and archives the finalized minutes in the official contract administration master file. These minutes serve as a vital contemporaneous record should disputes arise later regarding early verbal discussions.

The Contract Administration Plan (CAP)

A Contract Administration Plan (CAP) is a comprehensive, written operational management guide prepared by the public procurement team to direct the monitoring, surveillance, and closeout of a specific contract. While routine commodity purchases require only basic receiving and invoice matching, complex service, IT, and construction contracts require a fully articulated CAP.

Essential Components of a Robust CAP

The Quality Assurance Surveillance Plan (QASP)

A core subsection of the CAP for service and performance-based contracts is the Quality Assurance Surveillance Plan (QASP). The QASP establishes the systematic methods the public entity will use to monitor contractor performance against stated Service Level Agreements (SLAs) and Performance Work Statements (PWS). Common surveillance methods detailed in a QASP include:

• 100% Inspection: Applied to critical, high-risk deliverables (e.g., life-safety equipment installation, structural steel welds, custom software security modules) where any failure could cause catastrophic harm or substantial financial loss.
• Random Sampling: Statistically valid random sampling applied to high-volume, repetitive tasks (e.g., facility janitorial services, fleet oil changes, call center inquiries) where inspecting every occurrence is cost-prohibitive.
• Periodic Inspection / Surveillance: Scheduled audits conducted at predetermined intervals (e.g., monthly preventative maintenance reviews, quarterly inventory counts).
• Customer Feedback / User Surveys: Structured, objective surveys collected from end-users to gauge service satisfaction, supplemented by agency verification to avoid subjective bias.

Performance Monitoring Tools and Methodologies

Proactive contract monitoring requires objective, transparent tools that measure progress against established baselines rather than relying on subjective vendor assurances.

Milestone Tracking and Critical Path Method (CPM)

For complex service implementations and public works projects, the contract administrator tracks performance using milestone schedules and Critical Path Method (CPM) network diagrams. The critical path represents the longest sequence of dependent activities that must be completed on time for the entire project to finish on schedule. Absent available mitigation, resequencing, or schedule recovery, a delay to the controlling path delays forecast completion, justifying heightened surveillance and immediate intervention by the public buyer.

Key Performance Indicators (KPIs) and Service Level Agreements (SLAs)

Public contracts frequently translate broad performance expectations into quantifiable Key Performance Indicators (KPIs) governed by enforceable Service Level Agreements (SLAs):

• Quantitative Metrics: Metrics must be objective, measurable, and verifiable. Examples include:
  • On-Time Delivery Rate: Minimum 98.5% of purchase orders delivered within contracted lead times.
  • System Availability: Core enterprise server uptime of 99.95% during normal business hours.
  • Mean Time to Repair (MTTR): Emergency service restoration within 2 hours of notification.
  • First-Contact Resolution: Minimum 85% of citizen helpdesk tickets resolved without escalation.
• Financial Remedies and SLA Credits: SLAs should define measurement, reporting, escalation, and any agreed remedies—often structured as invoice credits or liquidated deductions—if the contractor fails to meet established performance thresholds. These credits are not penalties; rather, they reflect the reduced contractual value of the sub-par service received.

Standardized Inspection Checklists and Progress Reports

To eliminate subjectivity and prevent inconsistent monitoring across multiple project inspectors, the public agency must deploy standardized inspection checklists. These checklists map directly to contract specification sections, allowing inspectors to record objective pass/fail findings, take photographic evidence, and document exact measurements.

Contractors on multi-month projects should be required to submit regular Progress Reports (weekly or monthly) detailing:

• Work accomplished during the reporting period.
• Milestones scheduled for completion in the subsequent period.
• Deliverable status vs. baseline schedule (Schedule Variance).
• Cost expenditures vs. budgeted baseline (Cost Variance).
• Open issues, pending change order requests, and risk mitigation actions.