Layover

The Layover Audit Standard

Every Layover credential is built from verified titles, employment dates, and performance — sealed at mint, tamper-resistant after.

Last reviewed · May 8, 2026

01

The Audit Tiers

Layover mints two credential tiers. Both require a verified HR Confirmation as the mandatory floor. The tier reflects the breadth of triangulating evidence on top of that floor — not the candidate’s underlying score.

Full-Credential

HR Confirmation + HRIS performance review(s) + Manager Vouch.

Maximum triangulation. Three independent sources confirm titles, dates, and performance. The mark a recruiter sees as a diamond on the candidate’s Layover Link.

Core-Credential

HR Confirmation + (HRIS performance review(s) OR Manager Vouch).

A baseline credential with one performance source riding on the verified HR floor. The minimum tier accepted into the Hangar.

The Floor — HR Confirmation

HR Confirmation is non-negotiable. The Flight Inspector blocks any mint without one. Every claimed title and every claimed employment date is verified against this document before mint, and the verification is stamped into the audit ledger as a server-clock attestation.

Acceptable forms of HR Confirmation

  • HR Letter of Employment Verificationformal letter on company letterhead, often used for mortgages or visas
  • Most recent (or final) pay stubshows your title and the dates you were employed
  • W-2 or 1099proves yearly employment for the relevant tax year
  • Separation packettermination paperwork with HR-signed dates and title
02

The Altitude Algorithm

A candidate’s Altitude is a 1.0–5.0 weighted blend of two performance sources, scored across five sensors. The formula is simple by design — defensible in a single sentence.

The Formula

Altitude = Manager Vouch × 0.60 + HRIS Reviews × 0.40

The Manager Vouch carries higher weight because it represents direct, named accountability — a real, identified person who signed off on this candidate’s performance.

The Five Sensors

Each sensor is rated 1.0–5.0. The Altitude shown on a Layover Link is the overall blend; the per-sensor breakdown lives inside the audit pack.

Sensor
What it measures
Execution
Output quality and impact in the role's core function.
Adaptability
Response to changing scope, ambiguity, and shifting priorities.
Ownership
Initiative beyond directives. Accountability for outcomes.
Collaboration
Effectiveness across teams, peers, and dependencies.
Communication
Clarity, timeliness, and receptiveness in formal and informal contexts.

Partial Coverage Doesn't Penalize

Some records have a Manager Vouch but no HRIS reviews. Some have HRIS reviews on only two of five sensors. Layover does not penalize partial coverage by truncating the available evidence — each side is averaged over its own non-null entries. If only one source exists, that source weighs 100% of the score.

The credential tier (Full vs. Core) communicates the breadth of evidence; the Altitude itself reflects the quality of what’s there. This is the credit-score model: use what is verifiable, don’t punish gaps that aren’t the candidate’s fault.

Multiple HRIS Reviews

Some records carry multiple performance reviews on file. Each review is normalized to the same five-sensor rubric, and the consolidated HRIS score is the element-wise mean across reviews.

No recency weighting is applied. Layover does not retroactively weigh a 2024 review more heavily than a 2022 one — the algorithm stays one-sentence-explainable.

03

The Inspector Protocol

Every Layover record passes through a Flight Inspector before mint. The Inspector’s role is not to evaluate the candidate. It is to verify that the evidence supports every claim, that the documents are authentic, and that the audit ledger is sealed against future tampering.

Delete-After-Verify

Source documents are purged from storage immediately upon mint. Layover does not retain copies of HR letters, pay stubs, or performance reviews after the credential is sealed. The mint is the moment the original documents leave our infrastructure.

What is preserved is the cryptographic ledger: a SHA-256 hash of each verified document, the extracted structured data (titles, dates, sensor scores), the verified manager’s identity, and the Inspector’s verbatim attestation. Every timestamp in the ledger is written by the server, not the client browser — so the audit trail is monotonic and tamper-resistant against any clock drift on the uploading device.

Mandatory Attestation at Mint

Before mint, the Inspector affirms — through a signed ignition switch — the following literal statement, which is then recorded verbatim into the audit ledger:

Inspector — at mint

I have verified the claimed title(s) and employment dates against the uploaded HR Confirmation.

lib/admin/attestations.ts · CLAIMS_VERIFICATION_ATTESTATION

The SHA-256 Collision Check

Every uploaded document is hashed at upload. Before mint, the Inspector reviews any prior records whose document hash matches — catching reused HR letters across multiple candidate accounts before they enter the credential ledger.

PDF Metadata Heuristics

Producer, Creator, CreationDate, and ModificationDate are extracted from every uploaded PDF and surfaced in the Inspector’s review. Anachronism patterns — for example, a 2019-dated review whose Producer string reads “iLovePDF 2024” — are flagged for closer scrutiny.

04

What You Sign Off On

Three parties affirm a record before mint. Each affirmation is preserved verbatim in the audit ledger and surfaced — by name — in the audit pack the recruiter receives.

Candidate — at submission

The uploaded HR documentation supports every title and employment date on this record. SSN, salary, and home address are redacted.

lib/audit/copy.ts · CANDIDATE_CLAIMS_ATTESTATION

Manager — at vouch

The manager rates the candidate across the five sensors, identifies themselves through corporate-domain authentication or LinkedIn verification, and explicitly confirms the candidate’s titles and employment dates within the company.

A signed ignition switch carrying the manager’s verbatim attestation rolls out alongside this page. The vouch screens persist the manager’s identity, the per-sensor ratings, and a server-clock timestamp regardless.

Inspector — at mint

I have verified the claimed title(s) and employment dates against the uploaded HR Confirmation.

lib/admin/attestations.ts · CLAIMS_VERIFICATION_ATTESTATION

The Credential of Record

The Layover Link URL is the credential of record. Any downloadable asset — Clearance Keys, share cards — is a visual display of that record, not the record itself. Verification always resolves to the link.

Why these literals matter

Once a record is minted, the literal text of every attestation is part of the credential. UI copy can evolve; the affirmation stamped into the ledger cannot retroactively change. The audit pack a recruiter buys today reflects the standard that was in force on the day the record was sealed.

Return to Layover →