How should I record the evidence behind each product requirement I care about?
Quick answer
Use one row per requirement, and record the exact product or model, what you need it to do, the source and location of the evidence, when you checked it, and what remains uncertain. Separate what a source explicitly says from your interpretation. If you cannot trace a claim to a source, mark it unverified rather than treating it as established.
The question, the details, the next step.
I’m comparing products and keep losing track of where claims came from. What should I record for each requirement?
Make a log with one row per requirement, not one note per product. That makes it easier to compare what matters to you across several options and to see when a requirement has no supporting evidence yet.
For each row, capture:
- Requirement: A concrete need, such as “fits the space available” or “includes the feature I need.”
- Exact product: Brand, model, version, size, or other identifier shown in the material you checked. Use a placeholder if you have not confirmed it.
- Evidence: What the source actually states, plus a page, section, label, or other locator that will help you find it again.
- Source and date checked: Name the source and record the date you reviewed it.
- Assessment and uncertainty: Say whether the source supports the requirement, conflicts with it, or leaves it unanswered. Note any interpretation you made.
Keep the evidence wording distinct from your conclusion. A note like “seems suitable” is an assessment, not a source-backed claim.
How can I make the log clear about what the source says versus what I’m assuming?
Use separate fields for source wording and my assessment. In the first, summarize only the claim you can locate in the material. In the second, explain how you think it relates to your requirement and flag gaps. If the wording is ambiguous, record that rather than resolving it by guesswork.
For example, suppose a hypothetical listing says a product is “compact,” but gives no measurements. Your entry might look like this:
Requirement: Fits a space no wider than [your measured limit] Product: [brand, model, version] Source: [listing title or document], [section or location] Source wording: “Compact” (or a short, faithful summary) Date checked: [YYYY-MM-DD] My assessment: Not confirmed; the source gives no width measurement in the material reviewed. Next step: Look for a measurement in another identifiable source or ask the seller to confirm the exact model’s width.
That record does not claim the product will fit. It preserves what you checked and what you still need to establish.
What if I find conflicting information or the product details change?
Do not overwrite the earlier entry as if the conflict never happened. Add a new dated entry or keep a short history showing which source said what and when you checked it. Confirm that each source refers to the same exact model and version before treating the claims as a conflict; similar product names may refer to different items.
For example:
- [Date]: [Source A], [location] — states [claim].
- [Date]: [Source B], [location] — states [different claim].
- Status: Unresolved; model match or current details not confirmed.
- Next action: Check the exact model identifier or ask the seller a specific question.
A date tells you when you reviewed a source, not how long its claim will remain current. The log also cannot establish that a source is complete or correct; it helps you trace and assess the evidence you have.
Can you give me a reusable format that works for a short comparison?
Copy this template and repeat it for each requirement and product. If you use a spreadsheet, each numbered line can be a column; if you use notes, keep the labels together so the evidence is not separated from the product it concerns.
Requirement: [specific need] Product and exact model/version: [identifier as shown] Source name: [document, listing, label, or person] Source location: [page, section, field, or conversation date] What the source says: [faithful summary] Date checked: [YYYY-MM-DD] My assessment: [supports / conflicts / unclear / not checked] Uncertainty or assumption: [what is missing or inferred] Next step: [verify, ask, compare, or none]
Before deciding, scan for blank source fields, mismatched model identifiers, and conclusions based only on your interpretation. Keep an unresolved requirement visibly unresolved; that is more useful than filling the gap with a guess.
A practical checklist
Write each requirement as a specific need you can assess.
Record the exact product model, version, or identifier shown in the source.
Name the source and add a locator that helps you find the evidence again.
Date each check and keep the source wording separate from your assessment.
Mark conflicts, missing details, and assumptions as unresolved.
Recheck model identity before comparing claims from different sources.
A few more useful answers
Should I save the full source or just a link or note?
Record enough identifying detail to locate the material again, such as its name and section or listing field. A link or brief note alone may not preserve which claim you relied on.
How should I record a requirement that I cannot verify?
Mark it “not confirmed” or “unanswered,” say what evidence is missing, and write a specific next step. Do not convert an assumption into a verified claim.
How often should I update the log?
Add a new dated entry whenever you check a source again or find different information. The date records when you reviewed it; it does not guarantee the information remains current.