case study · facility & asset management

All of the network's equipment and faults, across every branch, in one place.

We built a fully Hebrew system for managing equipment, faults and maintenance across a multi-branch clinic network. Instead of an Excel file per branch and a WhatsApp group with the technician, the whole network gets a live picture of every piece of equipment, every fault and every maintenance reminder - across all branches, in real time.

Industry · clinic network Technology · Web App Project · 2026

overview

The story behind the project.

A clinic network maintains dozens of critical equipment items at each branch - devices, consumables and treatment gear. When every branch runs its own Excel file and coordinates repairs over WhatsApp with the technician, no one really knows what is working, what is missing and who already handled what.

Management wanted one place, in Hebrew, that brings together all the equipment, faults and maintenance across every branch - with role-based permissions, so each branch manager sees only what is relevant to them.

the solution

What we built.

A fully Hebrew system for a clinic network - equipment inventory, faults, maintenance, suppliers and reports on one screen that all branches see at the same time.

Equipment inventory by branch

Inventory management by branch, category and SKU, with minimum-level alerts and one-click PDF export.

Tickets and faults

Open a ticket by type and severity, and track its status from "open" all the way to "completed" - with a response time for each fault type.

Maintenance and calibration reminders

Automatic reminders for calibration, periodic checks and parts ordering - before it turns into an urgent fault.

Branches and technicians

A card for every branch and every technician, with equipment scope, shift and role-based access permissions.

Suppliers and spare parts

Supplier details and lead time for every part, so you know exactly how long it will take to restock a missing item.

Reports and PDF export

A ticket report and an inventory status report by date range, with PDF export for saving and sharing.

the system

Here is how it looks in practice.

Real screenshots from the system we built - the network dashboard, equipment inventory and ticket management, all in full right-to-left Hebrew.

clinictrack.app/dashboard
Screenshot of the equipment management dashboard for a clinic network - ticket volume, maintenance reminders and faults
Network dashboardTicket volume, maintenance reminders and faults from every branch - one live picture that opens each morning.
clinictrack.app/inventory
Screenshot of the equipment inventory screen - status working, in repair or missing, quantity vs. minimum, category and branch
Equipment inventory for every branchEach item with a status of working, in repair or missing, quantity vs. minimum, category and branch - and one-click PDF export.
clinictrack.app/tickets
Screenshot of the tickets and faults screen - type, severity, branch and reporter for each ticket
Tickets and faultsEvery ticket with type, severity, branch and reporter, sorted by urgency - from opening at the branch through to closing.

results

The result: one order across the whole network.

Instead of an Excel file per branch and WhatsApp with the technician - one live picture, with faults that never slip through the cracks.

Fewer surprise faults

Calibration reminders and minimum-stock alerts prevent faults before they stop treatment at a branch.

One picture for the whole network

All the equipment, faults and maintenance across every branch on one screen, in real time.

Zero Excel sheets

Instead of a file per branch - a single source of truth, with role-based permissions.

our approach

How we built the system

We sit with management and with the branch teams, understand how equipment and faults are really handled on the ground, and build a simple system they will want to use every day.

  1. 1

    Deep specification

    We sit with the team and map the real flow of information - who does what, when, and where things get stuck.

  2. 2

    Spotting the bottlenecks

    We pinpoint exactly where errors, duplication and delays occur - that is where the biggest value is.

  3. 3

    Custom development

    We build the system around your process, module after module, with testing every step of the way.

  4. 4

    Rollout and support

    We go live, train the team, and stay available after launch for ongoing improvement and expansion.