Free tool, no login
Build a performance work statement, a performance requirements summary, and a QASP
Describe the service you are buying and whatever performance objectives you already have. You get all three documents as one linked package: the performance work statement in results terms per FAR 37.602, the performance requirements summary that goes in the contract, and the quality assurance surveillance plan structured to FAR 46.401. One set of objectives runs through all three, so they cannot disagree. It will not invent a performance standard or an acceptable quality level on your behalf.
The service, the period of performance, and any objectives, standards, or acceptable quality levels you have already settled. Partial is fine, that is the normal case.
Free. No account. Nothing is stored against your name.
Or start from an example:
Drafting all three documents. Usually 15 to 35 seconds.
Common questions
What is a quality assurance surveillance plan?
A QASP is the document that says how the Government will verify a contractor met the requirements of a performance-based service contract. FAR 46.401(a) says the plan should be prepared alongside the statement of work and should specify all work requiring surveillance and the method of surveillance. FAR 46.401(b) adds that each contract shall designate where the Government reserves the right to perform quality assurance.
Does this tool write my acceptable quality levels for me?
No, and that is deliberate. An acceptable quality level decides how much deviation the Government will tolerate before performance is unacceptable, and it governs what a contractor is paid. Where you have not supplied one, the tool marks it as your decision rather than filling in a plausible number. Anything it does propose is labelled and has to be accepted by you before the plan will export.
What surveillance methods can it use?
The four in common use: 100 percent inspection, random sampling, periodic inspection, and customer complaint. The tool chooses one per objective and states why. 100 percent inspection suits low-volume high-consequence work, random sampling suits high-volume repetitive work and needs a sample size defensible against your AQL, periodic inspection suits continuous services, and customer complaint is usually a supplement rather than a primary method.
Is it really free, and do I need an account?
Free, and no account. Nothing is stored against your name.
What is a performance work statement, and does this write one?
A performance work statement (PWS) describes what the Government is buying in terms of required results rather than how the contractor should do the work. FAR 37.602 requires that, and requires the description to allow performance to be assessed against measurable standards. This tool writes the PWS, the performance requirements summary, and the quality assurance surveillance plan together from one set of performance objectives, so the three documents cannot describe different work. The PWS narrative is a draft to read and verify: the source tags protect the standards and the quality levels, and prose cannot be checked the same way.
What is a performance requirements summary?
The PRS is the table a contracting officer signs against: each required service, the performance standard, the acceptable quality level, and the deduction that applies when performance falls below it. It is Part 2 of what this tool produces, and it is the same objectives as the PWS narrative rendered as a table.
What does the review at the end do?
It reads the whole package back and argues with it. It reports three things: places where the work statement, the requirements summary and the surveillance plan cannot all be true at once; judgments worth looking at again before they bind a contractor, such as an acceptable quality level so tight the contractor prices in the risk; and anything the drafted narrative added that you never asked for. That last one matters most, because the source tags protect the table cells and nothing protects the prose. Where a fix needs no information you have not given, it offers the exact replacement wording and you can take it in one click. The review is advisory. It does not approve the package, it does not block the download, and it changes nothing unless you tell it to.
What happens after the plan is written?
The plan sets the standard once. Executing it means producing a surveillance record every period for the life of the contract, measured against those same criteria, and being able to compile them when someone asks for the on-time rate. That is a different job from writing the plan, and it is what ArcCompose does.
Built to FAR 46.401(a), which requires a plan to specify all work requiring surveillance and the method of surveillance, and FAR 46.401(b), which requires each contract to designate where the Government reserves the right to perform quality assurance. FAR 37.604 points to subpart 46.4 and permits the Government to prepare the plan or to require offerors to submit one. FAR Part 37 is among the parts in the June 23, 2026 proposed rules under the FAR Overhaul; Part 46 is not. Confirm the current text on acquisition.gov before relying on a specific paragraph.