The reader’s situation
The person buying the software may also be responsible for maintaining it. The proposed reader is a small business without a dedicated systems administrator and wants to prepare an accurate, on-brand piece of writing.
The specific decision
A report should answer a decision your team actually makes. Make day-to-day work understandable to a second person.
Proposed evaluation
Prepare a 400-word service page, a short email and a paragraph requiring factual correction.
- Reconcile one dashboard metric against the underlying sample records.
- Let a colleague repeat a task using a one-page handover.
- Provide a short brief, a style sample and a list of permitted facts.
Evidence to gather
- The current official documentation for the exact plan and feature.
- The plan name, region, billing term and date of each price checked.
- An original trial record showing the input, output and observed limitation.
- A clear explanation of how this lens changes the buying decision for this audience.
- Evidence that this page answers a distinct reader need rather than repeating another guide.
Questions for the category
- What content may be retained or used by the provider?
- Which limits apply to your actual drafting and editing workflow?
- Can your editor work in the applications they already use?
Editorial acceptance criteria
A finished article should answer its decision question with evidence and a concrete example. Merge it into an existing guide if the answer is materially the same. Remove irrelevant candidate tools, explain uncertainty and keep pricing claims dated.
Keyword volume and difficulty have not been measured for this brief. No product ranking, affiliate approval or purchase recommendation has been established.