Motorsport & Racing

Every discipline. Your way of racing.

From karts to rally cars, club racing to Formula One. Connect vehicle configurations, components and evidence through development, testing, competition and service.

Use the motorsport starter

17 record types · 40 optional fictional example records

Define your category and local context.

Keep discipline, vehicle class, country or jurisdiction, governing body or ASN, championship and season separate. Enter your own names, manage several programmes in one project, and link the rules and amendments that apply to each event.

Karting

Record engine hours, rebuild history, sprocket gearing and tyre set identities alongside heats and tests.

Circuit and club racing

Enter one vehicle in several series, retaining each entry’s configuration, class and eligibility evidence.

Endurance

Record driver stints, component running time and pit-service history, with explicit units and timing evidence.

Rally

Keep stage and road mileage scopes separate, record driver/co-driver pairing, and define component service intervals.

Other racing categories

Use local names and units for hillclimb, rallycross, rally-raid, drift, drag, oval, historic racing or your own category. Each programme keeps its country, authority, class and rule editions.

The four starter examples are starting points. Use your own names and fields for hillclimb, rallycross, drifting or another discipline and its local categories.

Motorsport: any category

First steps after applying
  1. Define your programme and rules

    Choose an editable karting, circuit, endurance or rally example, or start without examples. Enter your discipline, class, jurisdiction, authority, championship and season. Link the source editions and event instructions you actually use.

  2. Connect a vehicle and configuration

    Open a Competition vehicle, create a Vehicle configuration and record its components and setup values with units. Preserve earlier configurations for comparison.

  3. Record running, service and inspections

    Link your session, stage, heat or stint to its vehicle, event and configuration. Enter measured usage with units and retain actual service and inspection evidence. No sporting permission is inferred.

Read the motorsport starter guide

Review component totals by exact unit and usage scope, remaining service life from an explicit baseline, duplicate or inconsistent records, event preparation and affected entries when a linked rule edition changes. Plan and assign service work, record completion with evidence and an optional new baseline, then save the reviewed source versions and findings. Rebuilds preserve earlier usage history; incomplete evidence stays visible.

Use the motorsport starter

Link the rules for your programme.

Record each document’s issuer, edition, effective dates, applicability and exceptions. Link successor editions to discover affected entries and events, then retain applicability review evidence. Keep several sporting, technical, local or supplementary documents for each event or entry, with independent applicability reviews. Example countries and classes are fictional; external regulation websites are not monitored automatically.

From preparation to the next review.

Use the same process across racing disciplines. These actual app screens show event preparation, inspection, follow-up, service and saved-review comparison.

  1. Prepare

    Connect entries, vehicle configurations and fitted components. Keep sporting, technical, local and supplementary documents together, with a separate applicability review for each.

    Event preparation showing entries and attention or unknown findingsClick to enlarge ↗
  2. Inspect

    Check inspection outcomes and the current reviewed inputs. Record equipment certificate validity and inspection deadlines, then check them against the event date too.

    An inspection finding that retains a failed outcome requiring attentionClick to enlarge ↗
  3. Resolve

    Open an existing follow-up beside its finding, or plan one. Give it an owner, due date, corrective action and closure evidence, then recheck the current sources to record closure.

    Finding follow-up showing its owner, due date and current closure statusClick to enlarge ↗
  4. Service

    Plan and assign vehicle or component work. Filter due work by owner and status, and choose how far ahead to see service and equipment inspection deadlines. Retain the actual work and evidence.

    Native service record and the service action buttonClick to enlarge ↗
  5. Save and compare

    Preserve the reviewed source versions and compare two reviews. Download a printable handover of outstanding checks, owners, deadlines and evidence references for the selected event or full project.

    Earlier and later saved reviews with resolved findings in their comparisonClick to enlarge ↗

Changes that need another review stay visible.

New inputs, changed sources or recurring findings require another closure recheck. Incomplete coverage and removed sources cannot appear resolved in a comparison. Screens use fictional example data.

Detailed example: Formula One workflows

Explore setup submissions, power-unit allocations and parc fermé evidence in the separate F1 starter. Its rules and checks are not automatically applied to other disciplines.

Two cars. One connected race weekend.

Bring each car’s setup, submitted sheet and written authority decisions into one race-weekend review in ManyRows PLM. Explore a Formula One inspired workflow with the fictional Aster Racing team.

Choose a workspace, then review the template for a new project.

2
independently configured cars
68
power-unit elements
20
season allocation pools
ASTER RACING / HARBOUR WEEKEND
01:35 · Silent, with captions

Review the weekend. Keep the evidence.

Review setups, fitted parts, component life, allocations and work by car or event. Open the source records behind each finding and download the review.

ManyRows race-weekend review filtered to the Harbour event and Car 1, showing Download review and an energy-store allocation finding of four introduced elements against three allowedClick to enlarge ↗
Car 1 · Filter the findings while retaining the full-season allocation total: 4/3.

Focus on the car and event.

Save car, event, check, finding-status and search filters in the URL. Keep current fitments, component health and full-season allocations in view.

