What this resource establishes
This page explains how Halyard structures implementation evidence. It contains a worked measurement example and a template for evaluating results. These are methods and illustrative material, not a published client case study, testimonial or claim of achieved savings.
A useful evidence library grows from approved delivery records. Public client results require a verified baseline, a comparable observation period, documented limitations and permission to publish. Until that evidence is available, it should not be replaced with anonymous success claims.
Capture the starting workflow before changing it
Record the task boundary, participating roles, source systems, frequency and types of cases included. Observe preparation, review, correction and handoff effort separately, and record elapsed turnaround where it matters.
Describe what the current process does well and which controls must remain. Record the sampling period and unusual conditions. A baseline taken during an exceptional week may be a poor comparison for normal operations.
Worked example: measure the whole reporting task
Consider an illustrative reporting workflow. The task begins when approved source material is available and ends when an authorized person has reviewed the package for release. Preparation includes gathering documents and drafting the package. Review includes checking sources, correcting errors and confirming the release boundary.
Compare total staff effort using preparation time plus review time plus correction and handoff time for equivalent cases. Faster drafting can coexist with higher review effort. Report the combined result and the separate components so the reader can see the tradeoff.
Keep financial values and approved recipients authoritative. Include missing attachments, superseded records and absent reviewers in the test set. This example describes a test design; it reports no completed test or client outcome.
Retain evidence of the controls
For each important requirement, keep the test case, expected behavior, observed result, reviewer and resolution of failures. Include unauthorized access attempts, missing sources, conflicting records, incorrect output and fallback operation.
An overall pass percentage can conceal a serious failure. Report unresolved critical issues individually and explain what they prevent the workflow from doing. A demonstration with fictional material supports understanding of the interaction, not a conclusion about production reliability.
Separate capacity, cash savings and service improvement
Time released may create capacity for existing staff without reducing payroll. A shorter turnaround may improve service without generating additional revenue during the observation period. Keep those outcomes distinct.
To estimate released capacity, multiply a measured per-case effort change by a justified volume over a stated period, then account for monitoring and maintenance. Label estimates and assumptions. Do not present projected capacity as realized profit.
What a publishable case study should contain
A case study should state the initial problem, scope, baseline, changed workflow, controls, testing method, measurement period, adoption and observed result. Include the sample size, exclusions, other changes that could affect the result and known limitations.
Identify the client's approval for the exact wording, figures, quotes and assets. Team members' prior experience must be attributed accurately rather than presented as Halyard delivery. Reviews should come from real experience and remain voluntary.
Use the linked buying guides to ask an implementation provider for this evidence before treating a headline outcome as proof that the same approach will suit your firm.