How the pieces of ExpiryEdge fit together
A quick mental model of how expiries, types, templates, directory, workflows, reminders, and reports relate to each other.
What is it
ExpiryEdge is built around one core object - the expiry (a single deadline/renewal/obligation) - surrounded by features that either add structure to expiries, add context to them, act around their dates, or report on them afterward.
Why / when to use it
- Structure (classify and enrich what an expiry is): Expiry Types are simple category labels; Templates add reusable structured custom fields on top of that.
- Context (who/what an expiry relates to and what supporting material exists): the Directory holds vendor/contact/asset records you link to expiries; Documents and per-expiry Attachments hold the actual files.
- Action (what happens as the date approaches): Reminders send notifications; Workflows run a tracked, multi-step checklist, optionally triggered automatically by an expiry's date.
- Getting data in: create expiries one at a time, or in bulk via Bulk Import (from a spreadsheet you already have) or AI Smart Upload (from unstructured documents).
- Oversight: the Calendar gives a date-first view; Insights gives live analytics; Monthly Reports give dated PDF snapshots; the Activity Log gives a full audit trail; Shared Compliance Portals let you expose a read-only slice to outsiders.
- Everything else - Teams & Users, Billing, Settings, Docs, Integrations - is account/organization plumbing that supports the above rather than being about expiries directly.