Paddle City × Pickle Time Saved
Paddle City × Pickle Time

Planning a 600-player tournament together.

A working document, not a finished plan. You fill in the requirements, we turn them into an operational plan. Every field is editable and saves as you go.

01
You set the requirements
Categories, divisions, courts, dates.
02
We turn them into a plan
Stages, scoring, match volume, schedule.
03
We validate together
Correct what is wrong, add what is missing.
04
Configuration confirmed
Only then do we build it.

How to read this

  • ConfirmedAgreed by both sides.
  • AssumptionOur starting guess. Change it.
  • To confirmYour call.
  • RecommendedOur advice, not a requirement.
  • EstimateCalculated from your inputs.
01Tournament OverviewTo confirm

The basics.

Fill in what you know. Leave the rest blank.

Starting figure: 600.
~300 if all play doubles.
Courts available To confirm
Tournament days To confirm
Courts and days shape the schedule more than anything else here.
02CategoriesTo confirm

Which categories?

These determine the divisions you need, and the scheduling workload. Add your own if ours do not fit.

03DivisionsAssumption

Divisions per category.

A starting point, not a proposal. Rename, adjust team counts, remove, add.

Categories
0
Divisions
0
Teams allocated
0
vs expected
0
The last tile compares teams allocated here against your expected total. A large gap means the two do not agree yet.
04Format and Stage ConfigurationAssumption

Each division, its own format.

Open a division to set its stages and scoring. Match counts update as you type.

Recommended. Round robin for guaranteed games, then a short knockout for placements. Your call, and it can differ per division.
05Scheduling AssumptionsTo confirm

What shapes the schedule.

The operational inputs behind the estimate in the next section.

06Court Allocation

Courts drive everything.

More courts
  1. More matches at once
  2. Higher throughput
  3. Shorter tournament
Fewer courts
  1. Fewer matches at once
  2. Longer waits between rounds
  3. Longer tournament, or fewer games
Set courts in the overview or on the sliders below.
07Capacity EstimateEstimate

What it adds up to.

Calculated live from your divisions, stages and scheduling inputs. A planning aid, not a commitment.

Push these

Same values as the sections above. Change them here, they change everywhere.

Match capacity per day
0
Court utilization
0%

Planning estimate

Estimated matches
0
Estimated court hours
0
Estimated duration
0
Against planned days
n/a
Estimate only. The real schedule depends on confirmed registrations and actual match durations.
08Pickle Time RecommendationRecommended

How we would approach it.

Suggestions from running events at this scale. None are requirements.

Recommended approach Pickle Time

  • Finalize categories and divisions before registration opens.
  • Set the format per division, not one format for the whole event.
  • Use multi-stage formats so every team gets guaranteed games.
  • Estimate teams per division now, adjust when registrations land.
  • Check capacity before registration opens.
  • Build the schedule from confirmed registrations.
  • Keep courts, hours and rest adjustable through tournament week.
09Operational Workflow

How we support the event.

The path the tournament follows, planning through reports.

Planning

  1. Define categories
  2. Define divisions
  3. Define formats per division
  4. Configure stages and scoring
  5. Estimate capacity

Registration

  1. Open registration
  2. Monitor registrations
  3. Verify payments
  4. Lock divisions
  5. Generate brackets
  6. Generate schedule

Tournament day

  1. Check-in
  2. Live match management
  3. Live TV and command center
  4. Standings and results
  5. Reports
10What Paddle City Needs To ConfirmTo confirm

The open list.

Tick items as they are decided. Unticked items appear in the export as still open.

Tournament basics

Categories and divisions

Format

Operations

11PricingRate confirmed

Tied to participation.

The rate is agreed. The total follows the confirmed player count. No setup fee, no subscription.

₱25 / player
Players
600
×
Per player
₱25
=
Estimate
₱15,000
Illustrative, at the player count on the right. Final amount follows the confirmed count.
Platform fee at ₱25 per player
₱15,000

Your divisions allocate 0 players. If that differs from the basis above, we reconcile before invoicing.

12Product Evidence

The system behind it.

Pickle Time as it exists today.

tournament configuration
Create tournament wizard with steps, basics form and live summary panel
Tournament ConfigurationA five-step setup with live estimates and validation before launch.
divisions and fees
Division setup with entry fees and per team fee preview
Divisions and FeesOwn fee, team cap and match settings per division.
scheduling
Generated schedule across courts and time slots
SchedulingMatches across courts and time slots, no clashes.
match management
Match management with status counters and rounds
Match ManagementHundreds of matches by status, division and round.
brackets
Division bracket tree with scores
BracketsPer division, winners advance automatically.
registration
Registrations table with teams, divisions and payment status
RegistrationPlayers, teams, divisions and payment in one table.
check-in
Check-in desk with checked in, no show and pending counts
Check-InPlayers checked in and queued for matches.
standings
Division standings with wins, losses and point differential
StandingsLive leaderboards per division.
live tv
Tournament TV board with live scores, bracket and up next
Live TVCourtside board with live scores and brackets.
13Next Step

Send it back filled in.

Correct our assumptions, tick off what is decided, then send the summary over. We will build the real configuration from it.

Prepared for
Jason Tupas
Paddle City
Prepared by
John Pecson
Pickle Time
Paddle City × Pickle Time · Tournament planning Subject to confirmation

Send to Pickle Time

Generated from your inputs

Everything in this document, including what is still open. Copy it and send it over.