Bundle catalog

deliverables bundle

Statement of Work

A free, open-source set of 10 Markdown files for drafting and reviewing Statement of Work with explicit evidence, constraints, and approval boundaries.

Use this bundle to draft or review Statement of Work with source evidence, open questions, owners, and approval gates kept explicit. The page previews a deliverable guide, an overview, a workflow, and a quality rubric; the intended output is statement of work draft and approval record. Start source review with acquisition.gov — Far / 37.602.

Project-reviewed beta

10 Markdown files · 1,599 words · no signup · CC-BY-4.0

Professional review status

No professional domain review recorded

This bundle covers legal, financial, privacy, security subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.

Review before reliance: Authorized business, delivery, procurement, finance, tax, intellectual-property, privacy, security, and contract-law reviewers.

Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Is this bundle right for your task?

Who it is for

  • People drafting, reviewing, approving, or relying on Statement of Work
  • Teams working in Professional services, Procurement

When to use it

  • A Statement of Work draft needs a clear purpose, audience, evidence base, structure, and approval path.
  • An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.

What you need to provide

  • The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
  • Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.

Tasks and expected outputs

Questions it helps answer

  • Draft a statement of work without inventing parties, authority, scope, feasibility, acceptance, schedule, fees, terms, or commitment.
  • Prepare a reviewable statement of work draft and approval record with explicit evidence, limitations, validation, and approval boundaries.

What it helps produce

  • statement of work draft and approval record

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Statement of Work and return statement of work draft and approval record with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with acquisition.gov — Far / 37.602, then confirm that the reference is current and applicable. Inspect Statement of Work source-backed deliverable guide before drafting.

Context path: bundles/deliverables/statement-of-work

What the bundle includes

Frameworks

  • party, scope, deliverable, acceptance, schedule, commercial, and change review

Evaluations

  • Statement of Work source verification check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

Limitations and safe use

Do not use this for

  • Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.

Known limitations

  • FAR and GSA performance-based acquisition guidance applies to United States federal contracting and does not establish another engagement's parties, authority, scope, feasibility, acceptance, commercial terms, legal effect, or approval.
  • Task-specific conclusions require current inspected evidence for legal entity and authority records, governing agreement and order documents, approved objectives and scope, requirements and solution evidence, delivery capacity and dependencies, deliverable specifications, acceptance criteria and authorized approvers, schedule basis, pricing and tax approvals, IP and data terms, security review, change and termination terms, and signatures.
  • This bundle does not grant authority to bind a party, commit scope, personnel, dates or fees, accept terms, transfer rights, process data, waive requirements, sign, issue, or represent acceptance.

Safety notes

  • Minimize personal, customer, employee, financial, credential, security, privileged, medical, and unreleased information.
  • Preserve prompt-supplied facts as Provided and mark missing facts Needs verification; do not invent owners, dates, versions, reviewers, or system state.
  • Require explicit confirmation from an evidenced authorized reviewer before taking any action to bind a party, commit scope, personnel, dates or fees, accept terms, transfer rights, process data, waive requirements, sign, issue, or represent acceptance.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.