Using AcmeTime — entering an hour block
What you'll learn
- Tool: time.acme.local — SSO via Google.
- Required: date, hours (0.25 step), project code (AC- or OP-), one-line outcome.
- Outcome-style descriptions beat activity-style descriptions.
All hours go through AcmeTime (internal: time.acme.local). Each entry has four required fields: date, hours (in 0.25 increments), project code, and a one-line description of what you did. SSO sign-in via your Acme Google account; no separate password.
Project codes follow the format AC-XXXX (engineering) or OP-XXXX (operations). If you don't know your project code, ask your manager rather than guessing — wrong codes route the hours to the wrong cost centre and the entry has to be reversed by Finance.
The one-line description is read by your manager weekly; it is not just for your records. Write the outcome ("shipped login bug fix") not the activity ("worked on auth"). Outcome-style descriptions cut clarification messages roughly in half.
Key points
- Tool: time.acme.local — SSO via Google.
- Required: date, hours (0.25 step), project code (AC- or OP-), one-line outcome.
- Outcome-style descriptions beat activity-style descriptions.
Examples
"AC-1042 — shipped fix for /login 500 errors; rolled out to prod 16:00."
"AC-1042 — worked on bugs." Manager has to ask: which bug, did it ship, when?
Pitfalls
- Guessing the project code. Wrong cost-centre means Finance reverses + re-enters the row, slow.
- Activity-only descriptions. They drive the weekly clarification ping that wastes 20+ minutes.
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.