Contract valid-through dates

Required agreements need a clear end date—not “signed forever” by default.

Why we built it

Facilities treat signed storage agreements as current for a season or membership year, then expect renewal or re-sign. Contract valid-through dates add Agreement term controls on each contract template: choose 3, 6, 12, or 24 months from signing, pick until a specific date, or leave the agreement non-expiring. Expiry is computed from the customer signature timestamp (calendar end dates take precedence over month counts). Templates marked required feed Required agreement alerts so the dashboard and contacts list can flag missing or expired coverage.

Who it is for

• Admins editing templates under Settings → Contracts and documents.
• Teams aligning PDF language with real renewal cycles (calendar-year clubs, annual storage terms).
• Staff pairing term settings with Update agreements when cars change when fleets turn over mid-term.

What you can do

• Select a preset month count from signing for standard storage agreements.
• Switch to Until a date for fixed cutoffs (for example January 1 renewal).
• See a plain-language summary on the template (Valid for 12 months from signing or Valid through YYYY-MM-DD).
• Combine with required template flags so expiry drives compliance alerts—not manual spreadsheet tracking.

How it fits your day

Set 12 months on your main storage PDF, mark it required, and let alerts tell you who needs a new agreement after the term. Use a calendar end date when every customer should roll on the same day regardless of when they signed.

Get started

Open your primary storage template, set Agreement term to 12 months, save, and confirm the summary text. Send a test contract, sign it, and verify Required agreement alerts show the expected expiry window on that customer.