Recurring time entries: describe the Tuesday stand-up once, then pick the Tuesdays it actually happened. The summary tells you what will be written and which days are being left out, and why.
The stand-up is a single agreement with the client. Logging it means making the same entry again every week, so on a busy week it simply does not happen.
The weeks that were missed get rebuilt from memory in one lump, on whatever day the calendar still had room.
Repeating an entry blindly books a public holiday, a day of approved leave, or a day you already logged against another project.
A copy carried across a rate change prices every day at the old figure, and nobody notices until the invoice is questioned.
Describe it once, choose the days, read what will happen.
Client, project, what you did, start and end. That one definition is what lands on every date you pick.
Tap the days on the picker, a whole week at a time, or a run of weeks. Your public holidays and your approved leave are already marked on it before you book over them.
Skip weekends, skip public holidays, skip your active leave. Days that already hold an overlapping entry are set aside whether you ask or not.
The panel says how many entries will be created and how many days are being left out, with the reason for each and the task any skipped day collides with.
One button writes every remaining day. Each entry is matched to the client's purchase order on its own and priced at the rate that applies on that date.
One check while you choose, one on the way in.
Every selected date is compared with the entries you already have. The ones that clash are listed with the task they collide with, and left out of the batch.
If a day was booked between the preview and the save, the batch is refused whole and the colliding entries come back named, rather than half of it being written.
The picker marks the regional public holidays of the consultant's location and their approved and pending leave, so a skipped day is never a guess.
A batch that runs past a purchase order change prices each date separately, and every entry it creates keeps its own history.
A batch of entries is still a batch of hours on the client's purchase order, priced per day, see Budget Tracking
Yes. Pick the days on the picker, or copy an existing block to a date range. A standing Tuesday meeting for the whole quarter is a single selection; you get one entry per date, not one long entry.
Yes. Copy that block to a date range, or describe it again in the manual entry and choose the dates. Both produce one entry per date, each with its own dates and its own rate.
They are detected as overlaps, listed with the task they clash with, and left out of the batch. The remaining days are still created.
The picker marks the regional public holidays of the consultant's location and their approved and pending leave, and you choose whether to skip them. Skipped days are counted in the summary.
No. Each date is matched to the client's purchase order on its own and carries the rate that applies that day, so a batch spanning a rate change stays correct.
Organisation owners can create entries in a member's name from the team view, and the picker then uses that member's holidays and leave rather than your own.
Describe the standing meeting, pick the dates it happened, and let the exclusions do the careful part. Free for 30 days.