Follow a finding to its source.

Inspect exact submitted revisions and serial/quantity differences. Surface seal issues, duplicate fitment, missing evidence and incomplete scope.

Keep the evidence you reviewed.

Download selected findings, filters, capture time, source identities and coverage gaps as JSON. Review findings and permission to work remain separate.

From the rule to the next task.

Connect the records your team needs at three points in the race weekend.

Before qualifying · keep the submitted setup

Start a declaration from the session. Link the approved revision and actual sheet receipt, then record first pit exit or SQ1/Q1 end for a car that never exits.

FIA B3.5.1–B3.5.2 ↗

Before work · review the basis and conditions

Compare submitted and current settings, then review the permitted-work provision or written decision. Link actual execution times and removed-part custody evidence.

FIA B3.5.3–B3.5.4; Appendix B2 ↗

After running · record each serial’s history

Record mileage for the serials that ran. Keep a new power-unit element’s first competition-use evidence linked to its season account and review it separately from distance.

FIA B8.2.2–B8.2.9 ↗

Reference: 2026 FIA Sporting Regulations, Issue 09 · 1 October 2026. Checked 13 October 2026. Check current FIA editions ↗

Connect official notices to car-seal history.

Keep the original communication, receipt and acknowledgement together. Record each cover or seal action with its own evidence.

Separate receipt from acknowledgement.

Record the recipient, original document, receipt time and acknowledgement evidence. Review outstanding acknowledgements and conflicting clocks by car and event, then export the exact UTC timestamps.

FIA B1.1.2 ↗
ManyRows official communication receipt showing the document reference, recipient, acknowledgement state and UTC timesClick to enlarge ↗
Issue, receipt and acknowledgement are separate recorded events.

Follow each cover and seal action.

Record fitting, removal and inspection with a time, witness and source evidence. Link the previous event and relevant communication, then review conflicting cars, periods, seal references and chronology.

FIA B3.4 ↗
ManyRows car-seal history showing separate application and removal records with a seal reference, witness and UTC timesClick to enlarge ↗
A recorded seal removal does not end parc fermé or authorize work.

Every change has a context.

Follow driver-specific configurations, season allocations, and release evidence through the same product model.

01 / 02

Different drivers. Different parts.

Alex Vale and Mika Laurent run different aerodynamic and cockpit components. Each car has 21 individually identified fitted serials, with its own design specification and setup declaration.

CAR 1 / ALEX VALE
Aster Racing Car 1 configuration with individually identified fitted serialsClick to enlarge ↗
CAR 2 / MIKA LAURENT
Aster Racing Car 2 with its independent fitted component configurationClick to enlarge ↗
03

See exactly what changed.

Compare the frozen practice-arrival configuration with the current car. Identify the replaced wing serial, then follow the upgrade back to its engineering BOM.

Car 1 wing upgrade comparison showing one removed serial, one added serial, and 20 unchanged itemsClick to enlarge ↗
One wing replaced. A configuration history you can follow.
04

Track stock through first use.

Manage power-unit allocations by driver-season account. Distinguish an unused spare, a returning engine, and a new first-use commitment. Review the linked rule source and evidence.

Laurent energy-store pool showing four introduced elements against three permitted elements and an allocation reviewClick to enlarge ↗
Source-linked allocation review. People decide the sporting outcome.
05

Keep life with the serial.

Car 2’s fitted gearbox has run 130 km beyond its 3,000 km team maintenance limit. The replacement spare starts at zero with a separate mileage history.

Car 2 gearbox life meter showing 3,130 km used against a 3,000 km limit, exceeded by 130 kmClick to enlarge ↗
Team maintenance limits and season allocations stay separate.
06

Move from approval to evidence.

Setup approval pins the declaration to a revision. Both required inspections must pass before internal certification. Keep the written request and external authority decision alongside it.

Two required inspections passed and tied to the approved setup revisionClick to enlarge ↗
An approved revision. Two required checks. Traceable evidence.
07

Keep the submitted sheet tied to its revision.

Start a setup declaration from a session’s recorded car, event and driver. Enter settings, approve the revision, then record delivery and receipt evidence. Keep Pre-Sprint and Pre-Race control timing separate.

Harbour Car 1 qualifying setup-sheet submission linked to its approved declaration revisionClick to enlarge ↗
The declaration, submission and session timing each have their own record.
08

Follow the written decision through the work.

Start a follow-up reply with the same request and a link to the reply being replaced. Enter new written evidence, conditions and validity, then review the exact request revision, actual work timing and part custody.

Fictional written authority reply linked to the Harbour controlled-inspection requestClick to enlarge ↗
Internal approval and the written authority response retain separate evidence.
09

Review the weekend evidence.

See every submission and reply for a car and event. Follow their approved revisions and the UTC timeline, then download the complete record.

ManyRows weekend evidence register with setup submissions, written replies and a timeline of missing timestampsClick to enlarge ↗
Submissions, replies and timing in one place.
10

Choose the submitted revision.

