Ask what the finished work must enable
A customer may request an object, document or service while describing little about its intended use. Start with the practical outcome: where it will be used, who will use it and what it must help them do. Ask for relevant constraints and existing materials. Avoid treating a reference image as a complete specification. Two people can admire the same example while expecting different dimensions, functions or levels of finish from the work they are discussing.
Record unresolved choices explicitly
Write a short brief that separates confirmed requirements from options still being considered. Identify the necessary inputs and who can approve the work. A job can stall when several people comment but nobody has authority to make the final choice. Do not assume that the person introducing the project is also its approver. Include the point where additional decisions may change the scope or timetable, using your normal agreement process for any change rather than relying on an informal conversation alone.
Read it back before production
Give the customer a concise opportunity to confirm that the brief describes their request. Use concrete examples for words that could be interpreted differently. Internally, ask whether another competent person could begin the first task using the document and its linked materials. Correct the missing information before proceeding. Keep the approved version accessible alongside the job record. A brief is most valuable as a shared working reference; it loses that value when later decisions are scattered across messages that never reach it.
U.S. Small Business Administration: manage your business ↗
This article combines general educational guidance with original planning exercises. It does not claim first-hand field testing or an endorsement from the linked organization. Sources checked October 2026.
