Body
Table of Contents
Overview
TDX offers three ways to log time: Tickets, Projects, and Workspaces. Choosing the right method keeps individual service work, formal project budgets, and ongoing team operations each reporting accurately, which matters for billing, staffing decisions, and workload visibility.
Track time by matching your daily tasks to the correct category:
- Tickets for ongoing operational support
- Projects for unique initiatives with defined start and end dates
- Workspaces for general administrative or non-project team collaboration
| Method |
Tickets |
Projects |
Workspaces |
| Focus Area |
Operations & Support |
PPM Initiatives |
General & Admin |
| Purpose |
Use for recurring operational events, incidents, service requests, and routine maintenance |
Use for unique, non-recurring work with a definite start and end date, specific outcomes, or formal project tiers |
Use for general operational categories, administrative overhead, team meetings not tied to a specific project, or time off |
| Guidance |
Log hours directly against the specific ticket when handling day-to-day user support or expected business activities |
Log time against specific project tasks or issues using the TDX interface or your timecard |
Log general availability, overhead, or time-off types directly through your workspace schedule and My Timecard features |
| Constraint |
Time off (PTO) cannot be tracked on individual tickets |
Requires you to be assigned as a project resource or member |
Workspaces must have active time types enabled by an administrator. |
Purpose: Ticket time tracking captures effort spent resolving a specific, individually submitted service request or incident. Use for recurring operational events, incidents, service requests, and routine maintenance.
Guidance: Use the Ticket method whenever your work is tied to a discrete ticket number. When entering time, search for or enter the Ticket ID so the hours attach to the correct record.
Best Practices:
- Log ticket time the same day the work happens rather than batching it later.
- Keep entries scoped to a single ticket rather than combining several requests into one entry.
- Add a brief description of the work performed so anyone reviewing the ticket later understands what was done.
Purpose: Project time tracking is meant for formally scoped initiatives that have a defined timeline, budget, and project manager or sponsor overseeing them. Use for unique, non-recurring work with a definite start and end date, specific outcomes, or formal project tiers.
Guidance: Select the specific project (and task or phase, if applicable) rather than a general workspace. Choose a time type that reflects the kind of work performed, such as planning, development, or testing, since project managers rely on this breakdown for cost and progress reporting.
Best Practices:
- Log time against the task the approved project plan assigns it to.
- Enter time by the end of each day, or at least weekly, so project costs stay current.
- Avoid charging routine, non-project work to a project, since that distorts budget tracking.
Purpose: Workspace time tracking covers ongoing, non-project operational work that doesn't belong to a single ticket or a formally scoped project, such as recurring administrative duties, team meetings, or general maintenance responsibilities. Use for general operational categories, administrative overhead, team meetings not tied to a specific project, or time off.
Guidance: Choose the workspace that represents your team or function, and use it for steady, recurring work that doesn't have its own ticket or project.
Best Practices:
- Use the workspace categories your team has agreed on consistently so reporting stays comparable across people.
- Avoid using a workspace entry as a catch-all for work that should really be logged to a specific ticket or project, since that hides where time is actually going.
- Log time in hours.
- Enter time promptly rather than trying to reconstruct a week from memory.
- Keep descriptions brief but specific.