The ARCQTYPE Verification Standard

Evidence paths already built

Game statistics — supported screenshots and exported records can be read into an athlete's record with their source attached. Importing a file does not automatically make every result Verified; athlete identity, source and the result itself still matter.

Lift evidence — supported lifts use video evidence and checks that it came through the app on a genuine device. A typed lift number alone does not establish verification.

Connected weight data — supported scale readings can arrive through a connected health source. That does not make every connected-health field a verified performance result. Height remains a typed-input exception, not an independently verified measurement.

These paths give us evidence to assess, not a blanket verification claim. Timing, jump, agility and throwing measurements need their own accepted methods and source requirements; the football 40-yard dash time is a priority within that work.

Three evidence levels

We are introducing three public levels across athlete metrics. They describe the evidence behind a result—not a promise of perfect accuracy or a shortcut to a recruiting decision.

Unverified — a submitted result without the evidence required for an accepted level. It stays visibly unverified even when used in an athlete's score or other views.

Industry standard — evidence that meets a documented, attributed method accepted for that metric and sport. We are researching those requirements by sport, position and ARCQTYPE. A commonly repeated claim is not enough; unsupported methods remain unverified.

Verified — evidence accepted against the applicable verification requirements, including source, athlete, event and measurement method. It is not interchangeable with a self-entered number or a file that merely says “verified.”

These are the levels we are implementing before launch, not a claim every existing screen and metric already supports them. Exact requirements will be published as research and implementation are validated.

What the asterisk tells you

An athlete can have an ARQ Score without a verified football 40-yard dash time. Our prelaunch direction is to keep that limitation visible with an asterisk and clear evidence status, rather than hide the result or imply it is verified. Unverified information can influence the record without becoming verified information.

Achievements must make the same distinction: a verified achievement and an unverified achievement should be recognizable as different. We are updating score and achievement presentation alongside the evidence system.

A number is not the whole record

Our standard asks: who produced the result; which athlete and event it belongs to; how it was measured; when and under what conditions; what supports its status; and how it can be corrected or withdrawn.

A result should carry its context when it moves between systems. The accepted result must be the actual value used—not a verification label attached to a different number.

Football 40-yard dash time: documented laser timing

For football 40-yard dash times, our rule is documented laser timing from an accredited camp, combine or team source. Hand-timed football 40-yard dash times do not qualify as Verified.

Athletes will submit a PDF or certificate to ARCQTYPE. We are researching accepted sources and document formats, with checks tying the result to its athlete, event and timing method. A familiar camp name or a label on a screenshot alone does not establish acceptance.

Other sports require their own research. Where hand timing is supported as an industry-standard method, it may qualify for Industry standard with the required evidence. That is not a blanket exception for football 40-yard dash times or permission to accept an unresearched method.

Current approaches

Competitors document a team-administrator workflow for entering game statistics. That describes submission access, not a laser-timing protocol for every metric.

Competitors describe combines as a source of verified recruiting measurements. Those overviews do not establish one device or start/finish method for every event.

Competitors publish material distinguishing stopwatch and automated timing and advocating standardized testing. Those are vendor descriptions, not independent proof of every result's accuracy.

These examples are not a competitor ranking or evidence of one universal industry standard. We compare submission paths, methods, provenance, context and corrections; undocumented details remain unknown.

Measurement, evidence and inference

A measured performance, its evidence level and an inferred estimate answer different questions. A number can be measured yet lack authenticated provenance. An estimate is not an observed performance and must never be presented as an externally laser-verified time or verified percentile.

AI can help extract information, organize records and flag inconsistencies. It cannot make an unsupported submission true. Our scoring calculations remain proprietary; this page describes evidence standards, not formulas or unproven accuracy claims.

Video timing: postlaunch work

ARCQTYPE's in-app football 40-yard dash video timing system remains a separate postlaunch capability. Its output is user-uploaded/video-derived timing and does not meet the football laser requirement. This roadmap does not announce its public availability.

A standard that can improve

We are developing source-linked records and explicit correction, withdrawal and freshness rules. Changes to those rules should identify the applicable version. Disputed or revoked evidence must not silently continue to appear as current Verified evidence.

The goal is less uncertainty about the record and better-informed evaluation of the athlete. Evidence cannot promise recruitment, eligibility, selection or future performance.

References and revision history

Sources reviewed September 13, 2026. Version 0.3 highlights evidence paths already built and the remaining measurement-standard work; the landing-page entry is now in the header. Version 0.2 introduced the prelaunch three-level direction and separated postlaunch video timing. See also About the ARQ Score. Source-specific requirements continue to evolve through research and validation.