( 01 )Resources

Transparency is infrastructure too.

The current state of TurfTech's services, how we communicate incidents, and what we do so that maintenance never costs anyone a booking. This page is maintained by the team — no simulated telemetry, no number we can't stand behind.

Report a problem Go to the help centre

All services operationalState declared by the team

( 02 )Service status

Four services, one standard

What the club uses every day, and the state of each part right now. If something here isn't operational, this is the first place we'll say so.

Club web platform
Pro shop, tee sheet, tournaments and reports in the browser.
Operational
Player app
Bookings, digital scorecard and handicap on the member's phone.
Operational
Live scoring
Live leaderboards during tournaments and rounds marked in the app.
Operational
Integrations and API
The platform's connections to the club's other systems.
Operational

We operate to a 99.9% availability target across every service. We don't publish historic percentages we can't audit — when there is an incident, it appears on this page, with a name and a date.

( 03 )Communication

When something fails, you hear it from us

No system is immune to incidents. What makes the difference is the protocol — and ours has three moves, always in the same order.

( 01 )

Administrators told first

As soon as an incident is confirmed, the club's administrators get an email with what is affected, the expected impact and when we expect it back.

( 02 )

A notice in the app when players are affected

If bookings, the scorecard or live scoring are impacted, a notice appears inside the app itself — the member hears it from us, not from the failure.

( 03 )

A written report where it matters

Incidents with real operational impact get a report for the club: what happened, what was fixed and what we changed so it doesn't repeat.

( 04 )Scheduled maintenance

Maintenance the club never feels

Evolving the platform means maintenance windows. Three rules make sure they never get in the way of a Saturday morning on the 1st tee.

Overnight, when the course is quiet

Maintenance windows happen while the course is closed — never at the hours the pro shop and the players depend on the platform.

72 hours' notice

The club gets the date, the time and the estimated duration at least 72 hours ahead — plenty of time to adjust the routine if needed.

Bookings are never lost

Maintenance erases nothing: tee times, cards and handicap history stay exactly as they were before the window.

( 05 )Incident history

So far, a blank page

That's how we prefer it — and it's how we'll keep the record: public, dated and never edited after the fact.

Recent period

No incidents recorded in the recent period.

When an incident does happen, the record will be public on this page: what failed, who was affected, how long it lasted and what we changed so it doesn't repeat.

( 06 )Resources