Free Excel download β’ Edit online β’ Save & share with Drive β’ Export to PDF
A Schedule is a binding legal attachment appended to a main contract that sets out the specific commercial details β deliverables, fees, timelines, technical specifications, IP terms, or data processing requirements β that govern a particular engagement or transaction. Rather than embedding granular detail in the body of the agreement, parties use schedules to keep the main contract readable and reusable across multiple engagements while preserving full legal enforceability for every material term. This free Word download gives you a professionally structured, jurisdiction-aware starting point that you can adapt to any service agreement, employment contract, supply arrangement, or commercial deal and export as PDF for execution.
Operating without a properly drafted schedule leaves the most commercially important terms of your contract β what exactly is being delivered, by when, for how much, and who owns the result β dangling on informal emails or verbal agreements. When a deliverable is disputed, a payment milestone is withheld, or a contractor walks away with IP you believed you had purchased, the absence of a signed schedule is almost always the root cause. A well-structured schedule closes four gaps simultaneously: it defines deliverables precisely enough to trigger rejection and payment clauses; it sets milestone dates that create enforceable obligations; it assigns IP ownership in writing so there is no default rule to argue about; and it establishes a deemed-acceptance mechanism that keeps the project clock running. This template gives you all four protections in a format that attaches cleanly to any main agreement and satisfies the incorporation-by-reference standards applied by courts in the US, Canada, the UK, and the EU.
| If your situation is⦠| Use this template |
|---|---|
| Detailing the specific services or deliverables the contractor must provide | Schedule of Services / Statement of Work |
| Setting out all fees, rates, and payment milestones | Schedule of Fees / Pricing Schedule |
| Listing technical or product specifications for goods being supplied | Schedule of Specifications |
| Documenting data processing activities under a data protection agreement | Data Processing Schedule / DPA Annex |
| Attaching a detailed timeline with milestones and deadlines to a project contract | Project Milestone Schedule |
| Listing intellectual property licensed or assigned under a license agreement | Schedule of Licensed IP / IP Assignment Schedule |
| Enumerating assets, equipment, or inventory covered by a sale or lease | Schedule of Assets |
Why it matters: A deliverable described as 'consulting services' or 'design work' gives neither party a standard to measure against. When output is disputed, there is no contractual basis to reject it or withhold payment.
Fix: Write each deliverable as a specific, measurable output β format, content, performance standard, and word count or file type if relevant. If it cannot be measured, it cannot be enforced.
Why it matters: Contracts and their schedules frequently conflict on fees, timelines, or scope β especially when schedules are updated annually. Without a precedence rule, both parties believe their preferred document controls, and resolution requires litigation or arbitration.
Fix: Include a single sentence at the top of every schedule stating which document governs in the event of conflict, and be consistent across all schedules in the same agreement.
Why it matters: Schedules added after execution of the main agreement may be unenforceable in common-law jurisdictions unless supported by fresh consideration β meaning the core commercial protection the schedule provides (IP assignment, acceptance criteria, fee structure) may not hold.
Fix: Finalise and attach all schedules before the main agreement is signed. If a schedule must be added later, document the consideration β additional payment, extended scope β provided in exchange.
Why it matters: Without a deemed-acceptance clause, a client can withhold approval indefinitely without committing a breach, blocking milestone payments and extending the project with no legal remedy for the service provider.
Fix: Set a defined review period (typically 5β10 business days) and state explicitly that silence or failure to provide a written list of deficiencies within that period constitutes acceptance.
Why it matters: In most jurisdictions, work product created by an independent contractor remains the contractor's property by default. Without an assignment clause in the schedule, the client may pay in full but never own what was created.
Fix: Include an explicit IP assignment clause in every schedule covering creative, technical, or strategic work β or cross-reference the assignment clause in the main agreement and confirm it covers work under this schedule.
Why it matters: Milestone dates expressed as '30 days after written notice' or '2 weeks from project kickoff' create chains of ambiguity. If the notice or kickoff is disputed, every downstream date becomes unenforceable.
Fix: Use fixed calendar dates wherever possible. If relative dates are unavoidable, define the triggering event precisely and document the actual trigger date in a countersigned project initiation email or written notice at the time it occurs.
In plain language: Identifies which agreement the schedule is attached to, the schedule number or letter, the parties, and the effective date β linking the schedule unambiguously to the parent contract.
Schedule [NUMBER/LETTER] to the [NAME OF MAIN AGREEMENT] dated [DATE] between [PARTY A FULL LEGAL NAME] ('Client') and [PARTY B FULL LEGAL NAME] ('Service Provider').
Common mistake: Using only a generic title like 'Schedule A' without referencing the parent agreement by name and date. If the schedule is printed or filed separately, there is no way to establish which contract it belongs to.
In plain language: States in one or two sentences what the schedule covers and confirms it is incorporated into and governed by the main agreement.
This Schedule sets out the [DELIVERABLES / FEE STRUCTURE / SPECIFICATIONS] to be provided by Service Provider under the Agreement. In the event of any conflict between this Schedule and the Agreement, the terms of the [Agreement / this Schedule] shall prevail.
Common mistake: Omitting a precedence statement. When a schedule conflicts with the main agreement β for example, a fee schedule that is updated annually β the absence of a precedence clause forces parties to litigate which document controls.
In plain language: Lists any terms used in the schedule that carry a specific meaning, either cross-referencing definitions in the main agreement or introducing schedule-specific definitions.
Unless otherwise defined herein, capitalised terms shall have the meanings given to them in the Agreement. For the purposes of this Schedule, '[TERM]' means [DEFINITION].
Common mistake: Redefining a term in the schedule that is already defined differently in the main agreement. Conflicting definitions create ambiguity that courts resolve unpredictably.
In plain language: Describes in specific, measurable terms exactly what the party is obligated to provide β the core substantive content of most schedules.
Service Provider shall deliver the following: (a) [DELIVERABLE 1] by [DATE]; (b) [DELIVERABLE 2] by [DATE]; (c) [DELIVERABLE 3] by [DATE]. Each deliverable must meet the acceptance criteria set out in clause [X] below.
Common mistake: Using vague deliverable descriptions like 'strategic advice' or 'marketing support.' Vague scope makes it impossible to invoke acceptance criteria, withhold payment legitimately, or claim a breach when output is substandard.
In plain language: Sets out key dates, phases, or milestones with associated deadlines, distinguishing between mandatory dates and target dates.
Phase 1 β Discovery: commencing [START DATE], due [DATE]. Phase 2 β Development: commencing [DATE], due [DATE]. Time is [of the essence / not of the essence] for all milestone dates in this Schedule.
Common mistake: Failing to specify whether time is of the essence for milestone dates. Without this language, a missed deadline is a breach only if it causes material harm β making enforcement much harder.
In plain language: States the consideration for the services or goods described in the schedule β fixed fees, hourly rates, volume tiers, or milestone-linked payments β and the invoicing trigger.
Client shall pay Service Provider: (a) $[AMOUNT] upon execution of this Schedule; (b) $[AMOUNT] upon completion of Phase 1; (c) $[AMOUNT] upon final delivery and acceptance. All invoices are due Net [30] days from issue.
Common mistake: Expressing milestone payments as percentages without an absolute dollar cap. If the project scope expands, percentage-based fees can become disputed because the base value is no longer agreed.
In plain language: Defines the standard a deliverable must meet to be accepted, the review period the client has to approve or reject, and what happens if no response is received within that period.
Client shall review each deliverable within [10] business days of receipt and provide written notice of acceptance or a detailed list of deficiencies. Failure to respond within the review period shall be deemed acceptance.
Common mistake: No deemed-acceptance provision. Without it, a client can delay acceptance indefinitely, blocking the payment trigger without committing a breach.
In plain language: States who owns the work product created under the schedule β the client, the service provider, or jointly β and any licence grants if ownership is retained by the provider.
Upon receipt of full payment, Service Provider assigns to Client all right, title, and interest in the deliverables created under this Schedule. Service Provider retains ownership of all pre-existing tools, methodologies, and background IP, and grants Client a perpetual, royalty-free licence to use them solely as incorporated into the deliverables.
Common mistake: Assuming the default copyright rules will transfer ownership to the client. In most jurisdictions, work created by an independent contractor remains the contractor's property unless assigned in writing.
In plain language: Confirms that confidentiality obligations in the main agreement apply to information exchanged under this schedule, and addresses any schedule-specific data processing or security requirements.
All information disclosed by either party in connection with this Schedule is Confidential Information subject to clause [X] of the Agreement. Service Provider shall process any personal data in accordance with the data processing terms set out in Schedule [X].
Common mistake: Not cross-referencing the data processing schedule when the work involves personal data. Missing this link can put both parties in breach of GDPR or PIPEDA obligations.
In plain language: Confirms both parties have read and agreed to the schedule, with signature lines that tie execution back to the main agreement, including the date of signing.
The parties agree that this Schedule forms part of and is incorporated into the Agreement. Signed for and on behalf of [PARTY A]: ________ Name: [NAME] Title: [TITLE] Date: [DATE]. Signed for and on behalf of [PARTY B]: ________ Name: [NAME] Title: [TITLE] Date: [DATE].
Common mistake: Relying on the signature on the main agreement to bind parties to subsequently added schedules. Courts in several jurisdictions require that material amendments or attachments added after initial execution be separately signed to be enforceable.
In the schedule header, enter the full name of the main agreement, its execution date, and both parties' legal entity names. Assign the schedule a number or letter (Schedule 1, Schedule A) consistent with the numbering system used in the main agreement.
π‘ Check the main agreement's table of contents or definitions section to confirm the naming convention β mixing numbers and letters across schedules in the same contract creates confusion during disputes.
Write one to two sentences identifying what the schedule covers and whether the schedule or the main agreement takes precedence in the event of a conflict. Make this decision consciously β a fee schedule updated annually should typically override the body; boilerplate terms should not.
π‘ If you want the most recently signed schedule to govern, say so explicitly: 'In the event of conflict, the version of this Schedule most recently executed by the parties shall prevail.'
Identify any terms used in the schedule that are not already defined in the main agreement. Add a short definitions section at the top of the schedule body, using the same capitalisation and format as the parent contract.
π‘ Never introduce a defined term in a schedule that contradicts a definition in the main agreement without including an express override clause.
Write out every deliverable, service, asset, or data item covered by the schedule. Use numbered sub-clauses, not prose paragraphs. For each item include: a description, a format or standard it must meet, and the deadline or delivery trigger.
π‘ If a deliverable is iterative β such as software with multiple releases β specify the version numbering system and which version triggers the payment milestone.
Create a milestone table listing each phase or deliverable, the party responsible, the due date (calendar date, not a relative reference like '30 days after kickoff'), and whether time is of the essence.
π‘ Avoid relative date references like 'within 2 weeks of written notice' unless the notice trigger is itself unambiguously defined β chains of relative dates become impossible to enforce.
List every fee, rate, or payment in a numbered table. Link each payment directly to a deliverable or milestone in the schedule using the same numbering. Include the invoicing trigger, payment terms, and any late-payment rate.
π‘ State the currency explicitly if either party operates across borders, and add a single-sentence clause confirming whether fees are inclusive or exclusive of applicable taxes.
For each deliverable, write measurable acceptance criteria β format, content standards, performance benchmarks β and set a defined review period. Include a deemed-acceptance clause so the clock has a clear stop.
π‘ Keep review periods short: 5β10 business days for documents, 10β15 for complex deliverables. Longer periods encourage procrastination and slow your payment cycle.
Add or cross-reference the IP clause and ensure the signature block is completed by authorised signatories for both parties before any work under the schedule begins.
π‘ Send the schedule for signature at the same time as the main agreement where possible. Schedules signed weeks after the main agreement can face 'fresh consideration' challenges in common-law jurisdictions.
A contract schedule is a numbered or lettered attachment to a main agreement that sets out specific details β such as deliverables, fees, timelines, or technical specifications β that are incorporated into the contract by reference. It carries the same legal force as the body of the agreement and is binding on both parties once the contract is executed. Schedules are used to keep the main agreement readable while preserving the enforceability of granular commercial terms.
The terms are functionally equivalent β all three describe a document attached to and incorporated into a main contract. 'Schedule' is the dominant term in UK and Commonwealth drafting; 'Exhibit' is more common in US practice; 'Annex' is used frequently in international and government contracts. The label matters less than the incorporation language β the contract body must expressly state that the attachment forms part of the agreement.
In most jurisdictions, a schedule executed at the same time as the main agreement does not require a separate signature β the overall execution block typically covers it. However, schedules added after initial execution, or material amendments to existing schedules, should be separately signed by authorised representatives of both parties to avoid fresh-consideration challenges in common-law jurisdictions such as the US, Canada, the UK, and Australia.
A schedule of deliverables should include: a precise description of each deliverable, the format or standard it must meet, the party responsible, the due date as a fixed calendar date, the acceptance criteria and review period, the payment milestone it triggers, and the IP ownership position on completion. Vague descriptions like 'consulting services' or 'design work' are the single most common cause of schedule disputes.
Yes, if the contract contains a precedence clause that expressly grants the schedule priority. Without such a clause, courts typically read the main agreement as controlling, but outcomes vary by jurisdiction and the specific facts. The safest approach is to include a clear precedence statement at the top of each schedule β stating either that the main agreement governs, or that the schedule governs on the specific matters it addresses β and to resolve any conflicts before signing.
A deemed-acceptance clause states that if the client does not provide written rejection or a list of deficiencies within a defined review period, the deliverable is treated as accepted. Without it, a client can delay acceptance indefinitely without technically breaching the contract, which blocks milestone-linked payments and extends the engagement with no legal remedy for the service provider. Most commercial contracts set a deemed-acceptance period of 5β15 business days.
Ownership depends entirely on the contract language. In most jurisdictions, work created by an independent contractor remains the contractor's property by default β the client receives no ownership without an explicit written assignment. For employees, employer ownership is typically the default under employment law, but varies by country. Every schedule covering creative, technical, or strategic work should include an express IP assignment clause or cross-reference one in the main agreement.
Updates to an executed schedule should be made by a written change order or amendment signed by authorised representatives of both parties. The change order should identify the schedule being amended by name and number, state the specific changes, confirm all other terms of the schedule remain unchanged, and be dated and signed before any changed work begins. Verbal agreements to modify a schedule are generally unenforceable and should be avoided.
Yes. If a schedule involves processing personal data on behalf of another party β for example, a software development schedule where the contractor accesses a client's user data β GDPR requires a written data processing agreement between the controller and the processor. This is typically addressed as a separate data processing schedule or annex to the main agreement. Failing to include it exposes both parties to regulatory liability under the GDPR and equivalent legislation in the UK and Canada.
A Statement of Work is a specific type of schedule focused entirely on defining the scope, deliverables, timeline, and acceptance criteria for a service engagement. A schedule is a broader concept β it can cover fees, IP, data processing, assets, or any other detailed terms. All statements of work are schedules, but not all schedules are statements of work.
A contract amendment modifies terms already in the body of an existing agreement β changing a price, extending a term, or replacing a clause. A schedule is an original attachment that adds detail to rather than changes the main agreement. When you need to update a schedule after execution, you use a change order or amendment to the schedule, not an amendment to the main contract body.
An addendum adds new terms to a contract that were not included at the time of original execution β typically signed after the main agreement. A schedule is contemplated and attached at the time of signing. In practice, the distinction is procedural: both must be signed by authorised parties and both are fully binding once incorporated, but addenda typically require fresh consideration in common-law jurisdictions.
A Master Service Agreement sets standard commercial and legal terms β liability caps, warranties, governing law, payment terms β that apply to every engagement between the parties. Individual schedules or statements of work attached to the MSA contain the engagement-specific details. The MSA is the framework; the schedule is the deal. You need both, and the MSA's precedence clause governs when they conflict.
Software development schedules specify feature sets, sprint milestones, API specifications, acceptance testing criteria, and SLA commitments β all of which require precise measurable standards to trigger payment and limit liability.
Consulting and advisory firms use fee schedules and scope-of-work schedules to define billable deliverables, hourly or fixed-fee structures, and expense reimbursement terms separately from their master service agreement boilerplate.
Construction contracts attach schedules covering bill-of-quantities, payment milestones tied to project phases, retention amounts, and defects liability periods β each requiring precise dates and amounts to be enforceable.
Supply agreements use schedules to document product specifications, delivery quantities and lead times, pricing tiers with volume thresholds, and quality inspection standards β details too variable to embed in the master supply agreement.
In US contract practice, the equivalent of a schedule is commonly called an Exhibit or Attachment. The Uniform Commercial Code governs schedules in goods transactions and imposes implied warranties that the schedule cannot easily disclaim. Schedules added after initial execution require fresh consideration or written modification clauses under UCC Article 2 and common-law contract principles. Some states β including California and New York β have strong parol evidence rules that can exclude schedule terms if the main agreement includes a merger clause and the schedule was not attached at signing.
Canadian contract law follows common-law principles in all provinces except Quebec, where the Civil Code of Quebec governs. Schedules must be incorporated by reference in the main agreement to be binding; courts will not imply incorporation. In Quebec, contracts must comply with French-language requirements under the Charter of the French Language where the agreement involves a Quebec-based employer or consumer. PIPEDA and provincial privacy statutes require data processing schedules when personal data is shared under a commercial agreement.
UK commercial contracts frequently use schedules as the primary home for substantive commercial detail, with the main agreement containing only boilerplate terms. The Unfair Contract Terms Act 1977 and the Consumer Rights Act 2015 subject schedule terms in B2C contracts to a reasonableness or fairness test. Schedules must be clearly identified in the main agreement and made available to both parties before signing to be incorporated β hidden or unsigned schedules are routinely found unenforceable. GDPR as retained in UK law requires a written data processing schedule where applicable.
EU commercial law varies by member state, but schedules are universally recognised as binding when expressly incorporated into the main contract. GDPR Article 28 mandates a written data processing agreement β typically implemented as a schedule β whenever a processor handles personal data on behalf of a controller, with mandatory clauses specified by the Regulation. In France, Germany, and Spain, standard form schedules in B2B contracts may be challenged under local unfair contract terms legislation if the party imposing them holds significantly greater bargaining power. Cross-border EU contracts should specify governing law and jurisdiction explicitly in both the main agreement and any schedule.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Standard service or consulting engagements where the main agreement is already in place and the schedule covers routine deliverables or fees | Free | 30β60 minutes per schedule |
| Template + legal review | Schedules covering complex IP assignment, data processing obligations, or high-value milestone payments above $50,000 | $300β$800 for a solicitor or contract lawyer review | 1β3 days |
| Custom drafted | Multi-party construction projects, regulated-industry supply agreements, or schedules that form the core commercial instrument for a transaction above $500,000 | $1,500β$5,000+ | 1β3 weeks |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Start freeΒ Β·Β No credit card required
