How to write a task description that gives someone a clear starting point
A task description should explain the desired result and enough context to begin work. This tool helps turn short notes into a usable brief without inventing a larger scope.
Start with the right material.
- What you provide
- an opened task editor and supplied rough notes.
- The intended result
- Fill objective, scope and acceptance checklist; stop before saving.
How the workflow works.
State the goal, relevant background and known constraints, then describe what completion would look like. Keep unresolved requirements visible as questions rather than hiding them in polished prose.
What to check in the result.
Ask whether the assigned person could start with the information provided. Check that dependencies, links and acceptance conditions are real, and confirm any proposed ownership or deadline separately.
Inspect every prepared field in its real form context. The illustrated draft is a review artifact; it does not send a message, submit a form or confirm that an account record was changed.
Learn from the worked example.
The downloadable example shows a prepared draft for inspection. Compare its fields with the supplied facts and keep the decision to save, send or submit separate from preparing the content.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.