Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTeam
Device

How to view planned hours by employee

Check each employee's planned workload for Harbor Soho or another selected location. The read-only report summarises planned hours, planned blocks and planned employees from service-linked staff schedules for the selected period.

In this article

Use this report when a location manager, operations manager or staff planner needs to review planned workload before making staffing changes elsewhere.

The report opens from the employee reporting area and displays the `employee-planned-hours` page from the shared reports dashboard. It does not create, edit or delete employees, services, schedules or calendar events.

Before you start

  • Sign in to the protected Antylogic app.
  • Select an organisation and location. In the GB demo, use Harbor Demo Group and Harbor Soho.
  • Make sure the location has a timezone configured. Harbor Soho uses `Europe/London`.
  • Use an account with location report access, such as `reports:view` or another accepted report permission.
  • For populated rows, the location needs employees and `staff_schedule` calendar events linked to service calendar events.

Instructions

  1. 1.

    Open the report

    From the location workspace, open Reports, then Employees, then Planned hours. The direct route is `/:orgId/:locationId/reporting/employees/planned-hours`.

  2. 2.

    Check the period

    Review the period filter at the top of the report. If the route has no `periods` parameter, Antylogic creates a default period and stores it back in the route. Reporting days are interpreted in the location timezone.

  3. 3.

    Read the summary

    Use the summary block to check total planned hours, planned blocks and the number of employees planned for the selected period. Only schedule intervals that overlap the selected period contribute to these totals.

  4. 4.

    Review employee rows

    Scan the employee table to compare planned hours and blocks by person. Rows are sorted by planned hours in the latest selected period, highest first. Missing period data is shown as zero hours or zero blocks.

  5. 5.

    Compare periods

    Add a period to compare the current range with the immediately previous range of the same length. The route uses `YYYY-MM-DD_YYYY-MM-DD` chunks separated by `~`, and the table shows period-series values with a legend.

  6. 6.

    Handle empty results

    If no service-linked staff schedules match the selected filters, the report still opens and the employee table shows its empty state. Schedules linked to private or non-service events are excluded.

Validations and limits

  • The report request runs only when organisation, location and report access are present.
  • If no organisation or location is active, the page shows the location-required state and does not load data.
  • If the operator lacks report access, the page shows a permission error instead of the report.
  • Invalid `periods` chunks are ignored by the report service; if no valid periods remain, default periods are used.
  • Only `staff_schedule` intervals linked to a parent service event and with positive overlap inside the selected period count in the report.
  • Report export is available on web; native platforms show export as unavailable.

Expected result

The manager can confirm planned workload by employee, compare it with a previous period and identify how service-linked schedules are distributed across staff without changing operational data.

Related articles