Canonical URL: https://density.io/resources/campus-dining-occupancy-demand

# How should campus dining teams combine occupancy and arrival counts?

Density Entry with Atlas combines dining-hall entrance counts with occupancy reporting. A campus dining team can use those patterns to choose when to inspect service conditions and which operating changes to test. Staffing decisions also need observations of the work happening inside.

Density’s [education guidance](https://density.io/industry/education) identifies dining halls as a use for real-time occupancy. Separate demand for room space from incoming traffic and demand at individual service stations.

## Start with the dining decision

Suppose your team is considering moving a service break because students report a difficult lunch period. Define the question before choosing a chart: does the reported problem coincide with a burst of arrivals, a persistently full seating area, or a particular counter falling behind?

These possibilities call for different observations. Dining-hall occupancy describes the people within the measured boundary. Entrance counts describe crossings into it. Neither identifies who orders food, what they order, or how long a particular station takes to serve them.

Begin with [Density Entry](https://density.io/entry) for the doorway measurement. Review every route into and out of the proposed dining boundary with Density, including connecting doors. Keep a shared lobby outside the boundary if the question concerns the dining hall itself. The definition should match the operating decision.

## Equal occupancy can hide different arrival patterns

In this hypothetical example, two 15-minute lunch observations each begin with 100 people in the hall:

| Hypothetical 15-minute observation | A | B |
| --- | ---: | ---: |
| Starting occupancy | 100 | 100 |
| Entrances | 30 | 90 |
| Exits | 30 | 90 |
| Ending occupancy | 100 | 100 |

For A, **100 + 30 − 30 = 100**. For B, **100 + 90 − 90 = 100**. B records three times as many entrances during the interval, although both end with the same occupancy. An end-of-interval headcount alone would conceal that difference.

This example does not establish equal average or peak occupancy, because the sequence of crossings is unspecified. It also does not establish unique diners, meals served, queue lengths or required employees. People may enter more than once, and some crossings may be staff. Keep those distinctions when discussing a lunch rush.

## Put the signals beside each other in Atlas

[Density Atlas](https://density.io/atlas) supports occupancy and visits reporting, custom operating hours and downloadable charts and data. Use the same hall, dates and meal-service window when reviewing the two signals.

Density’s [Building Analytics guide](https://support.density.io/hc/en-us/articles/22170219483419-Video-Guide-to-Building-Analytics) explains that visits show entrances and require Entry sensors, while occupancy accounts for entrances and exits and requires full coverage. It also distinguishes peak and average reporting. Confirm the available views for your deployment before agreeing on a recurring review.

Choose periods that reflect the decision. A whole-day average cannot describe the particular lunch interval students raised. Compare similar teaching days and record exam schedules, special events and changes to opening hours beside the observations. Keep closed periods out of a comparison intended to describe service hours.

## Observe the work before changing the service plan

Use the count pattern to select observation windows. During those windows, have the dining team separately record the conditions relevant to the proposed change: arrival times at a counter, observed waits, which stations are open and when replenishment interrupts service. These are additional operating observations, not outputs implied by a hall occupancy chart.

If the room has spare seating while an observed counter queue grows, adding seats would not directly address that counter’s problem. If students report difficulty finding seats, inspect seating availability separately from the entrance rush. Give each proposed response the evidence that could justify it.

Test one limited service change, then review comparable periods using the same measurements. Evaluate the observed service experience alongside occupancy and arrivals. Differences in menus, schedules or open stations may explain a result; document them before expanding the change.

## Bring Density an operating question

Start with one dining hall, its entrance plan, meal hours and the service decision under consideration. Ask Density to connect Entry coverage and Atlas reporting to those boundaries, then agree which additional observations your operations team will collect.

[Book a Density demo](https://demo.density.io) or email [sales@density.io](mailto:sales@density.io) to plan measurement for your campus dining operations.