Identify the sample and the conditions you actually used. Keep observed facts, photos or video, possible explanations, and unknowns in separate parts of the record. Use the result to choose the next question or retest. Do not turn a small sample into proof that the hardware is safe, reliable, compatible, or representative of a future batch.[1]
The goal is not to create a laboratory report. The record should let another person see what hardware was reviewed and what the team did. It should also show what happened, what remains unclear, and what should happen next.
Start with the physical sample, not a catalog description
AIO means all-in-one empty hardware with the tank, heating system, and battery integrated into one device. Start the record with the supplier, product name, model number if provided, sample ID, quantity received, and review date. Add the color, material, structure, capacity, or other version details that help distinguish this item from another sample.
Photograph the received label and condition. Save the filename in the record instead of leaving the image in an unnamed phone folder. If a supplier later answers a question, the sample ID and dated image give both sides a shared reference.
Also record who received the sample and who performed the review, so a later question can return to the people who handled the item.
This identity work matters even when two samples look alike. A similar shell does not show that the internal components, control, instructions, or production version are the same. The record should describe the item in hand, not the category you expected to receive.
If the sample is accepted as a working reference, keep the original confirmation information and note where the reference sample is retained. A retained sample can support a later comparison.[1] It does not prove that a later order will perform the same way.
Write one narrow question before recording results
A useful sample record starts with a decision question. For example:
- Did the team receive the model and version it expected?
- What happened during the filling and capping steps the team actually used?
- Did the observed activation behavior match the instructions supplied for this sample?
- Which unanswered point must the supplier clarify before another review?
Keep the question specific to one condition or observation.[1] Broad prompts such as “prove this hardware works” or “confirm compatibility” hide the conditions and encourage a pass label that the evidence cannot support.
The question should lead to one next action: repeat the same review, ask the supplier, pause the item, compare another sample, or continue a commercial conversation. If the question cannot change an action, narrow it again.
Record the conditions your team actually used
Write down the formula or internal material reference and the fill amount used by your team. Add the filling method, capping or closure step, and time between steps. Record the storage orientation, environment, activation or output mode, and packaging used during the review. Add any other condition that may have changed the result.
Do not copy a duration, temperature, sample quantity, draw count, or acceptance rate from another supplier's checklist. Those numbers may belong to a different design, oil, process, instrument, or written specification. The record should tell the truth about this review, even when the team has not yet established a formal limit.
If a condition was not controlled or not recorded, write “unknown.” An honest unknown is more useful than a precise-looking value added later from memory.
Keep observations separate from possible explanations
An observation describes what actually happened. A possible explanation describes why it may have happened. Keep them in different sections.[1]
Useful observations are specific:
- “Sample B showed visible oil outside the tank after the recorded storage step.”
- “Sample C did not activate during the first recorded attempt.”
- “The mouthpiece on Sample D was not seated in the received photo.”
- “No visible change was observed on Sample E during this review.”
Do not turn the same lines into diagnoses such as “the seal failed,” “the battery is defective,” or “the oil is incompatible.” Qualified people need appropriate evidence before making that conclusion. Several conditions can produce similar symptoms. Put the possible explanation in the hypothesis section. Then list what remains unknown and ask the supplier a question tied to the sample ID and evidence.
The phrase “no issue observed” also has a limit. It means only that no issue was seen under the recorded conditions. It does not mean “never leaks,” “reliable,” “safe,” or “works with all oils.”
Link each photo or video to one observation
Photos and short videos are useful when another person can tell which sample, time, condition, and observation they show. Use a filename that includes the date and sample ID. In the log, place that filename next to the observation it supports.
Keep the image description literal. “Video shows the indicator did not appear during the recorded activation attempt” is an observation. “Video proves the battery failed” is a conclusion that may require more information.
Do not edit the image in a way that removes the surrounding condition needed to understand it. If you add an arrow or crop for communication, keep the original file too. The image is part of the conversation, not a substitute for the rest of the record.
Stop and escalate battery abnormalities or repeated problems
Stop the review if a battery behaves abnormally or the team observes swelling, smoke, unusual heat, odor, visible damage, or another safety concern.[1][2] Follow the team's workplace and supplier safety process. Do not continue testing to obtain a cleaner result. Lithium-ion product warnings have linked overheating and swelling with fire hazards, so these observations deserve escalation rather than diagnosis by guesswork.[2]
Repeated or unexplained problems also need a clear handoff. Record how many samples showed the observation and attach the evidence. Preserve the affected sample only as the team's trained process allows. Ask the supplier what information is needed next. A repeat pattern is a reason to investigate; it is not proof of one cause.
Retest after a meaningful change
An earlier record belongs to the product and conditions it describes. Review the need for a fresh sample or retest when a product detail changes. The detail may be the structure, material, color, dimensions, stated capacity, formula, filling or capping step, packaging, activation, output setting, firmware, or another control.[1]
Write the change next to the old reference and name the affected part of the review. A packaging change may require another fit review without repeating an unrelated observation. A product or filling-process change may affect several sections. The team should decide the scope from the actual change instead of automatically copying every old result forward.
The same rule applies when the change is unknown. Ask whether the sample and the hardware you plan to buy are the same version before relying on the earlier record.
End with a decision and an exact supplier question
Finish the record with observed facts, remaining unknowns, an owner, and one next action. A useful supplier question includes the supplier's model name or number, your sample ID, the observation, the condition, and the linked evidence. It asks for the missing information without asserting a cause.
For example: “On Sample C, the indicator did not appear during the activation attempt shown in video 2026-08-01-C-01. We used the mode and charging step in the supplied instructions. What information should we verify before repeating the review?”
The answer may lead to another test, a corrected instruction, a fresh sample, or a pause. Update the record rather than replacing the original observation. That history makes the next discussion easier to follow.
Use a practical scorecard to capture the identity, conditions, observations, hypotheses, unknowns, escalation check, change check, and decision in one place. If Briar Glass AIO is one of the samples being considered, verify the current product and order information on the product page before acting. The sample record should still stand on its own if that link is removed.
A good record does not make the sample look better. It makes the next decision clearer. Name the sample, write what happened, preserve what remains unknown, and repeat the affected review when the product or process changes.
References
- GreenDeagle editorial operating guidance, reviewed 2026-08-03. It supports the recordkeeping and decision process described here, not a product-performance, compatibility, inventory, delivery, safety, or supplier-performance claim. Current commercial context: https://greendeagle.com/products/briar
- U.S. Consumer Product Safety Commission product-specific lithium-ion battery warning