Bring in the files.
Import your roster and the race results as CSV. Confirm the columns and choose which race time to use.
team-roster.csv
race-results.csv
Find your runners.
Make results team-ready.
From a long finish list to the names that matter.
Match your roster, review the uncertain cases, and publish with confidence.
THE WORKSPACE
Explore demo Team results Synthetic demo
40 Team athletes29 Verified8 Needs review 300 source records
| Team athlete | Source name | Distance | Net time | Status |
|---|---|---|---|---|
| 001Maya Chen | Maya Chen | 10K | 00:42:16 | Verified |
| 002Sofia Alvarez | Sofia Álvarez | 10K | 00:44:03 | Verified |
| 011Taylor Reed | Two possible results | 5K | — | Needs review |
| 012Rafael Santos | Rafael Santos | 10K | 00:43:10 | Verified |
Uncertain matches wait for your decision.Fictional athletes. Real workflow.
BUILT FOR THE WORK AFTER THE FINISH LINECoachesClub managersContent teams
01 / THE WORKFLOWA finish list is a start.
A finish list is a start.
Your team results are the goal.
One workspace for the three steps between race-day data and a list you can share.
Check the match.
Unique exact names are checked against the source fields. Similar names and conflicting records need your review.
Taylor Reed 2 candidates Your decision needed
Share the results.
Export verified identities with valid finish times. Get a clean CSV or an HTML list, grouped by distance and sex.
CSV HTML
02 / CONFIDENCE, FROM THE SOURCEA name match
A name match
is only part
of the story.
The original record stays beside each suggestion. Repeated names, conflicting distances and unusable times are surfaced before export.
Read our privacy detailsYou make the uncertain calls.
Similarity helps you review. It is never treated as proof of identity or an automatic approval.
Your files stay with you.
Import, matching and exports run locally in your browser. No CSV uploads, accounts or tracking scripts.
A workspace that resets.
Files and decisions live in memory. Refreshing or closing the page clears the workspace. Save your exports first.
03 / WHAT WE’RE BUILDING NEXTPlanned integration
Messy source.
Structured result.
Human judgment.
We plan to connect Claude to BibOps through an MCP server (Model Context Protocol). Claude would interpret permitted race sources, propose column mappings and help compare ambiguous athlete records through scoped tools. Every proposed value would retain its source reference; uncertain identities would still require human approval.
The next inputs
- Race-result PDFs
- HTML result tables
- Links to official sources
Planned Claude + MCP workflow
- Inspect the sourceRead an operator-approved PDF, table or race source and retain the original references.
- Propose and compareSuggest field mappings and retrieve candidate records for side-by-side review.
- Approve and validateA person resolves uncertain identities. Deterministic checks decide which source-backed results can be exported.
Status: architecture planned. No public MCP endpoint or Claude API integration is active. The current MVP processes CSVs locally and does not send your files to Claude.
Closer to the team.
Closer to the problem.
BibOps is being built by Gustavo Marchioro, drawing on experience working alongside running teams in Brazil. It starts with a familiar task: finding a club’s athletes across thousands of finishers, then preparing the results for coaches and content teams.
We’re an early-stage product, building a focused tool for that work.
Talk to Gustavo gustavo@bibops.techA FEW PRACTICAL DETAILSBefore you
Before you
get started.
What can I use today?+
Import a team roster and race results as CSV, map the columns, review suggested matches and download CSV or HTML results. You can try the complete workflow with our synthetic demo.
Is BibOps using Claude?+
Not in the current MVP. Claude is planned for interpreting unstructured sources and assisting review. The current CSV workflow uses deterministic validation and name similarity, with human decisions for uncertain cases.
How will Claude connect to BibOps?+
The planned MCP server will expose source inspection, mapping, search, comparison and export-validation tools to Claude. Access will be authenticated and limited to the operator-approved session. Provider credentials will remain server-side. This is a proposed architecture, not a connector available today.
Are my race files uploaded?+
No. Files are processed in your browser’s memory. Refreshing clears the session. The hosting provider may retain technical access logs; see our privacy page for details.
Do I need an account or subscription?+
No account or payment is needed to evaluate this version. Check every result against the organizer’s source before publication. BibOps is not an official timing system.
The finish line isn’t
the end of the work.
Open the demo 40 fictional athletes. 300 sample records. One complete workflow.