GridLogic
Kart championship SaaS that imports results from PDF, spreadsheet or image files and computes standings, penalties and stats.
Amateur kart championships are usually run on spreadsheets: someone copies the results from the timing PDF, applies penalties by hand and redoes the standings after every round. GridLogic automates that path, from the results file to the published table.
What it does
- Organizes championships with categories, rounds, teams and drivers, each with a public page.
- Imports results from CSV, spreadsheet, PDF or image: it detects the format, reads, validates, shows everything for review and only then publishes.
- Applies five kinds of penalties (time with reordering, fixed time, points deduction, grid drop and disqualification), with a preview before confirming.
- Computes standings with dropped worst results, team standings and stats such as wins, podiums, fastest laps and consistency.
- Runs the public kart draw with an audit hash, so anyone can check the result wasn’t tampered with.
Decisions that mattered
File reading is a separate service. Parsing lives in a Python service with FastAPI, called by the NestJS API over HTTP. Python has the best tools for the job: pdfplumber for PDFs, pandas for spreadsheets and Tesseract for OCR on images.
Deterministic before clever. Results are read by rules and go through a validator, with no language model in the middle. In a championship, a made-up lap time is worse than a rejected file.
Drop scores that are easy to explain. To drop results, each driver’s points are sorted and the N worst are removed. That’s the rule the regulations already describe, so any driver can redo the math.
Where it stands
Published, with the interface in Portuguese, English and Spanish. Live timing and plan billing are still simulated. Smaller tools from the same ecosystem grew around it: PitWall, LapCompare and RaceAnalytics.