How the Productivity Wave report differs from the typical MSR and other reports?

Three truths about MSRs

  • They are required (CFR Subpart 1552.2) for all government awarded services contracts
    • If your Contract has only one CDRL it’s: A001 Contractor’s Progress, Status and Management Report / Monthly Status Report (MSR)
  • Identifying, collecting and consolidating the description of the work accomplished to support the cost is time consuming, particularly for the contract project manager
  • They yield little to no value to the Prime Contractor and Government, other than compliance with the reporting requirement and financial reporting data

The Productivity Wave solution has changed all of that . . . .

Well, except for the requirement, but everything else

Productivity Wave’s Custom Report Examples

PWS /SOW area
  • Analyze volume of activity by PWS/SOW area and trends over time
  • Use to rebalance resources or justify funding/resource levels
Deliverable Type
  • Support specific customer reporting requirements – Identify all meetings within a given time-period with a list of team members participating
  • Include CDRLs detail and performance report sections within reports
  • Ensure CDRLs are completed per contract requirements
Customer Business Unit
  • Analyze volume of activity by Unit and trends over time
  • Use to rebalance resources or justify funding/resource levels
Customer Significant Event(s)
  • Identify recently completed and future significant and supporting customer events for MSR
  • Identify the volume and total activities performed to support a specific event
  • Identify types and specific activities tied to event if desired
  • Identify activities by user and user role for resource loading
  • Analyze volume and quantity of activities by User and trends over time for performance assessments
Case Study / Narratives
  • Allows for a free form description of the features and benefits of support services provided (adds subjective data)
  • Allows the association of activities and events to a narrative from one or multiple contracts

Productivity Wave uses beyond the MSR

Customer Centric
  • Weekly reports to customers
  • In-Process activity data to support Customer / Contractor Meetings
  • Active Project Management of the contractor team
  • Quarterly metrics for performance reviews with customers
  • Award Fee justification
  • Annual performance summary for CPARS
  • Work volume trends to justify or support resource requirements
  • Task Initiation/Completion notifications including performance standards to define expectations and support customer inspection
  • Summary delivered activity lists to support customer acceptance
Company Centric
  • Implementation and adherence of Project Management and Quality Control processes
  • Internal audits of team performance / appraisals
    • Contract Project Manager
    • Individual Employees
    • Subcontractors
    • Specific Teams
  • Hard performance data for proposals, marketing and websites
    • Volume and quality of prior contract performance
    • Activity Types and specific activities tied to significant customer events
    • Case Studies and Narratives defining features and benefits of services provided
  • Reports can be run on a single contract or across multiple contracts and task orders

What Drives Your Current  MSR Format, Content and Process

Contractual and Government Requirements
  • CDRL A00x; Contractor’s Progress, Status and Management Report, Monthly Status Report (MSR)
  • DID: DI-MGMT-80227
  • CFR 1552.211-72 Monthly progress report
  • COR/PCO preferences and examples they have seen in the past

These typically define “What” information the report should contain and “When” it is submitted
However, the requirement typically specifies the report be prepared and submitted in “Contractor’s Format”

Corporate Processes and Standards
  • Reuse a process and format from prior / other prime contract(s)
  • Variation in formatting and process by contract, team, office, region, division, etc.



Content often driven by organizations other than the team executing the work (e.g., Business Development)
Process often driven by, “This is how we have always don’t it”, BUT WHY

How Productivity Wave Meets Reporting Requirements

CFR 1552.211-72
  • (a) The Contractor shall furnish . . . the combined monthly technical and financial progress report stating the progress made, including the percentage of the project completed, and a description of the work accomplished to support the cost.
  • (b) Specific discussions shall include difficulties encountered and remedial action taken during the reporting period, . . .
  • (b) . . . and anticipated activity with a schedule of deliverables for the subsequent reporting period
  • b. Description of the progress made against milestones during the reporting period;
  • c. Results. positive or negative, obtained related to previously-identified problem areas, with conclusions and recommendations;
    e. Problem areas affecting technical or scheduling elements, with background and any recommendations for solutions beyond the scope of the contract;
  • m. Contract schedule status;
    n. Plans for activities during the following reporting period;
  • a. Performance Status – Identify significant accomplishments and progress made during the affected reporting period by SOW/PWS paragraph.
    b.  Schedule Status – Identify schedule for and status of all deliverables.
  • a. Performance Status – . . .  Also identify significant challenges or risks encountered that impact the successful delivery of required services.
  • b.  Schedule Status – Identify schedule for and status of all deliverables. If the efforts are not on schedule, indicate the reason for the delay and provide a revised completion /delivery date
Productivity Wave
  • 1. Significant and Supporting Event Data (completed)
    2. Case Study / Narratives
    3. Summary Metrics Data
    4. Detailed Delivered Activities Report
  • 5. Detailed Delivered Activities comments (as needed)
    6. In-Process Activities with comments and / or status (as needed)
  • 7. Significant and Supporting Event Data (future)
    8. In-Process Activities due dates and comments / status (as needed)