Guide
An engagement letter and fee agreement tracker in Notion: no work without a signed scope
Engagement letter tracker in Notion: record template, scope, fee arrangement and signature status, and flag matters open without a signed engagement.
By Raghav R Handa, practising lawyer15 min read
TL;DR
- An Engagements database records, for every matter, the template used, scope, fee arrangement, retainer, sent date, signed date and status.
- A view of matters with no signed engagement is the safety net that stops unpapered work.
- Log scope changes as new rows, not edits, so you keep the history, and track template versions so you can find every client on an old one.
- Keep signature in a signature tool and the retainer ledger in trust software; Notion records status and links.
An engagement tracker makes sure every matter has a sent, signed and current engagement letter and fee arrangement. Build one database, relate it to Matters, and add one view: matters open without a signed engagement. That view is the safety net that stops unpapered work. Notion records status and links; the signature itself belongs in an e-signature tool, and any retainer money belongs in a trust ledger (see trust accounting). This guide gives the schemas, the workflows, the views, template version control and the scope-change protocol.
Why unpapered work is a risk
- Fee disputes. Without agreed terms, you argue about what was promised.
- Scope. The client assumes you are doing more than you are.
- Regulatory. Many regulators require written terms or specific information.
- Limitation. If it is unclear whether you act, you may be blamed for a missed date.
- Conflicts and money laundering checks. Skipped steps cluster around unpapered work.
What an engagement letter typically covers
Content requirements differ by jurisdiction and regulator, so use this as a checklist for what to record, not as a form.
| Element | Why it matters | Tracked as |
|---|---|---|
| Parties | Who the client is and who it is not | Client relation |
| Scope and exclusions | What you will and will not do | Scope text |
| Fees and billing terms | Basis and timing | Fee arrangement, rate or amount |
| Retainer and how it is held | Client money rules | Retainer amount (reference), trust ledger link |
| Client responsibilities | What you need from them | Text |
| Communication | How and how often | Cadence select |
| Termination | How either side can end it | Template version |
| File retention | How long you keep records | Retention period on matter |
| Technology and AI | Disclosure and preferences | AI consent select |
| Complaints and regulatory notices | Required information | Template version |
The databases
Engagements
| Property | Type | Why |
|---|---|---|
| Name | Title | Matter and version |
| Matter | Relation to Matters | Ties it to the file |
| Client | Relation to Contacts | Who signed |
| Template | Relation to Engagement templates | Which wording was used |
| Scope | Text | What is covered |
| Exclusions | Text | What is not |
| Fee arrangement | Select: Hourly, Fixed, Phased, Contingency, Retainer, Hybrid, Subscription | Billing method |
| Fee detail | Text | Rates, amounts, conditions |
| Retainer amount | Number | The agreed amount, not a balance |
| Sent, Signed | Date | The evidence trail |
| Status | Select: Draft, Sent, Signed, Declined, Superseded | Lifecycle |
| Days since sent | Formula | Chasing |
| Signed copy | URL | Executed document |
| Approved by | Person | Who authorised the terms |
| Replaces | Relation to Engagements | The earlier version |
Engagement templates and scope changes
| Database | Key properties |
|---|---|
| Engagement templates | Name, matter type, version, effective date, status (Current, Retired), link to the document, change summary |
| Scope changes | Matter, date, description, fee and time impact, approved by client (checkbox and date), approved internally, status |
Fee arrangements and what to track for each
| Arrangement | Track | Watch for |
|---|---|---|
| Hourly | Rates by timekeeper; estimate; billing cycle | Estimates that become promises |
| Fixed fee | Scope precisely; milestones; what triggers extra fees | Scope creep |
| Phased | Phases, amounts, completion criteria | Gaps between phases |
| Contingency | Conditions, how costs are treated; regulatory permissions | Restrictions on use in your jurisdiction |
| Retainer | Amount, how drawn down, replenishment | Holding money correctly |
| Hybrid or subscription | What is included; limits; review date | Unclear boundaries |
The workflow, step by step
- An enquiry becomes a Matter in the Enquiry status; the conflict check is recorded.
- A button creates an Engagement from the right template, linked to the matter.
- The lawyer completes scope, exclusions and fees and sets status to Sent when it goes out; the Sent date is recorded.
- A reminder view shows engagements Sent more than a few days ago and not Signed.
- On signature, record the Signed date, link the executed copy and set status to Signed. Only then does the matter move to Open.
- If the client declines, record it; the matter closes as declined, with a non-engagement letter.
- When scope changes, create a Scope change row and a new Engagement; mark the earlier one Superseded.
Views that protect you
| View | Filter | Purpose |
|---|---|---|
| Matters open, no signed engagement | Matter status is Open and no related Engagement with status Signed | The safety net; should be empty |
| Sent but not signed | Status Sent; sort by days since sent | Chasing |
| Scope changes pending approval | Not approved by client | Stops unapproved extra work |
| By template version | Group by template and version | Find clients on an old version |
| Exceptions | Work started before Signed (a checkbox you set with the reason) | Visibility of risky starts |
| Annual review due | Signed more than a year ago on a continuing matter | Prompt to revisit scope and fees |
// Days since sent
if(empty(prop("Sent")), "", dateBetween(now(), prop("Sent"), "days"))Template version control
Engagement terms change: a new regulatory requirement, a new fee clause, an AI disclosure. Treat the template like software. Give each version a number and effective date, record the version on every engagement, retire the old one, and use the by-version view to find every client on an old version if you must notify them. Keep a change summary on each version so a colleague can see why it changed.
A scope-change protocol
- When the client asks for something outside the scope, say so and say you will confirm.
- Record a Scope change row: what, why, estimated time and fee impact.
- Send a short written note to the client with the change and the cost.
- Do the extra work only after written approval (or per your regulator's rules).
- Record the approval and create the updated engagement.
"Thanks for raising [X]. That is outside the scope of our engagement dated [date], which covers [scope]. We can do it for [fee or estimate]. Please reply to confirm and we will start. Nothing changes in the meantime."
Non-engagement letters
Track enquiries you decline in the same system: a status of Declined, the date you told the person, and whether you flagged that time limits may apply. It is cheap protection.
What it does not do
- It cannot collect signatures or hold funds.
- It cannot decide what your regulator requires in an engagement letter; read your rules.
- It does not draft the letter; that is a template and a lawyer.
Common mistakes
- Opening matters before the engagement is signed because "it is urgent", without recording the exception.
- Editing the original engagement instead of adding a new one.
- No version on the template, so changes cannot be traced.
- No reminder view, so unsigned letters sit for weeks.
Connect it to intake (client intake), conflicts (conflict checks), fast client onboarding, the AI wording in the consent template and legal project management.
Frequently asked questions
Why track engagement letters in Notion?
Because unpapered work is a common source of fee disputes and complaints. A tracker shows, for every matter, whether the engagement letter is sent, signed and current, and flags matters that are open without one.
What should an engagement tracker record?
The matter, client, template and version used, scope of work, exclusions, fee arrangement, retainer amount, sent and signed dates, status, who approved, and a log of any scope changes.
Can Notion collect the signature?
No. Use an e-signature service for the signature and record its status and a link to the signed document in Notion.
What should an engagement letter contain?
Requirements vary by regulator, but typically the parties, scope and exclusions, fee basis and billing terms, any retainer and how it is held, client responsibilities, how you will communicate, termination, file retention, conflicts and complaint information. Check what your regulator requires.
How do I handle a change in scope?
Record it as a new engagement row (or an addendum) with the change, the fee impact and the client's approval, mark the earlier row Superseded, and get approval before doing the extra work.
How do I update my engagement letter template safely?
Version it, record the version on each engagement, and keep a view by version so you can find every client on an old version if you need to notify or update them.
What if work starts before the letter is signed?
It happens in urgent matters. Record why, send the letter immediately, track it as an exception on a dedicated view, and follow your regulator's rules on terms of engagement.
Do I need a non-engagement letter too?
Yes, for enquiries you decline. Track them so you can show you told the person you were not acting and flagged any time limits.
Related guides
- How to build a litigation case tracker in Notion: chronology, issues, evidence and hearings
- Contract lifecycle management in Notion: a lightweight CLM for small legal teams
- Legal project management in Notion: phases, budgets, scope and status reports
- Legal knowledge management in Notion: a precedent bank and firm wiki that stays current