Hours saved
Your scheduler gets 6.0 weekends back.
Put in what your festival actually spends on scheduling, results, certificates and registration — this shows what Ovaro gives your volunteers back, with the assumptions in plain sight.
Your festival, in numbers
Roughly how many performances get scored
Anyone who builds or fixes the running order
Hours currently spent, per season
Assigning classes, rooms, judges and times
Gathering score sheets and getting results out
Designing, printing or emailing every one
Typing in entries, matching e-transfers, reminders
Our assumptions — shown, not hidden
These are the shares of each task Ovaro removes, based on what configuring your syllabus, publishing a schedule, releasing results and generating certificates automatically takes off someone’s plate. They’re estimates, not measured statistics — adjust the hours above to match your own festival and the totals will follow.
- Building the schedule~70% removed
- Compiling and sending results~85% removed
- Producing certificates~95% removed
- Registration data entry & chasing payments~80% removed
Hours back, per season — an estimate based on your own numbers
| Job | Back | |
|---|---|---|
| Building the schedule | 21.0 hrs | |
| Compiling and sending results | 17.0 hrs | |
| Producing certificates | 14.3 hrs | |
| Registration data entry & chasing payments | 20.0 hrs | |
| Total volunteer hours back | 72.3 hrs | |
In weekends
6.0wknds
A weekend counted at 12 hours, across 4 people and about 600 entries this season.
Those hours are priced at zero, because your people are volunteers — which is exactly the point. This isn’t money saved on a line item; it’s a Saturday your scheduler gets to keep.
Curious what that costs? See pricing.
See it against your own numbers.
Bring your entry count and your current process. We'll show you exactly where the hours go and where they come back.