If something in timeSensor LEGAL 365 does not work as expected, we want to fix it for you as quickly as possible. How fast this happens depends heavily on how well your malfunction report is documented.

A message like "timeSensor is not working properly today" unfortunately forces us to ask follow-up questions before we can even start the analysis. This costs valuable time – yours and ours. The more precisely you describe the problem, the faster we find and fix the cause.

Why good documentation is in your interest

• Faster solution: We can start the analysis immediately instead of asking first.
• Fewer interruptions for you: No multiple follow-up questions that disrupt your daily work.
• Higher hit rate: Many malfunctions can only be reproduced if we know the exact circumstances.
• Traceability: Even with sporadic problems, a good description helps us recognize patterns.

Checklist: What belongs in every malfunction report

1. What exactly happened?
Describe the problem concretely – not "doesn't work," but what does not work (e.g., "When saving a case, the error message according to the attached screenshot appears").

2. What did you do before the error occurred?
The individual steps leading to the error (e.g., "Case opened → Document created → clicked Save"). This allows us to reproduce the problem.

3. Was haben Sie erwartet – und was ist stattdessen passiert?
Der Soll-/Ist-Vergleich hilft uns, das eigentliche Problem einzugrenzen.

4. The exact error message
Please provide the exact wording – preferably as a screenshot of the entire screen (including error number, if available). A screenshot often says more than a description.

5. When does the error occur?
Always? Only sometimes? Since when? Only since a certain time or update?

6. Who is affected?
Only you at one workstation, several people, or the entire entity? This greatly narrows down the cause.

These technical details help us additionally

• Operating System: Windows or macOS – and the version (e.g., Windows 11, macOS 15 Sequoia).
• Affected workstation / user: On which device or under which login does the problem occur?
• Time of occurrence: The approximate time helps us find the right spot in the server logs.

An example

❌ Insufficient:

"timeSensor is not working properly today – can you fix it?"

✅ Helpful:

"Since this morning (around 9:30 AM), I can no longer save documents at my workstation. When clicking on Save, the error message in the annex (screenshot) appears. My colleague at the next workstation has the same problem, but a third workstation works normally. The problem seems to occur only under macOS Sequoia. Everything was working fine yesterday."

With the second report, we can usually immediately start the analysis.

In brief

The more specific your report, the faster the solution. Take two minutes for a clear description – it will pay off for you many times over. Thank you very much for your cooperation!