Claude / IT Support & Reliable Workflows
Claude: write a weekly update that separates progress from plans
Collect dated accomplishments, unresolved issues and proposed next steps. Identify which delivery dates are agreed.
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 write a weekly update that separates progress from plans. 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
Collect dated accomplishments, unresolved issues and proposed next steps. Identify which delivery dates are agreed. 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.
Write a short weekly IT update with Completed, Blocked and Next sections. Preserve agreed dates and label proposed dates. Do not report a task complete from an intention alone.Review the result
Trace every completed item to evidence and every blocker to a concrete dependency or decision. Record each correction and its supporting source.
If the answer is wrong or incomplete
A confident status label can hide missing acceptance. Check the definition of done before using green or complete. 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.