Evidence-led research
AI Agent for Research
Build research agents that map claims to sources, compare applicability, find counter-evidence and expose what remains unknown.
A research agent should help a reader determine what is supported, what is disputed and what remains unknown. The number of pages retrieved is a weak measure of that job. A short evidence map that exposes a missing experiment can be more valuable than a long report that gives every source equal weight.
This guide is for research managers, technical strategy teams, product developers and analysts who investigate questions across documents and data sources. The focus is evidence collection and synthesis. Market sizing and customer discovery belong to the market research workflow; monitoring named competitors belongs to competitive intelligence.
Write a question that evidence could change
Replace “research sustainable packaging” with a decision question: which candidate materials have evidence relevant to the product’s required storage conditions, and what testing is still needed before selection? The second question defines a population, conditions, comparison and decision. It also gives the agent a reason to reject superficially related sources.
State the intended use of the answer. An initial landscape scan, a technical recommendation and a formal evidence review have different completeness requirements. Agree the source universe, date range, language coverage and exclusions. If the project cannot access relevant standards or full papers, that limitation belongs in the result rather than being concealed by confident prose.
Record the decision owner and what would change their mind. A useful research brief includes plausible competing hypotheses. If the agent is instructed only to find benefits of a preferred option, it may assemble a convincing but incomplete case. Ask explicitly for contrary evidence, boundary conditions and reasons the available studies might not apply.
A technical materials investigation
Illustrative exercise, using hypothetical evidence: a product team compares two protective coating candidates for an industrial component. It needs evidence relevant to repeated cleaning, operating temperature and adhesion to its actual substrate. The agent must prepare an evidence map, not certify either coating for use.
The search finds three hypothetical source types: a laboratory study on a different substrate, a field report with incomplete cleaning details and a manufacturer’s specification for the proposed product. The laboratory study can support a narrow claim about its tested conditions. The field report may suggest questions but cannot establish the missing cleaning regimen. The specification states the manufacturer’s declared limits; it is not an independent comparison.
The agent should resist merging these into “Candidate A performs best”. Instead, it records which requirement each source addresses and where applicability is uncertain. If no source tests the actual combination of substrate and cleaning process, the result should recommend an appropriate validation task for the technical owner. Absence of evidence in the reviewed set is not proof that the material fails.
The product team can then decide whether to commission testing, seek a supplier clarification or narrow the intended use. The research deliverable has advanced the decision even though it has not supplied a final winner. That is a more defensible outcome than generating a ranking whose assumptions are invisible.
Build a claim-evidence register
Use one row for each decision-relevant claim, not one row for every downloaded document. Several sources may support the same claim, and one source may support only part of it. Keep a separate source inventory for bibliographic details and access status.
| Question | Available evidence | Applicability limit | Next decision |
|---|---|---|---|
| Adhesion on the required substrate | Hypothetical laboratory study tests another substrate | Direct transfer of results is unproven | Technical owner defines a relevant test |
| Repeated cleaning performance | Hypothetical field report omits cleaning details | Exposure conditions cannot be compared | Seek methods or supplier evidence |
| Declared operating range | Manufacturer specification for the proposed product | Supplier statement; version and intended use matter | Confirm current specification and project fit |
| Overall choice | Evidence covers different conditions | No direct like-for-like comparison in the reviewed set | Do not produce an unsupported winner |
For each source, store the title, author or issuing organisation, publication date, version, persistent identifier where available, access date and the exact passage or table supporting the claim. Separate a direct observation from the author’s interpretation and from the agent’s synthesis. The reader should be able to audit that chain.
Search broadly, then screen deliberately
Develop query families from the question: subject terms, synonyms, alternative terminology, failure modes and relevant conditions. Search in the languages that could materially affect coverage. Arabic and English searches may retrieve different institutional material; translating one English query mechanically is not a complete bilingual strategy.
Log the databases or sites searched, query date, main filters and screening decisions. Deduplicate by persistent identifier and document version where possible. A preprint, conference paper and journal article may describe the same underlying work. Counting all three as independent confirmation exaggerates the evidence.
Crossref’s REST API documentation describes access to deposited scholarly metadata, including identifiers and publication information. Metadata can help discovery and deduplication; it does not establish that the agent has read the full study or assessed its methods.
Define inclusion and exclusion rules before screening. A source may be excluded because the population, intervention, context or outcome is irrelevant, not because its conclusion is inconvenient. Retain reasons for borderline exclusions. For a formal systematic review, qualified researchers must choose and follow the appropriate methodology; a broad web search should not be labelled exhaustive.
Check the state of the source, not just its existence
Verify that links resolve to the intended document and that cited identifiers match the title and authors. Check corrections, retractions and later versions where relevant. Crossref’s documented update filters can help identify registered updates, but absence of a metadata flag is not proof that a source has no issue.
For changing web content, retain the version or permitted snapshot used, with an access date. Distinguish a current specification from an archived one. If a source was removed or access is blocked, say which claim cannot be verified. The agent must not fill a missing citation with a plausible-looking URL.
Respect access and reuse conditions. An abstract or metadata record may be available even when the full text requires licensed access. Summarise within the permissions available and avoid reproducing long source passages. A research agent should not bypass access controls to make its coverage appear complete.
Synthesis requires comparison of methods and limits
Organise the final analysis around the decision, not the order in which sources were found. Compare study design, measurement method, sample, conditions and relevance. Two sources can reach different conclusions because they tested different situations. Describe that difference before labelling the evidence contradictory.
Keep numerical values attached to their units, denominator and uncertainty. Do not average results from incompatible tests simply because the numbers are easy to combine. If quantitative synthesis is appropriate, use a specified analytical method and qualified review. The data analysis agent can assist with reproducible calculations once the research design justifies them.
Use calibrated language: supported within the tested conditions, suggestive but indirect, inconsistent or not established by the reviewed evidence. Avoid converting “not statistically significant” into “no effect” without examining the study and its uncertainty. When an inference is useful, label it and state the assumptions that connect the evidence to the conclusion.
Set a stop rule and a route for unresolved questions
A research agent can keep searching indefinitely without improving the answer. Agree a stopping condition such as coverage of the specified source universe, completion of a documented query set and review of key contrary evidence. If the budget or deadline stops the work earlier, describe what remains unsearched.
Track information gain. New sources that repeat the same supplier claim do not necessarily reduce uncertainty. A single methods appendix may resolve more than another 20 summaries. Let the researcher redirect effort towards the decision’s weakest evidence link.
For the coating example, the stop decision could be: discovery is sufficient for a preliminary evidence map, but selection is blocked by the missing substrate-and-cleaning test. The next task belongs to the technical team, not another round of generic searching. Keep that distinction visible in the recommendation.
Evaluate citation support and decision usefulness
Test whether each citation actually supports the nearby claim, whether quoted values retain their context and whether important counter-evidence was omitted. Include fabricated references, duplicate publications, misleading abstracts, inaccessible full texts and documents containing instructions to alter the research plan.
Have subject specialists review a sample of accepted and excluded sources. Measure unsupported claims, missed relevant evidence, incorrect version handling and time required to verify the report. A source count or fluent summary score does not measure research quality. The agent evaluation framework can organise these checks without replacing domain judgement.
For custom research-agent development, agree the source access, evidence schema, review process and permitted outputs. Request information about a research agent with a real decision question, a small approved source set and an example of a conclusion your reviewers rejected. Those materials define the difference between useful synthesis and an attractive report that cannot be defended.