Compare manual and digital assessments by the full cost of each usable result that reaches the responsible clinician on time. Count every step in both workflows, from preparation through clinician review, including missing forms, corrections, support, security work, and data retrieval. Use your own volume and labor data, because generic platform savings are not a business case.
What unit should you cost?
Cost per form is usually the wrong unit. A printed sheet may be inexpensive while the completed workflow is not, and a software delivery may be automatic while clinician review still takes time. Use a unit such as the cost per usable assessment reviewed by the responsible clinician within the defined time.
Define "usable" before you measure it. A usable result belongs to the correct patient and episode and uses the intended questionnaire version. It meets the completeness rule, scores correctly, and is available where the clinician expects it. Apply the same unit to the same named measure, such as the PHQ-9 or GAD-7, in both workflows. Mixing questionnaires with different scoring and review requirements hides real work.
Where does the time go in each workflow?
Map the manual and digital paths from start to finish, and observe both under normal operating conditions. Answer these questions for each stage:
| Stage | Manual questions | Digital questions |
|---|---|---|
| Preparation | Who selects, prints, labels, and stocks the form? | Who configures the measure, schedule, and recipient? |
| Delivery | How is the form handed out or sent? | Which channel is used, and what happens after failure? |
| Completion | Who checks missing answers and patient identity? | What validation and matching occur before submission? |
| Scoring | Who calculates and verifies the result? | Which definition and version produced the score? |
| Review | How does the clinician find the result? | What queue or view shows that review is due? |
| Documentation | Where are the score, context, and interpretation recorded? | Which fields transfer, and which still need clinical entry? |
| Retrieval | How are earlier results found for comparison? | Can users trace the source and scoring history? |
| Exceptions | How are lost, late, incomplete, or duplicate forms handled? | How are failed messages, support needs, and mismatches handled? |
Do not compare a complete paper workflow with only the digital delivery step, and keep clinician review in both models. For each stage, count eligible assessments, delivery attempts, usable completions, and on-time clinician reviews. Record staff, clinician, rework, and support minutes, and the loaded labor cost for each role. Use observation or timestamped workflow data where possible, because estimates from a sales demonstration usually omit interruptions, exceptions, and follow-up.
What do manual and digital workflows really cost?
A manual workflow costs more than paper and ink. Staff control form versions and replace outdated copies, store and retrieve completed forms, and hand-score and verify each total. Duplicate entry into another record, missing pages, and unmatched forms all add staff time. So do secure transport and disposal, and preparing paper data for trends or aggregate reports.
A digital workflow costs more than the subscription. Count initial configuration and questionnaire validation, user setup, role design, access review, staff training, and workflow redesign. Add interface development and maintenance, support for failed deliveries and for patients who need help, and vendor management and incident coordination. Then include data export, migration, contract termination, downtime procedures, and recovery testing.
Privacy and security work is part of the digital cost as well. A vendor that creates, receives, maintains, or transmits electronic protected health information for a regulated practice may be a business associate. HHS cloud guidance says the parties need an appropriate business associate agreement and their own risk analysis. It also lists availability, backup and recovery, return of data, security responsibility, and use, retention, and disclosure limits as contract concerns.
A signed agreement is not a complete security evaluation. Budget staff time for due diligence, access design, vendor review, incident procedures, and periodic reassessment. Add the cost of exporting or returning data if the relationship ends. The platform selection guide turns those concerns into evaluation questions. Include only the costs that occur in your setting: these categories are prompts, not a national estimate.
How do you calculate the full cost?
Add every cost for the same period, then divide by usable, on-time reviews rather than by deliveries. A reproducible calculation can stay simple:
> Workflow cost = labor + materials + software + implementation + integration + support + security and compliance work + exit and transition cost
For labor, multiply time by the practice's chosen loaded rate. Separate fixed costs, such as configuration, contract review, security review, integration, training, and data migration, from variable ones. Variable costs may include user fees, messages, assessments, support, storage, and staff time. For shared fixed costs, state the period and volume used to allocate them, and show every input so another person can recalculate the result.
Dividing by deliveries understates the cost per usable result whenever some deliveries never become usable, on-time reviews. For example, with invented figures, a workflow costing $3,000 a month that sends 600 assessments works out at $5 per delivery. If only 400 come back usable and reviewed on time, the cost per usable review is $7.50. A lower subscription price does not help if fewer results reach the clinician when needed. The business-case guide explains how to turn the comparison into a decision without counting time, capacity, and revenue twice.
What must stay fixed whatever the cost?
Keep clinical, safety, and security requirements fixed, and compare cost only between workflows that meet them. Automatic scoring can remove arithmetic from the workflow, but the practice must verify the scoring definition and preserve version history. A trend display can improve access to earlier results without showing why a score changed. A reminder can increase delivery attempts, but it does not establish completion or clinical review.
Treat item-level safety routing as a required clinical control, not a benefit to trade against cost. The lower-cost workflow is unacceptable if it delays the responsible clinician or loses information needed for review. The APA's measurement-based care guidelines place collection inside a larger clinical process. That process runs from choosing measures to reviewing results with patients and using them in treatment planning. Cost that whole process, not only the collection step.
How do you run the pilot and decide?
Capture a baseline before changing the workflow. Then pilot the digital path with a representative service line, including failed delivery, noncompletion, corrections, support, review delays, and staff workarounds. Compare cost per usable completion and cost per on-time clinical review across the two workflows. Also compare completion and review coverage, rework and exception time, and staff and patient support needs. Data quality, source traceability, downtime, and export performance belong in the comparison too.
Cost is one constraint, not the only outcome. A practice might accept a higher direct cost for better on-time review, stronger source traceability, or a required contract export. Write that decision rule down before the pilot starts, then judge the results against it.