Output Management:
From Prompt to Production
Turn Claude responses into files that actually move through a Car-Mart dealership instead of sitting in a chat window.
A Jonesboro, Arkansas field collector finishes a 12-account daily route across Car-Mart BHPH customers. He has a stack of handwritten receipts, a notebook with payment promises, and a 2018 Camry and 2014 Silverado that still need follow-up. Today he spends 30 minutes reconciling everything with the office’s main system before he can create anything usable. The collector needs one clean page that shows which customers paid, which promised to pay by Friday, and which require a follow-up call Monday — formatted so it can be saved as a project file, emailed to the dealership, and referenced in next week’s standup without any retyping.
Tell Claude exactly what you need
Specify the format
Specify the destination
Specify the audience
Specify the verb
Build a default output format in your CLAUDE.md
Add a permanent section to your CLAUDE.md file that every Car-Mart field collector can reference. Include the exact column headers, filename convention, and tone rules used across Jonesboro, Conway, and Springdale. Once set, you can simply say “Use the standard daily summary format” instead of repeating the instructions.
One-page route summary template
Emailed to office + added to Project
| Account | Customer | Vehicle | Status | Action | Deadline |
|---|---|---|---|---|---|
| JM-4821 | D. Thompson | 2018 Camry |