How did the period go?
Planned and recorded hours for the whole period, month by month, with the main totals at a glance.
What an AI tool can do with PlanningPME and PlanningConnect data, and why it all depends on the data
An AI tool can build charts, comparisons and answers from your scheduling data and recorded hours in minutes, even if you are not an analyst. But it can only tell you something useful if the data is precise and specific. Try the demo to see both sides.
An interactive dashboard built on example data extracted through the PlanningPME and PlanningConnect reports: planned hours compared with recorded hours, analysed from different perspectives.
The demo works on a computer or a phone. People and clients are shown as codes, and the category labels inside the demo are in Italian.
Today almost anyone can ask an AI tool to turn a spreadsheet into charts, compare two periods or find where something went wrong, with no formulas and no programming. The analysis that once needed an expert is now within reach of the person who runs the scheduling.
The hard part is no longer the analysis. It is what the AI has to analyse. A tool that does not know who did what, for which client and on which day can only give you general advice or a confident guess. The more specific the data, the more useful the answer.
For more on what AI tools change in a company, and what they do not, read AI tools in your company.
In the demo, one set of precise data answers six different questions.
Planned and recorded hours for the whole period, month by month, with the main totals at a glance.
Planned against recorded hours for each person, to see who ran over the plan and who stayed under it.
The same comparison for each client and for each type of activity, such as billable work, warranty or maintenance contracts.
Planned work against the weekly capacity of each person, with absences already taken out.
Holidays, sick leave, permits and other absences, shown separately from the working hours.
The gaps between planned and recorded hours, flagged as in line when the difference is small.
Every analysis in the demo is possible because each hour is tied to a person, a client, an activity and a day.
Each event says who, for which client, which activity and which day. Without that detail, a question such as which client takes more time than planned has no answer.
The plan alone shows intentions, and the recorded hours alone show results. Only the two together, with absences, show where they differ and why.
The same client, the same category and the same person must always appear in the same way. If a name is written three ways, the AI counts three different clients.
Hours noted by the person doing the work, when it happens, are more reliable than hours typed in at the end of the month from memory.
Two sources, collected as the work is done and not rebuilt afterwards.
Every task assigned to a person on the shared calendar is a planned event, with its client, activity and hours. Read more about PlanningPME.
People record their work with the app, and the Timesheets and travel costs module produces a monthly export of the hours worked.
An AI tool reads the two sets of data and builds the analyses you ask for. See the monthly timesheet report for an example of the recorded data.
Good data comes with clear rules. These are the ones behind the demo, so you can verify any figure.
The hours of the task events in the PlanningPME export.
The labour hours in the monthly PlanningConnect files.
Only months that have recorded hours are compared. In the demo these are June to September 2026.
8 hours for each day from Monday to Friday, minus the person’s absences. Context events are left out.
Holidays, sick leave, permits, medical visits, recovery time and generic absences. Public holidays are shown apart and are not part of the total. Absences come from the plan, not from the recorded hours.
A gap counts as in line when the recorded hours are within 25% of the planned hours.
An AI tool does not know your business and does not decide for you. It can read the data, calculate and present it clearly. It cannot recover an hour that was never recorded, and it cannot tell whether a gap between plan and reality is a mistake in the estimate or a good reason. That judgement stays with the person who plans.
This is why the order matters: first reliable data collected at the source, then analysis. Read how the pieces fit together in job and time management. Where a shift started is one more detail you can record at the source: see GPS clock-in by industry.
What they change, what they do not, and where to start.
Read the guide →A monthly report of hours, travel and expenses by technician, client and job order.
See the report →Where a spreadsheet is enough, and where you need scheduling software.
Read the guide →Short answers about the data and the analysis.