The iTimekeep December 2025 release contains a new feature, improvements, and fixes for iTimekeep.

New Features

Bulk Submit Duplicate Detection

When submitting batches of time entries, iTimekeep can present a Possible Duplicate Entry save error during time submission when potential duplicate time entries are detected. When the Possible Duplicate Entry error displays, the system automatically refreshes the time entries for the affected day.

For the Possible Duplicate Entry save error to display, a time entry must be identical to another in the following criteria:

• Work date
• Matter
• Work hours
• Work description

  Note: Work description detection is not case sensitive.

• Selection codes

If duplicate time entries are intentional, they should be modified to either reconcile them into a single entry, or update the narrative field with additional detail to distinguish records.

Improvements

General application performance has been improved.

Fixes

• Issues with logging in where the system was unable to fetch subscriptions for the account.
• Sorting by Client Code caused iTimekeep to display a blank screen.
• The dashboard displayed data tied to the wrong time period.
• Inconsistency with saving updates to, or creating, pinned timers.
• Clicking a day on the previous month’s calendar in the Time Entry view triggered a page refresh.
• Timecards would open to Week 1, even when Week 2 should display by default.
• The weekly calendar would default to the previous week, instead of the current period.
• The calendar would load twice.
• Phase Code details would not display because the Client Code did not populate.
• Opening a day on the calendar, and then switching to the Dashboard caused the previously-selected day to persist.