Time and reporting
Daily Status Reports: hours against a project and an issue
What a DSR captures
Project and issue, not just a description
Each entry names the project and the specific issue it belongs to, so hours land on real work rather than on a free-text category nobody can report on.
Hours, status and a description
Say how long it took, where the issue stands now, and what actually happened — in the person's own words.
Several entries per day, with a running total
Most days split across more than one project. Add an entry per project, and the day totals up for you.
Preview before it goes out
See the submission as its recipients will, then send. Nothing is emailed until you have looked at it.
Extra recipients per submission
Your reporting manager receives it by default; add anyone else who needs today's picture on this particular day.
Manager view and Missing DSRs
Managers read submitted reports across their people, and a separate Missing DSRs report shows exactly who has not filed and for which dates.
Optional enforcement
Turn on Pending DSR Lock Enforcement and anyone with a missing report is held on the DSR screen until they file it, with admin accounts exempt. It is a company setting, so the level of enforcement is yours to choose.
An email people can turn off
Every user chooses in Notification Settings whether they receive DSR emails, so the ones who read them keep getting them and the rest are not trained to ignore their inbox.
Why the issue reference matters more than the hours
Plenty of timesheets ask for a project and a number. That is enough to invoice, and not enough to learn anything. When hours are attached to a specific issue, you can compare what a story was expected to take against what it took, see which epic absorbed a sprint, and tell rework from new work.
It also means nobody has to reconstruct the week on a Friday afternoon. The issue is right there in the picker, because it is the issue they were working on.
Chasing reports is a report, not a personality trait
Missing DSRs lists the people and the dates. That turns a daily nag into a five-second check, and it makes the gap visible before month end rather than during it.
Where the discipline needs to be structural rather than social, Pending DSR Lock Enforcement holds a person on the reporting screen until their report is filed. It is a switch each company sets for itself, so you choose the level of enforcement that suits your organisation.
- Missing DSRs report, by person and by date
- Optional navigation lock, enabled per company
- Admin and super-admin accounts exempt from the lock
What the hours become
Hours Per Project answers where a month went. Effort Allocation shows the split across projects for a person or a team. The Employee DSRs view reads the narrative rather than the numbers — useful in a one-to-one, and useful when a client asks what happened in week three.
Because projects also carry client hours, internal hours and a monthly estimate, the comparison between what was budgeted and what was logged is a report rather than a spreadsheet exercise.
Time and reporting: common questions
Can someone log time to more than one project in a day?
Is submitting a DSR mandatory?
Who receives the DSR email?
Related
Reports and analytics
Hours per project and effort allocation, built from DSR entries
Project management
The issues a DSR entry points at
Daily status reports people actually submit
What makes a reporting habit stick, and what kills it
Or go back to all features.
Try it against your own work
A workspace takes a couple of minutes to create. Put one real project in it and see whether this shape matches how your team already works.