Readiness: build your own checks
After this article you know how to add your own checks alongside the eight built-in ones — with a name, conditions, a time frame and a hint — and what to watch out for.
The eight built-in Readiness checks cover what goes wrong in almost every operation. What goes wrong in yours, we don't know — so you can build your own checks.
A custom check is: a name, a set of conditions, a time frame. When all of it applies to an event, it appears in the readiness list — just like a built-in one, with the same path to the event, the same “Assign as task” and the same dismissing.
Where to find it
Readiness in the sidebar → Settings at the top right → Custom checks block → New check.
Creating and changing them requires permission to edit the workspace settings. Everyone else sees the checks but cannot change them.
Creating a check
1 · Name. This becomes the headline of the row in the list. Write what is missing, not what you check: “Seating plan missing” reads better than “Seating plan check”.
2 · Hint (optional). One sentence about what needs to be done — “Request the plan from the customer”. It later appears as the reason under the row. The text stays exactly as you write it; it is not translated.
3 · Conditions. Pick a field, a comparison and a value. Several conditions apply together: all of them must match. At least one is required — a check without a condition would apply to every event.
The available fields are the same ones as in the Automations rule editor:
| Field | Example |
|---|---|
| Name | name contains a certain value |
| Guest count | greater than 100 |
| Budget | greater than 5,000 |
| Start | before a certain date |
| Date confirmed | is no |
| Status | is “Option” |
| Language | is English |
| Tags | carries one of several tags |
| Venues | takes place in a certain venue |
| Customer | is a certain contact |
4 · When should it report?
- Before the event — only from “event in at most X days”. For everything that has to be ready in time.
- After the event — only from “end was at least X days ago”. For follow-up work.
- Always — regardless of the date. For details that have to be right from the start.
The lead time is at most 120 days: that is how far the readiness window reaches ahead, a larger value would change nothing.
5 · Owner (optional). Whoever is set here is pre-selected in the assign dialog. Without one, the event's project lead is suggested.
6 · Active. A switched-off check stays saved and reports nothing.
Three examples
- “Seating plan missing” — guest count greater than 80, venue is the large hall, reports 14 days ahead.
- “Photos not delivered yet” — tag “Wedding”, reports 7 days after the event.
- “Check English documents” — language is English, reports always.
What you should know
- Up to 20 custom checks per workspace. More than that nobody reads; if you need more, you usually need a task template rather than a check.
- The row leads to the event, not to a specific tab. Unlike with the built-in checks, we don't know where your seating plan lives.
- It does not count. A custom check applies or it doesn't — there is no number behind it as with “3 documents without a recipient”.
- Deleting is permanent. Tasks already created from it stay, since they carry the name in plain text.
- There is still no overall score. Even with twenty custom checks, Readiness stays a list of open items, not a grade for an event.
Not available yet
- Custom checks do not trigger automations or emails. Whoever should be notified gets the item assigned as a task.
- Fields from other areas (documents, shifts, production lists) are not available as conditions yet — that is what the built-in checks are for.
How the readiness list works overall is described in Readiness: what an event is still missing.