Claude / Getting Started & Prompt Design
Claude: specify an output format that is easy to review
Prepare three sample service requests and decide which columns a reviewer needs. Define an empty-value convention in advance.
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 specify an output format that is easy to review. 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
Prepare three sample service requests and decide which columns a reviewer needs. Define an empty-value convention in advance. 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.
Convert these requests into a table with Request, Evidence, Next question and Owner. Use Not assigned for an absent owner. Keep one request per row.Review the result
Count input requests and output rows; check that owners are not inferred from who reported an issue. Record each correction and its supporting source.
If the answer is wrong or incomplete
A neat table can hide invented ownership. Test one deliberately incomplete request and check the empty-value convention. 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.