AgreeBoth sidesEducational outline

Statement of Work Educational Outline

Use this after the parties understand the project and before work starts. It is a discussion and drafting outline, not a universal contract or substitute for project-specific legal review.

Source: assistedfreelance.com/templates/statement-of-work

Context and limits

Before you use it

Identify every document that forms the agreement and how conflicts between them are handled.
Use the actual names, scope, currency, dates, approval process, and governing terms for the engagement.
Do not paste live credentials, sensitive personal data, or confidential account details into this outline or Lucy.

Blank reusable version

Copy, edit, and verify.

# Statement of Work — Educational Outline

## Parties and project reference
[Legal or business names, contacts, project title, and reference to any controlling agreement.]

## Objectives
[The project problem and intended practical outcome without unsupported guarantees.]

## Scope and exclusions
[Included work, quantities, boundaries, and explicitly excluded work.]

## Responsibilities and dependencies
Freelancer: [responsibilities]
Client: [inputs, access, decisions, approvals]
Dependencies: [facts and third parties the plan relies on]

## Deliverables
[Outputs, formats, source/editable files, documentation, and handover items.]

## Milestones and schedule
[Observable milestone, target date, review period, approver, and effect of delays.]

## Acceptance
[Acceptance criteria, test environment, issue-reporting process, and approval window.]

## Fees, expenses, invoicing, and payment
[Amount, currency, approved expenses, invoice triggers, due terms, taxes as applicable, and platform mechanics.]

## Revisions
[Included rounds, consolidated feedback, and revision boundaries.]

## Changes
[How added, removed, exchanged, or deferred work is described, priced, scheduled, and approved.]

## Intellectual property and licensing prompts
[New work, pre-existing material, third-party assets, transfer/license trigger, source files, and portfolio permission.]

## Confidentiality, privacy, and security prompts
[Information handling, minimum access, secure sharing, incident notice, return/removal, and applicable policies.]

## Pause, termination, and close-out references
[Refer to the actual rights, notice, payment, delivery, access-removal, and dispute wording that applies.]

## Approval or signatures
[Authorized names, roles, method of approval, and date.]

Copying and downloading happen in this browser. AssistedFreelance does not receive or save the template.

Completed fictional example

Harbor Street Bakery website SOW outline

Use this to understand the level of specificity, not as facts, pricing, tax treatment, or agreement wording for your project.

# Statement of Work — Harbor Street Bakery Website

## Parties and project reference
Harbor Street Bakery (client) and Jordan Lee Studio (fictional freelancer). Project reference: HSB-WEB-01. This outline must be read with the parties’ actual controlling agreement.

## Objectives
Make product and catering information easier to find and provide a usable catering inquiry path. No inquiry or sales volume is guaranteed.

## Scope and exclusions
Included: five responsive pages, catering form, basic analytics handoff, editor access, and update guide. Excluded: ecommerce, online payments, copywriting, photography, and ongoing administration.

## Responsibilities and dependencies
Jordan designs, builds, tests, reports risks, and completes the listed handover. Sam supplies approved content, brand assets, secure access, and one consolidated response per review. Timing depends on inputs and approvals arriving on agreed dates.

## Deliverables
Home, Products, Catering, About, and Contact pages; inquiry form; agreed source assets; third-party license list; analytics handoff; editor/admin access; and update guide.

## Milestones and schedule
1. Kickoff and structure confirmed. 2. Key page design approved after one consolidated round. 3. Staging build passes agreed checks. 4. Launch and handover completed. Written date changes record dependency impacts.

## Acceptance
Approved content is present; navigation and agreed links work; the form validates, reaches the designated inbox, and confirms submission; agreed mobile, desktop, browser, keyboard, and accessibility checks pass; handover items are supplied.

## Fees, expenses, invoicing, and payment
$5,600 USD fixed fee in four fictional $1,400 milestones tied to kickoff, design approval, staging acceptance, and final handover. Hosting or licensed assets require written preapproval. Tax treatment follows applicable requirements and is not invented here.

## Revisions
One consolidated design round and one staging correction round within the accepted scope.

## Changes
New pages, ecommerce, a new design direction, or other changed requirements need a written scope, price, schedule, and approval decision before work begins.

## Intellectual property and licensing prompts
The final agreement must distinguish project-specific work, Jordan’s reusable components, and third-party assets; name delivered source files; identify license responsibility and any transfer trigger; and request portfolio permission separately.

## Confidentiality, privacy, and security prompts
Access is shared through the bakery’s approved secure method, limited to what the work needs, and removed or reduced after handover. No live credentials appear in this document.

## Pause, termination, and close-out references
The parties will use the actual controlling agreement for pause, termination, payment, delivery, access removal, governing law, and dispute terms.

## Approval or signatures
Authorized names, roles, dates, and approval method to be completed only after review of the full agreement.

Field by field

Adapt it deliberately

Agreement stack: Name the parties, project, controlling terms, and what happens if documents conflict.
Scope and responsibilities: Match the brief and accepted proposal, then resolve any difference explicitly.
Milestones and acceptance: Use observable work, review windows, approvers, and clear test conditions.
Money and changes: State currency, expenses, triggers, and the written authorization required for changed work.
Rights and security: Identify pre-existing and third-party material, license or transfer triggers, access controls, and offboarding.
Close-out and approval: Refer to the actual pause, termination, dispute, governing-law, signature, and notice provisions.

Important considerations

Common mistakes

Do not call an outline legally complete merely because every heading is filled in.
Do not copy rights, termination, tax, or governing-law language without understanding its project and jurisdictional effect.
Do not start work while scope, authority, payment triggers, or controlling documents remain materially unclear.