← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

Results and Reports

Purpose

Explain how to review live results, use the Reports page, save reusable report templates, and use the dashboard export shortcuts for one-off file exports.

Prerequisites

  • The meet already has athletes, entries, or results worth viewing.
  • For live timing workflows, connectors and reads are already working.
  • For publishing workflows, the outbound connector or export target is already configured.

Results vs. Reports vs. Export

These are related but not identical surfaces in 2Timer.

Results

Use Results when you want to inspect or edit the live competitive outcome for entries and events.

Reports

Use Reports when you want formatted output for operators, coaches, announcers, scoring, or printing.

Export

Use the dashboard Export shortcuts when you want a specific file format such as:

  • 2T Backup
  • Lynx
  • Hytek
  • CSV
  • TFRRS Results
  • HTML Results

Viewing Live Results

During a race or meet, open the live result views to inspect rankings and entry outcome state.

2Timer computes place from the appropriate discipline-specific result model:

  • gun or chip timing for running
  • mark-based ranking for field events
  • team-score output for XC and T&F reports

Important field-event behavior:

  • horizontal jumps and throws can use full legal-mark series for tie-break context
  • vertical jumps use ordinary misses and attempts logic before any manual official resolution

For super-events, 2Timer can preserve separate sub-event scoring while still presenting the combined physical race context.

Common Result Statuses

Status Meaning
Entered Registered but not yet finished
Checked In Confirmed for staging or participation
Pending Arrived but result not yet fully recorded
Finished Has a result and is part of place computation
DNS Did not start
DNF Did not finish
DQ Disqualified
WD Withdrawn
No Height Vertical jump: no cleared height
No Mark Field event: no legal mark
Foul Field event: all attempts were fouls

The Reports Page

Open Reports from the meet navigation.

The current reports UI includes:

  • a searchable report list
  • canned report cards
  • saved custom templates
  • favorites
  • a page-level scope filter
  • a Custom report button that opens the custom-report modal

Filters and Scope

The reports page lets you narrow what you are looking at by:

  • source: all, canned, custom, or favorites
  • report type
  • name/description search
  • scope: all events or a selected event

That scope setting affects both canned reports and template views/downloads.

Canned Reports

The page ships with canned report presets based on meet sport and genre.

Examples include:

  • results-oriented reports
  • team results
  • start lists
  • participants reports
  • performance lists
  • finish line sheets
  • field event sheets
  • meet operations reports

The exact set depends on the meet.

Custom Reports

Click Custom report to open the report builder modal.

The current UI supports custom builders for report families such as:

  • results
  • MVP report
  • start list
  • performance list
  • participants
  • meet operations

Inside the custom report flow you can:

  • preview a report
  • download it
  • save it as a template
  • edit an existing template later

Saved Templates

Saved templates appear in the same report list as canned reports.

You can:

  • open a saved template
  • download from it
  • edit it
  • delete it
  • mark it as a favorite

This is the best workflow when you reuse the same packet or export shape repeatedly across sessions or meets.

Downloads from the Reports Page

The Reports page supports one-off downloads directly from canned reports, custom reports, and templates.

Current formatter choices used there are based on the report formatter registry and include common text and table outputs such as:

  • txt
  • html
  • html-fixed
  • csv
  • tsv

If a report has zero rows, the page warns instead of exporting an empty file.

Dashboard Export Shortcuts

The meet dashboard also exposes direct export shortcuts outside the Reports page.

Current dashboard export pills include:

  • 2T Backup
  • Lynx
  • Hytek
  • CSV
  • TFRRS Results
  • HTML Results

Use those when you already know the exact export family you need and do not need the full reports browser first.

TFRRS Results Export

For collegiate T&F workflows, the dashboard export area includes TFRRS Results.

Use this when you need the dedicated TFRRS results export rather than a generic report download.

Make sure athlete registration IDs and result data are ready before exporting.

Published and Connector-Driven Output

If the goal is continuous outward publishing during the meet, use connectors rather than repeated manual downloads.

Typical connector-driven publishing targets include:

  • local folder
  • S3 / R2

See Connectors for the setup side of that workflow.

XC Team Scoring in Reports

For cross country meets:

  • team scores are derived from scorer/displacer rules
  • team reports depend on correct team assignment
  • teams marked Unattached are excluded from team scoring
  • league or conference views depend on correct league setup

If team output looks wrong, verify team codes, unattached status, and league membership before assuming the report itself is wrong.

See Cross Country Scoring and Teams and Leagues.

T&F Team Scoring in Reports

For track and field meets:

  • scoring uses place points
  • only finals-round scoring counts
  • selected finals heats can be marked as scoring heats while others remain non-scoring
  • teams marked Unattached are excluded from team scoring
  • double-dual or head-to-head report splits depend on league setup
  • team-lane seeding depends on correct team Lane Slot setup, which can affect heat layout and downstream reporting context

Team totals then appear in the team-oriented report outputs.

If your meet uses head-to-head league views, verify the team league memberships or use the Generate Double-Dual Leagues macro from the Leagues page when appropriate.

See Track and Field Team Scoring, Teams and Leagues, and Team-Lane Seeding.

When to Reset Results First

If the report output is wrong because the underlying result layer is wrong, fix the data before trying to solve it with another export.

Use Purging Results and Resetting State when:

  • bad reads were imported
  • result state needs to be rebuilt
  • the meet structure should stay but the result layer should be cleared

Archiving the Meet

After the meet, export a full .2t backup from the dashboard export area.

That backup is the safest archive if you may need to restore or merge the meet later.

Recommended Workflow

  1. Check live results first.
  2. Fix statuses or obvious data problems before reporting.
  3. Use canned reports when one already fits the job.
  4. Use the custom report modal when you need a tailored output.
  5. Save recurring custom layouts as templates.
  6. Use dashboard export pills for specific format-driven exports like TFRRS, Hytek, Lynx, HTML, or .2t.
  7. Use connectors for continuous live publishing.

Common Problems

Problem Likely Cause Fix
Report is empty Current scope or filters exclude the needed rows Check event scope, search, and report type filters
Team report looks wrong Team assignment, unattached status, league setup, or scoring setup is wrong Verify teams, unattached teams, leagues, and scoring setup
Double-dual split output is missing Pairwise leagues were never created Create leagues manually or run Generate Double-Dual Leagues
Heat-based output feels inconsistent Team lane slots changed seeding layout Verify team Lane Slot assignments and reseed if needed
Export shape keeps changing each time A repeated workflow is not saved as a template Save the custom report as a template
Report output is wrong after bad import The result layer is wrong, not the report format Reset/rebuild results before exporting again
User expects a dashboard export in Reports That format lives in the dashboard export pills Use the dashboard export shortcut instead

Verification Checklist

  • Live results look correct before final export.
  • Filters and event scope are set intentionally.
  • Team-oriented reports were checked against scoring setup.
  • Teams that should not score are marked Unattached.
  • League-based reports were checked against the meet’s league memberships or double-dual macro output.
  • Team Lane Slot setup was verified if the meet uses team-lane seeding.
  • Reusable custom layouts were saved as templates if needed.
  • A final .2t backup was exported for archive.

Related Pages

Metadata

  • Last Updated: 2026-04-18
  • Version: 0.3
  • Status: Active