The Contracts table holds all contract records. It also controls all associated automation and notifications related to contracts. A representative record is shown below.

Figure 7. Sample contract record.
Required fields, marked with a red asterisk, are: Record Type, Internal Contract Owner, Contract Type, Days in Advance to Notify for Renewal, Contract Title, Contract Description, Contract Start Date, and Contract End Date.

Staff Use Case

This section covers the use case for staff members inside Agiloft.
Each record in the table holds information about an individual contract including details about the contracting party, approval information, attached contract file and supporting documents, and renewal details.

Contract Creation

Contract records may be created by members of the Admin, Contract Creator, Contract Manager, and Contract Owner groups.
Contracts may be created in one of two ways:

• Click New in the Contract table action bar
• Use the Create Related Contract button on the Renewal / Related Contracts tab to create a renewal, subcontract, or amendment from the current contract. This button is available only if the contract is in a Status of Signed, Active, Expired, or Canceled. Creating a new contract with the Create Related Contract button will automatically link it to the current contract by populating the Parent Contract ID field in the newly created record. For a more detailed explanation of creation by this method, see the Handling Related Contracts and Renewals section.

Contracts fall into one of four categories:

• Contracts
• Master Agreements
• Subcontracts
• Amendments

The Record Type field in the common area indicates the contract's category. "Contract" is the default Record Type for newly created contracts. It can be used to indicate either a stand-alone contract or a contract that exists under a master agreement. In the latter case, the Parent Contract ID can be filled in upon creation of the contract. Subcontracts and Amendments will be linked to a parent contract automatically, if they are created by clicking the Create Related Contract button in the parent contract record.

Figure 8. The type of contract is shown in the Record Type field.
Below the Record Type are fields storing the Assigned Team and the Internal Contract Owner. The default Assigned Team is the Contract Manager Team. The Internal Contract Owner is the person responsible for overseeing the contract and ensuring timely renewals and approvals. The list of available owners is filtered to users who are in the Contract Owner Team or the Contract Manager Team. The default Internal Contract Owner is the user who creates the contract record, provided that user is in the Contract Manager or Contract Owner Team. Users in the Contract Manager or Admin group can manually change the Assigned Team and Internal Contract Owner if needed.

Figure 9. The Internal Contract Owner is responsible for overseeing the contract.
Once the appropriate fields are filled in, the contract may be saved in a Status of Draft.
The contract's Status field is changed automatically by the system at appropriate points in the workflow, generally when an action button is pressed or when some condition is met; however, users in the Admin group can manually override the Status if necessary.
Information about the contract requester, external company involved, and locations related to the contract may be added by clicking the lookup icon next to those fields. If a desired Requester, Company, or Location does not exist, a record must first be created in order to link it to the Contract.

Creating companies and contacts during contract creation

In the Contract Party Information section, users can find and link to an existing company, or create new ones as needed. To find an existing company record, use the lookup icon to search for the company. If the contract party isn't found, staff users can add a new company by selecting New Company. Enter the name and address information, then click Create Company.

Figure 10. Create and link to new company records when filling out the new contract form.
Both company and location records are created in the background, and linked to the new contract when the record refreshes.

Figure 11. Company records created in the contract form are automatically linked after record creation.
Similarly, you can create new entries in the people table if the main contact for the contract party is not an existing contact. Select New Contact, enter the information, and click Create Main Contact. Multiple contacts can be created in this way, and then the primary contact can be selected from the Main Contact dropdown.

Figure 12. Create a new contact if the contract party is not yet in the system.
When Contract Requesters submit a new contract through the end user interface, they can enter new company and contact information, but they don't see the buttons to create new records. When a contract is submitted for review, Contract Managers can edit the contract party information, or click the button to confirm the new company or contact and finish adding records.
This setup is intended to prevent end users from creating duplicate companies with slightly different spellings and to ensure that contract managers have ownership and control of this data. Permissions can be changed easily to allow end users to use the buttons to create companies and contacts directly.
Note that it is important for the contract managers to evaluate the new additions and either replace with existing data or click the buttons to create the appropriate background data. Otherwise, the linked data can't be used in print templates and emails.

Creating contract attachments from default print templates

