A common method of performing checks is to look at boundary cases, or the maximums and minimums of our calculations. To do this, follow these steps:

1. Start by clicking on the %Utilization column header in our table visualization. This sorts the table in descending fashion, where our highest %Utilization number is at the top of the list. We can see what might be some anomalies of very high utilization, such as the %Utilization at the top, which has 175% for Cole, Camille.
2. To check this number, click on the Data view in the Views pane.
3. Find the EmployeeID field in the Hours table and click on the drop-down arrow in the column header.
4. Uncheck the (Select all) checkbox to unselect all of the values and then scroll down and check the box next to CCOLE.
5. Click the OK button. We can see that 4 hours were billed on a Sunday and another 10 hours on a Friday. Therefore, this calculation is correct since there are only 8 potential billable hours between the two days since Sundays are considered non-working days.

6. We can check the next highest case, which is for Perkins, Caitlen, by using the same process and deselecting CCOLE and selecting CPERKINS. Again, we can see multiple billable hours on Saturdays and Sundays. Hence, it appears that the maximums for our %Utilization calculation are actually correct.
7. Clicking back on the Report view, notice that, while we have filtered the table in the Data view, we can still see all of the data in the Report view. This is because filtering data in the Data view does not impact the Report view in any way; the filtering and sorting capabilities that are provided in the Data view are solely for the report author to use when verifying data.
8. Now, click the header for %Utilization in the Table visualization again. The data is now sorted in ascending order, with the lowest values for %Utilization shown at the top.
9. There are numerous instances of 0% %Utilization for cases where #TotalBillableHours is blank. However, there is one case for Irwin, Rachelle that shows 0% %Utilization but #TotalBillableHours as 6. We can filter for RIRWIN in the Data view of the Hours table by using the Search box just above the list of values that can be filtered.
10. First, enter CPERKINS in the search field and uncheck CPERKINS from the list of search results that are displayed. Then, enter RIRWIN in the Search field and check the box next to RIRWIN. We can see that the 6 hours were billed on a Sunday. Hence, our calculation is technically correct, and it is a good thing that we used the DIVIDE function with its ability to return a value in the case of a divide-by-zero.
11. Continuing down the list of rows in the Table visualization, in the Report view, the next potential anomaly is Beasley, Joni, who has only 2 #TotalBillableHours entries but 368 #TotalHours entries. Again, by checking the Data view for JBEASLEY, we can see in the footer that there are 71 rows of reported hours but that all of these rows except one are to a Category other than Billable. The same circumstance is true for BMACDONALD and SHESTER.

With these checks now complete, we can reasonably conclude that our calculation is returning valid results.