What the Contracts dashboard is for
Both layers of the module at a glance: the rate sheets the company offers, and the dated agreements customers have accepted, with expiry where it belongs.

Contracts has two layers, and the dashboard names them. A Contract is a reusable rate sheet: line items, labor rates, fees and clauses. A Customer Contract is that rate sheet proposed to and accepted by one customer or national account, with a term, covered buildings and a frozen price snapshot. Contracts are templates. Customer contracts carry dates, expire, and drive scheduled jobs and invoices.

Dashboard

Open Dashboard
Who it is for
The owner, the account managers, and whoever owns renewals.
Without it
An agreement's end date is on a PDF in a folder. Renewals are discovered when the customer stops paying or a competitor's truck turns up, and nobody can say how many rate sheets are actually in use.
What it shows
Two rows of cards. The contract layer: Total Active and Total Draft, drilling into All Contracts. The customer contracts layer: Proposed, Active, Expiring Soon and Expired, drilling into the Customer Contracts grid at the same bucket. Beneath them, By Status and By Tier breakdowns, and a Recent Contracts table with contract name, number, status, tier, how many customers are using it, and created date.
What it is worth
  • Expiry is a number, with a list behind it. Expiring Soon counts agreements ending in the next 90 days and opens them, so the renewal call list is one click.
  • Proposed is the follow-up queue. Agreements sent and not yet accepted are the sales conversations still open.
  • Which rate sheets matter. The Using column says how many customers sit on each contract, so a price change is made with its blast radius known.
  • Two layers, never confused. Draft and Active describe templates; Proposed, Active, Expiring and Expired describe agreements. The dashboard keeps them on separate rows.
Pays for itself the first agreement renewed because it appeared under Expiring Soon three months before its end date.

Where to go next

  • The top row drills into All Contracts; the second row into Customer Contracts, pre-filtered to the card you clicked.
  • For the next twelve months of occurrences these agreements owe, and their value at expiry, see the Obligations Calendar under Analytics.
  • For what the committed agreement revenue is worth by month, see the Revenue Outlook.

Good to know

  • Expiring Soon means the next 90 days. The same window the Customer Contracts grid uses for its Expiring bucket, so the card and the grid reconcile.
  • Expiry lives on the customer contract, never the contract. A rate sheet has no term; only the agreement built from it does.
  • The snapshot is frozen at acceptance. A customer contract shows pricing as accepted, so a later edit to the rate sheet does not silently change a live agreement.
  • Every dashboard is account-wide. Nothing here is scoped to the signed-in user.