Workflow template for operations and process improvement

Outstanding signatures follow-up list

Twice a week and before month end, whoever sends documents for signature gets one list from the e-signature tool's status export: what is waiting, on whom and for how long, what expires soon, what was declined or expired, and a reminder drafted for each waiting signer. Nothing is sent.

View this template on GitHub

Put this on your planBuild this in a sprint

Add it to a workflow in the FullyPowered Planner, beside the teams and roles that will run it. Book a fit call

The outcome

Nothing sits unsigned because nobody noticed. Every document still out for signature appears once, with the person it is waiting on, how long it has been with them and how long since they last touched it. Where documents are signed in a set order, the list names the one signer holding everyone behind them, so the follow-up goes to the right person instead of the whole chain.

Documents about to expire are pulled to the top before the signing request lapses, and documents that were declined or have already expired are set apart as decisions for the person who sent them. For every signer a reminder is due to, under your team's own rules, a short reminder is ready for the sender to read, adjust and send. A count at the top ties every document and every row back to the export, so nothing drops out between the tool and the list.

It reads the status export only, never the documents themselves. It sends no reminder, resends nothing, voids nothing and changes no record: a person does each of these. It says nothing about whether a signature is valid or a document binding.

Who starts the work, and when

The operations coordinator, the office manager or the sales operations person who sends documents out for signature runs it twice a week, and again in the last days of the month, when unsigned order forms and renewals cost the most. Each run starts from a fresh status export, so the list always reflects what the tool shows that morning.

Each sender approves the reminders for their own documents and decides what happens to anything declined or expired.

What they supply

  • The status export from your e-signature tool, one row for each signer of each document, with the columns document_id, document_name, document_type, sender, sent_at, recipient, recipient_role, signing_order, status (sent, viewed, signed, declined, expired or voided), last_activity_at and expires_at. If a column is named differently, or a status word is one the list does not know, the work stops and asks. It also stops and asks when a document and signer appear twice, the rows of one document disagree, signing order mixes blank and numbered, or activity is dated before sending.
  • Your team's follow-up rules: after how many days without activity a reminder is due, which document types are urgent and get a shorter wait, how many days ahead to warn of an expiry, and, for each kind of signer, who may remind them, or that they are never reminded from this list.
  • Today's date, when the export was taken, and who runs the list: the name or role that appears on it and in its questions.

What comes out

One follow-up list in a fixed order: what is waiting for a signature, with the signer each document waits on and the days in hand; what expires within the warning window; what was declined or has expired, as a decision for the sender; a drafted reminder for each signer due one, marked with who sends it; what is closed and needs nothing; and numbered questions. A count at the top shows every document and every row of the export accounted for.

Each reminder states only what the export shows: the document's name, who sent it, when it reached the signer and when the request expires. It carries no signing link; the sender sends it from the tool or adds the link.

An example

Illustrative example with sample data. The business, its clients, the people, the documents and every date below are illustrative. Company A is an illustrative 45-person commercial cleaning business. Its clients appear as Client B to Client M. Kit Alvarez, the sales operations coordinator, sends service orders and renewals out for signature for the two account managers, Maya Ostrander and Joel Pemberton; Tomas Reyner, the operations director, approves some orders before the client signs. Every person named is illustrative.

On the morning of Tuesday 24 November 2026, a week before month end, Kit exported the status of every open signing request and ran the list. The inputs come first, in full, so the workflow template can be run on them. The draft list it returned follows.

The inputs

1. The status export from your e-signature tool: signature_status.csv

One row for each signer of each document, with the columns document_id, document_name, document_type, sender, sent_at, recipient, recipient_role, signing_order, status, last_activity_at and expires_at.

