Customization

The All-or-Nothing Trap

Most compliance software forces a choice. Enterprise tools ship with rigid, predetermined fields — a “Status” dropdown with options you’d never use, no field for what you need to track.

Horizontal platforms like Airtable or Notion offer flexibility but demand weeks of configuration before you can track a single filing deadline. You become the product designer, building your compliance system from scratch.

Lextree takes a different approach. Every module ships with sensible defaults, and every default is fully customizable — add fields, remove what you don’t need, rename labels, reorder everything. Start with a working compliance system on day one, then shape it into your system over time.

Your Data, Your Way

Every dataset in Lextree — legal entities, contracts, insurance policies, board resolutions — uses a configurable template. The template controls which fields appear, what they’re called, and how they’re ordered.

Template Controls

Subscriber admins manage templates directly:

• Add custom fields to capture information specific to your organization, industry, or compliance requirements
• Remove default fields that don’t apply — hide what you never track rather than leaving it empty across thousands of records
• Rename field labels so the system speaks your organization’s language
• Reorder fields to put the most important information where your team expects it

Consistent by Default

Configure a template once — add a “Region” field to contracts, rename “Category” to “Practice Area,” remove “Fax Number” from contacts. That configuration becomes the default for every new record.

A new team member creating a contract sees the same fields, in the same order, with the same labels as every other contract. Custom fields appear alongside defaults with no visual distinction. Lextree’s template system works across all 17 modules — each independently configurable, consistently applied.

Field Types for Global Business

Generic platforms offer text fields, dropdowns, and dates. That covers task tracking.

It falls short for multi-jurisdictional compliance. Which state is your subsidiary registered in? What legal form does it take? How much does your Directors & Officers (D&O) policy cover in euros versus dollars?

Lextree provides field types designed for these realities.

Country Subdivision

Tracks not just a country but the specific state, province, canton, or territory within it. When you record where an entity is registered or where a license applies, you capture the full jurisdictional picture. No freeform text field where “California,” “CA,” and “Calif.” become three different entries.

Jurisdiction Form

Combines a jurisdiction with the specific legal entity form recognized under that jurisdiction’s law, using standardized Entity Legal Form (ELF) codes. A Delaware LLC, a UK Limited Company, a German GmbH, a Brazilian Ltda — each carries different governance requirements and filing obligations. The data model encodes these distinctions rather than leaving them to a text field.

Currency

Stores monetary amounts with their currency code. A multinational organization’s contracts, insurance policies, and tax obligations span different currencies. Lextree handles this natively — no manual formatting, no ambiguity about whether “500,000” means dollars, euros, or pounds.

When field types understand jurisdictions, legal forms, and currencies, every downstream feature inherits that intelligence. Filter entities by registration state, find contracts by currency, or identify subsidiaries by legal form.

Structure Without Rigidity

The full field type library gives you precise control over how data behaves.

Controlled Vocabularies

Selection fields define controlled vocabularies specific to your organization. Instead of freeform text where the same concept appears a dozen ways, your team picks from a curated list. Add options as needs evolve.

Contact fields validate as you type — email addresses, URLs, and phone numbers must match proper formats. These validations prevent the data quality problems that make compliance reporting unreliable.

Precision Data Types

Numeric fields respect their purpose. Percentages display and calculate as percentages — useful for ownership stakes and compliance thresholds. Currency amounts carry their denomination.

Date fields distinguish date-only values (filing deadlines, effective dates) from datetime values (meeting times, timestamps). They integrate with Events for automatic deadline reminders. Add a date field to any dataset, and it drives the notification system.

Yes/No fields support three states: yes, no, and unknown. Auto-renewal clauses, exemption applicability, sub-delegation authority — these questions often start as unknown and resolve over time.

Connected Across the Platform

Custom fields don’t exist in isolation. They connect to every cross-cutting platform feature.

Workflows and Events

Workflow structured data uses the same field types. A contract approval workflow captures the proposed value as currency, the jurisdiction as a country subdivision, the rationale as text.

Events integrate with custom date fields. Add a filing deadline, review date, or renewal trigger to any dataset — it drives event creation and reminders. You add the field; the notification system picks it up.

Timeline and Reporting

Timeline states and custom fields give records their full compliance context. Fields capture the specifics; Timeline captures how state changed over time. Together, they answer “What is this?” and “What has happened to it?”

Filtering and reporting use field types natively. Selection fields become filter options, date fields enable date-range queries, and country subdivision fields scope views to specific jurisdictions.

When you add a custom field in Lextree, it joins workflows, events, timelines, filtering, and reporting. The platform understands what each field is, not just that it exists.