Contract Repository Best Practices

Lisa Dannewitz · Friday

The Contract Repository in Contract Management Pro is the authoritative record for all executed contracts. For it to function correctly — delivering accurate search results, reliable reporting, and key lifecycle features like Amendments — two foundational configurations must be in place before go-live: Contract Repository Mappings and Contract Model Assignment. This article explains both: what they are, why they matter, and how to get them right.

1. Contract Repository Mappings

What It Is

When a contract request (CMR) reaches a Status of Contract Signed and a State of Closed Complete, CM Pro automatically creates a corresponding CNTR record in the Contract Repository. This CNTR creation is triggered by the Contract Configuration record — a setup object that maps your request table to the repository table and defines applicable conditions.

The Contract Configuration record includes a related list for Contract Repository Mappings — these are the field-level mappings that define which request fields populate which contract fields. In practice, implementors create the Contract Configuration record but commonly skip the next step, treating the field mappings as optional. Without them, the CNTR record is created, but its key fields remain blank.

Why It Matters

The Contract Repository Mappings should not be treated as optional. The CNTR record drives all downstream contract management. Blank fields have immediate and cascading consequences:

Key dates (start, end, renewal) are missing, so expiration alerts and renewal workflows do not trigger
Company and owner fields are empty, so search and filter by these values return no results
Financial fields like contract value are absent, breaking spend analysis and reporting

Best Practice: configure Contract Repository Mappings as part of your initial implementation, before any contract requests are submitted in production. Retroactive remediation of blank CNTR fields requires manual data correction at scale.

How to Configure

Field mappings are configured on the Contract Configurations. The general steps are:

Navigate to All > Contracts Core > Contract Administration > Contract Configurations
Open the Contract Configuration record for your contract type. If one does not exist, create a new record specifying the Request Table, Contract Repository, and Document Type.
In the Contract Repository Mappings related list within the Contract Configuration record, add a new mapping for each request field you want to carry over to the CNTR. Set the Mapping Type, Map From Field (on the request), and Map To Field (on the CNTR).
Save and test by submitting a sample contract request and verifying the resulting CNTR record is fully populated.

📄 Full documentation: Contract Configuration

2. Contract Model Assignment

What It Is

The Contract Model for the repository record is the field equivalent to the Contract Type for the contract request. It acts as a template that the system references when performing contract lifecycle actions — most critically, Amendments. Each contract type used in your implementation must have a corresponding Contract Model configured.

Why It Matters

The Amendment feature in CM Pro relies on CNTR records having a value set for Contract Model. If the Contract Model is blank, the Amendment action will not be available on that record — regardless of its status or any other configuration.

Best Practice: Review your list of active contract types before go-live and confirm a Contract Model is associated with each one. Add this to your implementation checklist as a required sign-off step.

How to Configure

Contract Models are configured in the CM Pro administration area. The general approach is:

Navigate to All > Contracts Core > Contract Administration > Contract Types
Identify all active contract types your organization will use in CM Pro.
For each contract type, associate a Contract Model in the embedded list.
Map only one contract model to a contract type.

📄 Full documentation: Create a Contract Type

Summary

Both Contract Repository Mappings and Contract Model Assignment are foundational to a healthy Contract Repository. They are not optional enhancements — they are prerequisites for the system to operate as designed.

Configuration	What Breaks Without It	When to Configure
Contract Repository Mappings	Key dates, company, and value fields are blank; search, reporting, and lifecycle alerts fail	Before the first production contract request is submitted
Contract Model Assignment	Amendment feature is unavailable for that contract type	Before each contract type is used in production

For complete step-by-step configuration guidance, refer to the product documentation:

📄 Full documentation: Contract Management Pro Documentation