document_id,document_name,document_type,sender,sent_at,recipient,recipient_role,signing_order,status,last_activity_at,expires_at
D-201,"Service order, Client B, office cleaning 2027",Service order,Maya Ostrander,2026-11-12 10:05,Lena Brookfield,Client signer,1,viewed,2026-11-16 14:20,2026-12-12
D-202,"Renewal order form, Client C",Renewal order form,Maya Ostrander,2026-11-18 09:00,Tomas Reyner,Internal approver,1,signed,2026-11-19 11:40,2026-11-28
D-202,"Renewal order form, Client C",Renewal order form,Maya Ostrander,2026-11-18 09:00,Grace Ilunga,Client signer,2,viewed,2026-11-20 16:05,2026-11-28
D-202,"Renewal order form, Client C",Renewal order form,Maya Ostrander,2026-11-18 09:00,Henrik Salo,Client executive sponsor,3,sent,2026-11-18 09:00,2026-11-28
D-203,"Site access form, Client E",Site form,Joel Pemberton,2026-11-23 15:30,Ana Kowal,Client signer,1,sent,2026-11-23 15:30,
D-204,"Service order, Client F, window cleaning",Service order,Joel Pemberton,2026-11-09 11:00,Rhea Castellan,Client signer,1,declined,2026-11-13 09:12,2026-12-09
D-205,"Renewal order form, Client G",Renewal order form,Maya Ostrander,2026-10-26 10:00,Paul Ndiaye,Client signer,1,expired,2026-11-02 08:30,2026-11-23
D-206,"Price change acknowledgement, Client H",Acknowledgement,Joel Pemberton,2026-11-10 14:00,Marta Quill,Client signer,1,voided,2026-11-11 09:45,2026-12-10
D-207,"Service order, Client J, deep clean",Service order,Maya Ostrander,2026-11-16 13:00,Ivo Marchetti,Client signer,1,signed,2026-11-17 10:10,2026-11-30
D-207,"Service order, Client J, deep clean",Service order,Maya Ostrander,2026-11-16 13:00,Sunita Varga,Client finance approver,1,viewed,2026-11-19 12:00,2026-11-30
D-208,"Service order, Client K, carpet care",Service order,Joel Pemberton,2026-11-17 09:30,Ben Okafor,Client signer,1,signed,2026-11-18 16:45,2026-12-17
D-209,"Service order, Client L, floor care",Service order,Joel Pemberton,2026-11-19 08:00,Tomas Reyner,Internal approver,1,viewed,2026-11-19 09:30,2026-12-19
D-209,"Service order, Client L, floor care",Service order,Joel Pemberton,2026-11-19 08:00,Bea Thornton,Client signer,2,sent,2026-11-19 08:00,2026-12-19
D-210,"Service order, Client M, 2027 renewal",Service order,Maya Ostrander,2026-11-13 09:00,Owen Hartley,Client executive sponsor,1,viewed,2026-11-17 10:00,2026-11-27

2. The team's follow-up rules, with today's date (typed by Kit)

Team: Sales operations, Company A
Today: Tuesday 24 November 2026
Export: signature_status.csv, exported 24 November 2026 08:30
Runs it: Kit Alvarez, sales operations coordinator
Reminder after: 3 days
Urgent document types: Renewal order form
Urgent reminder after: 1 day
Expiry window: 7 days
Reminders, by recipient_role:
- Client signer: the sender
- Internal approver: Kit Alvarez
- Client executive sponsor: not reminded from this list (the account manager raises it in person)

The output

OUTSTANDING SIGNATURES FOLLOW-UP LIST: Sales operations, Company A, Tuesday 24 November 2026

For: Kit Alvarez and each sender. Prepared from signature_status.csv (14 rows, 10 documents), exported 24 November 2026 08:30; the team's rules (as supplied).
Count: 10 documents = 6 waiting + 1 declined + 1 expired + 1 voided + 1 fully signed.
Rows: 3 signed + 5 viewed + 3 sent + 1 declined + 1 expired + 1 voided = 14 rows in the export.
Waiting signers: 6 = 3 reminders drafted + 1 not yet due + 1 not reminded under the rules + 1 held for a question. Later signers not yet reached: 2.

1. Waiting for a signature
D-202 Renewal order form, Client C (Renewal order form, URGENT). Sent by Maya Ostrander on 18 November 2026, 6 days ago. Expires 28 November 2026.
  Waiting on: Grace Ilunga (Client signer, signing order 2), viewed, with them since 19 November 2026 (5 days), no activity for 4 days.
  Blocking 1 later signer: Henrik Salo (Client executive sponsor).
  Already signed: Tomas Reyner (Internal approver), 19 November 2026.
  Reminder: due, see R1.
D-201 Service order, Client B, office cleaning 2027 (Service order). Sent by Maya Ostrander on 12 November 2026, 12 days ago. Expires 12 December 2026.
  Waiting on: Lena Brookfield (Client signer, signing order 1), viewed, with them since 12 November 2026 (12 days), no activity for 8 days.
  Reminder: due, see R2.
