Module 4 / Lesson 17
Solicitation and Attachment Reading
Lesson Snapshot
Think of the work statement as the blueprint for performance.
The work statement is where the opportunity becomes real.
Output or skill
Solicitation package file inventory
Overview
Explain the difference between a Performance Work Statement, Statement of Work, and Statement of Objectives in plain English.
Identify tasks, deliverables, standards, frequency, location, and government/contractor responsibilities inside a work document.
Translate work requirements into proposal, pricing, staffing, and performance questions.
Recognize why a work statement is not just descriptive; it drives cost, risk, and performance.
The work statement is where the opportunity becomes real. It tells you what the contractor must do. Beginners may read it casually, like a job description. Professionals read it like an operating manual and a pricing blueprint. Every task can create labor hours. Every frequency can create schedule pressure. Every deliverable can create administrative work. Every standard can create quality risk. If you misunderstand the work statement, your proposal, price, and performance plan will all be wrong.
Think of the work statement as the blueprint for performance. The proposal is your plan for building from that blueprint. The price is your estimate of what it costs to build and operate it. The contract performance system is how you prove you built it correctly. When the blueprint is misunderstood, everything downstream becomes unstable.
Learn
A PWS, or Performance Work Statement, usually describes the results the government wants and the standards the contractor must meet. A SOW, or Statement of Work, often describes the tasks or work in a more prescriptive way. A SOO, or Statement of Objectives, may give higher-level objectives and ask offerors to propose their own approach. Beginners do not need to become lawyers on day one. They need to ask practical questions: What must be done? How often? Where? By whom? To what standard? What must be delivered? What is provided by the government? What must the contractor provide? What happens if performance is poor?
['Requirement extraction table: requirement → frequency → location → standard → deliverable → cost driver → proposal proof.', 'Pipeline: work statement → labor plan → price → quality plan → performance tracker.', 'Responsibility map: government-furnished items on one side, contractor-furnished labor/material/equipment/reporting on the other.']
Visual placeholder: Solicitation package map. Show listing → attachments → PWS/SOW/SOO → pricing documents → clauses → amendments/Q&A → Section L/instructions → Section M/evaluation.
Solicitation package map
Show listing → attachments → PWS/SOW/SOO → pricing documents → clauses → amendments/Q&A → Section L/instructions → Section M/evaluation.
A work statement is like a recipe for a catering job. It is not enough to know 'serve dinner.' You need to know how many guests, what menu, what time, where, who provides dishes, who cleans up, and what happens if food runs out. In GovCon, 'grounds maintenance' or 'IT support' is only the label. The work statement tells you the serving size, ingredients, timing, tools, and quality standard.
See It
A PWS for landscaping says the contractor must mow 18 acres weekly from April through October, edge sidewalks twice monthly, remove weeds from landscaped beds, respond to snow events within four hours, and submit a monthly service report. A beginner sees 'landscaping.' A professional sees: seasonal labor plan, equipment hours, fuel, snow response standby, weather risk, reporting admin, quality inspections, and possible subcontractor backup. The PWS becomes a pricing and performance map.
Treating the work statement like background reading instead of the source of scope.
Missing frequency words such as daily, weekly, monthly, emergency, as-needed, or within four hours.
Ignoring deliverables like reports, meetings, logs, and quality documents.
Failing to separate government-furnished and contractor-furnished items.
Writing a proposal that repeats the PWS instead of explaining how the contractor will perform it.
Practice
Pause, draft your reasoning, then reveal the guide.
Think first
easy
Highlight all frequency words in a short PWS excerpt.
moderate
Turn five PWS tasks into a requirement extraction table with cost drivers and proposal proof.
difficult
Given a PWS with emergency response and recurring work, identify which requirements create staffing, equipment, and cash-flow risk.
scenario
A custodial PWS requires nightly cleaning, quarterly floor care, consumable restocking, and monthly quality reports. Build a scope-to-price map.
Choose or draft an answer first. Guidance stays hidden until you reveal it.
Think first
Write your own answer before opening the guide.
Apply
Use this as a practical decision checklist, not as a memorization exercise.
Decision check 1
Realistic opportunity application: Use a sample service solicitation with a listing, PWS, pricing schedule, amendment, and Q&A. Build a one-page document inventory. Mark which file tells you the work, which file tells you how to respond, which file tells you how price is structured, and which file changes or clarifies earlier instructions.
Decision check 2
The practical skill is document control. A beginner who reads only the public listing may miss the real requirements. A careful contractor follows the attachment trail before making promises.
Choose one common service you understand, such as cleaning, landscaping, cooking, or maintenance. Explain how a vague job title becomes a real operating plan once you define frequency, standard, location, and deliverables.
Review
The work statement is the operating blueprint. It turns a broad opportunity title into actual tasks, standards, deliverables, costs, and risks. A professional extracts requirements before writing or pricing.
Next, we will look at the two sections that tell the offeror exactly what to submit and how the government will judge the response: Section L and Section M.