eFirm: Engagement Letter Draft
When to use this
This skill is the eFirm-integrated execution of the engagement letter workflow. It fires automatically as the final step of [[efirm-matter-creation-flow]] once:
- Client identity is confirmed from intake ([[efirm-client-intake-form]]).
- Conflict check is complete and returns Clean ([[efirm-conflict-check]]).
- Fee quote is approved ([[efirm-fee-quote-builder]]).
The resulting document is the binding contract between the firm and the client. No billable work is recorded against the matter until the letter is executed.
Auto-populated fields
The system draws these from upstream data without manual re-entry:
| Field |
Source |
| Client legal name + address |
CRM / intake form |
| Matter title and description |
Matter creation form |
| Responsible partner name + team |
Matter assignment |
| Fee structure + estimate |
Fee quote builder output |
| Conflict-check confirmation |
Conflict check record (timestamp + outcome) |
| Matter number |
Auto-generated by eFirm |
| Trust / retainer details |
Fee quote (retainer amount + bank account) |
| VAT / tax registration details |
Firm profile |
Fields that require manual input by the partner:
| Field |
Notes |
| Scope of engagement (detailed) |
Must be precise; in/out items specified |
| Exclusions (what is not covered) |
Protects against scope disputes |
| Any matter-specific billing arrangements |
Deviations from standard rate card |
| Confidentiality obligations specific to matter |
If beyond standard terms |
| Governing law and jurisdiction |
Especially important for cross-border mandates |
Firm-branded template components
Every generated letter includes:
- Letterhead: firm logo, address, contact details, bar registration numbers.
- Opening: date, client name and address, re: matter reference.
- Scope section: auto-populated from matter creation, with space for partner additions.
- Fee and billing section: verbatim from approved fee quote; billing cadence; trust account details.
- Standard terms appendix: boilerplate drawn from firm's Knowledge Base ([[efirm-knowledge-base-curation]]):
- Limitation of liability
- Confidentiality and data protection
- Document retention and destruction
- File close-out procedure
- Complaints procedure
- Applicable professional regulations
- Bar-rule disclosures: jurisdiction-specific required disclosures (see below).
- E-signature block: signature fields for responsible partner + authorised client signatory.
Jurisdiction-specific disclosures
| Jurisdiction |
Required disclosures |
| KSA |
Licensed attorney bar number; disclosure of any limitation on scope required by KSA Bar; billing in SAR or USD as agreed |
| UAE (onshore) |
Law firm license number; Dubai Legal Affairs Department / Abu Dhabi Judicial Department registration reference; AML disclosure statement |
| DIFC |
DIFC registered firm number; DFSA disclosure if firm provides regulated activity; client money handling disclosure if retainer involved |
| ADGM |
ADGM registered firm number; FSRA equivalents |
| Lebanon |
Beirut Bar registration; professional fees schedule reference |
| France |
RPVA bar number; CNB disclosure rules; CARPA trust account reference |
| UK |
SRA firm number; Right to complain to Legal Ombudsman; cooling-off rights if consumer client |
| US |
State bar number; applicable Rules of Professional Conduct; client file retention policy |
E-signature workflow
- Draft auto-generated: routed to responsible partner's review queue.
- Partner review: partner approves, modifies scope or fee section, approves for sending.
- Transmission: sent to client via DocuSign or Tawqi3i (GCC-recognized e-signature platform) with:
- 5-business-day signature deadline.
- Reminder at T-2 days.
- Expiry and re-issue at T+10 if not signed.
- Client signs: e-signature platform records identity verification (email + SMS OTP as minimum).
- Completion event: on full execution, eFirm automatically:
- Sets matter status to Active.
- Triggers billing setup (timekeeper access, matter code, billing cadence).
- Grants document-management folder access to assigned team.
- Creates initial deadline entries per matter type defaults.
- Sends confirmation email to client.
- Audit record: signed PDF stored in matter file with signature certificate (metadata: signer identity, IP, timestamp, certificate of completion).
Tawqi3i note (GCC)
Tawqi3i is the UAE government's official e-signature and digital transaction platform recognized under UAE Federal Decree-Law No. 46 of 2021 on Electronic Transactions. For cross-border matters outside the GCC, DocuSign (eIDAS-compliant in EU; ESIGN-compliant in US) should be used instead. Confirm with the client which platform they accept before sending.
Audit trail
The following events are recorded immutably in the matter file:
| Event |
Data captured |
| Draft created |
Timestamp, auto-population source versions |
| Partner review |
Partner ID, changes made, approval timestamp |
| Sent to client |
Timestamp, recipient email, platform used |
| Reminder sent |
Timestamp |
| Client viewed |
Timestamp (if platform records) |
| Client signed |
Timestamp, IP address, identity verification method |
| Partner countersigned |
Timestamp |
| Matter activated |
Timestamp, triggering event |
The audit trail is accessible to the managing partner and compliance officer; it is privileged firm-client information.
What can go wrong
- Scope too vague: "Advising on the transaction" invites scope disputes. Define what is and is not included in scope with specificity.
- Fee quote not locked: if the fee quote in the engagement letter differs from the fee quote document, the letter controls — ensure they match.
- No counterpart language for multi-party matters: if multiple entities are signing, ensure all are named and each authorized signatory is identified.
- Sending before conflict check is complete: the conflict-check field in the auto-population must show "COMPLETE: CLEAN" before transmission is enabled.
- Wrong Tawqi3i vs. DocuSign: some government clients in KSA/UAE require government-approved platforms; confirm before sending.
Related skills
- [[efirm-matter-creation-flow]]
- [[efirm-fee-quote-builder]]
- [[efirm-conflict-check]]
- [[efirm-client-intake-form]]
- [[efirm-knowledge-base-curation]]
- [[draft-engagement-letter]]
1---2name: efirm-engagement-letter-draft3description: Use when the eFirm matter creation workflow needs to auto-generate a firm-branded, bar-compliant engagement letter pre-populated from CRM, matter, fee-quote, and conflict-check data. Covers the eFirm-integrated version of the standalone engagement-letter draft skill, including e-signature workflow (DocuSign/Tawqi3i), audit trail, and downstream matter activation. P0 — no substantive work begins until the engagement letter is signed.4license: MIT5---67# eFirm: Engagement Letter Draft89## When to use this1011This skill is the eFirm-integrated execution of the engagement letter workflow. It fires automatically as the final step of [[efirm-matter-creation-flow]] once:121. Client identity is confirmed from intake ([[efirm-client-intake-form]]).132. Conflict check is complete and returns Clean ([[efirm-conflict-check]]).143. Fee quote is approved ([[efirm-fee-quote-builder]]).1516The resulting document is the binding contract between the firm and the client. No billable work is recorded against the matter until the letter is executed.1718## Auto-populated fields1920The system draws these from upstream data without manual re-entry:2122| Field | Source |23|---|---|24| Client legal name + address | CRM / intake form |25| Matter title and description | Matter creation form |26| Responsible partner name + team | Matter assignment |27| Fee structure + estimate | Fee quote builder output |28| Conflict-check confirmation | Conflict check record (timestamp + outcome) |29| Matter number | Auto-generated by eFirm |30| Trust / retainer details | Fee quote (retainer amount + bank account) |31| VAT / tax registration details | Firm profile |3233Fields that require **manual input** by the partner:3435| Field | Notes |36|---|---|37| Scope of engagement (detailed) | Must be precise; in/out items specified |38| Exclusions (what is not covered) | Protects against scope disputes |39| Any matter-specific billing arrangements | Deviations from standard rate card |40| Confidentiality obligations specific to matter | If beyond standard terms |41| Governing law and jurisdiction | Especially important for cross-border mandates |4243## Firm-branded template components4445Every generated letter includes:46471. **Letterhead**: firm logo, address, contact details, bar registration numbers.482. **Opening**: date, client name and address, re: matter reference.493. **Scope section**: auto-populated from matter creation, with space for partner additions.504. **Fee and billing section**: verbatim from approved fee quote; billing cadence; trust account details.515. **Standard terms appendix**: boilerplate drawn from firm's Knowledge Base ([[efirm-knowledge-base-curation]]):52 - Limitation of liability53 - Confidentiality and data protection54 - Document retention and destruction55 - File close-out procedure56 - Complaints procedure57 - Applicable professional regulations586. **Bar-rule disclosures**: jurisdiction-specific required disclosures (see below).597. **E-signature block**: signature fields for responsible partner + authorised client signatory.6061## Jurisdiction-specific disclosures6263| Jurisdiction | Required disclosures |64|---|---|65| KSA | Licensed attorney bar number; disclosure of any limitation on scope required by KSA Bar; billing in SAR or USD as agreed |66| UAE (onshore) | Law firm license number; Dubai Legal Affairs Department / Abu Dhabi Judicial Department registration reference; AML disclosure statement |67| DIFC | DIFC registered firm number; DFSA disclosure if firm provides regulated activity; client money handling disclosure if retainer involved |68| ADGM | ADGM registered firm number; FSRA equivalents |69| Lebanon | Beirut Bar registration; professional fees schedule reference |70| France | RPVA bar number; CNB disclosure rules; CARPA trust account reference |71| UK | SRA firm number; Right to complain to Legal Ombudsman; cooling-off rights if consumer client |72| US | State bar number; applicable Rules of Professional Conduct; client file retention policy |7374## E-signature workflow75761. **Draft auto-generated**: routed to responsible partner's review queue.772. **Partner review**: partner approves, modifies scope or fee section, approves for sending.783. **Transmission**: sent to client via DocuSign or Tawqi3i (GCC-recognized e-signature platform) with:79 - 5-business-day signature deadline.80 - Reminder at T-2 days.81 - Expiry and re-issue at T+10 if not signed.824. **Client signs**: e-signature platform records identity verification (email + SMS OTP as minimum).835. **Completion event**: on full execution, eFirm automatically:84 - Sets matter status to **Active**.85 - Triggers billing setup (timekeeper access, matter code, billing cadence).86 - Grants document-management folder access to assigned team.87 - Creates initial deadline entries per matter type defaults.88 - Sends confirmation email to client.896. **Audit record**: signed PDF stored in matter file with signature certificate (metadata: signer identity, IP, timestamp, certificate of completion).9091## Tawqi3i note (GCC)9293Tawqi3i is the UAE government's official e-signature and digital transaction platform recognized under UAE Federal Decree-Law No. 46 of 2021 on Electronic Transactions. For cross-border matters outside the GCC, DocuSign (eIDAS-compliant in EU; ESIGN-compliant in US) should be used instead. Confirm with the client which platform they accept before sending.9495## Audit trail9697The following events are recorded immutably in the matter file:9899| Event | Data captured |100|---|---|101| Draft created | Timestamp, auto-population source versions |102| Partner review | Partner ID, changes made, approval timestamp |103| Sent to client | Timestamp, recipient email, platform used |104| Reminder sent | Timestamp |105| Client viewed | Timestamp (if platform records) |106| Client signed | Timestamp, IP address, identity verification method |107| Partner countersigned | Timestamp |108| Matter activated | Timestamp, triggering event |109110The audit trail is accessible to the managing partner and compliance officer; it is privileged firm-client information.111112## What can go wrong113114- **Scope too vague**: "Advising on the transaction" invites scope disputes. Define what is and is not included in scope with specificity.115- **Fee quote not locked**: if the fee quote in the engagement letter differs from the fee quote document, the letter controls — ensure they match.116- **No counterpart language for multi-party matters**: if multiple entities are signing, ensure all are named and each authorized signatory is identified.117- **Sending before conflict check is complete**: the conflict-check field in the auto-population must show "COMPLETE: CLEAN" before transmission is enabled.118- **Wrong Tawqi3i vs. DocuSign**: some government clients in KSA/UAE require government-approved platforms; confirm before sending.119120## Related skills121122- [[efirm-matter-creation-flow]]123- [[efirm-fee-quote-builder]]124- [[efirm-conflict-check]]125- [[efirm-client-intake-form]]126- [[efirm-knowledge-base-curation]]127- [[draft-engagement-letter]]
sboghossian