WEBVTT

00:00:00.350 --> 00:00:03.416
Open Client review checklist in the workflow
library.

00:00:03.416 --> 00:00:06.481
The builder shows its published status and
version.

00:00:06.481 --> 00:00:12.612
Scroll to Stages and tasks to see how each
task is assigned and scheduled relative to

00:00:12.612 --> 00:00:14.145
the work’s due date.

00:00:14.145 --> 00:00:17.594
This example has one Review stage and two
tasks.

00:00:22.350 --> 00:00:25.281
Click New workflow to begin a reusable
process.

00:00:25.281 --> 00:00:31.142
Give it a clear name, choose the work type,
and describe the result your team should

00:00:31.142 --> 00:00:31.508
produce.

00:00:31.508 --> 00:00:36.637
Here we use Quarter-end review for monthly
bookkeeping, with a short description of the

00:00:36.637 --> 00:00:38.102
review and internal handoff.

00:00:43.350 --> 00:00:44.418
Click Create draft.

00:00:44.418 --> 00:00:47.976
The new workflow starts as a draft with no
stages.

00:00:47.976 --> 00:00:52.602
The page explains why Publish is
unavailable: first add a stage containing at

00:00:52.602 --> 00:00:53.669
least one task.

00:00:53.669 --> 00:00:59.363
Keeping it as a draft lets you build and
review the process before anyone starts work

00:00:59.363 --> 00:01:00.075
from it.

00:01:06.350 --> 00:01:09.432
Click Add stage and name it Internal review.

00:01:09.432 --> 00:01:13.670
Choose Review as its kind, then add the task
Review reconciliations.

00:01:13.670 --> 00:01:19.064
Assign the Reviewer role and set the task to
fall on the due date.

00:01:19.064 --> 00:01:21.761
Leave Client-visible unchecked for this
internal task.

00:01:26.350 --> 00:01:27.621
Click Save stages.

00:01:27.621 --> 00:01:32.703
The unsaved-changes message disappears and
the task remains in the saved structure.

00:01:32.703 --> 00:01:36.938
Review the names, responsibility, and timing
before publishing your workflow.

00:01:36.938 --> 00:01:43.291
This tutorial leaves the example as a draft;
it does not start new client work.

00:01:46.350 --> 00:01:49.469
Click Global automations to review the
firm’s rules.

00:01:49.469 --> 00:01:55.317
Each card summarizes when the rule matches,
what it does, and whether it is enabled.

00:01:55.317 --> 00:01:59.606
Use those summaries to understand an
existing rule before changing it.

00:01:59.606 --> 00:02:03.115
We will create a separate reminder for this
demonstration.

00:02:07.350 --> 00:02:08.908
Click New global automation.

00:02:08.908 --> 00:02:13.972
Name the rule Review reminder, and choose
Work status changes as the trigger.

00:02:13.972 --> 00:02:19.816
Set the scope to Whole firm and add the
condition Board status is In review.

00:02:19.816 --> 00:02:24.880
Under Then, choose Notify a staff member,
select Assignee, and enter a useful

00:02:24.880 --> 00:02:25.269
reminder.

00:02:25.269 --> 00:02:28.775
Leave Also email this person unchecked for
this example.

00:02:33.350 --> 00:02:35.740
With Enabled unchecked, click Create
automation.

00:02:35.740 --> 00:02:41.716
The new reminder appears with an Off badge,
so saving it has not activated it.

00:02:41.716 --> 00:02:45.700
The rule keeps the selected notification
action and run order.

00:02:45.700 --> 00:02:50.481
Review the saved summary, then test the
conditions before considering whether to

00:02:50.481 --> 00:02:51.278
enable it.

00:02:55.350 --> 00:02:57.520
Click Dry-run on the new reminder.

00:02:57.520 --> 00:03:02.583
The result reports two matches and lists
Jordan Lee and Blue River as examples.

00:03:02.583 --> 00:03:06.560
Check whether those examples are the work
you intended to target.

00:03:06.560 --> 00:03:10.900
The rule remains Off, and this preview does
not send the reminder.

00:03:16.350 --> 00:03:18.703
Click Schedules to review recurring work.

00:03:18.703 --> 00:03:23.800
This example shows two workflows under Not
yet scheduled and no active schedules.

00:03:23.800 --> 00:03:28.505
A recurrence must be saved and configured
before it creates future work.

00:03:28.505 --> 00:03:34.387
Use this page to confirm the schedule state;
no recurring work is activated in this

00:03:34.387 --> 00:03:34.779
tutorial.
