SignSecure
Start free
Contract renewal eSignature

Renewals that sign themselves out on schedule

Contract renewal eSignature works best when nobody has to remember it. Set the number of days before term end, and a date-triggered Flow builds the renewal, sends it for signature, chases it on a cadence you choose, and files the signed PDF back on the account. Your team finds out it happened by seeing it done.

Start free See the Flow actions
Term ends 30 Nov T minus 60 days, trigger Scheduled Flow Send for Signature Renewal 2027 sent to Amara Whitfield Renewal-2027.pdf signed, filed on the account

Contract renewal eSignature on a date-triggered Flow

Everything below is standard Salesforce automation plus one invocable action. An admin can build it in an afternoon and nobody has to touch it again.

  1. 1
    Pick the date fieldContract end date, subscription term end, or your own custom date field on the account.
  2. 2
    Set the lead timeA scheduled path 60 days before that date, or whatever number your commercial terms need.
  3. 3
    Filter to the right recordsActive contracts, auto renew off, value above a threshold, whichever entry criteria fit.
  4. 4
    Call Send for SignaturePass the record id, the renewal template and the signer contact. The action does the rest.
  5. 5
    Let the merge fields fillNew term dates, pricing and the entity name arrive from the record, not from a rep.

The full Flow action reference

Flow: Renewal out for signature Scheduled path, T minus 60 Entry criteria Status = Active, Auto_Renew = false Send for Signature recordId, template, signer Update record Renewal_Status__c = Sent no code needed no scheduled job

Reminder cadence, expiry and escalation

Once the renewal is out, the chasing is a setting rather than a task. Three controls cover it, and each one is configured on the template so every renewal behaves the same way.

Cadence

Reminders on a rhythm you choose

A common pattern is day 3, day 7 and day 14 after send, then weekly. Reminders stop the instant the document is signed, so nobody is nudged about something they already did.

day 0 day 3 day 7 day 14
Expiry

A deadline that means something

Give the renewal an expiry date, comfortably before term end, and the link closes on that day. The record shows expired rather than open forever, so your pipeline of paper stays honest.

30 days open STATUS EXPIRED
Escalation

A human hears about it in time

Because status writes back to the record, a Flow can watch it. If the renewal is still unsigned at day 21, notify the account owner, create a task, or post to a Slack channel while there is still runway.

DAY 21, STATUS AWAITING Notify account owner Create a follow-up task Post to the team channel

More on automated signature workflows

Renewal reporting

Renewal reporting once the signed PDFs land on their own

Every completed renewal writes its facts back to the account record and files its sealed PDF there. That turns renewal tracking from a spreadsheet somebody maintains into a dashboard that maintains itself.

A live renewal book

Signed date, signer, status and time to sign all arrive as field values on the account, so a report can group renewals by quarter, by owner or by value and stay correct without anyone updating it. The signed PDF sits on the same record, which means a row in the report is one click from the executed document rather than a search through shared drives.

Next term end dates

Signed date plus term gives the next end date automatically, which is what the following year of scheduled paths runs on.

Renewal rate without a spreadsheet

Count completed against sent for any period. The numbers come from field values, so two people asking get the same answer.

How long renewals take

Time to sign is stored per agreement, so you can see whether a shorter lead time would actually help.

The paper trail is right there

Sealed PDF and certificate of completion sit together on the account, ready for audit or a diligence request.

Feeds next year's schedule

The written-back dates are what the next scheduled path reads, so the cycle continues on its own. See how the write-back works.

Questions about scheduled renewals

The practical things admins ask before they build the first Flow. Setup help is included with every paid plan, so you do not have to work it out alone.

Start free
Does this need code?
No. A record-triggered Flow with a scheduled path, or a scheduled Flow, calls the Send for Signature action with plain configuration. The Flow page lists every input.
Can different contracts use different lead times?
Yes. Put the lead time in a field on the record and let the scheduled path read it, or run separate Flows for separate contract types.
What if the terms change before it is signed?
Cancel the request from the record and send the new version. The cancellation and the reason are recorded on the history, so the trail stays complete.
Does a busy renewal quarter cost more?
No. Paid plans include unlimited documents at $12 per user per month billed annually, so volume never changes the invoice. Full detail on pricing.
Can our side countersign automatically?
Name a standing countersigner on the template and the second signature is requested the moment the customer finishes.
Which objects can this run on?
Contract, Account, Opportunity, Quote or any custom object your admin built, including the ones your renewals live on today.

Put next quarter's renewals on a schedule

Start free, build the Flow once, and the renewals go out whether or not anyone remembers them.

Start free See pricing