The Contract Types table in EvergreenWorx Contracts is used to define the various classifications of contracts your organization manages. Each Contract Type can optionally require approval and can be linked to one or more Approval Templates, allowing for customizable approval workflows based on the type of contract selected.
This article explains how to manage Contract Types, including how to add and deactivate them.
What is a Contract Type?
A Contract Type record defines the category or structure of a contract, such as Fixed-Price, Time and Materials, Subcontract, or NDA. These types:
-
Help categorize contracts for reporting and lifecycle workflows
-
Indicate whether approval is required before a contract can be activated
-
Control which Approval Templates are available for selection
When a Contract Type has multiple Approval Templates, the user creating the contract will be prompted to select one when initiating the approval process.
How to Add a Contract Type
To add a new Contract Type:
-
In the app, click the Change Area dropdown (lower-left corner of the screen).
-
Select Settings.
-
Under Configuration, click Contract Types.
-
Click New.
-
On the Contract Type form:
-
Enter a Name (e.g., “Fixed-Price Contract”).
-
Set Approval Needed to Yes or No, depending on whether this type of contract requires approval before activation.
-
(Optional) Add one or more Approval Templates using the related subgrid.
-
-
Click Save & Close.
The new Contract Type will now appear in the contract creation process.
How to Deactivate a Contract Type
Deactivating a Contract Type will prevent users from selecting it when creating new contracts, but will not remove it from existing records.
-
Navigate to Settings > Contract Types.
-
In the Active Contract Types view, locate the record you want to deactivate.
-
Select the row, and choose Deactivate from the command bar.
-
Confirm the deactivation.
To view deactivated types later, switch to the Inactive Contract Types view.
Best Practices for Managing Contract Types
-
Use clear and distinct names (e.g., avoid vague labels like “General”).
-
Use the Approval Needed flag to control workflow enforcement.
-
Attach relevant Approval Templates to simplify approval logic and give end users flexibility when more than one applies.
-
Deactivate outdated types instead of deleting them to preserve historical integrity.
-
Regularly review your list of types to ensure they align with business processes and reporting needs.