Skip to main content
A workflow is a checklist your team follows: what happens when an animal arrives, when an application comes in, when a volunteer joins. You write it once under Settings → Operations & forms → Workflows (or search for “Workflows”), and it runs many times, each time on one record. A running checklist is called a run.
The Workflows settings in RescueConsoleThe Workflows settings in RescueConsole

Workflows, with the checklists you can add from the starting set above your own.

The checklist is written here. The work happens on the record: an animal, a person or an adoption application, where each run appears with its steps to tick.

Who can write and run workflows

Somebody who cannot write a checklist still sees it, what starts it, and its steps, without the controls to change them.

Starting from the standard workflows

When you have no workflows yet, a banner asks Start with the checklists most rescues run? and offers them all at once:
  • Taking an animal in, on animals. It starts by itself on each new animal you add (an animal brought in by an import starts none).
  • Reviewing an adoption application, on adoption applications. It starts by itself on each new application. One added before 13 October 2026 starts only by hand until you set Starts on it. Its steps: read it and reply within two days, check the household answers against the animal, check their vet references, check their landlord’s rental policy, check the Aggravated Animal Cruelty site, search the Public Registry, speak to them, and decide, and say why. One added before 4 November 2026 has the four checks in the middle only if you add them.
  • Starting a new volunteer, on people. It starts by itself when somebody is first approved as a volunteer.
  • Thanking a gift, on people. It starts by itself on the donor when a gift is completed, and begins with a step that sends the donor_thank_you email when somebody ticks it.
  • A new foster placement, on people. It starts by itself on the foster carer when a placement is confirmed: the care sheet, the supplies, and a call due three days in.
  • A surrender request arrives, on people. It starts by itself when a surrender form arrives, by a condition on the form’s kind: reply within a day, ask about the animal, decide what you can offer. Accepting the request waits until the first two are done (see Surrender request), and answering it ticks the third.
  • When a foster application arrives, When somebody offers to volunteer and When a donor form arrives, on people. These start by themselves when that form arrives, and each begins with a step that sends an email when somebody ticks it.
If you have write on Communications, the email templates those steps send are added with them, unless you already have a template with the same key. Every step arrives required and on the task list. Change any of it once you have run it a few times. Some of their steps tick themselves when the record says they are done. In Taking an animal in: Scan for a microchip when the microchip number is filled in, Record the intake details when the intake source is, Photograph them when the animal has a photo, and Write their description when it has a description. In Reviewing an adoption application, Decide, and say why ticks itself when the application is approved or denied. A rescue that added these before 28 October 2026 was given the same, on any of those steps still under its own title with nothing it sends. If you started from these and a newer standard workflow is missing, the banner offers the ones you don’t have yet. A Taking an animal in or Starting a new volunteer added before 28 October 2026 still starts only by hand. To have it start by itself, set Starts on it: when a record is added, for the animals one, and when a volunteer is approved, for the volunteer one.

Making a workflow

1

Open the form

Press New workflow.
2

Name it

Give it a Name, such as “Dog intake”.
3

Choose what it runs on

Choose what it Runs on: Animals, People or Adoption applications. This cannot be changed later.
4

Say what a People checklist is for

For a checklist on People, choose what it is For: anything about a person, volunteering, fostering, adopting or giving. This decides what can start it by itself.
5

Describe it

Add a Description if you like: what it is for, and when to start one.
6

Create it

Press Create workflow.
The new workflow opens with no steps. A checklist with no steps cannot be started.

The workflow list

Each workflow is a card with its name, what it runs on, its description, how many steps it has and how many times it has run. The chip says In use or Turned off. When something starts it by itself, a line says so, such as “Starts automatically when a new animal is added.” Press Edit steps to open its steps, and Close to fold them away.

What starts a workflow

