Search intent is an interpretation, not a permanent label. An assumption ledger helps editors act on current evidence without forgetting the uncertainty behind the decision.
State the assumption plainly
Describe the likely reader, task, and desired next step in one short entry. Avoid broad labels such as “informational” when the team needs to distinguish setup help from vendor comparison or troubleshooting.
Attach observable evidence
Link query variations, result types, on-site behavior, customer questions, and the observation window. Separate direct observations from conclusions. Small or biased samples should be labeled as such.
Define a challenge condition
Write what would cause the team to revisit the assumption: sustained query changes, new product constraints, repeated reader confusion, or a conflicting page in the inventory.
Use it during briefs and refreshes
Review the ledger before commissioning a new route. Update the entry when evidence changes, retaining the earlier decision and date so the team can understand how its interpretation evolved.
