On this page6 sections
Core template
Fields worth keeping for every lead
| Group | Fields |
|---|---|
| Identity | URL, host, page or album title, product code, date and researcher. |
| Scope | Category, intended use, selected variant and quantity. |
| Observed | Visible images, measurements, captions, links and page messages. |
| Stated | Claims from a named page or contact, with date and route. |
| Unknown | Missing facts that could change the decision. |
| Action | Keep, compare, ask, hold or remove—with a reason. |
Language discipline
Separate saw, stated and inferred
“The public page displays a 55 cm chest width for size M. The diagram does not define whether this is flat width.”
“Size M fits a 110 cm chest perfectly.”
The first note preserves the page claim and its limit. The second turns an undefined chart into a fit guarantee.
Change log
Do not overwrite the old observation
When a price, contact, source link, chart or availability message changes, add a dated entry. Preserve the earlier value if it influenced a prior decision.
Short change entry
22 Aug: page now shows a different contact number; previous number retained in restricted history; lead paused until the change is confirmed through an authorized source.
Image context
A screenshot needs a source and a purpose
- Record the page URL and capture date.
- Keep enough surrounding context to identify the item.
- Note whether the image was public, provided in chat or restricted.
- Do not treat a screenshot as proof that the current page is unchanged.
- Do not publish passwords, private chats or personal information.
Next action
Every active record should have one owner and one question
Finish the note with the responsible person, next action, exact question and review date. If no action remains, mark the record kept, removed or archived so it does not return to the active queue.
A clear “unknown—remove” is more useful than an open bookmark that silently accumulates confidence.
