The one-page SLA updates live as you type — free to preview. Enter your email to copy or download it.
Enter your email to unlock your finished SLA — copy the formatted text to your clipboard or download it as a file (opens in any browser, prints to PDF). We'll also send you consulting launch tips — no spam, unsubscribe anytime.
Preview is always free · Email unlocks copy & download
The single biggest credibility test in an SLA. A 1-hour critical response time looks impressive in a proposal and becomes a liability the first week you're sick or in back-to-back client meetings. This generator defaults to 4 hours for critical issues and 24 hours for standard requests — numbers a solo or small-firm consultant can sustain on a bad week, not just a good one.
Resolution time is harder to control than response time — some requests are genuinely complex. The generator's output frames the resolution target as a commitment the parties track and report on (Section 9), with room for a documented extension on complex requests, rather than an absolute promise that turns every hard problem into a breach.
Most consulting SLAs don't need an uptime number at all — uptime applies to hosted systems, not advisory work. This generator makes it opt-in: include it only when a deliverable is a tool, dashboard, or system the client actually depends on being available, with a target (99%, 99.5%, 99.9%) that matches what you can realistically run.
"I'll get back to you quickly" means something different to every client. Naming the actual hours, time zone, and approved channels — and stating that the response clock starts at the next support-hours window for after-hours requests — removes the single most common source of SLA disputes: a client who expected weekend coverage nobody promised.
When something is actually stuck, "email me again" isn't an escalation path. Two tiers — a lead contact and a principal or practice-owner contact, with a stated threshold for moving from one to the other — gives the client a real lever without opening you up to being escalated-to for every minor delay.
A credit for a missed critical response (5-15% of that month's fee) makes the SLA mean something. A credit capped at a modest share of the month's fee (20-25%), stated as the client's sole remedy for a missed service level, is what keeps a reasonable performance promise from turning into unbounded liability over a bad week.
Scheduled maintenance, force majeure, client-caused delay, and third-party outages — four standard carve-outs that keep the SLA measuring what the consultant actually controls. Without them, a client's own slow approval or a vendor's outage can read as the consultant's missed commitment.
When to use it: Skip the SLA. The statement of work's own timeline and milestones already define performance — a separate SLA adds overhead without adding clarity.
When to use it: Add response times, a resolution target, support hours, and an escalation path. This is the most common SLA use case for a consultant — the client is paying for availability, and this is what makes availability specific.
When to use it: Add the uptime commitment on top of the above. Only turn this on when the client genuinely depends on something staying up — not for a deliverable that's just a document or a plan.
When to use it: Consider leaving service credits out, or setting them low. A long-standing relationship built on trust may not need a financial remedy clause — a reporting cadence alone keeps both sides honest.
When to use it: Include service credits with a clear cap. This is exactly the situation an SLA with teeth is built for — it gives a nervous client a concrete reason to trust the commitment instead of just your word.
A 1-hour or 2-hour response time wins the deal and then gets missed the first week you're sick, traveling, or deep in another client's work. Missing a stated SLA repeatedly is worse for trust than never promising speed at all — because now the client has a documented pattern of broken commitments, not just an impression of slowness. Write the number you can hit on a bad week, not your best one.
Uptime measures a system staying online — it has no meaning applied to advisory work, a report, or a one-time deliverable. Including it anyway (because "it sounds professional") creates a metric nobody can actually track and a term that reads as copy-pasted from a SaaS contract rather than written for the engagement.
Without named tiers and a threshold, a client's only move when something is stuck is to email more urgently or escalate socially (a frustrated call, a Slack message to someone else at your firm). A stated two-tier path with a clear threshold routes that energy into the process instead of around it.
An uncapped credit clause turns a single bad week into a meaningful hit to the engagement's economics, and turns every missed response into a negotiation about money instead of a performance conversation. A modest percentage per miss, capped per month, keeps the remedy proportionate — and this generator builds the cap in by default.
Response time is something you control; resolution time depends partly on the complexity of what's broken and how fast the client can get you what you need. An SLA that promises resolution as an absolute, with no room for a documented extension on a genuinely hard problem, sets up a dispute the first time reality doesn't cooperate.
Without carve-outs for scheduled maintenance, force majeure, client-caused delay, and third-party outages, a consultant can be on the hook for a missed service level that had nothing to do with their own performance — a client who sat on an approval for a week, or a vendor outage nobody controls. These four exclusions cost almost nothing to include and protect against the most common unfair-miss scenarios.
An SLA defines how well you perform during the engagement — the tools below cover the rest: win the client, price the work, scope it, sign it, bill it, protect it, and end it cleanly.
The ongoing engagement this SLA usually attaches to — retainer type, scope, fees, and renewal, ready in minutes.
The commercial framework above the SLA — master terms, the SOW mechanism, billing rails, IP ownership, a liability cap, and termination.
The single-engagement foundation — contractor status, enumerated services, payment terms with a deposit, IP assignment, and termination.
Delivering this SLA with help? Bring the subcontractor in properly — a defined workstream, flow-down of your client terms, fees, IP assignment to you, and a client non-solicit on one page.
Confidentiality alongside performance — mutual or one-way, with a survival period and standard exclusions.
What happens after the engagement ends — a narrowly scoped restricted market, restrictions, and a restriction period.
When it's time to end the engagement this SLA covers — notice, work in progress, final invoice, and surviving terms.
Win the next engagement before you need an SLA for it — client context, scope, pricing, and signature blocks on one page.
The full one-page consulting agreement — scope, payment, IP, confidentiality, and termination.
Make sure the fee behind this SLA's service credits is priced right — a defensible rate range by industry, experience, and service type.
Niche quiz, rate calculator, proposal, quote, contract, SOW, MSA, change order, contractor agreement, termination letter, non-compete, invoice, and more — every tool on the site, all free.
An SLA proves you'll perform — sharp positioning gets you the retainer to perform on. The Consulting Launch Kit gives you a one-line positioning statement, 3 productized offers with pricing, a rewritten bio, a cold-outreach email sequence, a proposal template, and a 30-day plan to land your first 3 clients — personalized to your niche, delivered instantly. Just $29.
Get the launch kit — $29 →One-time · No subscription · 7-day money-back guarantee