nomoretools™

Practice / Hours and work done

Hours and work done

Hours are recorded where they happen, or not at all. Everything in between is memory work on a Friday afternoon.

← All workflowsGo to the interactive example ↓

The starting point

The work
in between.

  1. The weekly sheet is filled in on Friday, from memory.
  2. Which hours belong to which job is estimated. The total is right, the split is not.
  3. Whoever does not hand the sheet in gets chased. That costs more time than filling it in.
  4. The figures end up in the billing and in the cost review. Both are as good as the memory on Friday.

A suitable design

What needs to
work together.

These components describe one possible individual scope. Scope and rules are agreed with your business.

01

Recorded where the work is

On the phone, in two moves, without signing in to a portal. If it takes longer than the paper sheet, it will not be used.

02

Suggestions instead of empty fields

Appointments, material draws and locations produce a suggestion. Agreeing is one tap. Correcting is one tap too.

03

Gaps report themselves the next day

Not at the end of the month, when what actually happened can barely be reconstructed.

An example decision card

Hours are missing for two people for yesterday

By the schedule both were on the same site. A suggestion is prepared but not entered.

The suggestion sits in the list of open questions. It is entered only if the person agrees.

What is the suggestion based on?
  • calendar entry: the same job, all day
  • material drawn against this job on the same day
  • no absence recorded
  • → likely but not certain, so a suggestion
Fictional starting point. You can interact with the following example.

07 · To hand over

The day sheet appears on the day.

Four entries were recorded on the move. Hand the state of the day to the job while the work, the duration and the context are still unambiguous.

Tuesday 11 August · team 2 · 7.5 hours recorded

Four entries are on the day sheet but have not been handed to the job yet.

State and handover

Assign the whole day to job A-2417

What is recorded is the job and the work. No location, no device time.

  1. 01 07:15 to 08:00 · travel outrecorded by the fitter as travel to the treatment room refit recorded locally
  2. 02 08:00 to 12:00 · fittingsubstructure in the plant room recorded locally
  3. 03 13:00 to 15:00 · reworktwo penetrations after a change to the plan recorded locally
  4. 04 15:00 to 15:45 · travel backreturn to the workshop recorded locally

State on the job

0 hrs

The entries stay editable until the day is handed over.

History

The starting position and the check that ran stay distinguishable.

  1. Team 2 · mobile Four blocks of time recorded with a note on the work; 7.5 hours in total.

An illustration. People, job and times are invented. No location data and no device data are collected.


The work stands next to the duration

Seven hours on their own say little. The short note on the work makes the entry understandable later, for the invoice, for a handover and for the cost review.

Handing over is its own step

Corrections are possible until the end of the day. After that every change stays visible, instead of quietly overwriting a sheet already handed in.

The countercheck

Where things
can go wrong.

Time recording tips into surveillance quickly. As soon as location data or device times run alongside, the relationship inside the business changes. Legally this is its own ground, and it belongs settled with the workforce before anything is built. We build the recording so that it describes the job, not the person.

A useful first trial includes this failure case explicitly. Fast processing alone is not success if checking and correction create more work.

Your first stage

Start where
the work improves.

For Hours and work done, we choose a bounded first outcome with your team. Existing specialist systems can stay where they fulfil necessary requirements. We compare time relief, payments that can end and the cost of the new way of working.

The workshop gives you priorities and a roadmap. You can continue internally or with support from Markus Kirchmair. The choice of model and agent follows the task, with data and rules retained outside an individual chat.

Explore the workshop →

Ready for the next change

Keep the work simple.

The first view should show the next relevant decision. Reasoning and sources remain accessible. We leave out unnecessary features and make actual progress visible.

When a rule changes, agents can help investigate the impact, prepare the adjustment and update tests and documentation. A qualified person assesses the result and its adoption.

Try a change →

Your first step

Say yes
to less.

Less unnecessary software. More room for your work. Let’s find the useful first step.