Faster Time works by asking your computer "What are you working on?" and then allocating time to the appropriate client/matter/activity. By default, Faster Time will ask your computer "What are you working on?" every second. This means that, technically speaking, if you can work really quickly and both start and finish something in-between when it asks, it is possible that Faster Time will miss something.
When configuring Faster Time, there is an accuracy setting that you can adjust through the Settings dialog:
Faster Time provides best results when set to 1-second accuracy
This should only be increased if you have an old computer.
Effects of Changing Settings
The accuracy setting controls how frequently Faster Time asks your computer "What are you working on?" On old computers, having Faster Time ask this question every second may slow them down which is why we provide this setting, however, there are some side effects when changing this. When you increase this value, Faster Time will ask less frequently which will increase the chances of it missing what you're working on or recording the time less accurately. Here's an example:
Let's assume you have Faster Time set to check every 60 seconds. It performs a check(T=0), and then five seconds later(T=5), you open up an email, draft something quickly, and then send 5 seconds before it checks again (T=55). In this case, Faster Time will completely miss the fact that you drafted the email because you did it in-between checks.
For another example, similar to the one above, let's assume you have Faster Time set to tick every 60 seconds. You're working on a Word document and it performs a check (T=0), and then 45-seconds later (T=45) , you open up an email, and start drafting something. Then it checks again (T=60) and you send the email 55 seconds later (T=115). Five seconds later (T=120) it checks again. In this case, Faster Time will miss the first 15 seconds of the email (T=45...60) because you started the email before its check. It also won't detect that you've finished the email until its second check (T=120). This means that the email you spent 70-seconds on will be less accurately recorded as 60-seconds.
Let's assume you have Faster Time set to check every 60 seconds. It performs a check(T=0), and then five seconds later(T=5), you open up an email, draft something quickly, and then send 5 seconds before it checks again (T=55). In this case, Faster Time will completely miss the fact that you drafted the email because you did it in-between checks.
For another example, similar to the one above, let's assume you have Faster Time set to tick every 60 seconds. You're working on a Word document and it performs a check (T=0), and then 45-seconds later (T=45) , you open up an email, and start drafting something. Then it checks again (T=60) and you send the email 55 seconds later (T=115). Five seconds later (T=120) it checks again. In this case, Faster Time will miss the first 15 seconds of the email (T=45...60) because you started the email before its check. It also won't detect that you've finished the email until its second check (T=120). This means that the email you spent 70-seconds on will be less accurately recorded as 60-seconds.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article