How to actually tell if it's working.

Prep for a reliable baseline

• SAME MACHINE, SAME BRAND, SAME SOFTWARE. Book the identical scanner and site every time and confirm the software version has not changed. GE Lunar 'CoreScan' and Hologic 'InnerCore' use different algorithms and are NOT comparable for VAT (or reliably for anything else) - never mix brands between baseline and retest.
• FASTED, EARLY MORNING, EVERY TIME. Recommend a consistent overnight fast of at least 8-12 hours and a first-thing-AM slot. A recent meal adds gut contents and fluid that read as tissue. If you truly cannot fast, replicate the EXACT same fed state (same meal, same timing) each scan - but fasted AM is the standard for a repeatable VAT baseline.
• HYDRATION HELD CONSTANT. Drink your normal amount on your normal schedule; do not water-load or dehydrate before a scan, and do not scan right after chugging a large volume. Empty your bladder immediately before. Body water reads as lean mass, so hydration swings masquerade as tissue change.
• NO EXERCISE FOR 24-48 HOURS PRIOR. Skip resistance training, hard cardio, sauna, and anything that shifts sweat, fluid, or glycogen. A workout the day before can inflate or deflate lean-mass and android-region readings.
• HOLD CREATINE AND CARB-LOADING IDENTICAL. Creatine supplementation and glycogen each pull water into muscle and can raise the lean-mass reading by ~1-2%+ with ZERO real muscle gain (each gram of glycogen carries ~3 g of water). Either be off both with an equal washout before each scan, or keep the exact same dose/intake at baseline and retest. Do NOT start creatine or do a carb refeed between scans - it will manufacture a fake lean-mass gain.
• AVOID GLYCOGEN/DIET SWINGS THE DAY BEFORE. Don't scan the morning after a big high-carb refeed or, conversely, a very-low-carb depletion day. Keep the preceding 24-48h of eating typical and similar between scans; glycogen and fluid swings move lean mass and can nudge the android/VAT region.
• MINIMAL, IDENTICAL CLOTHING - REMOVE ALL METAL. Wear a thin gown or the same seamless, metal-free garment each time. Take off jewelry, watches, piercings, underwire bras, belts, zippers, buttons, and phone. Metal and thicker fabric corrupt attenuation and comparability.
• NO RECENT CONTRAST OR NUCLEAR SCANS. If you've had CT/MRI contrast, a barium study, or nuclear-medicine imaging within about a week, reschedule - residual agent can distort the scan.
• WOMEN: MATCH THE MENSTRUAL-CYCLE PHASE. Cyclic fluid retention shifts weight and lean readings, so try to scan at the same point in the cycle and record the cycle day.
• BE WEIGHT-STABLE AT BASELINE. Don't set your baseline in the middle of a crash diet or a rapid-refeed week when fluid is in flux. Record everything: fast length, last meal, last workout, creatine status, hydration, garment, and cycle day - you'll need to reproduce it exactly.

How to run it

• Establish baseline under the standardized conditions above and WRITE DOWN every condition (machine ID, software version, time of day, hours fasted, last meal, hours since last workout, creatine on/off and dose, garment, hydration, cycle day). This record is what makes the retest comparable.
• Confirm with the facility that VAT is enabled (CoreScan on GE, InnerCore on Hologic) and that the same scan mode will be used. Empty your bladder right before the scan.
• Positioning: lie centered and straight on the table with arms and legs in the standard placement; let the tech use positioning aids and make sure hands/feet aren't clipped by the scan edge. Ask that the same auto-segmentation/regions be applied every time.
• Collect the FULL report: total and regional fat mass, lean mass, %fat, and VAT mass/volume/area. Ask the facility for their site-specific PRECISION ERROR and LEAST SIGNIFICANT CHANGE (LSC) - ISCD guidance is that reports state the LSC so you know the smallest real change.
• For the retest, reproduce EVERY recorded condition - same scanner and software, ideally same technologist, same time of day, same fast, same 24-48h no-exercise gap, same creatine status, same garment, same cycle phase.
• Interpret changes ONLY against the LSC. Any move smaller than the facility's LSC is statistical noise, not a real change. For VAT specifically, treat changes below roughly 130 g as noise (population LSC is ~130 g and precision is worse at lower BMI); demand a change that clearly exceeds the LSC before calling it real.
• Judge the TREND across two or three standardized scans, not a single before/after pair. Cross-check surprising DXA moves against scale weight, waist tape, and training/diet logs so you can separate a fluid/glycogen artifact from a genuine tissue change.
• Never compare your absolute number to a machine's 'normal' population range as if it were exact - compare each scan to your OWN prior scan on the SAME machine.

