Legal boilerplate is nested blocks, not retyped clauses
What counsel and ops repeat is not the whole letter.
It is blocks: a disclaimer, a confidentiality line, a pointer to the privacy policy, a footer. Five notices that differ only by project name drift the first time a lawyer edits half a sentence.
One disclaimer snippet. One footer snippet. Nest them. Edit the block, not five letters.
A FillIn window appears before expansion. ⌘/Ctrl+Enter inserts.
Blocks in the library, project names in FillIn
Do not start by scanning a company-wide legal wiki. Split the block you already retype.
- Install and grant accessibility. Expansion is in the focused field. No account required. See Getting started.
- Create
lg-disclaimerandlg-footer. Do not call themlegalorterms. See Groups. - Outbound notes are “nested blocks + this time’s explanation.” See FillIn.
- Expand in mail or a document. Fill the project name and the note for this send.
%s:lg-disclaimer%
About %filltext&name=project or feature%:
%fillarea&name=this note%
This note is not legal advice. How personal information is handled is in the product privacy policy.
%s:lg-footer%%s:lg-disclaimer% holds only the line that already passed review. Project name and this send’s scope are FillIn. If you need an internal memo versus a public notice, use %fillswitch%. Do not store two almost-identical full texts.
If the footer must point at the privacy policy, use the stable product page. Do not invent a new short link every time. English site: Privacy policy.
Which field
| What changes | Use |
|---|---|
| Project or feature name | Single line %filltext% |
| This note, this scope | Multiline %fillarea% |
| Internal versus public | Conditional %fillswitch% |
| An occasional “please have counsel review” | Optional %fillcheck% |
Do not leave “paste the latest disclaimer here” in the body. The latest disclaimer is edited once in lg-disclaimer.
The loop is still abbreviation, trigger, local replace. A clause that is already approved should not go through the keyboard again. A contract management system is a different product; this is a block you insert.
No HIPAA, no BAA
CodeExpander has no HIPAA certification and no BAA. The local snippet library is not described as a regulated medical-record or medical-billing system. Clinic, hospital, and payer compliance workflows are not on this product’s surface.
Expansion authority is this machine. Snippet bodies and FillIn answers stay local unless you turn on sync and accept a copy. The full statement is the privacy policy. Do not substitute a blog paragraph for that page.
Where it may fire
If mail and documents need the same block, leave the legal group global. If it wrecks chat, turn on ExpandIn (Pro) and keep the mail client and the document app.
Sharing a reviewed block is organization shared groups. The website edits a cloud copy. Machines expand after sync. See Team copy.
Do not
- Do not claim HIPAA, BAA, or SOC 2. Those are not selling points in this catalog.
- Do not stuff a full contract into one snippet. A snippet inserts a block. It is not a contract system.
- Do not let the blog replace the privacy policy.
- Do not use
termsorndaas abbreviations. See Abbreviation hygiene.
Related: Brand voice is one nested greeting, Support templates.