Scheduling holds one request and sends it at a future time you pick. A recurring request creates and sends fresh requests on a schedule you set.
Schedule a request for later
You can build a request now and have it go out on a date you choose.
- Open Requests and open the request you want to schedule.
- Work through the builder to the publish step.
- Choose Schedule request and set Select the publish date.
Until that date the request stays scheduled and your client can't see it.
It publishes at the time you set, allowing a little extra for processing.
To change the date, reopen the request and pick a new one. To cancel the schedule and keep editing, choose Unschedule and switch to draft.
When a scheduled request doesn't go out
A scheduled request tries to publish once. If it fails it won't retry on its own, so open the request and either set a new publish date or move it back to draft and schedule it again.
On the AML plan, a scheduled request won't publish if your verification credits have run out. Content Snare emails the request ownerThe one team member assigned to a request. when this happens. Top up your verification credits, then open the request and either set a new publish date or move it back to draft and schedule it again.
Repeat a request on a schedule
Open Requests, choose the Recurring/Bulk tab, then select New recurring request at the bottom of the list. If the list is empty, select Create new recurring/bulk request instead.
For a one-time send to multiple clients, see Send requests in bulk.
Setting up a recurring request:
- Choose the template to send.
- Assign the clients who receive it.
- Choose whether it starts Immediately or On set date.
- Set how often it repeats: Weekly, Monthly or Yearly.
- Set when it stops: Never, on an End date, or after a set Number of occurrences.
- On the Finalize step, choose whether to Close client access after the due date and whether to Leave requests as drafts when created. Both are off by default.
To see every individual request a recurring setup has created, open the recurring request and select View details. You manage each one there the same way you manage any other request.
Each run creates its requests at the time you set and publishes them, unless you've chosen to leave them as drafts. You can see when the next run is due under Next Scheduled Run.
Set the Generated request title with any of four tags, which fill in as each request is created:
{{Client Full Name}}{{Client Company Name}}{{Current Date (month and year)}}, which gives "March 2026"{{Current Date (full)}}, which gives "11.09.2026"
So a title of {{Client Company Name}} BAS {{Current Date (month and year)}} names each request "Acme Pty Ltd BAS March 2026".
Use Standard Request Duration (in days) to set the due date on each request the recurrence creates. The default is 14 days.
Every request that's created by a recurring workflow counts toward your plan's active request limit once it's published.
- If a run would publish more requests than your limit has room for, it fails and creates none of them. The recurring request shows the reason, so free up slots before the next run is due.
- If a run leaves its requests as drafts, it creates all of them, and each draft counts from when you publish it.
To free up slots, see I've hit my active request limit.
You can filter the list by status: Draft (a recurring request you've saved but not activated), Active, Paused or Complete.
Check each request before it goes out
To look over each request before your client gets it, turn on Leave requests as drafts when created under Request Settings on the Finalize step.
For a recurring request you've already set up:
- Choose Edit on it in the Recurring/Bulk list.
- Go to the Finalize step and turn on Leave requests as drafts when created.
- Select Update settings, or Update settings and keep as paused if it's paused.
Each run then creates its requests as drafts, and nothing goes to your clients until you publish each one. The switch is off by default, and any change you make to it applies from the next run.
To find the drafts, open the recurring request from the Recurring/Bulk list. Its details page lists the requests it has created, drafts included. To send a draft, open it and work through the builder to the publish step, as you would any other request.
Each run adds a new set of drafts, whether or not you've published the last set, so check for them after each run.
Before you publish a draft:
- Check the date under When is the request due?, because the run set it when it created the draft. A draft published a week after the run gives your client a week less.
- If Close client access after the due date is on, set a due date of today or later.
Assign clients to a recurring request
You can pick clients from your list, or import them from a spreadsheet during the client step. To import, choose Import from CSV and upload your file.
One CSV import takes up to 500 clients, and anything past row 500 is ignored rather than reported. For a longer list, split it across two or more imports. If any rows have a problem, use Download Errors and Warnings Report to see which ones.
Recurring/Bulk requests and your plan
Recurring and bulk requests are on every plan.