Write the result in one sentence.
Turn a broad request such as “research this market” into a specific result: “Compare these three options in two pages, use only these approved sources and flag any missing evidence.”
Now you can check the length, the options compared, the sources used and any gaps. You have something concrete to approve or revise.
Write a short task brief.
- Goal: What result should exist when the work is complete?
- Inputs: Which sources and files are approved for use?
- Boundaries: What must not be accessed, changed, or sent?
- Checks: What must you be able to verify before approving the result?
- Owner: Who can approve, revise, or stop the work?
- Exceptions: What should happen when information is missing or a check fails?
Plan for decisions and problems.
Plan around moments when new information changes what should happen next. Gathering approved inputs, creating a draft, checking it, and reviewing it are useful boundaries because each can produce a different next decision.
A task list also needs rules for moving between steps, handling failures and getting permission. Plan for problems as well as success.
Check the result before calling it done.
Call the work done when the agreed checks have passed and the responsible person has made the required decision. Keep unresolved questions visible.
If a required source is missing, say what is missing and which decision it prevents. A clear reason to pause can be more useful than a confident answer built on gaps. Use the free task brief to write down your own result, limits and checks.