Every workflow can be started by hand on a record. Under Starts, you can also choose an event that starts it by itself. only when somebody starts it means it never starts by itself. What is offered depends on what the checklist runs on and, on People, what it is for. Every People checklist, whatever it is for, can also start when a form they sent arrives, is approved or is rejected. A record brought in by an import, from a spreadsheet under Settings → Import or from an integration such as RescueGroups.org, starts none of these by itself, not even one set to start a number of days after it is added: what it records happened before it came in. When a form arrives These three come from Submissions: a form arrives when it first belongs to a person, and is approved or rejected when somebody approves or denies the application made from it (a submission is never decided on its own). They do not name a kind of form, and that is the point: the form’s kind is a condition, the same way an animal’s status is. So a checklist can start on a surrender request or a contact form, which nothing could do before.
A checklist written before this, which starts on a named kind such as when their volunteer form is received, keeps working and keeps saying so. Those are no longer offered for a new one, because a trigger and a condition say the same thing and read better.
When its status changes is the one that speaks your own words. Every other event is a moment RescueConsole knows about; your statuses are yours, so this one starts whenever an animal’s status moves at all, and you narrow it with a condition below: only when status is Available starts the checklist on that status and no other. Saving an animal without touching its status does not start it. For a choice that waits a number of days, set the number of days (1 to 365) beside it. It starts once per record, ever: finishing the checklist does not make it start again. If the day is missed, it still starts the next day, but not later than that. An event does not start a workflow on a record that already has an open run of the same workflow. Changing what a People checklist is For clears a starting event that no longer fits.

Only when

A workflow that starts by itself can also have conditions: the record has to meet all of them for the workflow to start. The box under the card reads Every time it happens until you add one.
1

Add a condition

Press Add a condition.
2

Say what it tests

Choose a field, a test and a value.
3

Save it

Press Save conditions.
The application’s kind is how one checklist that runs on Applications is for adoption applications and another for foster or volunteer ones, each with its own items: only when application kind is Foster. With no such condition the checklist starts on every kind. The form’s kind offers your forms by name. It only means anything where a form started the checklist: on a run nothing sent, there is no form to look at, so a condition about one does not hold and the checklist does not start. Where the animal is offers your own locations and the units inside them by name, so “a cat intake in Isolation” and “a dog intake in the kennels” can be different checklists. It remembers which place you picked rather than its name, so renaming a room later does not stop the checklist starting. The tests are is, is not, contains, is filled in, is empty, is more than and is less than. Where a field has a list, such as a status or a species, is and is not offer the list. For a custom field, choose a custom field… and type its key, which is shown under Settings → Data & customization → Custom fields. Conditions only decide whether an event starts the workflow. Somebody starting it by hand is not stopped by them.

Steps

Steps run in order, top to bottom. Use the arrows to move a step, and the bin to delete it. Type in a step’s title or instructions and click away to save: each change saves as you make it.
Changes to a workflow apply to runs started from now on. A run already under way keeps the steps it started with, so a finished run still says what was asked on the day.

Adding a step

1

Choose the kind of step

At the bottom of the steps, choose the kind of step.
2

Type its title

Type its title.
3

Add it

Press Add.

Step settings

A wait has one setting, Waits: how long, before the steps below it. The wait is measured from when it is reached, not from when the run started, so a wait after a step starts once that step is done.

Who does a step

Done by names a team role or a person, never both: choosing one clears the other. The roles are your team’s (directors, shelter managers, veterinarians, adoption counselors and the rest), never a portal role, and the people are those with a team role. A role is the better choice: a checklist outlives the people on it. When a run starts, a step that adds to the task list:
  • Done by a person gives its task to them, and the notifications bell (and the email, if they get one) says “You were assigned a task”, from that checklist. Somebody no longer on your team is passed over: the task is for nobody until somebody takes it.
  • Done by a role leaves the task unassigned and marked for that role: the task list’s Assigned to reads, for example, For adoption counselors. Everybody holding the role is told “For the adoption counselor role”, and whoever takes it assigns it to themselves.
On the record, each step says who does it, for example Done by adoption counselors.

A step that ticks itself

A step somebody does can also be ticked by the record. Under the step, the box reads Ticked by a person.
1

Open the box

Press Tick it by itself when….
2

Say what ticks it

Choose a field and a test, as for Only when.
3

Save it

Press Save Done when. The box then reads, for example, Ticks itself when microchip number is filled in, whenever the record is saved.
  • When a run starts, a step whose condition already holds starts done, and is not added to the task list. A chip scanned at the guided intake is not scanned again.
  • Whenever the record is saved, by anyone and from anywhere in the app, each open run’s steps are checked. One whose condition now holds is ticked, and its task is closed. A step after it that runs by itself, or a wait, goes on as usual, within five minutes.
  • On the record, the step says what will tick it (“Ticks itself when photo is filled in.”) and, once it has, “Ticked itself:” and why, so nobody takes it for a person’s tick. Untick it and it is ticked again the next time the record is saved while that is still true: change the record, or the step, instead.
  • On a checklist a form started, a step can be ticked by the form: the form’s surrender answer is filled in ticks it when the surrender request is answered, in any way. The standard A surrender request arrives has it on Decide what you can offer; one added before 4 November 2026 was given the same. Accepting a request never waits on a step like this.
