Reports built from the work, not from memory

What TaskLoop reports measure

TaskLoop reports measure four things: how many tasks get completed, how fast they are responded to and finished, how each staff member performs, and how guests rate the result. Every number comes from timestamps and ratings recorded on real tasks, not from a summary someone fills in at the end of the month.

The workflow, step by step

1. The data is captured as people work

Nobody types report data. When reception registers a request, when a supervisor assigns it, when a technician accepts it on the staff app and when they mark it complete, TaskLoop records the time. That is enough to work out response and completion times for each task.

2. The guest adds the rating

For guest requests, the guest rates the service after completion. That rating stays with the task, so you can see a fast but poorly rated delivery, or a slow but well rated one.

3. Managers review the reports

The general manager, building manager or department head opens the reports to see:

• Task completion rate. How many tasks are closed compared with how many are opened.
• Response time. How long it takes from request to someone taking ownership.
• Completion time. How long it takes from request to done.
• Staff performance. Completion and timing for each person.
• Guest ratings. How guests scored the service.

4. Act on what they show

Reports are only useful if they change something. Common actions include moving one attendant to the late-morning check-out peak, giving a new technician a shadow shift, tightening deadlines on a category guests keep rating low, or simply recognising the person whose tasks are always closed on time with good ratings.

Who uses it

What the screen shows

The reports present completion rates, response and completion times, staff performance and guest ratings over the period you choose. The live admin dashboard covers right now, meaning open tasks and department workload. The reports cover how things went over time. Together they answer two separate questions: what needs attention this hour, and what needs to change this month.

Measuring your own baseline

TaskLoop does not quote claims such as “X% faster” because your result depends on where you start. A more honest approach is to record your first weeks on TaskLoop as a baseline and then compare. Our article on cutting guest request response time explains which numbers to watch first.

Reading the numbers fairly

Operational numbers are easy to misread, so a few rules help keep reviews useful.

• Compare like with like. A room-move request and a chiller fault should not share one average. Look at similar tasks together.
• Look at trends, not single days. A long completion time on one busy check-out morning says little. The same pattern three weeks running says a lot.
• Read speed and ratings together. A team that closes tasks quickly but gets low ratings may be rushing. A slower team with high ratings may be doing the job properly.
• Check how deadlines were set. If deadlines are unrealistic, the late-task count reflects the planning, not the staff.
• Use staff performance to coach. The people whose numbers stand out, in either direction, are the first conversation to have, not the first person to blame.

A short weekly review with department heads, covering five minutes on completion rate, response time and the lowest-rated tasks, is usually enough to keep the numbers driving decisions.

Export and SLA targets

• Export. Reports export to PDF and CSV.
• SLA targets per category. Response and resolution timers are configurable per category and priority, and reports show response and completion times against them.

What it doesn’t do

• BI tool connections. There is no API for feeding report data into other systems.
• Financial reporting. TaskLoop reports on operational work, not revenue or costs. Those stay in your PMS or accounting system.