{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The GovCon Show","title":"S2E18 - The SOW that Wasn't","html":"","width":"100%","height":180,"duration":1144,"description":"The work description is not just another attachment.\nIt is the operating system of the contract.\nIn this episode of The GovCon Show, we break down what happens when contractors treat a Statement of Work, Scope of Work, Statement of Objectives, and Performance Work Statement like interchangeable labels.\nThey are not the same thing.\nA weak or misunderstood work description can create risk before the contract even starts. It can distort pricing, hide assumptions, create subcontract gaps, invite customer-direction problems, confuse acceptance criteria, and make fixed-price performance far more dangerous than anyone expected.\nThis episode explains why the label matters, but the substance matters more. A document called a SOW may not actually define the work well enough to price and perform. A SOO may give flexibility, but it also shifts responsibility to the contractor to define the solution clearly. A PWS may sound outcome-focused, but if performance metrics are vague, subjective, or outside the contractor’s control, it can become a trap.\nBefore you price, propose, subcontract, or perform, ask the hard question:\nCan we actually price, perform, manage, subcontract, and defend this work description?\nRun the Fixed-Price Conversion Risk Assessment at GovConAdvisoryGroup.com or schedule a GovCon Risk Triage Call before the price becomes a promise.","thumbnail_url":"https://img.transistorcdn.com/WivleeXGIwd_zHnQQqM8p41pOHA-SCzqvHtS6FeawHA/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wMWY0/MGYxMjUxODQzMjk3/MjYyN2QwYWYzNWM3/YWFhNC5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}