Prep for a reliable baseline

• Pick ONE sensor family and keep it for the entire experiment (baseline AND retest). Never compare a Libre fortnight to a Dexcom fortnight: different enzyme chemistries, smoothing algorithms, and factory calibration make the raw numbers non-comparable [strong]. Note that OTC wellness sensors add processing (Lingo smooths and clips its displayed range; Stelo smooths and reports every 15 min), so if you want quantitative data, choose a sensor you can export from (Libre 3, Dexcom G7, or Stelo via app/CSV export).
• Decide your ONE primary metric before you start, and the minimum change that would count as real. Recommended primary: incremental area-under-curve (iAUC, 0 to 2 h) of a fixed standardized test meal, averaged over 3 or more days per period. Secondary: mean glucose, CV, and time-above-140. Pre-committing to the metric and threshold is what stops you from cherry-picking a favorable number afterward [strong].
• Build a standardized test meal you will eat identically in both periods: same product, same grams of available carbohydrate (e.g., 50 g), same clock time, after the same overnight fast (8 h or more), with no caffeine and no exercise in the 2 h before or after. This single controlled stimulus isolates the drug far better than free-living fortnight averages, because it removes meal-to-meal food variation [moderate to strong].
• Standardize the background you are living in: fixed sleep and wake times, fixed (ideally zero) caffeine and alcohol, consistent meal composition and timing, no new supplements, and a written log. The drug is a small signal riding on top of food and activity, which are large signals. Hold the large signals constant or they bury the drug [strong].
• Weigh yourself daily and record menstrual phase, illness, and unusual stress. A few pounds of weight change or a different cycle phase can shift glucose as much as a modest drug effect; you will use these logs to reject any contaminated day or window [moderate].
• Get the drug timing right. If the agent needs days to reach steady state (most do), begin dosing far enough ahead that the entire on-drug fortnight is at steady state. If you are doing a washout crossover instead, allow at least 5 half-lives between the off and on windows [moderate].
• Insert the sensor 12 to 24 h before data collection begins and plan to discard day-1 readings: first-day values commonly run low or erratic during warm-up [moderate]. Place it on the back of the upper arm per the maker's instructions, and use the same arm and site type in both periods.

How to run it

• BASELINE FORTNIGHT (drug OFF): wear one sensor for 14 days on your standardized routine. On 3 or more non-consecutive days, run the standardized test meal and tag it in the app. Aim for greater than 70% sensor data capture across the 14 days; the international consensus treats 14 days at over 70% capture as the minimum for a representative glucose profile (Danne 2017; Battelino 2019) [strong].
• Export the data, drop day 1, then compute baseline metrics: mean glucose, GMI, SD, CV (= SD / mean x 100), time-in-range for a range you fix in advance (70 to 140 mg/dL for a non-diabetic, or the clinical 70 to 180), and per-meal iAUC, peak, and time-to-baseline for each test meal. Record BOTH the average and the spread across your test-meal days: that day-to-day spread is your noise floor and you will judge everything against it.
• Start the drug. Wait until it is at pharmacologic steady state before opening the retest window. Do not measure during the ramp-up unless the ramp itself is what you are studying [moderate].
• RETEST FORTNIGHT (drug ON): apply a NEW sensor of the same family to the same site, and repeat the identical 14-day protocol, including the same 3-plus standardized test meals at the same clock times, same fasting duration, same everything. Keep weight, sleep, caffeine, alcohol, and activity matched to baseline [strong].
• Compute the identical metrics for the on-drug fortnight (again dropping day 1). Compare primarily the test-meal iAUC (on versus off) and secondarily mean glucose, CV, and time-above-140.
• Judge the difference against your noise floor, not against zero. A change counts as real only if it exceeds BOTH (a) the day-to-day spread you measured within each period and (b) the roughly 8 to 10% sensor error plus the several-mg/dL between-sensor bias. A 2 to 3 mg/dL mean shift, or a small TIR wiggle in a healthy person, is noise [strong].
• To move from suggestive to credible: repeat the on/off blocks at least twice in randomized order (ABAB), have someone else dispense drug versus placebo so you are blinded, and hold to the pre-registered metric and threshold. An open-label single before/after (n=1) cannot separate the drug from placebo, expectation, or regression to the mean [strong].