The Attachments tab shows all attached files related to the contract and provides the user with options to create and edit related attachments. For certain contract types, when the Document Source is set to Standard Template or Modified Template, the Print Template to Generate field appears. The Document Source can also be set to 3rd Party or Internal – Other to indicate a document provided by the external contract party, or which has been internally generated but not from a template, respectively. The Print Template to Generate has a default value set based on the contract type. The Create and Attach action button is used to auto-generate a contract document from the MS Word print template specified in the Print Template to Generate field and stored in the Print Template File field. Clicking Create and Attach generates the document and creates an attachment record to hold the attached file. It also increments the Version Number field.
If the Contract Party Information section is not properly filled out and linked to records, a validation action warns the user to finish creating new records before generating the attachment.

Creating contracts and attachments from inbound emails

Attachments can be automatically generated from inbound emails containing attached files. Files from inbound emails are mapped to the Transitional Contract Files field in the contract, assigned a predetermined Attachment Title and Attachment Type value, and then converted into a new attachment record. The file is mapped into the Attached File field in the attachment record. If multiple files are attached to an inbound email, each one is converted into a separate attachment record for that contract.

Figure 13. Attachments are managed and created on the Attachments tab.

Working with attachments

The All Contract Attachments related table is also used to manually create and attach files to the contract, such as performance bonds, signed agreements, or other documents from the contract parties. Create attachments from within the contract record by clicking New on the related table's action bar.
The Select Files > Add/Remove from DS Envelope actions on the action bar can be used to add or remove selected attachments to and from the DocuSign envelope when using DocuSign integration. When these actions are selected, the To Be eSigned field is set to Yes or No, and the DS Files to Sign field on the DocuSign tab is updated with the attachments. The Select Files > Supersede File action sets the Status of the selected file to Superseded.

Figure 14. Attachments can be added or removed from the DocuSign envelope before sending.
For more information on Attachments, refer to the Error! Reference source not found. section.

Tracking insurance certificates

The Attachments tab also holds a related table that can be used to track insurance certificates separately from other types of attachments. Certificates can be found directly in the Insurance Certificates table, and in related tables in both the Company and Contracts tables.

Figure 15. Create and manage insurance certificates on the Attachments tab.
When you add an insurance certificate to a company record, it is automatically linked to all pending or active contracts with that vendor by a daily time-based rule (disabled by default).
To create a certificate from a contract record, click New on the related table action bar; the certificate will be automatically linked to the contract. You will need to look up the company vendor in the For Company Name field when creating certificates from a contract.

Figure 16. Use the lookup icon to find and link to existing insurance certificates.
The Insurance Certificate Owner (defined in the company record) is notified fourteen days before an insurance certificate's Expiration Date. When a certificate expires without being renewed, the Contract Managers of any related active contracts are notified on the date of the expiration.
For more information about insurance certificates and related automation, see the Insurance Certificates Table section.
Another method for managing insurance certificates
You may prefer to manage insurance certificates as contract attachments, instead of using the Insurance Certificates table. For example, if Contract Managers are responsible for renewing and maintaining insurance certificates, it may be best to use the Attachments table to hold the certificates, along with all other types of attached documents for contracts. Managing insurance certificates as contract attachments means the Contract Manager will receive email notifications instead of the Internal Certificate Owner.
If this method makes the most sense for your particular business, you can remove the default Insurance Certificates field from the contract layout. Then, go to the Attachment Type table and edit the record called Insurance Certificate. By default, this record's Status is Inactive; change the Status to Active to make it visible in the Attachments table.

Adding notes and sending emails

Notes relevant to the general contract process are entered into the General Notes field on the Details tab, and notes pertaining to the approval process are entered into the Approval Notes field on the Approvals tab.

Figure 17. The Approval Notes field shows notes from all approvers for the contract.
Emails can be sent to Internal Contacts and External Party Contacts from the Emails tab. First choose the type of Recipient(s) (Internal Contacts, External Party Contacts, or External Party and Internal Contacts), then click the lookup icon to select which contacts to email. Fill out the Email Subject and Email Text fields as needed, select any files to send with the email, then click Send Email.

Figure 18. The Emails tab provides a way to send email to contract parties and include attached files. It also shows all previous related emails.

Renewals and previous contracts

Information about the renewal process is stored on the Renewal / Related Contracts tab. Fields for capturing the Renewal Notification Date and Days in Advance to Notify for Renewal are provided as a default. If relevant, information about the renewal contract or previous contract are automatically updated by the system. Users typically do not manually link contracts.

Related assets