Only a step somebody ticks, which sends and sets nothing, can tick itself. A check is answered, and a step that sends a message, sets a field or creates a task is offered no Done when: give it one and then an action, and the Done when is dropped.

What a step does

Beside When ticked (or Does, for a step that runs by itself), choose what happens:
  • nothing else happens: the tick is the record that it was done.
  • send a message: sends one of your message templates. Choose the template, who it goes to, and anybody to Copy or Blind copy.
  • set a field: sets a field on the record to a value you choose.
  • create a task: adds a task on the record.
  • tell your team: tells team roles and people about the record, in the notifications bell and by email unless they turned that off. Type what to tell them (200 characters at most) and add each role or person under add a role or a person…. A role is whoever holds it when the step runs, and somebody who has left your team is passed over; the record’s step says how many it told.
A step that does something says so on the record, beside its tick box, before anybody ticks it. A ticked step sends its message or sets its field once. Unticking and ticking it again does not do it a second time.

Who a message goes to

The team roles are organization admins, directors, shelter managers, veterinarians, veterinary technicians, animal behaviorists, adoption counselors, volunteer coordinators, foster coordinators, animal control officers, intake officers, animal care technicians and read-only members. A copy to a role goes to everyone with that role. The message goes to whoever that person is on the day the step runs. If there is nobody, such as an animal with no adopter yet, the step records that it could not send.

Fields a step can set

A task a step creates

The task’s title, when it is due (a number of days after the step runs, or none), its priority (low, normal or high), and whether it is for nobody in particular or for whoever ticks this step. A task with a due date shows on the calendar.

Checks

A check is answered rather than ticked. If it fails says what a Failed answer does:
  • record it and wait for a person: the answer is kept, and the steps after it that run by themselves wait.
  • put the application on hold: on an adoption application checklist, the application goes on hold. On a People checklist started by a form, the form’s submission goes on hold.
  • reject the application: on an adoption application checklist, the application is rejected. On a People checklist started by an adoption, foster or volunteer form, the submission is rejected if nobody has decided it yet, and the application made from it is denied, which starts anything set to run when that form is rejected.
On an Animals checklist, only record it and wait for a person is offered. A failed check keeps the run open until somebody looks at it. Reopen clears the answer so it can be answered again, and takes back what the fail did, the hold or the rejection, while it is still the check’s. Reopening a check that rejected a form also puts the application it denied back where it stood, unless somebody has decided that application since.

Turning off and deleting

Turn off stops a workflow from starting, by an event or by hand. Runs already under way carry on. Turn back on undoes it. The bin deletes a workflow. A workflow that has ever run cannot be deleted, because that would erase the record of those runs: the app says “This workflow has been run, so deleting it would erase the record of those runs. Turn it off instead.”

Runs on a record

A run appears on the record it runs on: an animal’s Today tab, a person’s record, an adoption application, and a submission the run is about. Each run shows its name, how far it has got (such as 2 of 5, then Finished, or Stopped), and when it started.
  • Start a workflow… on the record lists the checklists you can start there. Choose one and press Start.
  • Tick a step when it is done. Skip marks a step as not done on purpose, and it shows as skipped. A step that ticks itself says what it waits for.
  • A step that runs by itself says “Runs by itself once the steps above are done, within five minutes.” A wait says when it ends.
  • If a step’s message, field or task could not be done, it says why, with Try again. A ticked step stays ticked: the work was done even if the email was not sent. A step that runs by itself and fails holds back the steps below it until Try again works.
  • Open shows the run on its own page, naming the record it runs on.
  • Edit this workflow opens the checklist here, in Settings, with its steps open. It shows only to somebody who can write workflows for that kind of record.
  • Stop ends a run that is no longer needed. A stopped run stays stopped.
A run is finished when every required step is done or skipped and no check has failed. Reopening a step on a finished run opens it again. Steps with Add to the task list also appear under Tasks and, once due, on the calendar.