20 Minutes Per Case. Down to 1.

The situation

Timpview was still running on paper preference cards. Case costing lived in Excel. To put a complete cost together for a single case, the team had to pull information from multiple places: the EHR, ENVI, the paper preference cards, and the spreadsheet. Roughly five different people were involved in that loop. It took about 20 minutes per case just to make sure everything was accounted for.

That process added up every single day. On top of the daily work, leadership was constantly asking for month-end reports, quarterly reports, and ad-hoc views. The same manual effort had to be repeated at scale. Circulators in the OR were still working from paper. Preference cards drifted. Actual usage was hard to track cleanly. Staying on top of cases felt like a constant chase.

What Finch delivered

Finch came in as a lightweight layer on top of what Timpview already had. No rip-and-replace. Preference cards moved from paper to digital. Case costing stopped living in a separate spreadsheet. The same work that used to take about 20 minutes and multiple people dropped to roughly a minute per case.

• Digital preference cards

  Cards circulators could actually use in the OR

• Actual usage tracking

  Planned vs. used, without paper drift

• Automated case costing

  No more jumping between EHR, ENVI, paper, and Excel

• One place for cases

  Stay on top of cases instead of assembling reports by hand

• Month-end and quarterly views

  Without the multi-person scavenger hunt

No training required. It just made sense.

A lot of software asks teams to learn a new system on top of everything else they already do. That is exactly the friction Finch is built to remove. At Timpview, the team did not need a formal training program to figure out how to build reports or find what they needed. Finch was intuitive, easy to navigate, and structured around how an ASC actually works. When questions came up, support was there. The center did not have to dig into another platform or spend weeks getting comfortable before the value showed up.

That matters because the alternative is familiar: wishing for deeper integration with systems the team barely uses, or feeling like they need to learn more about other operational systems just to answer basic questions. Finch sits on top of the data the center already has and presents it in a way that is built for the people running the facility, not for the people who built the EHR.

What changed in the OR

Digitizing the preference cards was not just a back-office win. Circulators finally had cards they could work from without paper. The process of knowing what was planned versus what was actually used became straightforward. Staying current on cases stopped requiring constant back-and-forth across systems and spreadsheets.

Because Finch sat on top of the existing stack, the clinical and materials teams did not have to abandon the tools they already used. They just stopped having to assemble the picture by hand every time.

Why this matters

A lot of ASCs are still living in the gap between paper preference cards and modern case costing. The workarounds (Excel, multiple systems, and a rotating cast of people who know how to pull the pieces together) function until they don't. Every case costs staff time. Every month-end request restarts the same manual process. And every new system the team is asked to learn adds more friction instead of removing it.

Timpview's experience shows what happens when preference cards become digital, case costing stops living in a separate spreadsheet, and the interface does not require a training curriculum: the time per case collapses, the OR team gets tools they can actually use, and leadership can stay current without turning every reporting request into a multi-person project.

Key findings

• Paper cards + Excel is a tax on every case

  When five people and four systems are required to cost one case, the minutes add up fast.

• Digitizing preference cards helps the OR, not just the office

  Circulators get usable cards; actual usage becomes trackable.

• You should not have to learn another system to get answers

  Finch is built to be intuitive for the people running the center, with support when needed — not a new platform to master.

• Lightweight beats rip-and-replace

  Finch worked on top of the existing stack so the center did not have to abandon what already worked.