Assets can be linked to individual contracts from the Assets tab. Assets must be added separately to the Assets table before they are available to attach to contracts.

Figure 19. Assets related to the contract are managed on the Assets tab.
Depending on the selection in the Asset Involvement field, different fields appear for the user to input linked assets.

Figure 20. For software assets, fields such as Software Title/Version and Software Manufacturer appear.
For hardware assets, select "For One or More Assets". For software assets, choose "For Software Application". For contracts with no linked assets, use "No Assets" from the Asset Involvement drop-down.

Signing contracts with DocuSign

A Signature tab appears to the right of the Assets tab. This tab contains fields for contract document Signers, and contains all fields related to DocuSign. The DS Files to Sign field holds attached files from the Attachments table that have a To Be eSigned value of Yes. The Refresh Files action button refreshes this field in case changes to the attachments were made in the same session under the contract's Attachments tab.
Fields under the Signers heading are used to populate the signature page of the contract's print templates and to add DocuSign tags if the contract uses DocuSign.
Once the contract is ready to sign, use the Create DocuSign Envelope action button to create a DocuSign Envelope record and attach the files held in the DS Files to Sign field. It also creates a DocuSign Recipient record for each signer. These records are then shown in the related tables for DocuSign Envelopes and DocuSign Recipients on the Signature tab. Only users in the Admin and DocuSign Users groups can access the DocuSign fields on the Signature tab. For more information on DocuSign, refer to the Error! Reference source not found. section and the detailed DocuSign User Manual at http://www.agiloft.com/documentation/docusign-users-manual.pdf.

Figure 21. Contract signers and DocuSign envelopes are managed on the Signature tab.

Handling Approvals

The order and nature of approvals depends on the Workflow Title selected on the Approvals tab. Selecting a Contract Type in the common area filters the available Workflow Title choices. For information on setting up the individual Workflows, refer to the Approval Workflows Table.
The order and nature of approvals depends on the Workflow Title selected on the Approvals tab. Selecting a Contract Type in the common area filters the available Workflow Title choices. For information on setting up the individual Workflows, refer to the Approvals Table section.

Figure 22. The Contract Type filters the available workflows.
To submit a contract for approval, first select the correct Workflow Title from the drop-down provided. Click Create Approvals to generate a set of Approval records in a Status of Queued. Once the records have been created, click Launch Approval Process to update the Status of the contract to Pending Approval and update the Status of the approval(s) with the lowest step number to Pending Approval. There may be more than one approval in the lowest step number for parallel approvals.

Figure 23. Select the Workflow Title to choose the series of approvals needed.
The system automatically notifies the first approver in the sequence. A progress bar also appears in the common area to provide a quick visual reference of the approval process.

Figure 24. The common area shows a progress bar of the approval process.
To advance the contract workflow, an approver will use one of three action buttons to change the Status of the approval record:

• Approve to send the contract to the next approver in the sequence.
• Require Changes to send the contract to the previous approver for changes.
• Permanently Reject if the contract requires significant changes.

Figure 25. Approvers use one of three action buttons to change the status of their approval record.
Both Require Changes and Permanently Reject require the user to enter notes in the Approval Notes field. These notes are appended to the Approval Notes field in the contract record and are also viewable from any other approval record linked to that contract.
As each approval is approved, the system notifies the next approver in the sequence that a contract is pending their approval. A list of all approval records is displayed under the Approvals Needed subsection and automatically updated as approval records are modified.
If a user who is not on the current approval team attempts to approve a contract, the system recognizes the error and prevents the user from completing the approval action.
When all the required approvals are received by the system, the contract Status is automatically changed to Approved.

Handling Related Contracts and Renewals

Related contracts are handled in the Renewal / Related Contracts tab of a contract record.
To create a related contract, select the New Record Type of the contract. The choices in the drop down are filtered by the Record Type of the originating contract. These fields are visible only when the contract's Status is Active, Canceled, Expired, or Signed. Clicking Create Related Contract maps relevant information from the current contract into the new one.

Figure 26. To create a related contract, select the New Record Type and click Create Related Contract.
If the new contract is a renewal, click Create Renewal Contract on the Renewal / Related Contracts tab of the parent contract. This button is only visible when the contract's Status is Active, Canceled, Expired, or Signed. A new contract generated in this way can be edited before saving.
If applicable, the system automatically links renewal contracts to any preceding contracts, creating a chain for auditability. Any assets linked to the preceding contract will be linked to the renewal contract as well. This information and related information on the contract process for renewals are stored in the Renewal / Related Contracts tab. Users typically do not enter information into the Renewal Contract and Previous Contract Information fields manually.

