Build a cockpit around proven contact coordinates.

1. System overview & core philosophy

DialedRide N+1™ is a client-side, local-first workshop for adjusting an existing bicycle cockpit and evaluating a prospective frame. The bottom bracket is the coordinate datum. The engine resolves steerer angle, headset cap and spacer projection, stem length and angle, bar reach and rise into modelled contact reach and stack, with fit adjustments for cockpit width, crank length and seatpost setback. Lateral stance is also reported separately. These effective coordinates are model outputs, not a substitute for measuring the fitted bike.

Sandbox: the default workspace for adjusting your current bike within the supported input ranges. N+1 Fit Translator: a candidate-frame workspace that compares a proposed build with your reference coordinates. A numerical match does not establish that the hardware can be assembled safely.

Currently available: Drop Bar and Flat Bar cockpits with Road and Gravel presets. TT / Triathlon controls and loading are temporarily paused; previously saved TT setups are retained locally.

2. Global Rider Profile

On first use, complete Body & Bike Data, then select Save Body & Bike Data — Open Sandbox. It becomes a compact summary below the navigation; use Edit Rider to reopen it. Rider measurements, bike settings and the comparison baseline are saved locally. Separate PCs or browser profiles do not synchronise this data. Clearing site data or using Clear All Data & Cache removes the saved rider and bike data.

Auto saddle height (mm) = round[inseam (cm) × 10 × (0.883, or 0.865 when inseam > 88 cm)]

For drop or flat bars, a manual saddle height more than 15 mm from the formula baseline shows an informational amber notice. It does not block the calculation. The formula is a starting point, not a clinical prescription.

3. Workspace 1: Single-Bike Sandbox

1. Define the reference bike. Enter frame reach, frame stack, head tube angle (HTA), and headset bearing top-cap height from the frame's published geometry or measurements.
2. Choose cockpit type. Select Drop Bar or Flat Bar. Changing bars preserves the selected frame category. The effective-reach model adds 0.4 × the width difference in millimetres from a neutral 420 mm drop bar or 600 mm flat bar. This is a fit adjustment, not a physical forward movement of the bar.
3. Configure hardware. Set stem length (60–140 mm in the Sandbox), stem angle (−17° to +17°), spacers (0–40 mm), bar width and reach, and drop-bar rise (0, +10, +15, or +20 mm). Set crank length (160–175 mm) and seatpost setback (−20 to +25 mm).
4. Save a baseline. Valid frame reach, stack and cockpit hardware are needed to calculate, solve, save or export a setup. Select Save as Baseline Bike to store the current contact coordinates as the comparison anchor and save the bike in the garage. Without a baseline, the target starts from the live setup. Loading a saved reference bike or auto-solving can also capture an anchor; on reopening the page, a valid restored reference setup can become the baseline automatically.
5. Experiment. The large Effective Reach / Stack readings follow the current frame and hardware. The smaller Target readings use the saved baseline plus Riding Intent and any stored posture adjustment. Check Base: [reach, stack] to see the anchor. Editing or saving Body & Bike Data leaves an existing baseline intact. Save as Baseline Bike replaces it deliberately; Revert to Baseline restores its frame and hardware; Clear removes the anchor without deleting garage bikes. Older baselines with unknown contact points or incomplete geometry must be loaded from a saved bike or saved again.
6. Use the posture meter. The Short / Upright to Long / Aero scale compares current coordinates with the baseline. Dragging it asks the solver to change hardware towards the selected posture. Review the resulting settings and advisories. It is a comparison aid, not a medical assessment.

4. Mechanical & handling advisories

The Sandbox raises real-time flags at these thresholds. They are prompts for component-specific checks; the app does not verify your fork, stem, frame, or rider's physical safety.

5. Workspace 2: N+1 Fit Translator