D-210 Service order, Client M, 2027 renewal (Service order). Sent by Maya Ostrander on 13 November 2026, 11 days ago. Expires 27 November 2026.
  Waiting on: Owen Hartley (Client executive sponsor, signing order 1), viewed, with them since 13 November 2026 (11 days), no activity for 7 days.
  Reminder: not reminded: the account manager raises it in person.
D-207 Service order, Client J, deep clean (Service order). Sent by Maya Ostrander on 16 November 2026, 8 days ago. Expires 30 November 2026.
  Waiting on: Sunita Varga (Client finance approver, signing order 1), viewed, with them since 16 November 2026 (8 days), no activity for 5 days.
  Already signed: Ivo Marchetti (Client signer), 17 November 2026.
  Reminder: held, see question 1.
D-209 Service order, Client L, floor care (Service order). Sent by Joel Pemberton on 19 November 2026, 5 days ago. Expires 19 December 2026.
  Waiting on: Tomas Reyner (Internal approver, signing order 1), viewed, with them since 19 November 2026 (5 days), no activity for 5 days.
  Blocking 1 later signer: Bea Thornton (Client signer).
  Reminder: due, see R3.
D-203 Site access form, Client E (Site form). Sent by Joel Pemberton on 23 November 2026, 1 day ago. No expiry date.
  Waiting on: Ana Kowal (Client signer, signing order 1), sent, with them since 23 November 2026 (1 day), no activity for 1 day.
  Reminder: not yet due, next due 26 November 2026.

2. Expiring by 1 December 2026 (within 7 days)
D-210 Service order, Client M, 2027 renewal: expires 27 November 2026, in 3 days. Still to sign: Owen Hartley (Client executive sponsor).
D-202 Renewal order form, Client C: expires 28 November 2026, in 4 days. Still to sign: Grace Ilunga (Client signer), Henrik Salo (Client executive sponsor).
D-207 Service order, Client J, deep clean: expires 30 November 2026, in 6 days. Still to sign: Sunita Varga (Client finance approver).

3. Declined or expired: a decision for the sender
D-204 Service order, Client F, window cleaning (Service order), sent by Joel Pemberton on 9 November 2026: declined by Rhea Castellan (Client signer) on 13 November 2026. Signed before it stopped: nobody. For Joel Pemberton to decide what happens next.
D-205 Renewal order form, Client G (Renewal order form, URGENT), sent by Maya Ostrander on 26 October 2026: expired on 23 November 2026. Signed before it stopped: nobody. For Maya Ostrander to decide what happens next.

4. Reminder drafts, for approval before sending
R1. To: Grace Ilunga (Client signer). Sent by: Maya Ostrander. About: D-202.
Subject: Signature needed: Renewal order form, Client C
Hello Grace,
Maya Ostrander sent you Renewal order form, Client C for signature, and it reached you on 19 November 2026.
It is now your turn to sign, and one more person signs after you.
The signing request expires on 28 November 2026.
When you have a moment, please review and sign it,
or reply to me if anything needs to change first.
Thank you,
Maya Ostrander
R2. To: Lena Brookfield (Client signer). Sent by: Maya Ostrander. About: D-201.
Subject: Signature needed: Service order, Client B, office cleaning 2027
Hello Lena,
Maya Ostrander sent you Service order, Client B, office cleaning 2027 for signature, and it reached you on 12 November 2026.
The signing request expires on 12 December 2026.
When you have a moment, please review and sign it,
or reply to me if anything needs to change first.
Thank you,
Maya Ostrander
R3. To: Tomas Reyner (Internal approver). Sent by: Kit Alvarez. About: D-209.
Subject: Signature needed: Service order, Client L, floor care
Hello Tomas,
Joel Pemberton sent you Service order, Client L, floor care for signature, and it reached you on 19 November 2026.
It is now your turn to sign, and one more person signs after you.
The signing request expires on 19 December 2026.
When you have a moment, please review and sign it,
or reply to me if anything needs to change first.
Thank you,
Kit Alvarez

5. Closed: no follow-up
Voided: D-206 Price change acknowledgement, Client H, voided 11 November 2026.
Fully signed: 1 (D-208).

