How tasks are generated
How a confirmed order becomes delivery, setup and pickup tasks, when it happens, what times the tasks get, and how event rules change it.
When an order is confirmed, PartyPad builds the crew work for it: the delivery, the setup if there is one, and the pickup. Automatic task generation is a Professional plan feature. On the Free plan you create tasks yourself on Tasks.
When it runs
PartyPad generates tasks when an order becomes Confirmed in one of these ways:
- you create it on Events with the status set to Confirmed, or change an existing order to Confirmed in Edit Event,
- your booking system sends it as confirmed, or confirms it later, through webhooks,
- a customer pays for it on your booking page,
- you confirm it in the PartyPad Admin app.
It does not run when:
- you bring orders in with Import Events,
- the order already has generated tasks. PartyPad never adds a second set.
For those cases, see Tasks not being created.
What it creates
With no event rules set up, the tasks follow the order's Delivery Type:
| Delivery Type | Tasks | Default time |
|---|---|---|
| Drop-Off | Equipment Delivery | 2 hours before the event starts |
| Equipment Pickup | 1 hour after the event ends | |
| Full-Service | Equipment Delivery | 3 hours before the event starts |
| Equipment Setup | 2 hours before the event starts | |
| Equipment Breakdown & Pickup | 1 hour after the event ends | |
| Customer Pickup | Pre-Event Equipment Check | 24 hours before the event |
| Post-Event Maintenance | 24 hours after the event ends |
If the order has a Delivery Date and Delivery Time, the delivery and setup use that instead of the default. A Pickup Date and Pickup Time set the pickup the same way. Orders from a booking system usually carry both.
Each task gets the event address, placed on the map, and the order's rental list, so the crew sees what's going out.
Who gets the tasks
Tasks built from the delivery type are offered to your contractors automatically. PartyPad ranks the contractors who fit the task, taking skills into account, and offers it to them one at a time. Each one accepts or passes, and an offer that goes unanswered moves on to the next. If everyone passes, the task stays unassigned and you're alerted to assign it yourself.
You can step in at any point: assign from Tasks, or build routes on the Dispatch board.
Event rules
Event rules replace the delivery-type list with your own. You set them up under Automation > Event Rules:
- Write a task template on the Templates tab: its type, timing and required skills.
- On Event Rules, pick the template and click Add rule.
- Add conditions if the rule shouldn't apply to every order. Conditions can test the total price, delivery type, guest count or rental agreement.
Rules behave differently from the delivery-type list:
- They run for every new order, whatever its status, Hold included.
- Their tasks are left unassigned, for you to assign or for contractors to claim.
- Once you have at least one rule, the delivery-type list is no longer used. If no rule's conditions match an order, that order gets no tasks.
Automation covers templates and rules in full.
Generate tasks by hand
Generate Tasks in Quick Actions on the Events page builds tasks for any order that isn't cancelled:
- Select the order.
- Tick the templates to use under Available Templates.
- Review the preview. You can adjust each task before saving.
- Leave Auto-assign tasks to available contractors ticked to offer them out, or untick it.
- Click Confirm. The button shows how many tasks it will create.
A template that already produced tasks for that order is skipped, so running it twice doesn't double the work.
After the tasks exist
Tasks follow the order. Move the delivery or pickup and they're rescheduled, change the address and they move with it, and cancel the order and every task that isn't completed is cancelled. See Order statuses.