Setup
Create an event in one pass
A guided wizard walks the essentials — which clubs are invited, the dates, how members get in. Nothing is buried three menus deep.
For clubs and trip operators
Run your club's events end to end.
Talusi HQ is the console behind the drive. Build the event, take the registrations and the money, then run the day itself — the roster, the gate, the board — while every member follows on their own phone.
Web console
Works at the gate
Every change logged
What it does
The whole event, in one console
Not a calendar with a payment link bolted on. The parts that make a convoy day work — and the parts you get asked about afterwards.
Registrations
Sign-ups that collect the money
Share the registration link; members sign up and pay by UPI, attaching the screenshot as proof. Rates are set in the console and every total is recomputed on the server — never taken on the browser's word.
The board
Say it once, everyone has it
Post an announcement and it lands on every member's event page — aimed at one club or the whole convoy. The change you make at the halt is the change they read.
Roster
Everyone in one list — gate included
The full participant list, editable down to the detail, and check-in at the gate from the phone in your hand as vehicles roll up.
Money
Receipts, refunds, and a paper trail
Mark what has been received, refund what must go back — with the held-money guards standing in the way of a wrong one — and read collected, refunded and still-held off one panel.
The plan
What you write, members read
The itinerary, hour by hour with its halts and map links, and Event Info sections for joining instructions and the fine print — both publish straight to the member page. Written once, never re-posted to a group chat.
The run of the day
From the first sign-up to the closed books
One event, one console, four moments where it usually goes wrong.
Before
The roster fills
Registrations and payments land as they come; the list is current without anyone maintaining a sheet.
Gate
Check them in
Vehicles arrive, you mark them present, and the count in the console is the count on the ground.
On the move
The board carries
The next instruction goes on the board and reaches every phone in the convoy; members mark themselves in at each halt.
After
Close the books
Receipts marked, refunds settled, and the numbers that answer "where did the money go".
Money you can defend
Club money is somebody else's money
The part of running events that keeps organisers up at night gets the strictest machinery in the product.
- Server-verified
- Amounts due are computed from the event's own payment configuration, on the server, every time — a form can ask, it can't decide.
- Proof attached
- UPI screenshots are parked against the participant the moment they are submitted, so a payment claim never rests on anybody's memory.
- Guarded refunds
- Refunds can't exceed what is actually held. The guard is in the engine, not in the operator's memory.
- Nothing quiet
- Every action that changes an event is written to an audit log — who did it, when, and what moved — so a number questioned weeks later has a history behind it.
The other side
Your members never see the console
What you publish in HQ shows up where they already are.
One link, no installs
The event page opens in any browser on any phone. Itinerary, announcements, their own payment position — shareable in the group the club already uses.
Or the Talusi app
For the members who drive all year, the native app carries the event day and their own driving life — trips, vehicles, costs — in one place.
See the member app
Two halves of one platform, built in the same house.
Get started
The next drive can run on this
Sign in with the account your club added to Talusi HQ and its events are waiting. Nothing to install — and nothing your members have to download.
app.talusihq.com
Bringing a club onto Talusi? Console access is set up by invitation — write to us and we'll get your organisation on: