Help Desk Software Requirements: A Scorecard For Your Trial

Help desk software requirements as a weighted scorecard: tests and fill-in fields for a 14-day trial, a scoring rule, a filled example and a free download.

The help desk requirements scorecard

Help desk software requirements are the jobs your helpdesk must do, written as tests and fill-in fields for trials. Group them by intake, workflow, time and billing, assets, knowledge base, reporting, admin, security, and price. Weight each, score only what you verified, and drop any tool that fails a must-have.

What changed in this update · Oct 30, 2026
  • Replaced the 2018 list of seven features with a weighted scorecard and a plain-text download.
  • Added security and price-and-terms rows.

The scorecard comes from the team behind SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone.

Why Score Requirements Instead Of Reading Feature Lists

Every vendor lists tickets, a portal, and reports. A list can't tell you whether a client's 7 p.m. email becomes a ticket, or whether Tuesday's hour reaches Friday's invoice. A test can.

Public buyers work this way. Nevada's purchasing office weights each evaluation factor before the solicitation goes out and scores mandatory minimum requirements as pass or fail. Virginia's IT procurement manual sets the criteria before the request for proposal is written, with every evaluator agreeing on the weights. UK guidance allows pass/fail criteria beside weighted ones, if the method says which failure disqualifies a bid.

Set the weights together, too. As one r/sysadmin member put it: "Management chooses the ticketing system based on the 99% of the program that SD never sees and they don't care about the wants/needs of SD when they make their decision."

The Help Desk Software Requirements Scorecard

Rows 1 to 17 are weighted tests, 18 to 20 a security pre-filter, and 21 to 23 price and terms.

Helpdesk requirements scorecard
HELP DESK SOFTWARE REQUIREMENTS SCORECARD
Tests and fill-in fields for a 14-day trial
Team: [name]   Technicians: [number]
Tool A: [name]   Tool B: [name]   Tool C: [name]

HOW TO SCORE
Weight (W), set before the first demo:
  3 must have, 2 important, 1 nice to have, 0 skip
Score:
  2 passed
  1 workaround, or a paid add-on you verified and
    added to row 21
  0 missing or failed, or only on a plan you won't buy
  NV no evidence yet: 0 in the sum, not a failure
Evidence: D vendor docs or demo, V verified by you.
  Write both, for example 2V, 1D, NV. Verified means:
  rows 1-17: a scenario you ran
  rows 18-20: a document that meets your condition
  rows 21-23: price and terms in writing for your plan
Points = W x score. Best possible = sum of W x 2.
Out: a 0D or 0V on a weight-3 row.
Hold: 2D, 1D, or NV on a weight-3 row, until V.

INTAKE
1. Email to ticket
   Pass if: replies stay on the same ticket
   W[ ] A[ ] B[ ] C[ ]
2. Self-service portal
   Pass if: users check and update their own tickets
   W[ ] A[ ] B[ ] C[ ]
3. Request forms
   Pass if: a form asks only what that request needs
   W[ ] A[ ] B[ ] C[ ]

WORKFLOW
4. Categories and statuses
   Pass if: your request types and states fit
   W[ ] A[ ] B[ ] C[ ]
5. Priorities and SLA
   Pass if: a missed target shows without a spreadsheet
   W[ ] A[ ] B[ ] C[ ]
6. Routing
   Pass if: tickets reach the right tech, no sorting
   W[ ] A[ ] B[ ] C[ ]
7. Mobile
   Pass if: techs can [task] from a phone
   W[ ] A[ ] B[ ] C[ ]

TIME AND BILLING
8. Time on the ticket
   Pass if: time is logged where the work is
   W[ ] A[ ] B[ ] C[ ]
9. Rates and contracts
   Pass if: [your billing models] all fit
   W[ ] A[ ] B[ ] C[ ]
10. Invoice and accounting
   Pass if: invoices reach [accounting package]
   W[ ] A[ ] B[ ] C[ ]

ASSETS
11. Device records
   Pass if: a ticket shows its device and history
   W[ ] A[ ] B[ ] C[ ]

KNOWLEDGE BASE
12. Articles in replies
   Pass if: answers reach users without retyping
   W[ ] A[ ] B[ ] C[ ]

REPORTING
13. Monthly report
   Pass if: [report] runs on a schedule and exports
   W[ ] A[ ] B[ ] C[ ]
14. Satisfaction survey
   Pass if: a closed ticket asks the user for a rating
   W[ ] A[ ] B[ ] C[ ]

ADMIN
15. Roles and permissions
   Pass if: each person sees only what they need
   W[ ] A[ ] B[ ] C[ ]
16. Directory sign-in
   Pass if: works with [Google, Microsoft 365, or AD]
   W[ ] A[ ] B[ ] C[ ]
17. Data out
   Pass if: export counts match the counts in the tool
   W[ ] A[ ] B[ ] C[ ]

SECURITY PRE-FILTER (no weights)
Write the condition. Y meets it, N does not, NV.
A needed N is out; a needed NV is a hold.
18. Multi-factor sign-in: [who, which methods]
                           Need[ ] A[ ] B[ ] C[ ]
19. Data location: [acceptable region]
                           Need[ ] A[ ] B[ ] C[ ]
20. Backup and recovery: [terms you need in writing]
                           Need[ ] A[ ] B[ ] C[ ]

PRICE AND TERMS
Set limits first. Score 2 within all limits,
1 with one exception you accept, 0 outside.
21. Monthly cost
   Ceiling: $[ ] a month
   Plan and add-ons: A[ ] B[ ] C[ ]
   Monthly total: A $[ ] B $[ ] C $[ ]
   W[ ] A[ ] B[ ] C[ ]
22. Contract and minimums
   Acceptable: term [ ], seat minimum [ ], notice [ ]
   W[ ] A[ ] B[ ] C[ ]
23. Getting started
   Required: migration help [ ], training [ ],
   setup fees up to $[ ]
   W[ ] A[ ] B[ ] C[ ]

TOTALS
Points:          A[ ] B[ ] C[ ]
Best possible:   [ ]
Share of best:   A[ ]% B[ ]% C[ ]%
Out or on hold:  A[ ] B[ ] C[ ]
Decision: [tool and plan], [date], [who signs off]

How To Fill In The Scorecard

UK government guidance suggests a trial that tries "one small but hard problem", tests integration with your current products, and tests the user experience. Virginia's manual adds that rating works only with "consistent application by the evaluators".

  1. Set weights and limits before the first demo

    Weight rows from last month's real problems. Write your budget ceiling, acceptable term, seat minimum, required migration help, and security needs.

    Common mistake: weighting everything 3. If every row is a must-have, none is.

  2. Record evidence, not impressions

    D means the vendor documents or demos it; V means you verified it, as the scorecard defines for each row type. A promise is NV. Defaults are why V matters: one r/ITManagers member warned that "by default, if somebody replies to the ticket thread who is not the submitter of the ticket, it creates a new ticket."

  3. Score the plan you'll actually buy

    A feature on a higher plan scores 0 unless that plan is the one you price. A paid add-on scores only after you verify it and add its cost to row 21. Another r/ITManagers member's experience shows why: "you need an add-on that increases the cost by about 50 percent for just 500 assets."

  4. Price the configuration, not the seat

    Row 21 is the plan, the add-ons, and the seats you pay for, as one monthly figure. Total cost of ownership also counts installation, training, and downtime. Score 2 under your ceiling, 1 with one exception you accept, such as annual billing, and 0 over it.

  5. Apply the gates, then compare

    A confirmed 0 on a weight-3 row, or a needed security item the tool lacks, removes it. A weight-3 row with only D or NV evidence holds the decision until it is V.

For ready-made test scenarios, use the trial checklists in our ticketing system comparison for teams that bill, and our IT helpdesk software guide for internal IT.

Filled-In Example For A Small MSP

Example: three technicians who bill clients hourly and on prepaid blocks. The tables score SherpaDesk product-wide from its documentation: D or NV only. Which plan includes each row stays NV until sales or support confirms it in writing.

