Stop reminders when the engagement scope changes

Stop the request when the underlying work changes

Stop the requests that no longer apply before the client spends time finding documents your team no longer needs.

Your request system handles the chase. When the reply contains supplier invoice PDFs that need to become an Excel schedule, try ParseMill for that next step: extract, review against the source and download a workbook. Reminder scheduling stays in your current tools.

Scope changes can be partial. A project may lose one deliverable while other agreed work continues. Record the boundary so staff do not cancel every request merely because the engagement status changed in another system.

Reconcile active requests with the decision

List affected request references, periods, reason, effective date, approving owner and required notification. Check native portal requests, scheduled messages and personal follow-up tasks. TaxDome: Request list includes distinct request statuses. Microsoft: Follow-up flags distinguishes clearing a flag from marking follow-up complete. Choose records that accurately describe the outcome rather than using a convenient completed label everywhere.

Keep a record of which sending controls were checked. A changed engagement note does not necessarily alter an independent reminder schedule. Verify the actual active work before telling the client that no further requests will be sent.

Apply a partial cancellation

Synthetic example: Riverbend Foods pauses a stock-report project but continues monthly bookkeeping.

The client should receive a clear explanation of which requests are paused and which remain needed. A blanket “ignore previous requests” would make the continuing work harder to complete.

Handle restart as a new decision

If the paused work resumes, review the old requirements before reactivating messages. Dates, document versions and contacts may have changed. Confirm whether the existing evidence remains useful and which items need a new period or description. Retain the original request identity when it is still the same obligation; otherwise create a linked new requirement with a reason.

Do not silently remove the pause note. It explains the elapsed time and the client's reasonable expectation that follow-up had stopped. A restart message should acknowledge the new agreement and state the current action and timing.

Verify that stopping work stops contact

Inspect the next scheduled cycle and any recurring templates. Confirm that paused requirements are absent from outbound messages but still visible to the responsible internal owner. Check that continuing requirements have not accidentally inherited the pause.

A useful test uses one cancelled, one paused and one continuing item. Staff should describe three different outcomes, not three completed documents. the related workflow guide explains accurate reminder states. Use the workflow audit checklist to record accidental reminders after scope changes and identify which independent schedule or handoff caused them.