Understanding Description Quality Indicators
What the quality indicator means and how to write descriptions that meet audit standards.
The Quality Indicator
When you write a description for a time entry, a quality indicator appears showing one of three levels: "Too short", "Acceptable", or "Good". This helps you gauge whether your description provides enough detail for compliance purposes.
Too Short
Descriptions flagged as too short lack the detail auditors expect. Entries like "worked on project" or "meetings" will not survive an audit review. Aim for at least a sentence explaining what specific activities were performed.
Acceptable
Acceptable descriptions provide enough context to understand the work, but could benefit from more detail. For routine tasks, this level is usually sufficient.
Good
Good descriptions clearly explain what was done, why it was done, and what the outcome was. These entries are audit-ready and contribute to high-quality AI-generated reports.
Tips for Better Descriptions
- Be specific: "Implemented caching layer for API responses" instead of "development work".
- Include the purpose: "Analyzed performance bottleneck in data pipeline to reduce processing time".
- Mention outcomes when relevant: "Fixed authentication bug that prevented login for SSO users".