PadBoard Quick Guide — How to Run a Session | Audrim Digital Marketing Services

PadBoard — Quick Guide

PadBoard decides who plays next, on which court and with whom, and keeps score. It runs in a browser and keeps working with no internet at the venue.

Create a free account at audrim.ph/register. Anyone can sign up — no invitation needed.
In the portal, open Order Service and press Order on the plan you want: ₱250 a month for up to 4 courts, or ₱500 for up to 8 courts plus saved rosters, templates and club branding.
We send you an invoice, usually within one business day.
Pay by scanning the GCash / Maya QR code shown with the invoice, then upload a screenshot of your receipt as proof of payment.
Once we confirm it, PadBoard is activated on your account and your receipt is emailed to you.
It renews monthly. Your dashboard shows the date access ends and warns you during the final week.

Sign in at audrim.ph and click PadBoard under Subscribed Tools, at the top of your dashboard.
There is no separate PadBoard login — your portal account is the login.
Once it has loaded, it keeps working offline for a week without signing in again.
Add PadBoard to your home screen. On Android or a laptop, use the browser's install option; on iPhone or iPad, use Share → Add to Home Screen.
This matters most on iPhone and iPad: Safari clears a site's stored data after seven days without a visit, and home screen apps are exempt. Your saved sessions stay put.

Fill in session name, venue, and number of courts.
Choose a rotation and a scoring level (both explained below).
Set a game timer in minutes. It starts at 0, which means no timer — games run to the target score.
Paste every player's name into the Players box at once — separated by commas or one per line.
Everything here can be changed later, mid-session, from the Settings tab.

Fill courts — puts the next players on every free court.
Auto-fill — off by default, so you decide when players go on. Switch it on in the top bar and courts refill the moment they free, the way a paddle rack does.
End game — records the game and frees the court.
Tap a team — what this does depends on the scoring level: it either records them as the winner, or awards them the rally.
Undo — reverses the last action, including a whole game ending.
Put four on — fills one specific court.

Paddle rack — strict first in, first out. Exactly like the rack on the fence.
Fair rotation — whoever is owed a game plays next; among equals, it picks pairings nobody has had recently.
Skill tiers — courts reserved for a skill level.
Winners split — winners stay on but split up and take new partners.
Challenge court — winners hold the court as a pair against challengers.
Round robin — strict rotation through a fixed group.
Winners split and challenge court both have a hold limit, so nobody can occupy a court indefinitely.

None — a match timer only. One tap to end a game.
Winner only — tap the winning team. One tap per game.
Points — tap a team to award them the rally. Undo point reverses the last one.
Points with server tracking — as above, plus the server number, court positions, and the score called the way it should be said aloud (4 - 2 - 1). A green dot marks who is serving.
Side-out and rally scoring, target score, win-by-two and a hard cap are all set in Settings.

On by default. The Announce button in the top bar is the master switch for everything spoken.
Calls follow a referee: “Point”, “Second server” or “Side out”, then the score as three numbers.
One court at a time. Pick which in Settings → Announce on court. Several courts calling at once would only talk over each other.
Settings → Announce score chooses every point, or only when the serve changes hands.
Settings → Voice picks any voice installed on the device, with a Test button. Voices that need an internet connection are deliberately not listed.

Up next — the queue. ↑ moves someone up one place, ⤒ moves them to the front.
Players — add one player or paste a list, pause someone sitting out, mark them Left when they go home, and nudge a rating with − / +.
Fairness — games played, time waited and consecutive sit-outs for everyone, with a spread summary. This is the screen for settling "when am I next?".
Settings — every rule, changeable mid-session. Also the session report and ending the session.
Diag — build number, activity log, and the diagnostics export.

Edit — swap one player for someone waiting, or replace all four by hand.
Edit → Partners — four players have three possible pairings, so pick the one you want. Only before the first rally: once points are on the board they belong to a side, and moving somebody across would rewrite who won them. After that, abandon the game and refill.
Abandon — for an injury or a washout. Recorded, but not counted as a win or loss.
The timer turns amber when a game runs past its expected length, and red when it runs well over.

Settings → Session report — a printable record of the session so far: every player, every game, scores and results.
Settings → End session and start a new one — closes running games, backs the session up, and returns to a fresh start screen.
Past sessions — the second tab on the start screen. Reopen and print any earlier session, including ones still only on this device.

Nothing changes. Games, scoring and the queue all keep working.
The session saves continuously on the device and survives the tab closing or the lid shutting.
It backs up to your account automatically once there is a signal again.
Ending a session with no signal is safe. It is kept on the device and uploaded the next time you open PadBoard with a connection.

A Club tab appears beside New session and Past sessions.
Save roster keeps a list of names; load it next week instead of typing them again.
Save as template keeps a whole setup — courts, rotation, scoring, timer — under a name like “Weeknight”.
Set your club name and logo and they print at the top of every session report.
All of it is kept on the device and backed up to your account, so a replaced tablet does not lose it.

Did the rotation ever feel unfair? When, and to whom?
Did you always know when you were next?
With server tracking on — was the app's call ever wrong? This is the one we most want checked.
Was anything harder than it would have been with a paddle rack?
Was there anything you wanted to do that the app would not let you?
Would you want this at your regular session?

Tap Flag in the top bar and describe what happened. It takes a few seconds and marks the exact moment.
Then Diag → Export diagnostics and send us the file. It contains everything needed to reproduce the session exactly.
If the app ever shows a red warning banner, stop trusting the screen and tell us — that means it has detected its own fault.