Product guides
Six automations that take hand-offs off your plate
Project management automation for agencies, kept simple: six rules that assign, notify and tidy up at every hand-off, and the limits worth knowing first.
8 min read
Hand-offs that happen on their own.
Write a rule as a sentence. When a job moves, changes or sits in a column too long, Skybase can assign it, set its status or priority, move it, archive it or tell the right people. Every change a rule makes shows on the job with the rule's name.
How a rule reads
An administrator builds each rule in the project's settings, under Automations, the way you would say it out loud. Skybase runs it straight after the change is saved, or once a day for rules that wait on time.
A project can have up to 25 automations, and they run from the top of the list down.
An automation rule named Review hand-off, switched on: when the status changes to In review, assign to Leo Ortiz, then notify Tom Becker. It has run 12 times. Beside it, Brand guidelines v3 moves to In review, the rule reassigns it from Priya Shah to Leo Ortiz, a row marked with a violet bolt records that in the job's activity, and Tom Becker, the client, is notified.
Start from an example
Choose Examples beside New automation and pick a rule. Each one comes filled in with your own columns, statuses and people, and opens in the editor for you to check. Nothing is saved until you do.
Some appear only when they fit: Bugs are important needs a Bug job type, Blocked escalation a Blocked status, and Started without an owner an In progress column. The examples that set a priority only ever raise it.
Rules that wait
Some rules wait on time. Once a day, Skybase looks for jobs that have been in a column for the number of days you chose, counted from when each one arrived. Pair it with archive the job, and Done clears itself two weeks after the work is finished.
The automation examples, with Archive jobs in Done after 14 days picked. Saved and switched on, the rule reads: when a job has been in Done for 14 days, archive the job. Its daily scheduled check ran on Brand audit, which had sat in Done since 30 September, so the job is archived and hidden from the board, and a row marked with a violet bolt in its activity says the rule archived it.
See why a job changed
Every change a rule makes shows in the job's activity under the rule's name, with a lightning bolt, and its notifications carry the name too.
Each rule keeps its last 50 runs, marked Ran, Nothing to change, Skipped or Failed, with the reason when it did not run.
A change a rule makes can set off another rule, up to three rules in a row, and its run says Set off by, then the rule's name.
A rule never runs twice in one chain, so two rules cannot pass a job back and forth. A bulk change sends each person one notification per rule, listing the jobs.
Only administrators can add or change a rule. Team members see every rule and its runs, read-only, so nobody has to ask why a job moved. Guests never see them.
If a column, status or job type a rule uses is deleted, or someone it names leaves the project, the rule switches itself off and says why on its card.
FAQ
Everything else Skybase does is on the features page, and the automations guide walks through building a rule.
Product guides
Project management automation for agencies, kept simple: six rules that assign, notify and tidy up at every hand-off, and the limits worth knowing first.
8 min read
Running projects
How to set up a kanban board for agency work: columns for stages, statuses for states, job types, priorities and due dates that everyone can read.
9 min read
Free plan, no credit card. Automations are on every plan.
Free plan · No credit card · Clients always free