Back to results
Explore the library298 guides total · goals, work & tasks
By goal

Choose what you want to achieve.

By work or interest

Choose a setting you work or spend time in.

By task

Choose the kind of help you want.

Counts show all available guides. Filters combine to narrow your results.

Communicate clearlyGuide

Make a vendor-demo scorecard before you see the sales pitch

Ask the supplier to demonstrate concrete tasks and record what you actually see.

Illustrative resourceNot tool-testedSmall teams comparing software demonstrations
What you’re working towards

Observable demo tasks, evidence boxes and not-shown outcomes rather than unsupported scores

Download playbook .md

Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides

Saving needs JavaScript. Reading and downloading this guide does not save it.

Make a start

One step at a time.

3 steps

Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.

Start with the synthetic example, then adapt each prompt to your task.

01

Open a chat and use the complete sample

A vendor is a possible supplier. This scorecard is an observation sheet for its demonstration, with no result filled in yet. Open https://chatgpt.com. If you have access, choose New chat. Copy all the instructions below (the prompt), including the SAMPLE INPUT, into the message box and send it. You do not need to upload a file. You should see four task-based observation cards with empty result fields and clear evidence criteria. The wording can differ from the worked example, but the facts and constraints must agree. If you cannot access this service, use another text assistant available to you; account requirements and limits may differ.

Your starting prompt
Create a vendor-demo observation sheet for the four needs. Write an observable demonstration request and pass condition for each, with unfilled result and notes fields. Explain that Not shown is different from Fail. Use only the supplied facts; mark missing information rather than inventing it. Return written text only. Do not send, publish or change anything in another service.

SAMPLE INPUT
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional evaluation of a project-list tool. Team needs: find a project by exact code; export only the currently filtered list; rename a draft without publishing; understand what happens when saving fails. Demo uses supplier-provided made-up records only. No scoring weights, budget, procurement decision or security assessment supplied. Need a four-task observation sheet with request, pass evidence, not-shown option and notes. Do not infer that a tool meets a need from a sales claim or award points before the demo.
02

Compare, correct and save

Compare the answer with the complete sample input and the checks below. The four supplied needs each have an observable pass condition. If a fact is missing, changed or invented, paste the correction prompt below into the same chat. Read the revised result again; if it still fails, correct the text yourself before using it. Copy the reviewed result into a new note or text document. Keep real publication, decisions and sending for a separate human review.

Your starting prompt
Check your previous answer against the SAMPLE INPUT in my first message. Test each point below. For a failure, show the problem and then return a complete corrected answer; for a missing source fact, keep it explicitly unknown. Do not invent a successful check.
- The four supplied needs each have an observable pass condition.
- No task is pre-scored and Not shown remains distinct from Fail.
- The example asks for made-up demo records and does not imply a purchase or security approval.
03

Optional: use your own facts

Open a new chat. Copy the prompt below and replace [PASTE YOUR INPUT HERE] with your own non-sensitive source text, facts and limits for this task. Include any desired headings, count or length. Send the whole message. Expect the same kind of written result, using your facts. Check every source fact and limit yourself; the example’s names and totals do not apply. If a detail differs, show the exact mismatch and ask for a complete correction. Save the checked draft before any separate decision to use or send it.

Your starting prompt
Make a supplier-demo observation sheet for each need below. Give an observable demonstration request and pass condition, leaving results and notes blank. Keep Not shown distinct from Fail. Use only supplier-provided made-up records and run any failure demonstration only in the supplier’s safe test setup. This does not assess security or authorize a purchase.

Use only my input. Ask for information needed to finish rather than guessing. Return written text only; do not send, publish, book, submit or change another service.

MY INPUT
[PASTE YOUR INPUT HERE]
Optional: improve the result

Capture evidence consistently

Prepare a note format that makes later comparison fairer. This extension uses the worked example. Return to that example chat, or paste its input and your checked example answer into a new chat first. Do not apply its sample values unchanged to your own input.

Advanced prompt
Add a common evidence-note template: demo date, demonstrated steps, observed result, limitation stated, and follow-up question. Leave all fields empty and add no numeric rating system. Keep the same SAMPLE INPUT from my first message unless I explicitly replace it.
Show, then try

See the shape of the result.

This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.

The starting point

Synthetic input
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional evaluation of a project-list tool. Team needs: find a project by exact code; export only the currently filtered list; rename a draft without publishing; understand what happens when saving fails. Demo uses supplier-provided made-up records only. No scoring weights, budget, procurement decision or security assessment supplied. Need a four-task observation sheet with request, pass evidence, not-shown option and notes. Do not infer that a tool meets a need from a sales claim or award points before the demo.

Copies text only. For image or file tasks, use the source files named in the steps too.

Download source .txt

The intended result

Illustrative output
Worked example written for this guide, not output recorded from a live AI session.

Use supplier-provided made-up records only; run the failure demonstration only in the supplier’s safe test setup.

1. Exact-code search
Ask: Show a search for one supplied project code.
Pass evidence: The matching project appears and its displayed code exactly matches the query.
Result: [Pass / Fail / Not shown] Notes: [ ]

2. Filtered export
Ask: Filter the demonstration list, export it and open the export.
Pass evidence: Exported records match the visible filtered records, with no extra records.
Result: [Pass / Fail / Not shown] Notes: [ ]

3. Rename a draft
Ask: Rename a draft and show its status afterward.
Pass evidence: The new name is saved and the item remains a draft.
Result: [Pass / Fail / Not shown] Notes: [ ]

4. Failed save
Ask: Demonstrate a save failure in the supplier’s safe test setup.
Pass evidence: The interface explains whether changes saved and what the user can do next.
Result: [Pass / Fail / Not shown] Notes: [ ]

Not shown means evidence was not demonstrated; it does not prove the feature fails. Leave results blank until the demo. This sheet does not assess security or authorize a purchase.
Download result .txt
You’re the final check

Check the worked example.

These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.

Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.

A few things to watch for.

  • A slide claiming a feature exists is not the same evidence as seeing the task work.
  • Do not test failures on production accounts or ask for private customer records.

What has been checked?

Documentation
No dated source review recorded.
Included files
No scoped artifact-check record.
AI workflow
Not run in a recorded consumer-AI workflow.
Time savings
Time savings not measured

Copy these instructions

Your browser blocked automatic copying. Select the text below and copy it.