1. Transfer your setup. In the Sandbox, select Translate Setup to New Frame (N+1 Configurator) → to replace the baseline with the current Sandbox coordinates and carry over cockpit type and relevant hardware. Revert first if you want to translate a saved baseline. Simply opening the N+1 tab keeps an existing baseline; if none exists and tape measurements are incomplete, it captures the valid Sandbox setup for Method A. A blank workspace with garage bikes loads the newest saved baseline, or the latest saved bike if none is marked as a baseline.
2. Choose the target source. Method A: Current Bike offers Sandbox reference bike, which uses the saved baseline, or Tape measurements. Tape measurements require positive saddle height and reach to hoods / grips, plus explicitly entered saddle setback and saddle-to-bar drop; zero is valid for the latter two. Reach is the horizontal saddle-to-contact distance minus setback. Stack is saddle height projected vertically using the reference seat-tube angle, minus drop. Method B: Body Fit Model estimates a starting target from rider dimensions, saddle height, the Road or Gravel preset and Riding Intent. When Method A reports that the Sandbox has moved away from its saved reference, Use current Sandbox setup captures a new baseline.
3. Set riding intent. Relaxed / Stable, Neutral / Balanced and Performance / Aero share one setting across the Sandbox, Method A and Method B. Relaxed shortens target reach by 0.8% of modelled torso-plus-arm length and raises stack by 20 mm. Performance lengthens reach by the same amount and lowers stack by 20 mm. The reach shift is usually around 11 mm, depending on rider proportions. Neutral adds no shift. The Sandbox shows the shift beside its posture gauge.
4. Enter candidate geometry. Supply the new frame's reach, stack, HTA and headset cap. Review discipline advisories and check contact position and control access if changing between drop and flat bars.
5. Run the solver. Select Calculate Optimal Hardware (or Auto-Solve to Target in the Sandbox). The drop / flat solver ranks builds by a weighted balance of target distance and hardware changes. Within 5 mm counts as a coordinate match; missing that window adds a penalty. It favours reusing the saved baseline hardware for the same cockpit type, otherwise the current build, without enforcing a fixed order of spacer, stem and bar changes. It searches common stem lengths in 10 mm steps, −17°, −6°, +6° and +17° angles, and owned/current values. Drop bars also have a +15 mm rise option alongside existing rise settings. Bar reach and width, crank length and seatpost setback stay at the entered settings.
6. Review the app's mechanical checks. Proposed spacers plus headset cap never exceed 30 mm. No proposed option trips the handling advisories in section 4 (for example, no stem at −10° or steeper and none of 120 mm or longer on gravel, none under 5 mm of spacers on gravel, and no +10° or steeper on road). If the cap alone is over 30 mm, or no build passes these checks, the solver says so. Passing these checks does not establish physical compatibility or safety.
7. Review the options. If the recommended result needs no changes, it appears alone. Otherwise up to three distinct options are listed, each showing what changes from the current build. An option never needs a kind of part (stem or bar) that the top option avoids. Option 1 is applied automatically only when its coordinate distance is 15 mm or less.
8. Check mismatch and apply. If the top recommended build is more than 15 mm from the target, an amber geometry mismatch banner appears and nothing is applied automatically. Select Apply on a listed option only if you accept the offset. Applying an option updates the relevant bike's hardware and closes the result drawer.

Coordinate distance d = √[(build reach − target reach)² + (build stack − target stack)²]

Lateral stance is reported separately and is not included in this distance. When translating between drop and flat bars, the candidate reach calculation omits the width-based reach adjustment; check lateral stance and actual hand position separately. Cross-discipline matches need a real-world control and clearance check even when reach and stack are close.

6. Exporting the Build Setup Dossier

Select Export / Print Build Dossier for the active Sandbox or translator setup. Review the preview, then select Print / Save PDF to print or save a PDF through your browser.

• Configured frame geometry: bike name, frame reach, stack and HTA.
• Contact audit: target, configured build, offset, and status for horizontal reach, vertical stack, and lateral stance width.
• Saddle and pedalling foundation: shared saddle height, saddle setback, seatpost setback and crank length. Saddle setback prints as Not entered unless a measurement was supplied; it is not inferred from seatpost setback.
• Assembly hardware: stem length and angle, spacers plus headset cap, bar reach and width, and bar rise.
• Verification: mechanic / fitter sign-off and a reminder to verify manufacturer torque specifications before dynamic testing.

Status labels are coordinate comparisons. Passed or Acceptable does not certify component compatibility or roadworthiness.

7. Scope & Legal Disclaimers

These notices do not remove statutory consumer rights or liability that cannot lawfully be excluded. Consumer terms and notices remain subject to the Consumer Rights Act 2015 and its fairness requirements. The wording below should be read subject to those protections.

• No Purchasing or Sizing Liability:
  DialedRide N+1™ is an exploratory geometric modeling and mathematical estimation tool provided solely for informational and comparative purposes. DialedRide, its creators, developers, and contributors accept no liability or responsibility for any financial loss, purchase decisions, component acquisitions, frame choices, or mechanical outcomes arising from the use of this software.
• Physical Verification Mandate:
  Riders, builders, and mechanics are solely responsible for physically verifying all frame geometry charts, component compatibilities, cable/hydraulic hose routing clearances, manufacturer sizing recommendations, and real-world ride comfort prior to purchasing or assembling any bicycle, frameset, fork, or cockpit component. A mathematical match in Cartesian space ([X,Y] coordinates) does not guarantee physical suitability, handling satisfaction, or ergonomic comfort for any individual athlete.
• Not a Medical or Clinical Assessment:
  DialedRide N+1™ executes deterministic trigonometric coordinate translations based strictly on user-supplied numbers. It does not assess joint angles under dynamic load, spinal mobility, soft-tissue compression, pelvic tilt, or musculoskeletal pathology. It is not a substitute for a comprehensive in-person dynamic bicycle fitting or clinical musculoskeletal assessment by a qualified professional.
• Hardware & Structural Safety:
  Athletes and mechanics bear sole responsibility for verifying component torque ratings, fork manufacturer carbon steerer spacer limits, and physical frame/component clearances prior to dynamic operation.
• Governing Jurisdiction:
  This software, its calculation algorithms, and all associated documentation are governed exclusively by the laws of England and Wales. Any disputes arising hereunder shall be subject to the exclusive jurisdiction of the courts of England and Wales.