Report Logic
Many LCPtracker reports are able to reference an employee’s current and historic addresses when generating data. When an employee has two or more, addresses during the period being reported on, the system will allocate hours against each address appropriately.
The following report logic is in place when a report references multiple addresses or geographic areas for an employee:
Referencing a Historical Address’ Move-out Date
If an employee has both a ‘current’ address and a ‘historical’ address, the system will be looking at the move-out date associated with the historical addresses to determine which address falls into the time frame of the report parameters.
The move-out date is considered the last day at an address. The next day is the new, or current address.
Reports that Run by Calendar Date
When an address changes in the middle of a 7-day period on a calendar-date based report, the hours will be totaled by day based on the address that was current for that respective day.
Reports that Run by Week-end Date
For reports that are filtered by week-end date, the most current address will be reflected for that respective week-end date.
For example, if employee has more than one address and the address move-out date lands in the middle of the week, the system will use/display the new, most current address instead of the old address.
Reports that Contain a Head Count
If there is a head count for each location category, and an employee falls into two location categories (be it by city or geographic area, etc.), then the employee will be counted twice.
However, the ‘Totals’ row or section will only show the employee counted once on the overall project totals.
Support
If you have any further questions, please feel free to contact our Support Department Monday through Friday, 5:00am through 5:30pm PST:
- Call: (714) 669-0052 option 4
- Email: Support@lcptracker.com or,
- Chat: via the LCPtracker database through the “Live Chat” feature.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article