Step 1 of 7
Parties to this agreement
Identify the buyer and the supplier. These details appear on the SOW and are used for contract execution and payment.
Buyer (Client)
Supplier (Service Provider)
Step 2 of 7
Project overview
Describe the project at a high level. This becomes the opening section of the SOW and sets the context for everything that follows.
2–4 sentences is sufficient. Be specific about the problem being solved.
Step 3 of 7
Scope of work
Define exactly what is included — and what is not. Ambiguity here is the cause of most contract disputes. Be specific.
List each distinct deliverable or service component. E.g. "Helpdesk support (8am–8pm Mon–Fri)", "Monthly SLA report", "Annual technology review".
This section is often more important than the in-scope list. Define the edges clearly.
Step 4 of 7
Service levels and acceptance criteria
Define measurable standards. These are the criteria used to confirm milestone completion and resolve any disputes about quality.
E.g. "P1 incidents: 4-hour on-site response", "Report delivery: by 5th working day of each month", "Uptime: 99.5% measured monthly".
Step 5 of 7
Commercial and payment terms
Set the fees, payment schedule, and any commercial conditions.
Each milestone marks a payment stage. Be specific about what constitutes completion — these define when payment falls due under the SOW. Milestones are recorded in the document; BundleIQ does not currently hold or release funds against them.
Step 6 of 7
Special conditions and legal clauses
Select any additional clauses relevant to this agreement. These are added to the standard SOW template.
Step 7 of 7
Review and generate
Review the SOW below. When you are satisfied, generate the final document. It will be saved to your contract library and downloaded for you to sign.
ℹ️ What happens next: The SOW is saved to your BundleIQ contract library and downloaded as a document you can send to the other party. Sign it using your usual e-signature service, or in wet ink. BundleIQ does not send it for you and does not hold a signed copy — keep the executed version with your own records.