Human-readable text is structured content, not an unrelated PDF attachment. It can reference roles and parameter values so the document a signer reads is generated from the same contract object the client signs.
Language selection
Provide one HumanReadableText document per supported language. Clients select an exact language match and otherwise fall back to the first available document. Put the primary/legal fallback first.
Bind values into text
Use the contract human-readable element model for:
- paragraphs and sections;
- lists and tables;
- emphasis and links;
- parameter values;
- role names and role-reference values;
- conditional content supported by the schema.
Do not paste calculated values as fixed prose. A parameter reference ensures the rendered value follows the signed instance.
Rendering
Render through a contract-aware tool so parameter formatting, language choice, and supported elements remain consistent. Do not build the signing view from a separate prose copy.
Use LegalLab to load the contract XML and preview its human-readable languages while authoring a template.
Approval checklist
Before proposing a template:
- Render every language.
- Substitute boundary values for every parameter.
- Confirm required roles, counts, dates, fees, units, and termination rules agree with the machine section.
- Confirm links and attachments are durable and authorized.
- Confirm no unsupported language silently falls back to misleading text.
- Have the Trust Provider review both sections together.
A translation can change legal meaning. Machine translation is a drafting aid; each production language version requires appropriate review.
