PRODUCT

Capture the work your systems miss.

CountPilot gives recurring, easy-to-overlook activity a fast way into your data without turning documentation into another job.

Evaluate free for 30 days See the interface

QUESTIONS OPERATIONS TEAMS KEEP ASKING

Where does the day go when the work never reaches a system?

How many walk-up user requests do we actually handle?

How much effort goes into equipment handovers and returns?

Which recurring activities are growing week by week?

Do we need more capacity, or do we first need better evidence?

CountPilot does not pretend to make the decision for you. It provides a transparent baseline for spotting patterns, challenging assumptions and planning with better evidence.

One interaction. One entry.

Large controls scale to fill the available screen. Common activities stay within immediate reach, so logging the work does not become a second workflow.

Designed for Full HD touchscreens
Mouse and keyboard operation supported
Visible queue for rapid entries
Unique event IDs prevent duplicate entries

CountPilot touch interface with configurable service activities

Submenus where detail matters.

A frequent activity can be recorded directly. Where a distinction is needed, CountPilot opens a submenu. This keeps the main screen calm while supporting more complex workflows.

Example: laptop handover for installation, repair or secure erasure.

CountPilot submenu with three follow-up actions

Configure without changing code.

German and English labels, icon, colour, category, standard time, order and submenu can be edited in the PIN-protected administration area.

New activities can be added and obsolete ones archived. Field IDs and historical reporting remain intact. Configurations can be exported and imported.

General and optional Employee mode.

General mode records entries without employee attribution. Employee mode first presents a neutral name selection and then the familiar activity screen. After the entry, CountPilot returns to employee selection.

Technicians can have individual, effective-dated working-hour profiles that contribute to capacity figures.

Switching between general capture and employee mode

Two reporting levels.

Aggregated

Daily and weekly values, comparison, capacity and data completeness. Employee data, event times, activity types and peak times are excluded server-side.

Privacy-reduced daily and weekly figures

Detailed

Activity types, hourly distribution, weekday-hour grid and optional employee differentiation for justified operational analysis.

Daily rollovers, weekly reports and exports.

Before the automatic reset, CountPilot stores the completed daily total in the daily archive. After Sunday closes, a weekly report covers Monday through Sunday, with calendar week and year in the filename.

The complete activity log can be exported as CSV. Historical and current values remain available together.

events.csvtagesarchiv.csvWeekly_Report_CW_XX_2026.csvstate.json

EXAMPLE DATA · FULLY SYNTHETIC

What you can see after one week.

This example shows how scattered, easy-to-miss work can become one shared operational baseline.

Example data

143general user enquiries

37equipment handovers and returns

26access and password requests

18unplanned support callouts

Estimated workload67.5 hrsbased on configured standard times

Mon48

Tue42

Wed39

Thu52

Fri43

The insight you gain depends on your configuration, assigned standard times and the completeness of your activity capture.

Resource planning with clear limits.

Standard times, active or opening days, working-hour profiles, technician numbers and target utilisation provide a transparent planning basis. Previous-week comparison, a rolling four-week average and data completeness support interpretation.

Reconstructed historical daily values are labelled as using the current standard time where no original event time exists.