Can any rider change records?
No. Rider submissions can be captured, but official attendance, distance, and member changes depend on the configured workflow and operator review.
Questions we expect
The FAQ keeps the public story honest about what RomrHQ does, what it does not do, and why Telegram-first is an intentional launch choice.
Trust and permissions
RomrHQ is designed around bounded Telegram groups, club-scoped records, and operator permissions rather than broad self-service access.
No. Rider submissions can be captured, but official attendance, distance, and member changes depend on the configured workflow and operator review.
No. Readiness summaries show evidence against club thresholds. Leadership keeps promotion and membership authority.
Group binding is part of the setup story so commands operate in the intended club and chapter context.
Privacy and records
The launch site captures qualification and referral data. Club runtime data belongs to the operational product and should be handled separately from the marketing funnel.
Demo requests collect contact and club basics. Rider referrals can include role, leadership contact, and the operational pain needed to route the nomination.
The product records the club-scoped member, ride, attendance, distance, and readiness facts required by the operating workflow.
No. The product story is built around club-scoped records and private pilot conversations, not public profiles.
Setup and culture
RomrHQ is not trying to replace club culture or turn the chapter into a generic SaaS workspace.
The first product works where the validated club workflow already happens, which reduces adoption drag for riders.
A pilot should start with group binding, operator roles, member records, ride workflow, and readiness thresholds.
Public pricing, dues, voting, discipline, broad ERP, and WhatsApp-first support are outside the launch product.