{"id":12331,"date":"2026-04-05T09:57:33","date_gmt":"2026-04-05T02:57:33","guid":{"rendered":"https:\/\/upbase.io\/blog\/professional-service-agreement\/"},"modified":"2026-04-05T22:33:40","modified_gmt":"2026-04-05T15:33:40","slug":"professional-service-agreement","status":"publish","type":"post","link":"https:\/\/upbase.io\/blog\/professional-service-agreement\/","title":{"rendered":"How to write a professional service agreement that actually protects your agency"},"content":{"rendered":"\n

A professional service agreement (PSA) defines the rules of engagement between your agency and every client you take on. <\/p>\n\n\n\n

Get it right, and you have a document that prevents scope creep, guarantees payment, and gives you legal ground to stand on when things go sideways.<\/p>\n\n\n\n

Most agencies use a generic contract they found online, swap in their company name, and hope for the best. <\/p>\n\n\n\n

That’s how you end up doing 40% more work than you quoted, chasing invoices for 90 days, and losing ownership of frameworks you built years before the client showed up.<\/p>\n\n\n\n

If you run an agency or lead a small services team, this guide breaks down exactly what belongs in your PSA, clause by clause, with example language you can use today<\/strong>.<\/p>\n\n\n\n\n\n<\/marker>\n<\/defs>\n\nWhat happens when your PSA is weak (or missing)<\/text>\n\n\n\nScope creep<\/text>\n40% more work, same fee<\/text>\n<\/g>\n\n\n\nLate payments<\/text>\n90-day invoice chasing<\/text>\n<\/g>\n\n\n\nIP disputes<\/text>\nClient claims your tools<\/text>\n<\/g>\n\n\n\n\n\n\n\nA strong PSA prevents all three. Here’s how to build one.<\/text>\n<\/g>\n<\/svg>\n\n\n\n

What is a professional service agreement?<\/h2>\n\n\n\n

A professional service agreement is a legally binding contract between a service provider and a client. <\/p>\n\n\n\n

It spells out what work gets done, how much it costs, who owns the output, and what happens if either side wants out.<\/p>\n\n\n\n

For agencies, the PSA is the single most important document in every client relationship. <\/p>\n\n\n\n

It’s not a formality. <\/p>\n\n\n\n

It’s the thing you point to when a client says “I thought that was included” or “we assumed you’d handle that too.”<\/p>\n\n\n\n

A strong PSA covers seven areas: scope of work, change orders, payment terms, intellectual property, confidentiality, termination, and liability. Skip any one of these, and you’re exposed.<\/p>\n\n\n\n

A PSA is not the same thing as a proposal.<\/strong> Your proposal sells the work. Your PSA governs it. They’re separate documents with separate jobs.<\/p>\n\n\n\n

PSA vs. MSA vs. SOW: which one do you actually need?<\/h2>\n\n\n\n

Agencies throw around “MSA,” “SOW,” and “PSA” like they’re interchangeable. They’re not. Using the wrong one costs you flexibility or leaves gaps in your legal coverage.<\/p>\n\n\n\n

<\/th>Professional service agreement (PSA)<\/th>Master service agreement (MSA)<\/th>Statement of work (SOW)<\/th><\/tr><\/thead>
What it does<\/strong><\/td>Governs a single project or engagement<\/td>Sets overarching terms for an ongoing relationship<\/td>Defines specific deliverables, timelines, and fees for one project<\/td><\/tr>
When to use it<\/strong><\/td>One-off projects or first-time clients<\/td>Long-term clients with multiple projects<\/td>Under an MSA, to scope each new project<\/td><\/tr>
Scope<\/strong><\/td>Self-contained: covers legal terms + project details<\/td>Legal terms only, no project specifics<\/td>Project specifics only, no legal terms<\/td><\/tr>
Best for agencies that<\/strong><\/td>Take on project-based work with defined start\/end dates<\/td>Have retainer clients or recurring engagements<\/td>Already have an MSA and need to add new projects fast<\/td><\/tr>
Renegotiation<\/strong><\/td>New agreement per project<\/td>Rarely renegotiated; new SOWs added underneath<\/td>New SOW per project, same MSA<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The practical answer for most agencies:<\/strong> Start every new client with a PSA. If the relationship grows into ongoing work, upgrade to an MSA + SOW structure so you don’t renegotiate legal terms every time you kick off a new project.<\/p>\n\n\n\n

If you’re a 5-person agency doing project work for SMBs, a well-built PSA handles 90% of your contracts. <\/p>\n\n\n\n

You don’t need an MSA until you’re juggling multiple concurrent projects for the same client.<\/p>\n\n\n\n

A common mistake:<\/strong> some agencies try to use a proposal as their PSA. Proposals are sales documents. <\/p>\n\n\n\n

They describe what you plan to do and what it costs. But they rarely include IP clauses, liability caps, termination rights, or dispute resolution. <\/p>\n\n\n\n

If your “contract” is just a signed proposal, you’re legally exposed.<\/p>\n\n\n\n

Keep them separate. Send the proposal first. Once the client says yes, send the PSA for signature.<\/p>\n\n\n\n

The 7-clause agency PSA stack<\/h2>\n\n\n\n

Most PSA templates online were written for enterprise procurement departments or law firms. <\/p>\n\n\n\n

They’re 20 pages of boilerplate that doesn’t address the things that actually burn agencies: scope creep, disappearing clients, and IP disputes over work you built on your own dime.<\/p>\n\n\n\n\n\n<\/marker>\n<\/defs>\n\nThe 7-clause agency PSA stack<\/text>\nEach clause solves a specific agency problem<\/text>\n\n\n\n1. Scope of work<\/text>\nPrevents scope creep<\/text>\n<\/g>\n\n\n\n2. Change orders<\/text>\nMakes extras routine<\/text>\n<\/g>\n\n\n\n\n\n3. Payment terms<\/text>\nProtects cash flow<\/text>\n<\/g>\n\n\n\n4. Intellectual property<\/text>\nKeeps your frameworks<\/text>\n<\/g>\n\n\n\n\n\n\n5. Confidentiality<\/text>\nProtects both sides<\/text>\n<\/g>\n\n\n\n6. Termination<\/text>\nClean exit for both sides<\/text>\n<\/g>\n\n\n\n\n\n\n7. Liability and indemnification<\/text>\nCaps your risk exposure<\/text>\n<\/g>\n\n\n\n\n\nYour agency is protected<\/text>\nScope defined \u00b7 Payments secured \u00b7 IP retained \u00b7 Exit planned<\/text>\n\n\n<\/svg>\n\n\n\n

The 7-clause agency PSA stack<\/strong> strips a professional service agreement down to the seven sections that matter most for agency-client relationships. Every clause exists to solve a specific problem agencies face. <\/p>\n\n\n\n

Clause 1: Scope of work<\/h3>\n\n\n\n

This is where most agency contracts fail. Not because the scope section is missing, but because it’s too vague.<\/p>\n\n\n\n

“Provide digital marketing services” is not a scope of work. Neither is “website redesign” or “brand strategy engagement.” These descriptions are invitations for the client to interpret the scope however they want.<\/p>\n\n\n\n

Your scope clause needs four things:<\/p>\n\n\n\n

What you will deliver.<\/strong> List every deliverable by name, format, and quantity. Not “social media content” but “12 Instagram static posts per month, delivered as Canva files.”<\/p>\n\n\n\n

What you will not deliver.<\/strong> Exclusions are as important as inclusions. If your website project doesn’t include copywriting, say so. If your SEO retainer doesn’t cover paid ads, write it down.<\/p>\n\n\n\n

How many revision rounds are included.<\/strong> Two rounds per deliverable is standard. Anything beyond that gets billed hourly. State the rate.<\/p>\n\n\n\n

Client responsibilities.<\/strong> What does the client need to provide, and by when? Brand guidelines, login credentials, content approvals, feedback on drafts. <\/p>\n\n\n\n

If the client doesn’t hold up their end, you need language that extends your timeline automatically.<\/p>\n\n\n\n

Here’s example scope language for a web design project:<\/p>\n\n\n\n

“Provider will design and develop a 10-page responsive website using WordPress. Deliverables include homepage design, 9 interior page templates, mobile optimization, and a 30-minute training session on the CMS. Two rounds of design revisions are included per page. Copywriting, stock photography, and ongoing maintenance are excluded from this engagement.”<\/em><\/p>\n\n\n\n\nEvery scope clause needs these four elements<\/text>\n\n\n\n\u2713 What you will deliver<\/text>\nName, format, and quantity<\/text>\n<\/g>\n\n\n\n\u2713 What you will not deliver<\/text>\nExclusions prevent assumptions<\/text>\n<\/g>\n\n\n\n\u2713 Revision rounds included<\/text>\n2 rounds standard, hourly after<\/text>\n<\/g>\n\n\n\n\u2713 Client responsibilities<\/text>\nMaterials, feedback, deadlines<\/text>\n<\/g>\n\n\nIf a neutral third party read your scope clause,<\/text>\nwould they know exactly what’s included and what’s not?<\/text>\n<\/svg>\n\n\n\n

Clause 2: Change order process<\/h3>\n\n\n\n

Scope creep is not a client problem. It’s a contract problem.<\/p>\n\n\n\n

If your PSA doesn’t have a change order clause, you have no mechanism to say “that’s extra” without it feeling adversarial. The change order process makes scope changes routine, not confrontational.<\/p>\n\n\n\n

Your change order clause should specify that any request outside the defined scope requires a written change order before work begins. The change order should include the additional scope description, revised timeline, and additional cost. <\/p>\n\n\n\n

No verbal approvals. <\/p>\n\n\n\n

No “we’ll figure it out later.”<\/p>\n\n\n\n

The line that saves agencies money:<\/strong> “No work on any change request will begin until both Parties have signed the Change Order.”<\/em><\/p>\n\n\n\n

That single sentence turns every out-of-scope request into a business conversation instead of a surprise invoice.<\/p>\n\n\n\n

Here’s what this looks like in practice. A design agency is building a 10-page website. <\/p>\n\n\n\n

Three weeks in, the client asks to add an e-commerce section with 50 product pages. <\/p>\n\n\n\n

Without a change order clause, the agency either does the work for free (killing margin) or says “that’s extra” and the client feels blindsided.<\/p>\n\n\n\n

With a change order clause, the conversation is simple: “We’d love to add e-commerce. Per our agreement, I’ll send over a change order with the additional scope, timeline, and cost. <\/p>\n\n\n\n

Once you sign it, we’ll get started.”<\/p>\n\n\n\n\n\n<\/marker>\n<\/mask><\/defs>\n\nHow the change order process works<\/text>\n\n\n\nClient asks<\/text>\n“Can we also…”<\/text>\n<\/g>\n\n\n\n\n\nYou check scope<\/text>\nIn or out?<\/text>\n<\/g>\n\n\n\n\n\nSend change order<\/text>\nScope + cost + time<\/text>\n<\/g>\n\n\n\n\n\nBoth sign<\/text>\nThen work begins<\/text>\n<\/g>\n\n\nWithout this process<\/text>\nAgency does free work \u2192 margin dies \u2192 resentment builds<\/text>\nThe contract does the hard conversation for you.<\/text>\n<\/svg>\n\n\n\n

No awkwardness. No argument. The contract did the hard work for you.<\/p>\n\n\n\n

\n

Build your PSA in a tool that tracks every clause.<\/strong> Upbase<\/a> lets you store contract templates, link them to client projects, and track change orders alongside your task management, so nothing falls through the cracks.<\/p>\n<\/blockquote>\n\n\n\n

Clause 3: Payment terms<\/h3>\n\n\n\n

Late payments are the number one cash flow killer for agencies under 20 people. Your PSA is your first line of defense.<\/p>\n\n\n\n

Deposit before kickoff.<\/strong> 25-50% upfront is standard for project work. Retainers should be billed in advance of the service month. Never start work without money in the account.<\/p>\n\n\n\n

Milestone-based payments.<\/strong> For projects over $10,000, tie payments to deliverables, not dates. “50% upon signing, 25% upon design approval, 25% upon launch” is clearer and more enforceable than “net 30.”<\/p>\n\n\n\n

Late payment consequences.<\/strong> Include an interest rate on overdue invoices (1.5% per month is common) and the right to pause work if an invoice is more than 15 days past due.<\/p>\n\n\n\n

Kill fee.<\/strong> If the client cancels mid-project, what happens? Your PSA should specify that all completed work gets paid for, plus a percentage of the remaining contract value (10-25% is typical).<\/p>\n\n\n\n

Payment terms are not negotiable details you figure out later. <\/p>\n\n\n\n

They belong in the contract from day one.<\/p>\n\n\n\n

For retainer clients,<\/strong> your payment clause looks different. Bill at the beginning of each month for that month’s work. Include language that specifies unused hours don’t roll over (unless you want them to). <\/p>\n\n\n\n

And define what happens if the client wants to reduce retainer hours mid-engagement. <\/p>\n\n\n\n

Most agencies require 30 days’ notice for retainer changes.<\/p>\n\n\n\n\n\n<\/marker>\n<\/defs>\n\nRecommended payment structure for projects over $10k<\/text>\n\n\n\n\n\n\n\n\n\n50% deposit<\/text>\nUpon signing<\/text>\n<\/g>\n\n\n\n25% midpoint<\/text>\nDesign approval<\/text>\n<\/g>\n\n\n\n25% final<\/text>\nUpon launch<\/text>\n<\/g>\n\nContract signed<\/text>\nMilestone hit<\/text>\nProject complete<\/text>\n\nTie payments to deliverables, not dates. Never start work without money in the account.<\/text>\n<\/svg>\n\n\n\n

Clause 4: Intellectual property<\/h3>\n\n\n\n

IP is where agency contracts get messy fast, especially for agencies that build reusable frameworks, templates, or proprietary tools.<\/p>\n\n\n\n

The standard approach: the client owns the final deliverables upon full payment. You retain ownership of your pre-existing IP.<\/strong><\/p>\n\n\n\n

Your pre-existing IP includes any tools, templates, code libraries, frameworks, or methodologies you developed before or independent of the client engagement. <\/p>\n\n\n\n

The client gets a license to use those things as they appear in the deliverables, but they don’t own them outright.<\/p>\n\n\n\n

This matters. If you built a reporting dashboard template that you use across 15 clients, one client can’t claim exclusive ownership of it just because you used it on their project.<\/p>\n\n\n\n

Portfolio rights<\/strong> also belong here. Most agencies want the right to showcase client work in case studies and portfolios. Include a default provision that allows this, with the option for the client to opt out in writing. Don’t make portfolio use something you have to ask for after the fact.<\/p>\n\n\n\n\nWho owns what after the project<\/text>\n\n\n\nClient owns<\/text>\nFinal deliverables<\/text>\nCustom designs and assets<\/text>\nContent created for the project<\/text>\n\u2191 Only after full payment<\/text>\n<\/g>\n\n\n\nAgency retains<\/text>\nPre-existing templates<\/text>\nCode libraries and frameworks<\/text>\nProprietary methodologies<\/text>\nPortfolio usage rights<\/text>\n<\/g>\n\n\nClient gets a license to use agency tools as delivered. Not ownership.<\/text>\n<\/svg>\n\n\n\n

Clause 5: Confidentiality<\/h3>\n\n\n\n

You’ll see client financials, marketing strategies, login credentials, and internal communications. <\/p>\n\n\n\n

They’ll see your processes, pricing models, and team structure. Both sides need protection.<\/p>\n\n\n\n

Your confidentiality clause should define what counts as confidential information, state that both parties will keep it private, and list the standard exceptions (publicly available information, independently developed information, and legally required disclosures).<\/p>\n\n\n\n

Set a duration.<\/strong> Confidentiality obligations should survive the contract for 2-3 years. Indefinite confidentiality clauses are hard to enforce and make clients nervous.<\/p>\n\n\n\n

One thing agencies often miss: make sure your confidentiality clause doesn’t accidentally prevent you from using the client’s brand name.<\/strong> If your confidentiality language is too broad, referencing the client in your portfolio could technically violate it. <\/p>\n\n\n\n

That’s why the portfolio rights clause in the IP section matters.<\/p>\n\n\n\n

Clause 6: Termination<\/h3>\n\n\n\n

Every contract needs an exit door. The question is whether that door leads to an orderly transition or a legal fight.<\/p>\n\n\n\n

Your termination clause needs three scenarios:<\/p>\n\n\n\n

Termination for cause.<\/strong> Either party can end the agreement if the other side materially breaches the contract and doesn’t fix it within a cure period (10-15 business days is standard). Non-payment counts as a material breach.<\/p>\n\n\n\n

Termination for convenience.<\/strong> Either party can walk away for any reason with 30 days’ written notice. This protects both sides. Clients aren’t locked into an agency they’re unhappy with, and agencies aren’t stuck with a client who’s become toxic.<\/p>\n\n\n\n

What happens after termination.<\/strong> The client pays for all work completed through the termination date. The agency delivers all completed and paid-for work. Both sides return each other’s confidential information. Pre-existing IP stays with the agency.<\/p>\n\n\n\n

The clause that protects your team’s time:<\/strong> “Upon termination, Client shall pay Provider for all Services performed and expenses incurred up to the effective date of termination.”<\/em><\/p>\n\n\n\n

Without this language, you risk eating the cost of work already done.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Clause 7: Liability and indemnification<\/h3>\n\n\n\n

This is the “what happens when things go wrong” clause. It’s not fun to write, but it’s critical.<\/p>\n\n\n\n

Limitation of liability.<\/strong> Cap your total liability at the total fees paid under the agreement. Without this cap, a client could theoretically sue you for damages that far exceed what they paid you. <\/p>\n\n\n\n

For a $15,000 website project, you don’t want to be on the hook for $500,000 in “lost revenue” because the site went down for a day.<\/p>\n\n\n\n

Indemnification.<\/strong> Each party agrees to cover the other’s losses if their own negligence or breach causes a problem. If the client gives you copyrighted images and you get sued, the client covers your legal costs. <\/p>\n\n\n\n

If you deliver code that infringes on a third party’s patent, you cover the client’s costs.<\/p>\n\n\n\n

No indirect damages.<\/strong> Exclude consequential, incidental, and punitive damages. You’re responsible for delivering what you promised, not for every downstream business impact the client can imagine. <\/p>\n\n\n\n

How to write scope language that prevents scope creep<\/h2>\n\n\n\n

Scope creep doesn’t start when a client asks for extra work. It starts when your scope language leaves room for interpretation.<\/p>\n\n\n\n\nWeak scope vs. strong scope<\/text>\n\n\n\n\u2717 Weak<\/text>\n“Provider will manage Client’s social media presence<\/text>\nacross relevant platforms.”<\/text>\n<\/g>\n\n\n\n\u2713 Strong<\/text>\n“Provider will create and publish 12 Instagram posts and 8 LinkedIn<\/text>\nposts per month. Each post includes one custom graphic and a caption<\/text>\nof up to 200 words. Community management and paid ads are excluded.”<\/text>\n<\/g>\n\nThe weak version invites “Does that include responding to DMs?” The strong version already answered it.<\/text>\n<\/svg>\n\n\n\n

Here are three rules for writing scope that holds up:<\/p>\n\n\n\n

Use quantities, not categories.<\/strong> “Social media management” can mean anything. “8 LinkedIn posts per month, each with a custom graphic and 150-word caption” cannot be misinterpreted.<\/p>\n\n\n\n

Define the process, not just the output.<\/strong> If your process includes a discovery phase, wireframing, two rounds of feedback, and a launch checklist, write each step into the scope. <\/p>\n\n\n\n

When a client skips discovery and wants to jump straight to design, you can point to the contract and explain why the process exists.<\/p>\n\n\n\n

List what’s excluded.<\/strong> For every deliverable you include, there’s an adjacent service clients assume is included. Website design projects attract requests for copywriting, SEO, ongoing hosting, and content updates. <\/p>\n\n\n\n

Call out each exclusion. <\/p>\n\n\n\n

It’s not negative. <\/p>\n\n\n\n

It’s clear.<\/p>\n\n\n\n

The best scope language answers this question: if a neutral third party read this clause, would they know exactly what’s included and what’s not?<\/strong><\/p>\n\n\n\n

If the answer is no, rewrite it.<\/p>\n\n\n\n

Here’s a before-and-after to show the difference:<\/p>\n\n\n\n

Weak scope language:<\/strong> “Provider will manage Client’s social media presence across relevant platforms.”<\/em><\/p>\n\n\n\n

Strong scope language:<\/strong> “Provider will create and publish 12 Instagram posts and 8 LinkedIn posts per month. Each post includes one custom graphic (1080x1080px for Instagram, 1200x627px for LinkedIn) and a caption of up to 200 words. Community management, paid advertising, influencer outreach, and platform analytics reporting are excluded.”<\/em><\/p>\n\n\n\n

The weak version invites the question “Does that include responding to DMs?” The strong version already answered it.<\/p>\n\n\n\n

Common PSA mistakes that cost agencies money<\/h2>\n\n\n\n\n5 PSA mistakes that cost agencies money<\/text>\n\n\n\n1<\/text>\nUsing the same contract for project work and retainer work<\/text>\n<\/g>\n\n\n\n2<\/text>\nNo cure period before termination \u2014 one missed deadline ends the deal<\/text>\n<\/g>\n\n\n\n3<\/text>\nVague IP language \u2014 client claims your pre-existing frameworks<\/text>\n<\/g>\n\n\n\n4<\/text>\nNo client obligations section \u2014 you absorb delays they cause<\/text>\n<\/g>\n\n\n\n5<\/text>\nLate payment clause with no teeth \u2014 interest, pause rights, or holdbacks<\/text>\n<\/g>\n<\/svg>\n\n\n\n

Using the same contract for project work and retainer work.<\/strong> A project PSA and a retainer PSA need different payment structures, different scope definitions, and different termination terms. A project ends when deliverables are complete. A retainer renews monthly. Don’t force one structure to do both jobs.<\/p>\n\n\n\n

No cure period before termination.<\/strong> If your contract allows immediate termination for any breach, a client could argue that a missed deadline (even by a day) is grounds to walk away without paying. <\/p>\n\n\n\n

Always include a cure period that gives both sides time to fix problems.<\/p>\n\n\n\n

Vague IP language around pre-existing tools.<\/strong> If you use Figma templates, code libraries, or strategy frameworks across clients, your PSA must explicitly carve those out. <\/p>\n\n\n\n

Otherwise, a client could claim ownership of tools you use with every other client.<\/p>\n\n\n\n

Forgetting the “client obligations” section.<\/strong> Your timeline depends on the client providing feedback, approvals, and materials on time. If your PSA doesn’t address what happens when the client goes silent for three weeks, you absorb the cost of the delay.<\/p>\n\n\n\n

No late payment teeth.<\/strong> A late payment clause without consequences is decoration. Include interest charges, the right to pause work, and (for extreme cases) the right to withhold deliverables until payment is received.<\/p>\n\n\n\n

Tools for creating and managing your PSAs<\/h2>\n\n\n\n

You don’t need a lawyer to draft every contract from scratch. Start with a solid template, customize it to your engagement, and have a lawyer review your first version.<\/p>\n\n\n\n

Here’s what the typical agency stack looks like for contract management:<\/p>\n\n\n\n

Tool<\/th>What it does<\/th>Best for<\/th><\/tr><\/thead>
PandaDoc<\/td>Document creation, e-signatures, templates<\/td>Agencies that want signing workflows built in<\/td><\/tr>
DocuSign<\/td>E-signatures and contract tracking<\/td>Agencies focused on getting contracts signed fast<\/td><\/tr>
HelloSign (Dropbox Sign)<\/td>Simple e-signature workflows<\/td>Small teams that want something lightweight<\/td><\/tr>
Google Docs + template<\/td>Free, collaborative editing<\/td>Solo consultants and very early-stage agencies<\/td><\/tr>
Upbase<\/a><\/td>Docs, tasks, and client management in one workspace<\/td>Agencies that want contracts linked to project delivery<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The tool matters less than the habit. Pick one and use it for every engagement.<\/p>\n\n\n\n

\n

Stop managing contracts in one tool and projects in another.<\/strong> Upbase<\/a> keeps your client agreements, project tasks, timelines, and communication in a single workspace. No more digging through email threads to find the SOW a client approved six months ago. See how it works \u2192<\/a><\/p>\n<\/blockquote>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Free professional service agreement template<\/h2>\n\n\n\n

We built a fill-in-the-blank PSA template designed specifically for agencies and service teams. It covers all seven clauses in the agency PSA stack, with placeholder text you can customize in 15 minutes.<\/p>\n\n\n\n

Download the free professional service agreement template \u2192<\/a><\/strong><\/p>\n\n\n\n

The template includes:<\/p>\n\n\n\n