Status, tags, and risk

Beyond the contract text itself, three pieces of metadata do most of the work organising your portfolio: status, tags, and risk level. Understanding what they’re for makes the dashboard, filters, and reports useful.

Status — where the contract sits in its lifecycle

Every contract has exactly one status. The options:

• Draft — being drafted or under internal review. Hasn’t been signed yet.
• Active — signed and in force. The default for most contracts in a working portfolio.
• Expired — past its end date.
• Terminated — ended before its natural expiry.
• Superseded — replaced by a newer agreement.

A contract is also tagged “In review” automatically in the UI whenever it has an in-progress review — that’s a derived badge, not a status you set. The five values above are the only ones you choose between.

Status drives:

• The dashboard’s “Active contracts” tile counts only active rows.
• The default filter on the Contracts page hides expired, terminated, and superseded unless you explicitly include them.
• Key-date reminders fire only on active contracts (no point reminding you about an expired NDA).

Status is set manually — Clment never auto-promotes a contract. The discipline of setting it correctly is what makes the dashboard accurate.

Tags — your own taxonomy

Tags are free-form strings you attach to contracts. Use them however your team likes:

• By counterparty industry — healthcare, government, finance
• By contract family — nda-mutual, msa, sow, dpa
• By project or year — q3-2024, project-aurora, vendor-2024
• By status nuance — awaiting-counter, legal-review-needed, cfo-signoff-required

A contract can have any number of tags. Filters on the Contracts page support multi-select with AND logic.

Style tips that pay off:

• Pick a separator convention and stick to it — kebab-case or snake_case, not both.
• Avoid synonyms — pick vendor OR supplier, not both.
• Don’t tag what’s already a real field. active is a status, not a tag. nda could go either way — we recommend using the Type field, but if you want both that’s fine.

To rename a tag across many contracts, contact support; we’ll batch-update.

Risk — your subjective signal

Risk is a five-level enum: Unknown, Low, Medium, High, Critical.

Contracts start at Unknown when uploaded — Clment doesn’t auto-classify risk. You set the level once you’ve looked at the contract. Risk is your team’s subjective answer to “if this contract goes wrong, how badly?”.

What risk drives:

• Sort and filter on the Contracts page — “show me all high-risk contracts expiring in the next 90 days” is a common executive-review query.
• The risk-distribution chart on the dashboard.

A reasonable convention to start with:

• Critical — would materially affect company outcomes if it goes wrong (key customer, top supplier, M&A, IP licensing of core tech).
• High — significant exposure but recoverable (large-budget vendor, multi-year SaaS commitment, exclusive partnership).
• Medium — meaningful but standard (mid-size vendor, standard MSA).
• Low — boilerplate / low-stakes (mutual NDA, standard order form).
• Unknown — not yet classified. Useful as a “needs review” filter.

Refine the rubric for your business; consistency matters more than the exact thresholds.

Setting tags in bulk

You can multi-select rows on the Contracts page and use Bulk tag to add or remove a tag across all of them at once. Useful right after a back-catalogue upload.

Status and risk are set per-contract from the contract page — there’s no bulk-edit for those today.

See also

• Searching and filtering
• Key dates and reminders