Prep for a reliable baseline

• Pick ONE device and never cross-compare brands. Oura and WHOOP use different sensors and different staging algorithms; a metric is only valid against ITSELF over time. Wear it the same way every night (Oura: same finger, snug; WHOOP: snug band, correct placement).
• Wear it continuously through a learning window before you trust any baseline. Personal baselines take time: Oura builds its HRV/RHR/Readiness baseline over ~14 days of wear; WHOOP compares against a rolling 30-day HRV baseline. Treat Readiness/Recovery scores in the first 2-4 weeks as unreliable.
• Baseline during a 'boring normal' stretch: usual bed/wake times, no travel, no illness, typical (not peak, not deload) training, no unusual alcohol. Do NOT baseline over a vacation, race week, or while sick — you will bake a distorted reference into everything you compare later.
• Standardize the bedroom: cool, dark, quiet, and the same every night. Room temperature and body temperature both move HRV and resting heart rate.
• Lock in consistent sleep and wake times. Regularity is itself a tracked metric and it stabilizes all the others; irregular timing is the biggest self-inflicted source of noise.
• Protect the pre-sleep window on baseline nights (this is where confounders hit hardest): no alcohol, no late/large meals, no late intense exercise, and keep caffeine well before bedtime, so the baseline reflects a genuinely rested you.
• Keep a daily one-line confounder log: last alcohol (amount + time), last caffeine time, last meal time/size, hard workouts, illness symptoms, menstrual cycle day, and time-zone/DST changes. Without this log you cannot interpret any later change.

How to run it

• 1. Set up one device and wear it continuously through the learning window (Oura ~14 days, WHOOP ~30 days). Ignore all scores during this period — the algorithm is still personalizing.
• 2. Define your baseline as a ROLLING AVERAGE over multiple typical nights, not a single night. Research on night-to-night variability shows single nights are noisy; use >=7 nights for duration/regularity and 14 nights for HRV/RHR to get a stable number.
• 3. Record the RELIABLE metrics as your primary read: nocturnal average HRV, resting/lowest heart rate, total sleep time, and sleep regularity/timing. Log deep and REM only as SECONDARY, directional context.
• 4. Compute your personal normal RANGE, not a point: baseline mean plus/minus your typical night-to-night swing (roughly one standard deviation). A single night outside the range is noise; a sustained shift of the average is signal.
• 5. Standardize retest conditions to match baseline exactly: same device and firmware, same wear, same bedroom, and the same evening behaviors (same caffeine cutoff, no alcohol, no late heavy meal, no unusual late workout, not jet-lagged, similar sleep timing).
• 6. Retest as a multi-night average (>=7 nights, ideally 14), then compare NEW average vs BASELINE average. Never conclude a health change from one night against one night.
• 7. Interpret directionally and honestly: a persistent RHR rise (~5-10 bpm) and/or HRV drop vs. baseline = incomplete recovery, illness, alcohol, or stress. For deep/REM, only weigh LARGE, sustained shifts and disregard small nightly wiggles (the stage estimate is not precise enough to support fine reads).
• 8. Escalate to a clinician, not the app, for anything diagnostic: chronic short sleep, loud snoring or witnessed breathing pauses, a persistent SpO2/breathing-disturbance flag, unrefreshing sleep, or excessive daytime sleepiness. The wearable screens and flags; a home sleep apnea test or in-lab polysomnography diagnoses.

Prep for a reliable baseline

• Pick ONE modality and never switch it between tests. Treadmill, cycle ergometer, and outdoor running all yield different VO2max numbers (cycling typically runs several mL/kg/min lower than treadmill because it uses less muscle mass). A treadmill baseline and a bike retest are not comparable.
• Standardize your pre-test body state and write it down: no vigorous or unusually long exercise for 24-48h, no alcohol for 24h, no large meal within 2-3h (light meal is fine), hold caffeine constant (either none for 3-6h, or the exact same dose every time), well hydrated, a normal night of sleep, and not sick or within ~2-4 weeks of a real illness.
• Control the environment: same time of day, similar ambient temperature (avoid heat), same altitude, same shoes, same bike fit. Heat, dehydration, and altitude all depress the number independent of fitness.
• For a lab (graded/CPET) baseline: choose a facility that uses a metabolic cart (indirect calorimetry) and a standardized incremental protocol (Bruce, modified Bruce, or an individualized ramp) run by a trained technician. This is the gold standard; test-retest ICC is ~0.93-0.95.
• For a wearable baseline: use a chest-strap HR monitor rather than wrist-only optical HR if the device supports it (wrist HR error feeds straight into the estimate), and let the algorithm settle by doing several steady-effort outdoor runs or walks with good GPS over 1-2 weeks before you record the baseline number.
• Log the exact setup: device model AND firmware version, lab/cart and protocol, HR source, route, conditions. If you can't reproduce the conditions later, you can't trust the comparison. Record weight too, since VO2max is per-kg.

