Build a source pack before asking Bot to research
Prepare an approved source list, a decision question, and a fact-versus-interpretation ledger for a focused research task.
A source pack makes research easier to check. Instead of asking for everything about a market, define a decision and supply the material needed to investigate it. The workflow works with pasted extracts or shareable documents; live browsing is optional and environment-dependent.
Prepare the input
Choose three to five relevant sources. Record their titles, links where available, dates, and why each matters. Include the question you need answered and the information you do not yet have. Prefer original documents for product terms or technical claims.
Run the workflow
Ask the assistant to extract facts first, then compare. Give each finding a source reference. Keep absent information distinct from a negative finding. If two sources disagree, preserve the difference rather than average them into a new claim.
Prompt to copy
Decision question: [question]. Sources: [material and references].
First build a ledger: finding, source, date, scope, uncertainty.
Then explain the material differences relevant to my decision.
Separate source claims, your interpretation, and open questions.
Do not infer that a feature is absent because it is not mentioned.
Finish with three targeted verification questions.
Review a worked example
In an illustrative supplier comparison, one page lists a monthly fee and another lists usage-based charges. The useful finding is that the pricing units differ. Calling one cheaper without a shared usage assumption is premature.
Open a sample of the cited sections. Check dates and scope, then inspect the recommendation. It should be possible to trace the conclusion back to the ledger.
When a source is a summary of another document, try to obtain the original before relying on an important claim. Keep the summary labeled if the original is unavailable. Check that a quotation has not lost the condition in the next sentence. A claim can be accurately copied and still be misleading when its scope is omitted.
Use it again
Save the approved question and ledger format. On the next refresh, revisit the sources that drive the decision rather than rebuild a broad report. See Bot for the personal assistant direction or contact Golub when research needs a maintained connected service.
More guides
Your first useful Bot workflow: turn notes into an action list
Start with supplied notes, a defined output, and a short review. Build an action list without inventing owners or deadlines.
Write a one-page operating brief for your Bot
Give your assistant stable working rules, task boundaries, and a review standard without burying the current job in a long persona.
Turn a successful one-off task into a repeatable checklist
Document the inputs, output, stop conditions, and review steps of a working Bot task before considering a schedule.
Find your next workflow
Browse more categories or explore Golub Bot.
All guides