Attendance
- The question
- When was someone present?
- Useful context
- Attendance event and schedule
- The boundary
- Presence does not establish completed work.
DRYVN TIME & WORK
Time tracking that connects hours to the work behind them.
A total of eight hours tells you how much time was recorded. It takes an assignment, an activity and a review decision to explain the work behind it. Dryvn connects timesheets to assigned work and team-defined output measures, without treating every quantity as the same kind of result.
Example working dayApproved · illustrative
| Assignment / activity | Hours | Reported output |
|---|---|---|
| Service guide localization | 5.5 | 1,200 words |
| Customer support cases | 2 | 8 cases |
| Internal coordination | 0.5 | No output measure |
Total recorded time8 hours
Words and cases describe different work. They are not added into a combined output total.
An illustrative approved timesheet records 5.5 hours of localization with 1,200 words, 2 hours of support with 8 cases, and 0.5 hours of internal work. The hours total eight; words and cases remain separate.
Three different questions. Three different records.
AttendanceTimesheetsReported output
The questionWhen was someone present?Where did recorded time go?What did someone report completing?
Useful contextAttendance event and scheduleWorking period, activity and assignmentWork item, measure and quantity
The boundaryPresence does not establish completed work.Hours do not establish quality.A quantity needs its unit and review status.
Timesheets
- The question
- Where did recorded time go?
- Useful context
- Working period, activity and assignment
- The boundary
- Hours do not establish quality.
Reported output
- The question
- What did someone report completing?
- Useful context
- Work item, measure and quantity
- The boundary
- A quantity needs its unit and review status.
ONE CONTINUOUS EXAMPLE
Follow one piece of work through the period.
A delivery lead assigns localization work using a work item and its measurement unit. The employee records 5.5 hours against that work and reports 1,200 words. The same day also contains two hours of support and half an hour of internal coordination.
The employee submits the working period for review. The assigned approver can approve or reject it; a rejected week remains available for correction and resubmission. Approved output is then available to the authorized report.
The diagram follows just the localization row. It does not imply that attendance events automatically populate a timesheet, or that a submitted record has already passed review.
- 01Recorded
Keep the assignment
The employee records time against the assigned work and reports output in the configured unit.
- Recorded time
- 5.5 hours
- Reported output
- 1,200 words
- 02Submitted
Review the period
The assigned approver reviews the timesheet. A submitted quantity is pending, not an approved result.
- Responsibility
- Assigned approver
- Decision
- Approve or reject
- 03Approved
Read the report
The approved localization output contributes to the report for the selected metric and date range.
- Approved quantity
- 1,200 words
- Separate measure
- Cases reported independently
A rejected week can be corrected and resubmitted through the existing time-recording workflow. Approval is a review outcome, not an assessment of the work’s quality.
The same localization example moves from recorded work to a submitted timesheet and then an approved output report. Submission and approval are separate states.
MEASURES THE TEAM UNDERSTANDS
Let the work define the unit.
A localization team may count words against a work item. A support team may count cases. A service-delivery team may record agreed deliverables. These are examples of team-defined measurement, not connections to an external ticketing or delivery tool.
Keep the definition of each measure clear: what counts, which work it belongs to and the period being reported. A report filtered to a word-based metric should not silently combine that quantity with cases.
Operations leads can use the report’s employee and work-item views to inspect reported quantities in context. Approved quantities form the authoritative view; any optionally included submitted quantities are identified separately.
- Use a consistent unit for comparable work.
- Keep recorded time separate from reported output quantity.
- Read status and reporting period alongside each number.
DIFFERENT RESPONSIBILITIES
Record, review and interpret with different questions.
Employee
Which assignment and activity did this time support? What output did I report, and does the week need correction before resubmission?
Approver
Is the submitted period ready to approve, or should it be rejected for correction? The decision belongs to the assigned review process.
Operations lead
What approved output is visible for this metric, period and scope? What context is needed before comparing employees or work items?
KEEP THE INTERPRETATION HONEST
A report should open a conversation, not close it.
An approved output quantity records what has passed the configured review. It does not by itself establish quality, customer value, effort or individual productivity. Different assignments may carry different complexity even when they use the same unit.
Use totals to locate a useful question, then look at the work and its context. An authorized CSV export can support further analysis; the important point is to keep the metric, period, unit and status with the exported information.
For schedules, attendance and absence around the working day, explore the wider Time & Work page. This page focuses on recording, allocation, review and reporting.
QUESTIONS, ANSWERED
A few things to know before you choose.
Is attendance the same as a timesheet?
No. Attendance events describe presence in their schedule and timezone context. Timesheets describe recorded time against activities and assignments. This page does not promise automatic conversion from punches to timesheet entries.
Can we record output alongside hours?
The existing work model supports measurement units, work metrics and reported output associated with assigned work. The example keeps 1,200 words and 8 cases separate; it totals only the eight recorded hours.
What happens when a timesheet is rejected?
The employee can correct a rejected week and resubmit it through the supported workflow. Submitted and approved states remain distinct, and the assigned approver makes the review decision.
Does the team-output report include unapproved work?
Approved output is the authoritative reporting basis. Where the existing report offers an option to include submitted output, pending quantities are identified separately and should not be presented as approved results.
Can we export the report?
The existing team-output report supports an authorized CSV export. Keep the selected metric, reporting period, unit and approval status with the data when analyzing it elsewhere.
Does recorded output measure productivity or quality?
A quantity alone cannot establish either. Work complexity, quality and organizational conditions need their own context and human interpretation. No automatic productivity score is promised here.
A PRACTICAL NEXT STEP
Make the hours easier to explain.
Bring an example of your assignments and measures. We can discuss the time-recording and reporting scope available to your team.