Select an approved revision and check its car, event and driver. Use that revision when recording the submitted sheet.

ManyRows revision chooser showing an approved declaration and its car, event and driverClick to enlarge ↗
Choose the revision used for the actual submission.
11

Use one clock across the team.

Enter and review session, submission and work times in UTC. Recorded seconds and fractions stay intact across team timezones.

ManyRows setup submission editor with UTC entry, seconds and millisecondsClick to enlarge ↗
The same recorded time in every timezone.
12

Read the reply before work.

Review the recorded decision and conditions beside the work. Expand the evidence and record details when you need them.

ManyRows written reply with a recorded decision, highlighted conditions and approved requestClick to enlarge ↗
Review the decision and conditions together.
13

Compare the submitted setup with today’s declaration.

Compare recorded ride heights, camber, torsion rates and control maps. Read exact submitted and current values on your phone, and keep the submitted revision and missing evidence together in the JSON download.

ManyRows setup comparison showing a front-wing setting difference between the submitted revision and a later internally approved declarationClick to enlarge ↗ManyRows setup comparison showing a front-wing setting difference between the submitted revision and a later internally approved declarationClick to enlarge ↗
A declaration difference needs review. Separate evidence establishes when physical work occurred and whether it was permitted.
Internal release certificate for revision 1 of the qualifying setup declarationClick to enlarge ↗
The setup declaration is internally released. Physical car fitment is a separate operation.

Start with the same model.

Review the template against your available record capacity. Start with the structure, or include the fictional Aster Racing examples to explore the connections.

27
record types
593
optional example records
6
inspection plans

What the template connects

  • Car specifications and design BOMs
  • Drivers and season accounts
  • Serialized parts and car fitment
  • Power-unit pools and first use
  • Setup-sheet submissions and written authority replies
  • Official communication receipts and car cover/seal history
  • Sessions, work orders, inspections and weekend review
First steps after applying
  1. Compare the two cars’ fitted serials

    Open each Race Car and inspect its Car Specification, fitted component lines, serial mileage and driver-season allocation pools. Keep the design BOM and physical fitment connected.

  2. Review and submit the exact setup revision

    Open a Car Setup Declaration, approve the intended revision and complete its required inspections before internal certification. Record the Setup-sheet Submission with that exact approved revision, recipient, UTC submission time and receipt evidence.

  3. Review the weekend’s written evidence

    Open Race-weekend review for the intended car and event. Review the Evidence register, UTC timeline, recorded Authority Responses and work-order evidence; retain written scope, conditions and validity when deciding whether work may proceed.

Read the racing starter guide

Common questions

Where do I find the next task?

Project Home separates Workflows, Work queue and Records. In Work queue, focus on work assigned to you, overdue, unassigned or blocked tasks, then open the native record, next planned step or exact unfinished prerequisite. Additional records and evidence gaps remain visible; completing a planning step does not complete an inspection or authorize sporting work.

Do I have to include the example records?

Apply the model without example records, choose a smaller walkthrough, or include the full set of 593 fictional linked example records. The template preview checks your workspace’s remaining record capacity before application.

Does the template arrive with the releases shown in the video?

The video records actual approval, inspections, and internal certification in a prepared demo. The reusable template starts its setup declarations as drafts so your team can complete its own review and checks.

What does the race-weekend review check?

It checks submitted revisions, car/session identity, control timing, fitment and setup-value differences, component life and seals, season allocations, first use, session mileage, request/work drift, written responses, execution/custody evidence, communication acknowledgements and car cover/seal history. Filter by car or event and download recorded values as JSON. Missing evidence and incomplete scope remain visible.

Does a setup difference mean a regulatory breach?

The comparison shows recorded values in the submitted revision and the current saved declaration. Later changes can be intentional or permitted work. Review actual work timing, applicable rules, exceptions and written permission separately. Custom fields and values absent on both sides are excluded from the comparison.

Are setup submissions and authority replies prefilled?

Submissions, authority replies, official communication receipts and car cover/seal events start empty so your team can enter actual evidence. Workflow shortcuts carry references; settings, decisions and times remain your inputs. Select the exact approved declaration or request revision. The receipts and written replies in the screenshots are fictional entries added for the demonstration.

How do the register and revision chooser help?

The Evidence register includes all submissions and replies in the car/event scope, even when the Findings view is filtered. Its UTC timeline preserves missing timestamps as unknown. Choose approved revision loads the linked source’s approval history and frozen scope before you explicitly use an ID. Work-order reply previews read the saved conditions and compare scope and timing; they do not authorize work.

Is this an official FIA compliance tool?

The template demonstrates representative engineering workflows and links rule sources to evidence. People review inventory categories, exemptions, seals, allocations, penalties, and sporting permission.

Connect your team’s next change.

Use the racing template as a starting point, then adapt the parts, checks, and review workflow to your team.

All team, driver, event, and evidence data is fictional. The model draws on selected 2026 FIA workflows; it carries no FIA affiliation or official certification. Internal approval and sporting permission are separate decisions.