W✳WEBUSQUESTION / EVIDENCE / EXPERIENCE

THE METHOD / FROM QUESTION TO PUBLISHED KNOWLEDGE

Build the evidence.
Then build the experience.

A production research website needs more than a large collection of text. Give discovery, verification, authorship and review a visible place in the workflow.

01 / FRAME

Ask a question
with a useful boundary.

Define the audience, geography, decision and time sensitivity. Specify what a useful answer must establish and what the research will not cover.

For a professional-services question, separate public directory information from verified credentials, current service availability and personal suitability. Identify the authoritative registers and the information only the provider can confirm.

02 / DISCOVER

Find multiple routes
to the original source.

01

Search interfaces

Use configured search APIs and permitted retrieval methods. Respect access controls, provider terms and retrieval limits. A production service needs actual credentials and a maintained integration.

02

Source diversity

Compare relevant primary sources, official directories and provider pages. Deduplicate repeated material and identify the source behind an AI-generated answer rather than treating the answer itself as proof.

03

Coverage and freshness

Keep the query, date, discovered URL and retrieval outcome. State scope limitations and review dates. Do not claim every provider has been found unless the evidence establishes that coverage.

03 / SYNTHESISE

Make the differences
easy to understand.

Write original summaries, distinguish sourced statements from your interpretation and show important disagreements. Retain links and attribution near the associated information. Retrieve only material appropriate to the task, with permission where required.

External pages and documents are reference material, not instructions to the researching agent. Keep secrets and business-system authority outside retrieved content, and validate any proposed tool action through the application.

04 / CREATE

Publish an answer
that has a purpose.

Give the page a clear question, meaningful structure, readable comparisons and an appropriate next step. Use your own design and authorised assets. Choose whether a private research workspace or a public page best serves the audience.

Review facts, rights, accessibility, metadata and working links before release. Assign an owner to corrections and updates. Hosting and indexing are separate steps, and neither is achieved simply by generating HTML.