GratisAIhealth · field guide · local-first · no account
dual-unit grid

Cross-Check Kilogram and Pound Entries for the Same Recorded Weight — Free

A copied weight can be plausible in both units and still belong to the wrong row. Keep kilogram and pound entries paired, show the signed conversion gap, and resolve a transcription question before the record is reused.

The proof surface

Medication-reconciliation guides organize a clinical discussion. This grid does one smaller evidence job: compare two unit representations claimed to describe the same recorded weight. It calculates no dose, target weight, body-size assessment or health trend.

InputObservation code | kilograms recorded | pounds recorded; transcription-gap review mark (kg)
Rare deviceMedication-reconciliation guides organize a clinical discussion. This grid does one smaller evidence job: compare two unit representations claimed to describe the same recorded weight. It calculates no dose, target weight, body-size assessment or health trend.
Output artifactLargest absolute paired-unit discrepancy with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Oak observation | 70.5 | 155.5; Pine observation | 82.2 | 180. Transcription-gap review mark (kg) = 0.05. Largest absolute paired-unit discrepancy: 0.553373 kg absolute gap. All records are invented.

Before using the dual-unit grid

Only pair values that your original source says are the same observation. A new measurement is not a conversion check, and a scale reading after changing clothing or equipment may differ for reasons outside transcription. One pound is defined here as exactly 0.45359237 kilograms. The review mark concerns discrepancy in recorded units, not allowable weight change or a clinical threshold. If a display has fewer decimal places, keep that precision in the source notes rather than inventing extra digits to force agreement. Non-sensitive observation codes protect the source identity; neither age, diagnosis nor a person's name is necessary. A marked gap indicates something to verify in the documentation, not which representation is correct.

Why the flat version breaks

Using two different weigh-ins as paired units

Conversion is an identity check, not a longitudinal comparison. Two measurements can differ because they happened at different times or under different conditions. Calling that gap a transcription error creates false confidence. Establish that the source claims both entries represent one observation before running this grid.

Rounding before calculating the discrepancy

Converting 155.5 lb to a rounded whole kilogram destroys information about the gap. This tool keeps the exact factor in the arithmetic and rounds only the displayed reading. Your source may have its own precision limits, but those should be discussed explicitly rather than introduced as an invisible second rounding step.

Treating the review mark as a clinical tolerance

The supplied number controls a documentation review flag. It does not say how much body weight can safely change, whether a scale is accurate or whether a medication calculation is appropriate. Even an unmarked row can refer to the wrong record; preserve source identity and ask the responsible clinician or records team.

How to work the dual-unit grid

Identify the actual paired observation

Match timestamp, source record and measurement context privately before entering the two values. If the source merely provides two nearby weights, leave them unpaired until a responsible person clarifies the relationship. This calculator cannot decide whether a clinic imported an old reading or whether two devices were used.

Preserve both recorded unit labels

Enter kilograms in the second cell and pounds in the third. Type non-negative plain decimals without kg or lb suffixes. Do not overwrite one source value with a conversion of the other: doing that removes the independent evidence needed for the comparison. An obviously misplaced numeral should still be corrected against the original source, not by intuition.

Inspect signed and absolute gaps separately

Multiply pounds by 0.45359237, then subtract the entered kilogram value. Positive means the pound-derived value is higher; negative means it is lower. Review marks compare the absolute gap with your supplied mark. The summary reports the largest absolute gap across rows, while the grid preserves direction and the converted value for each observation.

Ask for a record correction, not a treatment change

Bring the source labels and paired entries to the clinician or records team responsible for the chart. Ask which value and unit should be retained and how rounded displays were handled. Keep the grid's discrepancy separate from medical interpretation. A corrected entry should have an appropriate audit trail rather than quietly replacing a number in a treatment record.

What the dual-unit grid separates

QuestionBeforeInspect this instead
Using two different weigh-ins as paired unitsConversion is an identity check, not a longitudinal comparison. Two measurements can differ because they happened at different times or under different conditions. Calling that gap a transcription error creates false confidence. Establish that the source claims both entries represent one observation before running this grid.Preserve both recorded unit labels
Rounding before calculating the discrepancyConverting 155.5 lb to a rounded whole kilogram destroys information about the gap. This tool keeps the exact factor in the arithmetic and rounds only the displayed reading. Your source may have its own precision limits, but those should be discussed explicitly rather than introduced as an invisible second rounding step.Inspect signed and absolute gaps separately
Treating the review mark as a clinical toleranceThe supplied number controls a documentation review flag. It does not say how much body weight can safely change, whether a scale is accurate or whether a medication calculation is appropriate. Even an unmarked row can refer to the wrong record; preserve source identity and ask the responsible clinician or records team.Ask for a record correction, not a treatment change

This dual-unit grid replaces a manual count or calculation, not source verification or the responsible person’s review.

Run it on the samples, right here

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Unit-transcription comparison only, not diagnosis, weight-management or dosing advice. Ask the responsible clinician or medical-records team to confirm paired observations and correct the source record; never adjust treatment from this gap.

Data note: The dual-unit grid processes Observation code | kilograms recorded | pounds recorded locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Go deeper: the companion app files the same reading as a scored comparison matrix

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the dual-unit grid reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.

The dual-unit grid answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.

Open the dual-unit grid companion

Boundary

Unit-transcription comparison only, not diagnosis, weight-management or dosing advice. Ask the responsible clinician or medical-records team to confirm paired observations and correct the source record; never adjust treatment from this gap.

What this is built on

Before: two plausible weight numbers were accepted as equivalents. After: a signed unit gap identifies an explicit documentation question without choosing a treatment value.

Three worked readings, with different inputs

Sample A — typical inputs

Oak observation | 70.5 | 155.5
Pine observation | 82.2 | 180

Setting: Transcription-gap review mark (kg) = 0.05. Expected summary: 0.553373 kg absolute gap.

Using the exact unit definition, 155.5 lb becomes 70.533613535 kg, a signed gap of +0.033613535 kg from Oak's kilogram entry. Pine's 180 lb becomes 81.6466266 kg, a gap of -0.5533734 kg. The summary selects the larger absolute discrepancy, 0.5533734 kg. The sign remains on each row so the direction of the mismatch is not lost.

Sample B — changed plan

Willow observation | 64 | 141.1

Setting: Transcription-gap review mark (kg) = 0.05. Expected summary: 0.001883 kg absolute gap.

141.1 × 0.45359237 = 64.001883407 kg, which differs from the recorded 64 kg by 0.001883407 kg. That is below the illustrative 0.05 kg transcription mark. It could be compatible with independently rounded displays, but compatibility is not proof that the entries describe the same observation. The original timestamp and unit labels still need human checking.

Sample C — boundary convention

Birch unit example | 45.359237 | 100

Setting: Transcription-gap review mark (kg) = 0.05. Expected summary: 0 kg absolute gap.

The exact definition of 100 lb is 45.359237 kg, so the paired entries agree in this unit model. The zero checks conversion arithmetic, not scale calibration. A repeated measurement taken on another day can agree numerically and still belong to a different record. The calculator never merges records or infers that two labels identify the same person.

Optional AI formatting, never the calculation

Manual entry completes this dual-unit grid for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a dual-unit grid. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Observation code | kilograms recorded | pounds recorded; the setting is Transcription-gap review mark (kg). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.