6. Questions for Kit Alvarez
1. D-207 Service order, Client J, deep clean: Sunita Varga's role, "Client finance approver", is not in the reminder rules, so no reminder was drafted. The document has been with her for 8 days with no activity for 5, and the request expires on 30 November 2026. May a client finance approver be reminded from this list, and who sends it?

Draft for Kit Alvarez and each sender. Read from the status export only; no document was opened.
Nothing has been sent, resent or voided, and no record has been changed.

Where it fits

  • Operations and process improvement, which keeps paperwork moving and owns the twice-weekly sweep.
  • Sales, where an unsigned order form at month end is revenue that slips into next month.
  • Executive and office support, where the office manager chases signatures for owners, partners and directors.
  • Professional services, where engagement letters and statements of work wait on a client signer before work can start.
  • Real estate, where leases, renewals and addenda pass through several signers in a set order.
  • Software and technology, where order forms and renewals go out in batches before the quarter closes.
  • Established businesses, where dozens of documents are out at once and the follow-up lives in one person's inbox.
  • Growth and scaling, when the number of documents out for signature outgrows a weekly glance at the tool.

What has to change for your company

Map your tool's export columns to the ones the workflow template expects, and list the status words your tool uses. Write down your follow-up rules once: the wait before a reminder, the document types that are urgent, the expiry warning window, and for each signer role who may remind them, so a client's executive is never chased by the wrong person. Agree who answers the questions the list raises. It runs in ChatGPT, Claude, Copilot or Gemini, from the export you supply; it needs no connection to your e-signature tool.

What has been checked

FullyPowered AI wrote this workflow template. It was editorially reviewed on 19 November 2026. It was tried on its example on 19 November 2026; the record is published with it, with the small edits made afterward and a second run on the edited example by the editing session, not a blind run. It has not yet been tested in a client environment, and has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.

Testing in your environment means running it on two or three past exports your team remembers well, with hard cases written in advance: a renamed column, a status word your tool uses that the list does not know, a document signed in order where the second signer is holding it, a signer role missing from your rules, a request past its expiry date that still shows as waiting. The person who runs it checks every line against the tool before any reminder goes out. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.

Who decides

People decide

Your people keep

  • Which reminders are sent, and by whom
  • What happens to a document that was declined or has expired
  • Answers to the questions the list raises
By design

It does not

  • Sends no reminder
  • Resends nothing
  • Voids nothing
  • Changes no record
  • Says nothing about whether a signature is valid or a document binding

Questions people ask

Who is this for?

Whoever sends documents for signature: an operations coordinator, office manager or sales operations coordinator. It runs twice a week and again late in the month.

What do I need to supply?

The status export, your team's follow-up rules, today's date and who runs the list.

Does it send the reminders?

No. It drafts a reminder for each signer due one, and the sender reads, adjusts and sends it. It resends and voids nothing.

Does it need a connection to my e-signature tool?

No. It reads the status export you supply, never the documents themselves, and runs in ChatGPT, Claude, Copilot or Gemini.

What has been checked?

It was editorially reviewed and tried on an example. It has not yet been tested in a client environment, or as a packaged version in ChatGPT, Claude, Copilot or Gemini.

What it connects to

The business systems this workflow template works with, what it reads from each and what it writes to it, from a reviewed reading of its own text.

Writes to it: nothing.

What it connects to
How it works with the systemReads from it
Works from an export from an e-signature service.Reads from itEach signer of each document with its status, sent and expiry dates.

The full workflow template

Everything above is the outline. The complete workflow template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in FullyPowered’s public repository.

View the full template

Free with an account. Sign in by email: no password and no card.

Next step

Put this workflow template to work for your team: on your plan, or built with you in a sprint.

  1. 01

    The full workflow template

    Free with an account. Sign in by email: no password and no card.

  2. 02

    FullyPowered Planner

    Add it to a workflow in the FullyPowered Planner, beside the teams and roles that will run it.

  3. 03

    Build this in a sprint

    In a sprint, FullyPowered adapts this workflow template to your rules, proves it on your own work and puts it in the hands of the roles that own it.

These workflow templates are examples and a starting point, not a complete list. We can build any workflow for your company, including one that runs several steps, in a Workflow Sprint or a scoped implementation.

Rather talk it through first? Book a fit callDiscuss adapting this

FullyPowered Planner. A card to start, everything unlocked, nothing charged for seven days.Security & your informationPlanner termsRefunds