How to run it

• LAB PATH (most reliable): Book a graded cardiopulmonary exercise test (CPET) with a metabolic cart. Keep the same modality (treadmill or cycle) for every future test.
• Arrive rested and fueled per the prep rules, at the same time of day. Do the lab's standardized warm-up, then the technician runs an incremental ramp to volitional exhaustion.
• Push to a TRUE maximum. The result is only a valid VO2max if maximal-effort criteria are met: respiratory exchange ratio (RER) above ~1.10, a plateau in VO2 despite rising workload, RPE around 9-10/10, and heart rate near your age-predicted max. Ask the technician to confirm these on your report; a test you quit early is a VO2peak that undercounts you.
• Take home the actual mL/kg/min value AND the raw data, not just a fitness category. You need the number to compare later.
• WEARABLE / FIELD PATH (accessible, lower resolution): Pick ONE method and freeze it: your watch's estimate (with a chest strap), or a validated field test (Cooper 12-minute run, 1.5-mile run, or Rockport 1-mile walk) using the same published equation every time.
• For a device estimate: complete 2-3 qualifying steady-effort runs in the days beforehand, then record the stabilized value or a 7-day average, never a single spike. For a field test: run/walk at genuine full effort on the same track/route, capture raw time and HR, and plug into the identical equation each time; do it twice within a few days and average to set the baseline.
• Write the number down next to the logged conditions (device/firmware, HR source, temperature, sleep, weight, any illness) so that on retest you can separate real change from noise.

Prep for a reliable baseline

• Pick ONE test and ONE collection type, then hold it constant forever. For everyday tracking that means first-morning uACR. For quantified panels (protein, stone risk, cortisol) it means a full 24-hour collection. Never compare a first-morning sample to an afternoon random sample; posture, meals, and exercise shift the numbers.
• Use the same lab and the same assay each time. Albumin immunoassays and creatinine methods are not perfectly harmonized between labs, so switching labs can create a fake trend. Write the lab name and method on your record.
• For a first-morning uACR, control the 24 hours before: no heavy or prolonged exercise (it causes transient albuminuria that looks like kidney damage), no alcohol binge, and no unusually large protein load or extreme over/under-hydration. Keep the night before ordinary.
• Do not collect during a confounder: active urinary tract infection, fever or acute illness, or menstruation/visible blood (blood contaminates protein and heme readings). Reschedule instead of collecting through them.
• For a 24-hour collection, get the CORRECT container in advance and ask the lab which preservative each analyte needs. Cortisol, catecholamines/metanephrines, and oxalate collections often require an acid preservative and must be kept cold and out of light. The wrong tube silently invalidates the result.
• Have a clean-catch, midstream technique ready: brief external cleaning, start the stream into the toilet, catch the middle portion, finish into the toilet. This is what keeps skin cells, discharge, and bacteria out of the cup.
• Plan delivery. Urine degrades at room temperature (pH drifts, cells lyse, bacteria multiply). Refrigerate and get the sample to the lab the same morning, or follow the mail-in kit's cold/timing instructions exactly.

How to run it

• FIRST-MORNING uACR (the everyday tracker): Order 'urine albumin-to-creatinine ratio,' not a bare dipstick. The lab must report albumin AND creatinine and compute the ratio in mg/g.
• On waking, do a clean-catch midstream collection of your FIRST void of the day, before coffee/exercise. Fill to the container line, cap, and label with the exact clock time.
• Deliver refrigerated the same morning. Record four things every time: the ACR number, the lab/method, the date and time, and any confounders (workout, illness, cycle day). The number is only comparable alongside those notes.
• 24-HOUR COLLECTION (protein, stone-risk chemistry, cortisol): Get the right preservative container(s) from the lab first.
• At a fixed wake time, empty your bladder into the toilet and DISCARD it. Note that exact clock time. This is your start; the discarded void belongs to the previous day.
• For the next 24 hours, collect EVERY void into the container. Keep it refrigerated (and dark, if acid-preserved) the whole time. Missing even one void understates the true total.
• At the same clock time the next morning, do one final void INTO the container to close the 24-hour window, even if you have to go early or force it. Deliver promptly.
• Validate completeness before trusting the result: the lab reports total volume and total creatinine. Adult creatinine excretion should land near 15 to 20 mg/kg/day for women and 20 to 25 mg/kg/day for men. A value well below that means you missed voids and the panel understates your real excretion, so repeat it.
• For 24-hour cortisol (UFC) specifically, plan at least TWO separate collections up front, because a single day's value is too variable to act on.

