# First product trial checklist

Pretectal · Updated October 2, 2026
Guide: https://pretectal.com/start-building

Use this checklist before a limited team trial. It records what you have checked; it does not replace testing or certify a product. Mark items that do not apply and explain why.

Product:
Owner:
Version / preview:
Reviewer:
Date:
Status: prototype / ready for a limited trial / needs revision

## The task

- [ ] A specific user and task are named.
- [ ] Someone who does the task confirmed the problem matters.
- [ ] The first version has a clear scope and explicit exclusions.
- [ ] Three acceptance checks describe observable behavior.

Notes / evidence:

## The working path

- [ ] The user can complete the task from input to the correct result.
- [ ] Empty, incorrect, and unexpected inputs have understandable outcomes.
- [ ] Displayed facts, links, and calculations have been checked where relevant.
- [ ] Reloading or returning to the tool behaves as the user expects.
- [ ] The intended screen size and keyboard path have been tried.
- [ ] The last working version can be recovered.

Notes / evidence:

## The user trial

- [ ] An intended user tried the task without step-by-step coaching.
- [ ] Confusion, wrong results, and interruptions were recorded.
- [ ] The most important problem was fixed and the task was tried again.
- [ ] Any claim of improved speed or fewer errors has a recorded comparison with the previous process.

Task given:
Tester / date / device:
Observed result:
Fix and retest:
What remains uncertain:

## Content, access, and live AI

- [ ] The team knows which content and data the tool is allowed to use.
- [ ] Real accounts, shared data, and integrations are reviewed before connection, if needed.
- [ ] User access is tested against the intended permissions, if applicable.
- [ ] If AI runs inside the product, representative outputs and failures have been evaluated, and an owner can monitor cost and quality.
- [ ] The AI contribution is described accurately; unfinished review is not presented as approval.

Notes / evidence / items that do not apply:

## The handoff

- [ ] A named person owns the tool and its updates.
- [ ] Operating notes explain how to change content and report problems.
- [ ] The current version and known limits are recorded.
- [ ] The next maintainer can find the code, data, and recovery instructions.
- [ ] A feedback date and a decision about continuing the trial are scheduled by the team.

Open issue | Owner | Action needed before wider use
--- | --- | ---
 | |

Decision and scope of the trial:
Next feedback date:

Product brief: https://pretectal.com/resources/product-brief.md