> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loisforword.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Versions

> How to duplicate, customize, and share playbook versions across teams and workflows in LOIS for Word, including rule-level changes and rollout to Word users.

LOIS for Word gives you flexibility to adapt playbooks across teams and use cases—without duplicating effort.

## Shared rules across playbooks

You can write a rule once and share it across multiple playbooks. When a rule is linked:

* Updates to that rule automatically apply to all linked playbooks
* Learning and fallback improvements propagate across instances
* You reduce maintenance while keeping consistency

If needed, you can break the link to customize the rule independently in a specific playbook.

**Examples:**

* One indemnity rule used across Sales, Procurement, and DPA playbooks
* A governing law fallback shared across global teams

***

## Use a master playbook strategy

Start with a **master playbook** that contains your full rule set, and then use it to spin off tailored playbooks by mixing and matching subsets of rules.

**Why it works:**

* Centralized rule management
* Updates flow from the master to child playbooks
* Reduces setup time for new stakeholders

**Example:**

* Create one master playbook
* Build slimmed-down versions for Sales, Procurement, or Investors with only relevant rules
* Keep shared rules linked for automatic updates

***

## Duplicate and customize playbooks

You can duplicate any existing playbook to create a new version. When duplicating:

* You can maintain or break links to shared rules
* Each version can be tailored for specific contract types or review styles
* Great for managing regional/legal variants or team-specific playbooks

**Examples:**

* Create a U.S.-focused and EU-focused version of your Vendor playbook
* Tailor a more aggressive fallback strategy for early-stage deals

***

## Build hybrid playbooks

Combine rules from different sources to create a custom workflow for a specific contract type.

**Examples:**

* MSA + DPA hybrid for SaaS agreements
* Commercial + Lease playbook for franchise agreements

***

## Flexible creation options

Build your playbooks however you prefer:

* Use out-of-the-box benchmark playbooks
* Manually write rules from scratch
* Upload redlined contracts to generate rules
* Import and modify existing internal playbooks

***

## Version control

You can create and manage different versions of the same playbook for different use cases:

* Track changes over time
* Compare versions used by different teams
* Maintain a history of fallback evolution

***

## Shared learning

As you save successful redlines and fallback examples, LOIS for Word improves future suggestions across all playbooks that use those rules.

* Shared rules benefit from shared feedback
* Rule improvements apply automatically across linked playbooks
* You can still choose to break links for one-off adjustments

***

## Efficiency benefits

This system gives you both **consistency** and **flexibility**:

* Write rules once, reuse everywhere
* Minimize redundant work
* Easily spin up new playbooks for specific teams or use cases
* Maintain alignment while supporting variation

***