triangle

Recording Closures in PioneerTime

Modified on: Fri, Mar 24, 2023 at 10:45 AM



Learn how to record University Business closures in PioneerTime for non-exempt and non-benefited employees (paid bi-weekly).


This article applies to non-exempt employees, non-benefited employees, and their respective supervisors.



When the university issues a business closure (ex. inclement weather) employees scheduled to work may be eligible to substitute the scheduled time with the closure pay code in PioneerTime. 
When the university issues a closure some departments will still need to report to campus and others might need to work remotely. Employees are encouraged to consult with their unit leader to determine how this will look for their department. 


If employees will not be working please use the following directions to account for this time on their timecard.



The "Closure" pay code in PioneerTime is reserved for University-wide closures only and should not be used for departmental closures.


For benefited, monthly paid employees, no closure entry is required and the day of closure can be left blank on their leave calendar. Since benefited monthly employee's do not record hours worked and only leave, this would be reflected as a normal day worked.



To enter the closure pay code for bi-weekly employees:

1. Log into PioneerTime (My.du.edu>PioneerTime).


2. Select the correct pay period, and double-click on the employee's name to open and review their timecard. 


3. Locate the date of closure and select the closure pay code from the pay code menu. Enter the number of scheduled hours for the day in the amount column and hit save:




For non-benefited employees use the closure NB pay code:




For employees with multiple jobs/positions ensure that the closure time is coded to the position scheduled for that day by selecting that position in the transfer set column- Editing Timecards and Transfer Sets (For Supervisors).


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.