A practical method
A demo evidence card
A demo evidence card with project identity, tested behavior, data boundaries and publication limits. Work through the prompts in your own notes. No information is submitted or saved here.
Project identity
Name the task, creator, version and permission to display. Avoid a customer name or logo unless there is explicit documented consent.
Visible behavior
List routes and controls; mark each implemented, simulated, missing or unknown. Include responsive and keyboard paths.
Data and integration
Identify sample data, storage, external services and security boundary. A static mockup must not be described as a production system.
Evidence and limits
Record what was actually tested, by whom and when. Keep measured outcomes separate from expectations; publish no unsupported results.
Publication review
Check rights, accessibility, technical status, accuracy and support ownership. A steward decides whether the case belongs on a separate showcase host.
Record the outcome
- What is the proposed next step, and who owns it?
- What evidence supports it, and what remains unknown?
- What would make you pause or change direction?
- When will the decision be reviewed?
Keep private details in your own records. This is a reading guide, not a submission form.
Adapted from an owner-supported proposal draft. This is general planning material, not evidence of an operating service, completed engagement or professional advice. Read the source and scope note.