Figure 27. Renewed contracts show details about the previous contract on the Renewal / Related Contracts tab.

Contract Processing

This section covers the remaining Status changes not mentioned in the explanations above.
Once a contract changes to a Status of Signed, the system automatically updates the contract to a Status of Active when the Contract Start Date occurs.
Similarly, the Status is changed when the Contract End Date occurs. If the contract does not have an associated renewal contract, the Status is automatically set to Expired; if the contract does have a renewal, the Status is set to Renewed. If the contract is auto-renewing, the Contract End Date is increased by the Renewal Term in Months and the contract remains Active.
To cancel a contract, click the Cancel Contract button in the common area. Additionally, users of the Admin group can manually change the contract status to Canceled.

Figure 28. Cancel Contract appears in the contract common area.
If the contract has a Status of Approved, the Mark as Signed button is visible in the common area. This button updates the contract Status to Signed.

Figure 29. The Mark as Signed button is a quick way to change the status to Signed.

Turning Off Approvals

Contract Management tables have Approval handling set up by default. The associated processes may be turned off in order to use Agiloft as a contract repository. To turn off Approvals, do the following:

1. Edit field permissions to allow the Contract Manager Group to edit the Contract Status field in their own contracts and in others' contracts.
2. Remove status-changing buttons from the layout: Submit for Approval and Mark as Signed.
3. Remove the Approval tab and related fields from the layout.

For help on configuring table layouts, please refer to the Administrator Reference Manual or online help.

End User Use Case

This section covers the use case for end users in a Contract Management context.
Members of the Contract Creator group are internal employees accessing the system via the end user interface. Contract creators, also called contract requesters, are users who submit requests for contracts but do not work on other users' records. Below is a representative home page for an end user in the Contract Creator group.

Figure 30. Home page for Contract Creators in the default end user interface.

Contract Creation

Users in the Contract Creator group may create contracts by clicking the Submit a Contract link or tab on the home page. A simplified contract form is presented to the end user. Many of the fields are hidden from the layout or restricted by field-level permissions.

Figure 31. Contract Creators see a simplified contract form in the EUI.
In the Contract Party Information section, users can find and link to an existing company and contact, or create new ones as needed. Select New Company and then enter the name and address information. After the contract is submitted for review, Contract Managers can confirm the new company to finish adding a record. Similarly, end users can suggest a new company contact by filling out the fields in the Party Main Contact section of the form.

Once the required information is filled in, the contract can be saved for later revisions. The contract requester can also press the Submit for Review button to request approval from a Contract Manager. Contract requesters can be contacted to update the submitted contract, but they are typically no longer involved in the approval process from this point forward.
After the contract requester submits the contract for review, a contract manager decides whether to continue with the approval process or reject the contract request.

Working with Contracts

At any time, the contract requester can view contracts they previously submitted by clicking the My Contracts tab. Contract Creator group members can edit select fields in contracts they own. Certain fields such as Contract Amount, Contract Start Date, and Contract End Date (among others) are not editable by the contract requester if the contract's Status is Pending Approval, Approved, Signed, Active, Renewed, or Expired. This is to prevent changes to currently active or in process contracts.
The contract requester can view all contracts they have permission to see by clicking on the All Contracts home page link or tab.

Ownership

Records in this table are owned by the Contract Requester. Specifically, a record is owned by the user whose ID matches the number in the Requester ID field. By default, the Contract Requester is the user who created the contract record.

Automation

The Contracts table has the following rules set up. Rules which are run based on a schedule (rather than those which are event-triggered) are identified by the prefix "TB", for time-based.

Create: All New Contract Actions

Purpose: This rule handles all update and linking actions upon creating a new record.
Runs: When created by web or API.
Search Filter: None.
Priority: 1
Actions:

I: All New Contract Actions

I: Set Renewal Notification Date based on Renewal Type

Create/Edit: If Transitional Contract Files field has value, convert to Attachment

Purpose: This rule handles new attachments uploaded to the Transitional Contract Files field by converting them into Attachment records.
Runs: When edited by email, web or API.
Search Filter: R: Transitional Contract Files field changed
Priority: 15
Actions:

