Technology library

Technology · guide

Build a technology shortlist before you request demos

Before you compare products, write down the work the software needs to support, who will use it, what data it will hold, and which systems it must connect to. Include how you'd leave. A short list with checked facts will tell you more than a general ranking.

Start the guide
01

Understand the work

Before the checklist

What this guide helps you do

It's easy to leave a software demo wanting features you hadn't thought about an hour ago. Before you book one, write down the problem you're trying to solve, who needs the system, and what would make a switch worthwhile.

If you are starting a practice

You may not know every future workflow yet. Start with the work you expect to do every week, the people involved, and the information that has to move safely between them.

If you already run a practice

Write down the problems your current tools cause. Which ones matter enough to justify moving to another system? Use those problems to guide the comparison.

An example of the resultA two-page comparison of three products. Each answers the same questions, links to dated evidence, flags what you still don't know, and explains why you're keeping or dropping that option.
02

Start here

Start here

Before you start

  • Start with the operational problem and the people who must use the product.
  • Separate vendor statements from contract terms, documentation, and hands-on verification.
  • Plan data export and service continuity before signing a contract.

Make sure this fits

Use this for an early, practice-level technology selection before product demonstrations or contract review.

Pause when

  • A product has already been selected and the task is implementation or incident response.

Gather before you begin

  • A named workflow
  • The roles who use it
  • A list of systems it must connect to

What to have when you finish

  • A dated shortlist with verified facts, explicit unknowns, and exit questions
Why this helps

The demo may look great while leaving your biggest questions unanswered: How much work is the move? Can you get your data back? What will your team have to set up?

03

Do the work

Guided process

Work through the steps

  1. 01

    Describe the problem in one sentence

    Who handles itWorkflow ownerTimingBefore researching vendorsWhyIf you can name the job the software needs to do, you have something useful to judge each feature against.Save thisA one-sentence problem statement
    Pause or get help when

    Pause if the team cannot agree on the workflow owner or intended outcome.

  2. 02

    List what you need to verify, including how to leave

    Who handles itOperations and privacy leadsTimingBefore demosWhyYou may need contracts, support documents, or a test account to answer questions the demo doesn't cover.Save thisA verification checklist with source links and dates
    Pause or get help when

    Obtain qualified privacy, security, legal, or accessibility review when sensitive data or consequential contract terms are involved.

  3. 03

    Compare the same facts across a short list

    Who handles itSelection teamTimingAfter evidence collectionWhyAsk each vendor the same questions so you can compare the answers and see what's still missing.Save thisA dated comparison and decision record
    Pause or get help when

    Do not treat an unknown as a pass or rely on a compliance marketing label.

04

Finish well

Adapt, record, review

Record what you decided and what comes next.

If your situation is different

  • Security, accessibility, contracting, and migration review depth should match the data and workflows involved.

Check your work

  • The shortlist contains no more than five products
  • Every must-have has a verified fact or an explicit unknown
  • The team has an export and continuity question for each vendor

Editable worksheet

Write down who will follow up.

Record who will follow up, where the approved records live, and what still needs an answer. Save the draft in this browser or print a copy. Browser storage is not secure record storage. Do not enter client details, credentials, health information, financial account numbers, or sensitive employee information.

Your draft stays in this browser.

Keep a copy

Download a PDF to keep or an editable Word document to continue working. The file is created on your device.

Removes the answers saved in this browser.

Common mistakes

  • Treating vendor marketing, a demo, or BAA availability as proof that the product fits the practice.
05

Verify the work

Sources and review

Sources and limits

Scope: This worksheet supports technology research. It is not a security certification, procurement guarantee, or determination that a product is compliant for a particular practice.

Approved claims and boundaries

What evidence should a practice collect before comparing technology products?

Compare the same workflow, contract, security, accessibility, portability, support, and exit facts across a bounded shortlist, while leaving unavailable facts marked unknown.

Applies to: General technology research before a product is selected or a contract is signed.

  • This does not certify security, privacy, accessibility, or legal compliance.

Source record

  1. Practice Hub research methodologyLudara · Governing project standardChecked 2026-07-23
  2. Sample Business Associate Agreement ProvisionsU.S. Department of Health and Human Services · Official federal guidanceChecked 2026-07-23

Last reviewed: 2026-07-23. Information and requirements can change; confirm consequential decisions with the cited authority or an appropriate professional.

Report a possible error or better source