Documentation score for SherpaDesk, functional rows 1 to 17
RowWScorePointsEvidence
1. Email to ticket3NV0Replies post to the ticket; other senders not documented
2. Portal22D4Users check and update tickets
3. Forms12D2Fields shown per class
4. Categories and statuses21D2Fixed statuses; custom fields as a workaround
5. Priorities and SLA22D4Goals per priority; due time shown; closed-ticket report
6. Routing12D2Rules send a class to a technician
7. Mobile1NV0Site copy only: time from the app
8. Time on the ticket32D6Timer, timesheet, or "cmd time" by email
9. Rates and contracts32D6Rate plan per client; prepaid hours
10. Invoice and accounting (QuickBooks Online)32D6"Ready to Invoice"; invoices push to QuickBooks Online
11. Device records12D2Assets link to tickets; High Camp, $55 per agent per month ($50 billed annually); 0 if you price Base Camp
12. Articles in replies12D2"Create KB"; public articles attach
13. Monthly report22D4Scheduled by email; Excel export
14. Satisfaction survey11D1No built-in survey; your own link
15. Roles and permissions12D2Queue limits; rates hidden from techs
16. Directory sign-in12D2Google and Microsoft 365 sync with sign-on
17. Data out2NV0CSV, XLS, XML; completeness not documented
Subtotal3045Functional subtotal from documentation, not a trial result: 45 of 60
Security pre-filter, rows 18 to 20
RowConditionSherpaDesk
18. Multi-factor sign-inEvery technician, appNV: app or SMS, opt-in per user; enforcement not documented
19. Data locationU.S. regionNV: cloud only, on Microsoft Azure; region not documented
20. Backup and recoveryRecovery terms in writingNV: ask support
Price and terms facts, rows 21 to 23
RowSherpaDesk
21. Monthly costBase Camp: $45 per agent per month ($40 billed annually). First agent free, forever: three technicians pay $90 a month ($80 billed annually)
22. Contract and minimumsNo contract; cancel any time
23. Getting startedNo onboarding fee; migration included. On-premises AD over LDAP carries an implementation fee, amount not published

Source: SherpaDesk pricing and support docs. Prices as of October 2026.

Score rows 21 to 23 against your own limits. Rows 1, 8, 9, and 10 carry weight 3 without a V, so the decision is on hold until the trial verifies them. The security rows are holds too. A tool confirmed to have no time tracking would score 0 on rows 8 to 10 and drop out, whatever its total.

Helpdesk requirements scorecard Plain text · 3 KB · 23 rows, 3 tools · updated Oct 30, 2026
Download Scorecard

Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.

Loading form…

Score SherpaDesk In Your Own Trial

How this works in SherpaDesk

From Ticket To Time Entry To Ready To Invoice

You log time on the ticket with a timer, a timesheet, or "cmd time" in an email reply. Each client carries its own rate plan, and a contract can hold prepaid hours. Unbilled time and expenses wait in "Ready to Invoice", grouped by contract, until you bill them. The accounting hand-off works with QuickBooks Online, Xero, and FreshBooks.

A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin. Base Camp is $45 per agent per month ($40 billed annually); High Camp is $55 per agent per month ($50 billed annually). First agent free, forever. 14 days free, no card. Working alone? Single Agent is $0 with ticketing, time tracking, and invoicing; see our free helpdesk guide.

See SherpaDesk Pricing

Who this isn't for

Teams running a formal enterprise RFP, or shopping for a service desk, need more than this. SherpaDesk's own limits: We don't build RMM. We integrate with yours, and the stack stays yours. It runs in the cloud only, device records need High Camp ($55 per agent per month, $50 billed annually), and QuickBooks Desktop is a file export. On-premises AD over LDAP carries an implementation fee, amount not published.

Frequently Asked Questions

What is the best basic helpdesk software?

The one that passes your weight-3 rows at a price under your ceiling. TechTarget lists a helpdesk's tools as software to track help requests, a knowledge base, and a database of customer records. If you bill, add time on the ticket, rates, and invoicing.

How many helpdesk tools should you trial at once?

Two, or three at most. Fourteen days covers two tools well; a third needs someone with real hours to give it. Score every tool on the same rows and weights, and keep the weights fixed once the first demo is over.

How do you weight requirements?

Start from last month's problems: a lost request or an unbilled hour points to a weight-3 row. Expect trade-offs. One r/msp member with a team under 10 techs said "every PSA on the market seems to have some kind of shortcoming." Weights decide which one you can live with.

Should a small team start with a free helpdesk?

It can, if you work alone or don't bill clients for your time. Score a free plan on the same card as paid ones; the other rows decide. Our guide to free ticketing systems shows what each free plan leaves out.

How do you use the scorecard in a vendor demo?

Send the vendor your weight-3 rows and limits before the call, and ask them to show each one live. Mark what they show as D, what you later run yourself as V, and anything promised as NV. Ask for the plan and monthly total for your headcount in writing.

About the author
Patrick Clements Co-founder & CEO, SherpaDesk

Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.

Published Nov 8, 2018 by

Run a help desk your clients can set their watch by

Tickets, SLAs, time tracking and invoicing in one place. Your first agent is free, with no contract.