Overtime, time-off, and edge cases
What you'll learn
Special days have their own codes; log honestly, don't double-count.
- Standard week = 40h. Over 45h triggers a manager flag — log honestly anyway.
- Time-off codes: HOLIDAY-AC, PTO-AC, SICK-AC. No project code needed.
- On-call: one 24h block + separate paged-work entries — never double-count.
Acme's standard week is 40 hours. Anything over 45 in a week is flagged for your manager — not because you're in trouble, but because sustained overtime is a process-failure signal the team needs to investigate. Log the hours honestly; do not under-report to avoid the flag.
Public holidays go under the HOLIDAY-AC code at your normal daily hours. Personal time off (PTO) uses the PTO-AC code; sick leave uses SICK-AC. None of these need a project code — the time-off codes substitute for one.
On-call rotations: log the on-call block as a single 24-hour entry per shift with code ONCALL-AC, then log any actual paged work as separate hourly entries against the relevant project code. Don't double-count.
Travel: travel time during the business day counts. Travel outside business hours (your morning commute, a 22:00 flight) does not. Travel that overlaps both — log the in-hours portion only.
Key points
- Standard week = 40h. Over 45h triggers a manager flag — log honestly anyway.
- Time-off codes: HOLIDAY-AC, PTO-AC, SICK-AC. No project code needed.
- On-call: one 24h block + separate paged-work entries — never double-count.
- Travel: only the portion overlapping business hours is logged.
Pitfalls
- Under-reporting overtime to avoid the >45h flag. Defeats the process-improvement signal.
- Double-counting on-call shift hours and paged-work hours.
- Logging full out-of-hours travel time.
Ask the L&D team
Stuck on the workflow? In a real Adept deployment this routes to your company's L&D Claude project; in the demo it opens a fresh Claude chat.