Why your agent should draft from your templates, not a blank page
Published
Short answer
When an AI agent writes a contract from scratch, it invents the legal text, and you have to check every clause. When it drafts from your own approved template, it only fills in the client, scope, price and dates, and you check a handful of fields. Templates make agent drafting faster to review, more consistent and much safer.
Two ways to ask for a contract
From scratch: "Write a consulting agreement for Acme." The agent produces something reasonable and generic. It picks a governing law, a liability cap and a notice period. Some may match what you'd want, some won't, and you only find out by reading every line.
From a template: "Make a consulting agreement for Acme from our standard template, 40 hours a month at 120 an hour." The agent opens the template your lawyer approved, fills in the client, hours, rate and dates, and asks for anything missing. The clauses are already yours.
What changes when you use templates
| From scratch | From your template | |
|---|---|---|
| Legal text | Invented each time | Approved once, reused |
| What you review | Every clause | The filled-in fields and any changes |
| Consistency | Each contract differs | Every contract matches |
| Risk of odd terms | High | Low |
| Speed to send | Slow, because review is slow | Fast |
How fields make it work
A good template marks the parts that change from client to client as fields: the client's name and address, the start date, the price, the scope. When the agent drafts, it fills those fields in, from what you said, from the client record, or by asking you. Everything else stays as written.
In Pledge, fields show up as chips in the draft. Click one to see or change its value. Empty fields are highlighted, so you see at a glance what's still missing.
Reuse the clauses. Fill in the details.
- Reusable
Approved clauses
The legal text already written in your template.
- Changes per contract
Client-specific fields
Client, scope, price and dates from the request or client record.
Combined into
A draft to review
Check the filled fields and any clause changes you requested.
Ask for missing details instead of letting the agent guess.
Setting up templates that agents use well
- Start with the three you send most. For most agencies: a consulting or services agreement, an engagement letter for single jobs, and an NDA.
- Turn every variable into a field. If it changes between clients, it's a field.
- Name templates clearly. "Consulting agreement, hourly" and "Consulting agreement, fixed price" beat "Contract v3 final".
- Have a lawyer review them once. Then every contract the agent drafts inherits that review.
Ready-made starting points: the consulting agreement template, the engagement letter template, the statement of work template and the NDA template.
When to let the agent go beyond the template
Templates aren't a cage. You can still ask for changes: "Add a clause about hosting costs" or "make the confidentiality mutual". The difference is that you're reviewing a small, visible change to text you trust, not a whole new contract.
Questions
- Can AI agents use my existing contract templates?
- With Pledge, yes. Your agent lists and reads the templates in your workspace and drafts new contracts from them.
- What is a contract field?
- A placeholder in a template for something that changes between contracts, such as the client's name, the price or the start date. The agent fills fields in instead of rewriting the text.
- Can the agent change the template's clauses?
- It can change a draft when you ask it to, and you see the change before sending. The template itself stays as it was.
Try Pledge
Contracts, time, plans and leads for small agencies, with an MCP server for Claude and ChatGPT. Pledge is in private beta: leave your email and we will send an invite.