← Tenderely BPM
MODULE
Contract management end to end in one flow.
Signing is not the end of a contract process but its middle. The real risk comes after: nobody watches the end date, and the contract either renews itself or lapses unnoticed. Tenderely BPM keeps tracking the contract after the signature.
What does a contract process repeat?
01
Request and draft
For which deal, with which party, from which template — without a structured request, legal asks the same questions every time.
02
Internal approval
Approval steps change with value and type, so who must sign off has to follow a rule.
03
Negotiation rounds
Changes from the other side and which version is current must be tracked; signing the wrong version is a real risk.
04
Signature
Signing order and signatory authority belong on the record, and the executed copy in one place.
05
Obligations in force
Commitments that are not put on a calendar are remembered only when they are breached.
06
Expiry and renewal
Miss the notice period on an auto-renewing contract and you are committed for another term.
Where does this break down today?
Contracts live in a folder
Executed copies sit in a shared drive or a drawer, and because nobody asks when each one ends, nobody knows.
End dates slip
A contract noticed after the notice period has passed stays in force for another term.
The current version is unclear
Files bouncing through e-mail produce "final_v3_latest", and sometimes the wrong version gets signed.
Nobody is sure who approves
The rule is in a policy document but enforcing it depends on memory, and the gap surfaces at audit.
What changes with Tenderely BPM
01
Requests arrive structured
Party, subject, value and term come in as fields, so legal is not chasing missing information.
02
Approval branches on value
Who signs off is decided by rule, and the rule lives in the flow rather than in a document.
03
Versions on the record
Each round is a step, so which file arrived when — and which version is current — is visible.
04
End dates warn you
Renewal and notice dates drive timers, and the person responsible is warned as they approach.
05
The counterparty joins from outside
A public form link lets them upload documents or give approval without an account.
FAQ
Does it track contract end dates?
+
Yes. Expiry and notice dates are fields on the record, timers run against them, and an approaching renewal reaches the person responsible as a warning. The renewal decision can itself be a step.
Can we use electronic signature?
+
The process manages the signature step and the upload of the executed copy; which signing method you use is up to you. Who approved which version, and when, is recorded either way.
Can we use our own templates?
+
Yes. Your template file attaches to the record and travels with the fields from the request form. Which template applies to which deal can be decided conditionally.