C: Convert to Attachment

Summary: This converts the values in the Transitional Contract Files, Transitional Attachment Title, and Transitional Attachment Type fields into a new Attachment record and links it back to the Contract via the Contract ID.

U: Blank out Transitional Contract Files field

Updated Fields: Transitional Contract Files, Transitional Attachment Title, and Transitional Attachment Type.
Updated Values: Null.
Summary: This resets the Transitional Contract Files, Transitional Attachment Title, and the Transitional Attachment Type fields to empty after the conversion takes place.

Edit: Updates by Party

Purpose: This rule handles notifications for contracts that are updated by an outside party without direct access to the system, as well as the Attachment Type and Attachment Title for inbound files.
Runs: When edited by email or web.
Search Filter: R: Updates by Vendor or Customer Team
Priority: 1
Actions:

E: Email Owner and Contract Manager Team of Outside Party Update

Sent To: Contract Manager Team, Internal Contract Owner.
Template Name: Outside party has updated contract.
Summary: This email notifies the relevant users that an outside party has updated the contract.

I: Handle Inbound Files

Edit: All edit actions by web or api

Purpose: This rule handles the processes resulting from changes made by staff or rules.
Runs: When edited by web or API.
Search Filter: None.
Priority: 2
Actions:

I: All Edit Actions with API

Edit: Update Renewal Notification Date if underlying fields change (web, API)

Purpose: This rule updates the Renewal Notification Date if the Contract End Date, Days in Advance to Notify for Renewal, or the Advance Notice Required to Cancel Autorenewal (days) change.
Runs: When edited by web.
Search Filter: R: End Date, Days in Advance, Advanced Notice to Cancel, or Renewal Type changed last user mod
Priority: 3

I: Set Renewal Notification Date based on Renewal Type

Edit: Refresh Approvals when Number of Approvals Needed Changes (web, API)

Purpose: This handles the recalculation of next steps and concurrent approvals when additional approvals are added or removed. This rule will update the Lowest Step, Next Step Number, Concurrent Approvals, and Next Approvals fields in all linked approval records. The linked record action uses a chain through the Latest Contract ID to reach the linked approvals and then runs several update fields actions, each of which is based on a saved search.
Runs: When edited by web or API.
Search filter: R: Number of Approvals Needed Changed last modification
Priority: 10

L: Run Contract Creation Actions in Approval

Summary: The actions below update several fields in the Approvals table.
Chain: Contract  Approval through fields: All Contract Approval Notes, Contract Assigned Team, Contract Company Name, Contract Amount, etc.

U: Set Next Step

Updated Fields: Next Step Number
Updated Values: Use the MT: Same contract, higher Step Number, not Not Needed, sorted ascending by Step Number search.

U: Set Concurrent Approvals

Updated Fields: Concurrent Approvals
Updated Values: Use the MT: Approval for same contract with same step number search.

U: Set Lowest Step Number

Updated Fields: Lowest Step Number
Updated Values: Use the LF: Contract ID matches, sorted by Step Number search.

U: Update Next Approvals in Approval Records

Updated Fields: Next Approvals
Updated Values: Use the MT: Same contract - Step Number matches Next Step Number and Status is not Not Needed search.

TB: Notify of upcoming expirations (disabled)

Purpose: This rule controls the email notifications for upcoming expirations of contracts
Runs: Every 2 days at 3 AM.
Search Filter: R: Renewal date is tomorrow and Renewal Type is not one-time
Priority: 5
Action:

E: Email Contract Owner about Renewal Date

Sent To: User in the Internal Contract Owner field
Template Name: Contract renewal notification date has arrived.
Summary: Reminds the Contract Manager of the impending renewal date of a contract.

TB: Daily Check for Start Date (disabled)

Purpose: This rule checks for contracts whose start date has arrived and changes the Status accordingly.
Runs: Every 2 days at 4 AM.
Search Filter: R: Status is signed and Start Date is today or earlier
Priority: 6

I: Actions When Start Date Arrives

TB: Daily Check for Expiration Date (disabled)

Purpose: This rule checks for contracts whose End Date has arrived and takes the appropriate actions.
Runs: Every 2 days at 2 AM
Search Filter: R: Active contract expired today
Priority: 5

I: Handle Expired Contract

Workflow

The Contracts table has the following default workflow:

Reports

The Contracts table contains the following default Charts/Reports: