Many companies use fynk not only as a contract repository, but as a system to manage time-critical obligations — especially recurring duties like maintenance, inspections, or compliance checks.
Currently, reminders can be configured, but there is no escalation mechanism if an obligation is not fulfilled on time.
This creates a significant operational and compliance risk.
Real-world use case:
A contract requires maintenance every 6 months
A responsible person is assigned
A reminder is sent before the due date
If the maintenance is NOT performed:
There is no automatic escalation
No visibility for management
No enforcement mechanism
In many industries (manufacturing, healthcare, real estate, etc.), missing such obligations can lead to:
safety risks
legal liability
financial damage
What’s missing:
We need a configurable escalation workflow, for example:
If obligation is overdue by X days → notify responsible person again
After Y days → escalate to manager
After Z days → escalate to a defined escalation group
Optional: change contract status automatically (e.g. “at risk”)
Why this matters:
This is not an edge case — it is a core requirement for contract lifecycle management in any organization dealing with operational contracts.
Without escalation logic, companies are forced to:
build external workarounds
rely on manual tracking
accept unnecessary risk
Suggested features:
Multi-level escalation rules
Time-based triggers
Dependency on document uploads (e.g. proof of execution)
Audit trail for escalations
Dashboard visibility (overdue obligations)
Call to action:
If your organization manages contracts with recurring obligations, this feature is critical.
👉 Please like this request to help prioritize it — this would unlock a major step towards true operational contract management in fynk.