One bowl is not one session

Two counters answer two questions

A fresh load records new material. A timed cycle records operating time. Keep both counters, because a single load can remain in the chamber across several cycles. Multiplying fresh mass by every reheat overstates the amount acquired.

The anonymous example describes roughly 0.10 to 0.15 g in one load, reused across an uncertain four to eight six-minute sessions. The earlier arithmetic midpoint was 0.125 g. The current editable example uses the owner-selected 0.15 g per bowl and 36 timed minutes. The original uncertainty remains. These figures do not define an ideal load, a recommended number of cycles or complete extraction.

A worksheet that avoids double counting

Give each load an identifier. Record fresh mass once, alongside the scale resolution or the fact that it was estimated. Add the number and duration of its timed cycles separately. A record of 0.1 g from a coarse scale does not support a claim of milligram accuracy.

For a charge observation, record the battery's known age or unknown status, displayed temperature, cold versus warm restarts and the comparable timed minutes. Use records of ordinary existing use. Do not increase consumption, bypass a cutoff or repeatedly force a depleted cell to restart to complete a worksheet.

A calendar total divided by days gives a budgeting average. Keep missing-day coverage visible. One recorded day cannot establish an ordinary month, and a missing day should not be presented as a measured zero. The calculator keeps the entered window denominator visible so readers can assess that limitation.

What the record does not measure

Elapsed timer minutes do not reveal continuous heater power, chemical recovery or absorbed THC. A personal stopping point may reflect a preference, an interruption or an observation. It is not automatically a measured chemical endpoint. Do not turn the record into a temperature schedule or a target for more sessions.

Use the cost calculator to explore how changing fresh mass and timed minutes affects different parts of the account. The battery guide explains why runtime per charge is a separate observation.

Keep the log optional

The utility below holds entries in memory until you explicitly save them on this device. Its export preview lets you inspect the contents before downloading. There is no reader account or automatic cloud upload. Avoid putting names or identifying details into free-text notes.

One useful log is more valuable than an elaborate collection of guessed numbers. Fresh mass, comparable time and dated receipts support accounting. Potency guesses, effect ratings and claims about identical hardware do not improve these calculations.

A charge is another counter

The corrected owner report concerns one 68-selected-minute mixed-use charge, with nine vaping and three cleaning blocks. Approximate 54 vaping / 14 cleaning minutes are derived, not exact per-block allocations. It does not replace the uncertain cycles-per-bowl observation. A charge can span several loads; one load can also span a charging interruption. Record fresh mass, heating time and charge boundaries independently.

Give each event the right identity

A load ID identifies one fresh input. A session ID identifies a heating event, with an optional load link and optional charge link. A charge ID identifies the battery observation. A load can span two charges; a charge can span multiple loads. Shared counts do not establish that two records are the same event. The separate reported nine-stage MAC same-bowl sequence is not identified as the charge's nine vaping blocks.

Cleaning-only records use no fresh load. They must not increase the material count, herb cost or residue collection. Unknown-purpose entries stay unknown. The log permits mixed selected durations, incomplete cycles, elapsed time and interruptions without replacing missing values with zero. Fresh mass and scale resolution are separate; an estimate stays an estimate.

The charge summary stores aggregate counts and derived subtotals without inventing twelve individual records. If individual sessions later become available, the aggregate remains context rather than another set of sessions to add. Review/correction actions preserve the previous record and a reason. Deleting the entire log clears that trail too. Legacy prose remains unchanged and unlinked; migration does not guess IDs or turn an approximate string into a measured mass.

A blank worksheet for an existing routine

Print this page or download the blank JSON worksheet below. No account, test schedule or extra consumption is required. Saving and importing are local choices. Review the exact export snapshot before sharing it; notes can still contain information you would prefer to keep private.