> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getbased.health/llms.txt
> Use this file to discover all available pages before exploring further.

# Send feedback or suggest a better range

> Prepare a useful public GitHub report in your selected units, review the draft, and recover it if a new tab or clipboard action fails.

## Send feedback

Choose **Send Feedback** in the desktop header or **Send feedback** in mobile **Tweaks**. Select a bug report, feature request, idea or other message, then enter a title and description.

For a bug, include what happened, what you expected and the steps to reproduce it. **Open GitHub draft** prepares an issue; it does not submit one. Review the draft on GitHub and submit it there using your GitHub account.

The report adds app version, selected unit system and range mode, browser, viewport, theme and AI provider. It does not automatically attach profile details, lab records, conversations or credentials. Anything you type or attach on GitHub can still be public, so remove identifying health information and secrets first.

### Recover a draft

* If the new tab is blocked, use **Continue on GitHub**.
* **View or copy full report** shows the complete text.
* If the report is too long for a prefilled URL, copy the text and paste it into GitHub; the app keeps the full report.
* If clipboard access is denied, the text is selected for manual copying.
* Closing and reopening the form in the same page and profile keeps your draft. Editing the form invalidates its previous generated preview.
* Switching profiles clears the feedback form and its preview. Feedback drafts are transient: they are not saved across page reloads, included in backups or synced.

## Suggest a better marker range

Open a built-in marker's detail and choose **Suggest a better range** when available. The app opens a public GitHub proposal with the catalog ranges in your selected **SI**, **US**, or **Australia / NZ** units.

The proposal separates:

1. **Current catalog values:** marker, units, reference/optimal bounds, female overrides and contextual support. Leave these unchanged so the comparison is clear.
2. **Proposed change:** the actual new bounds and unit, whether the proposal concerns reference or optimal/contextual guidance, and the population or collection conditions to which it applies.
3. **Evidence:** a source link, why it applies and any important limitations.

For example, a US-unit glucose proposal should show the current catalog bounds in mg/dL. Put your proposed mg/dL bounds in **Proposed range**, rather than overwriting the current values. If your source uses another unit, state that explicitly.

The proposal contains public catalog data, not your own measured result, imported laboratory ranges or profile details. Custom markers and personal range overrides use their own editing workflow rather than this built-in catalog proposal.

### Female-specific ranges

The template shows catalog female overrides independently of the active profile's sex. That documents the proposed population; it does not mean female ranges were applied to a male profile.

**Not set** is intentional when no female optimal interval is defined, including SHBG and estradiol. It must not fall back to the default male wellness interval. A missing override field can still inherit its default bound, such as the lower bound of the ApoB/ApoA1 ratio.

Do not put your own date of birth, diagnoses, laboratory report or other private health details into the public proposal. A useful range suggestion needs the intended population and evidence, not your personal record.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.