1. Import employee hours reports
Select one or more DAS Employee Hours HTML files. Assign the corresponding Monday–Sunday dates after import.
Add weekly HTML reports
Drop files here or use Browse. Multiple files can be selected at once.
No files uploaded
2. Import weekly Activity Masterfiles
Upload the DAS AM08a Activity Master File report (.txt or .html). Each report is effective for one Monday–Sunday week.
Add Activity Masterfiles
Running-board start and finish times determine actual driving time. Each file needs a valid week.
No Activity Masterfiles uploaded
Calculation rules and export details
- DAS Employee Hours identifies actual allocations; Activity Masterfile supplies original running-board spells. Modified driving activities with suffixes (.a, .b, .c, etc.) use the overlapping masterfile boards where available. If no original board overlaps, Dashours uses the DAS allocated spell and flags Activity modified. Modified split duties over 12 hours use declared DAS HOURS rather than their gross span.
- Reallocated duties take precedence over the original duty. If there are no reallocations, the original duty is used.
- Driving includes four-digit duty codes, with optional letter suffixes (5299, 5299.a, 5513.ab), and LAT codes.
- Standby (S duties), connecting (BOCC) and other explicitly assigned non-driving activities are kept separately. Layovers & Breaks are residual time between board assignments; they are not necessarily meal breaks. Non-driving = assigned non-driving + layovers and breaks + excluded split swing.
- Overtime starts after 7h 20m per employee-day. Total OT = max(0, worked time minus 7h 20m). Driving OT = max(0, driving time minus 7h 20m). For split shifts, an inferred unreported swing break is excluded from the total-OT basis and also excluded from Layovers & Breaks, preventing a second subtraction. OT less Layovers & Breaks is simply Total OT minus unassigned break/layover duration; it may be negative and does not replace payroll OT.
- Split-duty payroll HOURS remains the basis for total overtime where applicable, excluding the inferred swing break. Driving time, however, is always measured from matched running-board intervals; LAT duties use DAS FROM/TO until board-level LAT data exists.
- Every file must cover a full Monday–Sunday week. Overlapping or incomplete ranges cannot be exported.
- Overnight duties are supported. Full-day 00.00–24.00 absence entries are excluded from worked time.
- Masterfile running boards are preferred. If any duty, including unsuffixed Loyang duties, has no usable match, DAS Employee Hours becomes the fallback: FROM–TO for regular duties, or declared HOURS for spreads over 12 hours. These are duty-hour estimates, not verified running-board driving time. All fallback assignments are explicitly identified in Remarks, including the exact reason.
- Excel includes BC Summary, Daily Summary, Activity Audit, Running Boards, Activity Modified, DAS Fallbacks and Checks. BC Summary column headers have Excel notes explaining the definitions; hover over the header cells in Excel. Only duties without usable DAS timing data remain unresolved and block export.