Editorial Standards
Our goal is to publish clear, practical information that complements the calculator.
Sourcing
We review widely used public health guidance and standard references to ensure our explanations are broadly consistent with common practice.
Review and updates
We revisit core pages periodically and respond to reader feedback by clarifying language or adding context.
Corrections
When we learn something is unclear or incorrect, we update the page and add a brief note.
Sources we consult
We reference widely used public health guidance and standard texts to ensure explanations align with common practice. We avoid single, sensational studies without context.
Conflicts of interest
We disclose material relationships that could influence content and avoid promotional bias in articles and tools.
Corrections policy
When we discover an error, we correct it promptly. For substantive changes, we add a short note with the date. Readers can request corrections via our Contact page.
Language & clarity
We use plain language and concrete examples, prioritize ranges over absolutes, and aim for accessible reading level without diluting accuracy.
How We Create Content
- Evidence-aligned baselines: We use widely accepted ranges (e.g., ~30–35 mL/kg) and practical adjustments for activity, heat, altitude, and life stage.
- Clarity over jargon: We favor plain-English explanations, examples, and checklists.
- Risk communication: We call out overhydration risks (e.g., hyponatremia) and when electrolytes are preferred.
Review & Update Cycle
- Quarterly editorial review.
- Ad hoc fixes for clarity, accessibility, or bug reports.
- Version date posted for transparency. Current editorial cycle reviewed: November 07, 2025
Corrections
Report errors via our Contact page. We log substantive corrections and adjust examples when assumptions change.
Editorial Masthead
- Product & Copy Lead: Responsible for calculator UX and plain-language copy.
- Engineering: Implements the tool logic and performance optimizations.
- Content Editor: Ensures readability, consistency, and glossary accuracy.
- QA Reviewer: Tests examples and checks links, tables, and schema markup.
We welcome expert reviewers for future editions. Reach out on the Contact page.
Sourcing Policy
- Prefer primary sources (guidelines, consensus statements) and authoritative reviews.
- Avoid cherry-picking; when ranges vary, we explain assumptions.
- Note when evidence is limited and defaults are based on practical consensus.
Conflicts of Interest
We do not accept compensation to alter calculator logic or copy. Any sponsorships or affiliate relationships will be labeled clearly.
Reading Level & Accessibility
We aim for clear, plain-English explanations (~8th–10th grade reading level) and scannable lists to aid comprehension.
Scenario Selection
Examples reflect common cases (desk days, hot/humid training, altitude, pregnancy/breastfeeding). Edge cases are noted as educational, not prescriptive.
Citations & Attributions
When we reference external material, we summarize in our own words and provide context rather than lifting text verbatim.
Roles & Responsibilities
- Research: Curates baseline ranges and adjustment frameworks.
- UX Writing: Converts methodology into plain-English steps and examples.
- Frontend: Implements accessible forms and responsive layouts.
- Data QA: Tests edge cases and validates unit conversions.
How to Reach the Team
Use the Contact page with the subject “Editorial Feedback” for content suggestions or corrections.
Advisory Network
We periodically invite external reviewers with relevant expertise to comment on clarity and accuracy. Participation does not imply endorsement.