Here are the core terms you will see across Contracts Connected, and how they fit together: a Project holds Commitments, each Commitment sends a Package of Templates to a Vendor, and those become signed Contracts.
If the terminology feels like a lot at first, that is normal, since most of it maps to how contract administration already works in the field.
The key terms
Project: the top-level container for a single job. Everything you do lives inside a Project.
Vendor: the outside company you contract with, such as a subcontractor or supplier. You manage these on the Vendors page.
Commitment: the unit you create and send to a Vendor. A Commitment combines a Name, a Project, a Package, and a Vendor.
Package (also called Contract Package): a bundle of Templates that go out together in one Commitment.
Playbook: a reusable project profile that applies the right Package plus compliance requirements when you set up a Project.
Template: a reusable document you build once and use across many Commitments, such as a contract, a document request, or an acknowledgement.
Contract: the signable document inside a Commitment.
Contract Signer: the person assigned to sign a Contract. This is a role on the contract itself, not a permission level. (For permission levels, see What do the user roles mean?.)
Task: a to-do or a document request, such as asking a Vendor to upload a certificate of insurance.
What happens next
Once these terms click, the workflow reads cleanly: you create a Commitment inside a Project, it sends a Package of Templates to a Vendor, and you track the resulting Contracts and Tasks through to completion. You will see these same labels reused across the Project, Commitment, and Vendor screens.
If this doesn't work
If a label on your screen does not match this list → the product is actively evolving, so a word may differ in your account. Reply with a screenshot and we will confirm the current wording.
If you are unsure whether something is a Package or a Playbook → a Playbook is chosen at project setup and brings a Package plus requirements with it, while a Package is the document bundle itself. See What is the difference between a Template, a Playbook, and a Package?.
Related Articles
Still have questions? Just reply, and we're happy to help.