Claude / Claude Research & Review
Claude: review a research scope before accepting a report
Define the comparison question, geography, date range and acceptable sources. Exclude private systems you have not authorized for this task.
Environment and inputs: Claude user guide · Feature and source access depend on the active account, app and organization settings. Optional file or app steps have a text-excerpt fallback. No fixed model version, price or usage quota is assumed.
What you will make
A practical Claude guide to review a research scope before accepting a report. Use the sample input and prompt, then check the result. Use a fictional support-document review as the practice setting. Keep passages and your interpretation in separate output fields.
Prepare the source and scope
Define the comparison question, geography, date range and acceptable sources. Exclude private systems you have not authorized for this task. Open Claude and start a focused conversation, or use the appropriate existing project for recurring work.
Try this prompt
In Claude, provide the prepared input, then send the following request. For real work, replace fictional details with approved facts.
Draft a research scope for a small-office continuity plan. Separate mandatory questions from optional background and specify evidence needed for every recommendation.Review the result
Check whether the final scope can be answered with the allowed sources and whether it matches the actual office environment. Record each correction and its supporting source.
If the answer is wrong or incomplete
An expansive scope can bury the decision under background reading. Prioritize the questions whose answers change the plan. Put the source excerpt and the request in separate labeled blocks. For longer reviews, retain paragraph labels so corrections remain traceable.
Practice and completion check
Repeat with one incomplete input. Check the answer against the review criteria, remove unsupported claims and save the prompt with its source version. This workflow has not been verified in a customer deployment.