Course
Start with the places, systems, and assets that belong to one course.
How TurfIQ is being built
Keep the field story with the place it happened.
The intended workflow is practical: document an issue, keep the maintenance context with it, and make that history easier to find when the next decision arrives.
The product direction
Keep the issue, evidence, and field context together.
TurfIQ is being researched as a course operating memory. Its intended job is to help a team retain the context behind field issues and find that history when the next decision comes up.
Hole
Keep each observation connected to a useful on-course location.
Surface
Add the turf, irrigation, or operating surface that gives the record meaning.
Station / asset
Retain the station, controller, zone, or component context for later review.
Availability
TurfIQ is invitation-only and still in development.
Not publicly released
There is no public self-serve launch or general product access today.
Research-led access
Walkthrough requests help us learn where the product direction could be useful.
Human judgment remains essential
TurfIQ is intended to support work in the field, not replace local knowledge or safety procedures.
Current research status
The work is not being presented as a finished public product.
- The production authentication route has been fixed.
- API-level authorized course isolation has been verified in both directions.
- The private course workspace model is in place.
- Work remains before an invitation-only release, including final authenticated UI acceptance.
Start the conversation
Request a TurfIQ walkthrough.
Request a no-obligation conversation about the product direction, your course context, and when Founding Pilot consideration may open. This is not a self-serve product demo.
Apply for Founding Course Access