Golf Club Operations App
Budget: $5,000 – $10,000 AUD
I’m ready to commission a comprehensive system that runs seamlessly as both a responsive web app and a fully-featured mobile app. The goal is to bring every operational need of our golf club into one secure, easy-to-extend platform with role-based access for Staff and Administrators.
Core modules I need in the first release
• Event & trophy winner tracking with photo upload
• Maintenance reporting with photo upload and status workflow
• Event scheduling and wait-list management that ties into task schedules (tasks can be pre-dated to an event)
• Digital workplace procedures and onboarding materials
• Council-required compliance logs (e.g. fridge temperature)
• Staff compliance, certificate and qualification tracking with expiry alerts
• Workplace health & safety: incident logging, material data sheets, equipment manuals
• Sponsorship relationship tracking
Technical expectations
– Secure authentication and granular access control so staff see only what they need while administrators have full oversight.
– Clean, modern UI that looks and behaves consistently on phones, tablets and desktops.
– A modular codebase and database structure that lets me switch modules on/off and plug in new ones later without refactoring the whole system.
– Cloud-ready deployment with automated backups.
– Exportable reports (PDF/CSV) across all data sets.
I will provide branding assets and sample spreadsheets for current paper forms; you translate them into intuitive digital workflows. Suggest your preferred stack along with any low-code or open-source frameworks that will speed development without locking us in.
Deliverables
1. Working web & mobile applications (production build).
2. Source code in a private repo with install/readme.
3. Database schema & basic seed data.
4. Administrator guide and brief end-user cheatsheet.
5. Post-launch support window for bug fixes.
Show me relevant projects you have shipped—especially membership or compliance platforms—and outline how you would structure modules to keep future expansion straightforward.
We have already started a version ourselves, but it needs more detail and is a bit clunky.
We can provide access to what we currently have to use as a base.
Core modules I need in the first release
• Event & trophy winner tracking with photo upload
• Maintenance reporting with photo upload and status workflow
• Event scheduling and wait-list management that ties into task schedules (tasks can be pre-dated to an event)
• Digital workplace procedures and onboarding materials
• Council-required compliance logs (e.g. fridge temperature)
• Staff compliance, certificate and qualification tracking with expiry alerts
• Workplace health & safety: incident logging, material data sheets, equipment manuals
• Sponsorship relationship tracking
Technical expectations
– Secure authentication and granular access control so staff see only what they need while administrators have full oversight.
– Clean, modern UI that looks and behaves consistently on phones, tablets and desktops.
– A modular codebase and database structure that lets me switch modules on/off and plug in new ones later without refactoring the whole system.
– Cloud-ready deployment with automated backups.
– Exportable reports (PDF/CSV) across all data sets.
I will provide branding assets and sample spreadsheets for current paper forms; you translate them into intuitive digital workflows. Suggest your preferred stack along with any low-code or open-source frameworks that will speed development without locking us in.
Deliverables
1. Working web & mobile applications (production build).
2. Source code in a private repo with install/readme.
3. Database schema & basic seed data.
4. Administrator guide and brief end-user cheatsheet.
5. Post-launch support window for bug fixes.
Show me relevant projects you have shipped—especially membership or compliance platforms—and outline how you would structure modules to keep future expansion straightforward.
We have already started a version ourselves, but it needs more detail and is a bit clunky.
We can provide access to what we currently have to use as a base.