Professional services agreements set the ground rules for work before it begins. In Wisconsin, small wording choices can shift significant risk—who pays for scope creep, who owns the work product, who takes on third-party claims, and how disputes are handled. This checklist is designed for Wisconsin businesses, consultants, agencies, and in-house teams who are reviewing or negotiating a professional services agreement (PSA) before signing.
Use the points below to spot red flags, clarify expectations, and identify practical negotiation levers that reduce surprises once a project is underway. If a draft raises concerns, address them now—after kickoff, leverage and options narrow quickly. For related guidance, see Master Service Agreements in Wisconsin: Key Clauses and Legal Support for Your Deals.
Quick Wisconsin Checklist: What to Confirm Before You Sign
- Scope definition: Are deliverables, milestones, and acceptance criteria specific and measurable? Is out-of-scope work clearly excluded?
- Change management: Is there a written change order process with timelines, required approvals, and pricing rules?
- Indemnity allocation: Does each party cover the risks it controls (e.g., IP infringement, bodily injury, property damage, data claims)? Are caps, carve-outs, and procedures clearly stated?
- IP ownership and licenses: Who owns final deliverables? What rights does each party have to pre-existing tools, templates, and know-how?
- Payment and acceptance: Are payments tied to objective milestones and acceptance? Are invoices, dispute windows, and late-payment terms clear?
- Confidentiality and data: Is confidential information defined and protected appropriately? For data, who is responsible for security and incident response?
- Insurance: Are required coverages and endorsements stated with limits that match the risks?
- Term, termination, and transition: What are the termination rights, notice periods, and offboarding obligations?
- Dispute resolution: Are escalation steps, venue, governing law (Wisconsin), and relief options clear?
- Operational fit: Do timelines, approvals, and communication obligations reflect how your team actually works?
Scope of Services and Change Management: Avoiding Scope Creep
Define Exactly What Is Being Delivered
Scope creep is one of the most common sources of cost overruns and disputes. The PSA should include a statement of work (SOW) or exhibit that lists deliverables with enough detail that both sides can tell what is in, what is out, and when work is complete. For related guidance, see Minnesota Professional Services Agreements: Scope, Deliverables, and Payment Terms Counsel.
- Deliverables and format: Describe outputs (e.g., “brand guidelines, 30 pages, PDF and native files”).
- Milestones and dates: Set realistic dates; specify dependency on client inputs.
- Acceptance criteria: Use objective criteria (e.g., “meets spec X, passes test Y”).
- Assumptions: Call out assumptions used to price the work (e.g., “data provided cleaned to field-level spec”).
- Exclusions: List what is not included (e.g., “ongoing maintenance excluded unless separately scoped”).
Build a Practical Change Order Process
Projects evolve. A written change process keeps changes visible and fairly priced.
- Written request and impact analysis: Require a short written change request with schedule and price impact before work proceeds.
- Approvals: Identify who can approve changes on each side and how (email signatures are often sufficient if stated).
- Pricing rules: For fixed-fee work, specify hourly rates or unit pricing for out-of-scope tasks. For time-and-materials, clarify rate sheets and any not-to-exceed amounts.
- Timeline adjustments: Changes that add work should extend deadlines accordingly.
Red Flags
- Vague scope: Phrases like “as needed” or “industry-standard deliverable” without detail invite disputes.
- Unilateral change rights: If one party can change scope without written agreement, expect friction.
- Implied free rework: Open-ended “satisfaction” standards without limits function like unlimited revisions.
Indemnity and Risk Allocation: Who Carries What Risk
Match Indemnities to Control
Indemnity provisions shift the cost of certain claims (like third-party lawsuits) to the party best positioned to prevent them. In many Wisconsin PSAs, a balanced approach includes:
- IP infringement indemnity: The party providing deliverables typically covers third-party IP infringement claims arising from those deliverables, with carve-outs if the client supplies the materials or mandates the design.
- Bodily injury/property damage: Each party covers claims caused by its personnel's negligence or willful misconduct.
- Data-related claims: If services involve personal or confidential data, allocate responsibility for security measures, incident response, and related claims based on who controls the systems and data flows.
Define Procedures, Caps, and Exclusions
- Tender and control: Require prompt notice of a claim and allow the indemnifying party to control the defense with a duty to keep the other informed.
- Settlements: No settlements that admit fault or impose obligations on the other party without written consent.
- Liability caps: Many PSAs include an overall cap on direct damages (e.g., a multiple of fees). Consider whether indemnity obligations are within the cap or carved out—this is a major negotiation lever.
- Exclusions: Carve-outs for confidentiality breaches, data events, IP infringement, or willful misconduct are common points to address expressly.
- Duty to mitigate: State that both sides must take reasonable steps to limit losses.
Red Flags
- One-way indemnity only: If one side bears all risks regardless of control, rebalance.
- No defense obligation: If indemnity excludes defense costs, the protection may be hollow.
- Unlimited liability in practice: A nominal cap with broad carve-outs can function as no cap at all.
Intellectual Property and Work Product: Ownership, Licenses, and Background IP
Clarify Ownership of Deliverables
Wisconsin PSAs vary on ownership. Options include client ownership on payment, service provider retention with a license, or a hybrid approach. Align the structure with how deliverables will be used.
- Client ownership: State that final deliverables are assigned to the client upon acceptance and payment. Include cooperation obligations to sign further documents if needed.
- Provider ownership with license: If the provider needs to reuse methods or templates, grant the client a license that is clear on scope (e.g., internal use, transferable to affiliates, perpetual, worldwide).
- Hybrid: Client owns the specific work product; provider retains ownership of embedded background tools with a license back to use as necessary.
Address Background IP and Pre-Existing Materials
- Background IP definition: Identify tools, frameworks, code libraries, training materials, or design systems developed outside the engagement.
- License terms: Grant the necessary rights to use background IP included in deliverables. Avoid accidental ownership transfers that block future reuse.
- Third-party components: If open-source or third-party content is included, disclose license terms and responsibilities for compliance.
Work Made for Hire vs. Assignment
“Work made for hire” language may not apply to many service deliverables unless they fit narrow categories. A written assignment is often used to transfer ownership of the final deliverables. Many parties use both concepts for belt-and-suspenders coverage, along with a present assignment clause and a promise to sign further documents if needed.
Red Flags
- Silent on background IP: If not addressed, ownership disputes can block go-live or handoff.
- License gaps: If you rely on vendor tools, ensure the license gives you the rights you actually need.
- Conditional ownership without clarity: If ownership transfers only on “final acceptance” but acceptance is vague, payment and rights can stall.
Have questions about your draft PSA or IP language? Use our contact form to speak with our firm about representation, or call 414-253-8500 to schedule a consultation and talk through next steps under Wisconsin law.
Payment, Milestones, and Acceptance: Linking Deliverables to Cash Flow
Structure Payments to Milestones
Payments tied to clear milestones keep work and cash aligned.
- Milestone billing: Each payment corresponds to a defined deliverable or phase with acceptance criteria.
- Time-and-materials (T&M): For T&M, include rate sheets, overtime rules, and a not-to-exceed amount if predictability matters.
- Retainers or deposits: If applicable, describe when applied and how replenishment works.
Acceptance and Cure
- Review window: Provide a set number of days for the client to accept or reject deliverables with specific reasons tied to the spec.
- Deemed acceptance: If no response within the review window, acceptance occurs automatically—balance this with a reasonable time period.
- Cure process: If rejected for nonconformance, the provider has a set time to correct and resubmit.
Invoicing Mechanics and Disputes
- Invoice detail: Require enough detail to evaluate charges (dates, hours, tasks, expenses).
- Dispute window: Set a timeline for written billing disputes; undisputed amounts should be paid on time.
- Suspension rights: State whether services can be suspended for nonpayment after notice.
Red Flags
- Front-loaded fees without deliverables: Consider balancing risk by tying early payments to tangible outputs.
- No acceptance process: Without acceptance mechanics, disagreements can drag on and delay payment.
- Open-ended expenses: Add caps or pre-approval requirements for travel or third-party costs.
Confidentiality, Data, and Insurance: Operational Protections
Confidentiality Basics
- Definition: Cover nonpublic business, technical, financial, and personal data disclosed in any form.
- Use and disclosure limits: Restrict use to performing under the PSA; allow disclosure to personnel with a need to know who are bound by confidentiality obligations.
- Return or destruction: On termination or request, return or destroy confidential information, subject to standard archival copies.
- Survival: Confidentiality should survive termination for a reasonable period.
Data Handling and Security
If services involve personal information or sensitive business data, include data-specific provisions:
- Security measures: Reference a written information security program or baseline controls (encryption, access controls, logging).
- Incident response: Define prompt notice timelines and cooperation duties in the event of a security incident.
- Subprocessors or subcontractors: Require equivalent obligations and prior approval if appropriate.
- Data location and transfers: State where data resides and limitations on cross-border transfers if relevant.
Insurance and Endorsements
- Core coverages: Commercial general liability, professional liability/errors and omissions, workers' compensation, and if applicable, cyber liability.
- Limits: Match limits to the exposure created by the scope, data sensitivity, and project value.
- Endorsements: Additional insured status for ongoing operations, waiver of subrogation where appropriate, primary and noncontributory wording, and evidence via certificates upon request.
Red Flags
- Weak confidentiality carve-outs: Exceptions should be narrow (e.g., already known, independently developed, public through no fault).
- No cyber coverage where needed: If data handling is central to the services, consider specific cyber liability requirements.
- Unclear subcontractor use: If subcontractors will handle sensitive work, tie them to the same obligations.
Disputes, Termination, and Wisconsin Law: Practical Considerations
Term and Termination
- Convenience termination: Allows one or both parties to end the agreement with notice. Consider reasonable wind-down, transition assistance, and payment for work performed to date.
- Termination for cause: Breach, insolvency, or repeated failure to perform, typically with a cure period before termination is effective.
- Effect of termination: Spell out final payments, delivery of in-progress work product, licenses needed to continue internal operations, and return of confidential information.
Dispute Resolution
- Escalation steps: Internal executive meeting within a set timeframe before litigation can help resolve issues early.
- Mediation or arbitration: If used, define the forum, rules, and whether interim court relief is allowed.
- Venue and governing law: Specify Wisconsin law and venue in a Wisconsin court to avoid uncertainty.
- Injunctive relief: Carve-out for urgent relief to protect IP or confidentiality.
Remedies and Limitations
- Types of damages: Consider excluding consequential damages, while addressing carve-outs for breaches that justify broader remedies.
- Limitation periods: If the PSA shortens the time to bring claims, ensure the period is reasonable and consistent with business risk.
Operational Fit and Governance
- Project governance: Identify project leads, meeting cadence, and reporting requirements.
- Approvals: Clarify who can approve changes, accept deliverables, and sign off on invoices.
- Records and audits: For T&M work, allow reasonable audit rights to verify hours and expenses.
Negotiation Levers and Practical Tradeoffs
When both sides have legitimate concerns, focus on practical levers that share risk fairly:
- Scope vs. price: Tighten scope language instead of pushing for broad warranties that are hard to meet.
- Indemnity vs. cap: If expanding indemnity, consider a higher liability cap or a specific sub-cap for IP claims.
- Ownership vs. license: If the provider needs to reuse methods, give the client ownership of the specific deliverables and a license back for embedded tools.
- Schedule vs. acceptance: Allow reasonable acceptance windows in exchange for firm milestone dates.
- Data risk vs. insurance: Balance security commitments with cyber coverage and incident cooperation terms.
Common Wisconsin-Specific Touchpoints
Many PSAs governed by Wisconsin law address the following in a straightforward way, avoiding ambiguity:
- Attorney's fees clauses: Decide whether the prevailing party can recover fees in a dispute; keep the clause balanced to deter marginal claims.
- Independent contractor status: Confirm that personnel remain independent contractors and that each party handles its own taxes and benefits.
- Non-solicitation and non-hire: If included, make terms reasonable in duration and scope to support enforceability under Wisconsin principles.
- Survival clauses: Identify which obligations continue after termination (confidentiality, IP, payment, indemnity, dispute resolution).
Short Examples: How Clauses Work Day-to-Day
Scope Example
A PSA states two design rounds are included, with additional rounds billable at listed hourly rates via change order. This prevents unlimited rework and sets a predictable path if preferences change.
Indemnity Example
The provider indemnifies the client for third-party IP claims based on the delivered software, but not if the client modifies the code or combines it with unapproved components. This aligns responsibility with control.
IP Example
The client owns final training materials, while the provider retains its underlying templates and methods. The client receives a perpetual, internal-use license to the templates to ensure ongoing utility.
Data Example
Incident notice within 72 hours, joint investigation, and allocation of notification costs based on the system at fault. Cyber coverage supports these commitments.
Frequently Asked Questions
Should a professional services agreement in Wisconsin use work-made-for-hire language, an assignment, or both?
Many services deliverables do not fall neatly into work-made-for-hire categories. Using both concepts can reduce uncertainty: include a present assignment of the final deliverables upon acceptance and payment, plus a promise to execute further documents if needed. Also define background IP and grant the licenses each side needs to operate.
How can a mutual indemnity be balanced if the parties have different risk profiles?
Match obligations to control and add financial boundaries. For example, each party indemnifies for its own negligence and IP it supplies, while overall liability is capped with carefully chosen carve-outs. If one side bears more risk, consider a higher cap specific to that risk, additional insurance, or narrower indemnity triggers.
What does a practical change order process look like for fixed-fee projects?
Use a one-page form that states the requested change, reason, schedule impact, and price (e.g., hourly rates or a new fixed fee). Require email approval by named contacts before work starts. Adjust milestone dates proportionally and reference the main PSA so the change order becomes part of the contract.
When should a license to use pre-existing tools or templates be perpetual versus time-limited?
If the client needs ongoing use of deliverables that include provider tools (like design systems or code libraries), a nonexclusive, perpetual, internal-use license often makes sense. Time-limited licenses may be appropriate for pilots, subscription-tied materials, or situations where the provider's competitive position could be harmed by broad, permanent rights.
What insurance endorsements are commonly requested for services engagements?
Additional insured status on commercial general liability, primary and noncontributory wording, and waiver of subrogation are common. For technology or data-heavy work, cyber liability with incident response coverage may be requested, along with proof of professional liability/errors and omissions coverage.
Next Steps
If you are reviewing a Wisconsin professional services agreement and want to reduce risk before signing, our firm can help evaluate scope, indemnity, IP ownership, and the practical mechanics that keep projects on track. Use our contact form or call 414-253-8500 to schedule a consultation and discuss representation.
Disclaimer: This article provides general information about Wisconsin professional services agreements and is not legal advice. Reading it does not create an attorney-client relationship. Laws and contract terms vary by situation. Consult an attorney about your specific agreement.
Related articles
Attorney advertising. This page is for general informational purposes only and is not legal advice. Reading this page or contacting the firm does not create an attorney-client relationship.