Blog

All Employees shall have access to create Excuse Requests. The employee can create an Excuse Request, view the created request at any time. The employee who created the request can cancel it until it is approved completely.

Creating Excuse Request in FOX HR

When the employee clicks on the ‘Excuse Request’ card on the Employee Requests page, the system shall navigate to a new screen for creating the Excuse Request. On top of the page, the page’s path shall be displayed as ‘Employee Requests / Excuse Request.’

The screen shall have the following fields for the employee to enter the details:

• Excuse Date – The date on which the employee requests an excuse shall be captured in this field. This field shall be a date field with a date picker for the user to select the excuse date. This field is mandatory.
• Excuse For – The type for the excuse shall be selected from the field, which shall be a dropdown field with the following values. The default value shall be ‘Full Day.’
  • Full Day
  • Late Arrival
  • Early Departure
• Reason Type – The reason for the excuse shall be captured in this field. The field shall be a dropdown field with the following values. The default value shall be ‘Official.’
  • Official
  • Personal
• Comments – The employee shall be able to enter any comments regarding the Excuse Request in the ‘Comments’ field. This shall be a text field and a non-mandatory field.
• Attachment – There shall be an option for the employee to attach files related to the Excuse request. The employee shall be able to attach more than one file. The attachment option shall have the standard options, like the employee shall be able to select a specific file and attach it. Once attached, the employee should be able to view it. Attachment is not a mandatory option.

• Submit – There shall be an option to submit the Excuse Request. Once all the mandatory fields are entered, the user shall be able to Submit the request. Once submitted, the Request will be saved and moved for approval. The submitted Excuse Request shall be available in the ‘My Request’ tab in the Dashboard for the employee to view or cancel it. Once submitted, the system shall navigate back to the Dashboard screen.

• Cancel – If the user does not want to submit the request, then the user can click on cancel, which will cancel the request without submitting/processing further. Once cancelled, the system shall navigate back to the Dashboard screen.

Viewing an Excuse Request

The employee who has created the Excuse Request shall be able to view the Excuse Request at any time by going to the ‘My Requests’ tab under the Dashboard. The employee who has created the Excuse Request can cancel until the request is approved completely.

The Approvers can also view the Excuse Requests from the ‘Action’ tab under the Dashboard. The Approvers are the users available in the Workflow levels for the Excuse Requests.

Each Excuse Request shall be shown under the ‘Actions’ tab and ‘My Requests’ tab in the dashboard. On clicking on the option, the system shall navigate to a new page with complete details of the Excuse Request.

The page shall be divided into five areas: Header, Request Details, History, Workflow Status, and Workflow Comments.

In the Header area of the page, the following details shall be available:

• Request Type – The title of the Request shall be displayed. In this case, the title shall be ‘Excuse Request.’
• Date of creation of the Request – The date of creation of the Excuse request shall be displayed. The date format should include the date & time.
• Cancel Request – There shall be an option for the employee who has created the request to cancel until the request is approved completely. The person who has created the request can only cancel the request, so the ‘Cancel Request’ button shall be visible only for the employee who has created the request.

• Employee Profile Photo
• Employee ID
• Employee Name
• Job Title
• Request Status – The status of the Requests shall be displayed. The various statuses of the Requests are ‘Pending,’ ‘Cancelled,’ ‘Approved,’ and ‘Rejected.’ There shall be a specific colour code for each status as the background colour of the Requests Status text.
• Approve – There shall be an option to approve the request. Only the users in the workflow levels of the request shall have this button visible. Once approved or rejected by the workflow level user, the button will not be displayed for that user. If the user cancels the request, the approve/reject button shall not be visible.
• Reject – There shall be an option to reject the request. Only the users in the workflow levels of the request shall have this button visible. Once approved or rejected by the workflow level user, the button will not be displayed for that user. If the user cancels the request, the approve/reject button shall not be visible.

In the Request Details area of the page, the following details shall be available:

• Excuse Date: The date of the excuse in the request shall be displayed.
• Excuse For: The excuse type in the request shall be displayed.
• Reason Type: The reason for the excuse in the request shall be displayed.
• Comments: Any comments entered in the Excuse Request shall be displayed.
• Attachment: Any attachment added in the Excuse Request shall be displayed, and approvers can view it.

In the ‘Employee Excuse History’ area of the page, the details of the employee’s last five Excuse requests shall be available. The history shall be displayed in card view, and each card shall have the following details:

• Heading – There shall be a heading for the card, which shall be the ‘Excuse For’ of the request.
• Status of the request – The status of the requests shall be displayed, with the date & time of action.
• Reason Type – The reason type in the request shall be displayed.

In the Workflow Status area of the page, the following details shall be available:

The workflow levels for the Excuse Request shall be displayed in card views. Each workflow level shall have a card. There shall be an option to scroll left or right to view the cards if the number of cards is more than the page width. 

Each card shall have the following details:

• The sequence of the Workflow level – The sequence of the workflow level shall be displayed at the top of the card. This will be in numeric sequence starting from ‘1’ till the end of the workflow level. The sequence number background shall be in colours with respect to the status of the workflow level.
• The status of the Workflow level – The status of each workflow level shall be displayed. If the status is pending, then it will show ‘Pending.’ If it’s approved, it will show status ‘Approved’ with the date/time of approval. If the status is rejected, then it will show status as ‘Rejected’ with the date/time of rejection. If delegation is provided by any of the approvers in the workflow level, then that also should be notified. If the user cancels the request, that status also needs to be displayed between the levels.
• Profile Photo of the Approver – The profile photo of the approver shall be displayed.
• Name of the Approver – The name of the approver shall be displayed.
• Job Title of the Approver – The Job Title of the Approver shall be displayed.
• Received Date/Time – The date and time in which the approver receives the request in the workflow level shall be displayed. If the workflow level didn’t receive the request for action, then the Received date/time will be blank.

In the Workflow Comments area of the page, the following details shall be available:

There shall be an option for the users who have access to view the details of the request to put comments at any point in time. The comments entered will be tagged against the user with the timestamp.

• Name of the person – The name of the person who put the comment shall be displayed.
• Date/time of Comment – The date and time the comment is added shall be displayed.
• Comment – The comment shall be displayed.
• Add new Comment – There shall be an option for the user to add new comments by clicking on the Add button.

There shall be a ‘Back’ button to close the detailed request view page. On clicking on the ‘Back’ button at the end of the page, the system shall navigate back to the Dashboard page.

Processing of approved Missing Punch Request in Payroll

Once the Missing Punch Request is approved, there should be an entry added by the system in the attendance details; the system shall add an entry for the day with the same IN/OUT as the shift for the excused day so that there are no differences in attendance and payroll process. The new entry created shall be available in the attendance view and reports. Also, this day will be marked as a normal day in payroll processing.

In short, once the Excuse Request is approved, that day in the attendance module should be automatically marked as present, and the standard shift for the day for the employee should be assigned for the day so that there is no difference in the attendance and payroll.

Notification

When the employee submits the Excuse Request, a notification will be triggered to the first approver. For Excuse Request, a push notification shall appear for the first approver near the right top of the web page. Also, there will be an Email notification for Excuse Request to the approver, requesting to view and approve the request. The approver can either go to the dashboard and approve the request from his ‘Action’ tab or the mail notification; there shall be an option to approve the request directly.

To sum up

Employees can easily handle excuse requests in FOX HR, enabling employees to track the excuse request accurately.