Prep for a reliable baseline

• Decide the QUESTION before buying any kit, because it dictates the test: monitoring known/suspected gut inflammation points to calprotectin; colorectal-cancer screening points to FIT or Cologuard (on a schedule, not as a tracker); curiosity about your microbiome has no validated tracking answer. Buying a random 'gut test' first is how people generate noise they then over-interpret.
• Lock ONE lab and ONE assay/kit brand and write down the exact product (e.g., BUHLMANN fCAL for calprotectin). Results are method-dependent: a calprotectin value from one assay is not interchangeable with another, and microbiome results from different labs/pipelines are effectively different measurements. Retests must use the identical method or the comparison is meaningless.
• For calprotectin, plan to collect the FIRST bowel movement of the morning. Calprotectin rises the longer stool sits in the colon between movements, so first-morning stool is both highest and the most standardizable time point (Lasson 2015).
• Clear known confounders in the days before sampling: stop NSAIDs/aspirin (they raise calprotectin), note PPI use, avoid sampling during or right after an acute GI infection, and (for FIT/blood-based readouts) avoid menstruation and obvious rectal bleeding. If you want a stable baseline, do not sample during a flare or a stomach bug.
• For any microbiome test, hold your diet stable for at least several days beforehand (the gut community shifts within 24-48h of a diet change) and record any antibiotics in the prior weeks-to-months (a single antibiotic course perturbs the community for weeks and sometimes far longer). Without this, a 'change' is just your last few meals or a prescription.
• Use the correct stabilized collection device and read its instructions before collection day (e.g., BUHLMANN CALEX Cap stabilizes calprotectin and elastase for safe room-temperature transport). Uncontrolled room-temperature delay degrades the sample; storing stool at room temperature more than ~3 days is not advisable for calprotectin.
• Prepare a simple log to fill in every time: date, exact time of collection, Bristol stool form, recent meds (NSAIDs, PPIs, antibiotics), recent travel/illness, menstrual status, and the specific product/lot used. This log is what makes two data points comparable months apart.

How to run it

• Confirm the test matches your question and is validated for it. Calprotectin = inflammation monitoring. FIT/Cologuard = cancer screening. Microbiome composition = exploration only, not a metric. If a product promises a 'gut health grade' or 'food sensitivity map,' treat it as entertainment, not data.
• Register the method: same lab, same assay/kit, same reported units, and the reference cutoff that lab uses (for calprotectin the common decision points are roughly <50 ug/g normal, 50-150 borderline, >150 suggests active inflammation; cutoffs are assay-specific, so use YOUR lab's).
• Collect the baseline on a non-confounded day: first-morning bowel movement, sampled per the device instructions. Because a single spot of a formed stool is not representative, follow the kit's sampling pattern (multiple sites) rather than one dab.
• For calprotectin specifically, consider two samples on two separate mornings and average them. Day-to-day biological variability is large, and a single value can mislead; two well-separated samples materially reduce the odds of a spurious high or low.
• Ship the same day per instructions and keep cold if the kit requires it. Do not let the sample sit over a weekend.
• Record the numeric result WITH units and the lab's cutoff, plus your full log entry. A bare number with no method, units, or conditions is not trackable.
• Retest under identical conditions only: same lab, same kit, same first-morning timing, diet-stable, no new medications, not during an illness. Change any one of these and you are no longer measuring the same thing.
• Apply a real-change threshold before reacting. For calprotectin, treat a shift as meaningful only if it crosses a clinical threshold (e.g., moves from <150 to >150 ug/g) or is roughly a two-fold change, because biological plus analytical variability easily produces swings like 60 to 110 with no true change. For microbiome outputs, treat any single-taxon difference as a hypothesis, not a result.
• Confirm surprises by repeating before acting, and route anything clinical to a clinician: a positive FIT or Cologuard requires a diagnostic colonoscopy (do not just re-run the stool test), and a rising or persistently elevated calprotectin warrants medical evaluation, not self-treatment.