Canonical URL: https://density.io/resources/open-area-office-utilization # Which sensor system should you use to understand open office areas? [Density Open Area](https://density.io/open-area) measures occupancy within larger office areas. Measuring desk neighborhoods and collaboration spaces separately helps a workplace team see where people spend time and which areas warrant a layout change. A busy office can contain crowded collaboration areas and rows of unused desks. A building entrance count cannot show that difference. Measure the areas inside the floor that could change. ## Match the measurement to the workplace question Density's [workplace sensor guidance](https://support.density.io/hc/en-us/articles/37761559048987-Waffle-in-the-Workplace) distinguishes three useful measurement choices. ### Open Area for people counts within a space Choose Open Area when you need the headcount within an area. Compare counts across desk neighborhoods and collaboration spaces to see where people work, rather than treating the floor as one number. ### Entry for entrances, exits and building demand [Density Entry](https://density.io/entry) measures doorway crossings that contribute to occupancy. Use it when arrivals, departures and building or floor-level demand are the relevant questions. An entrance count alone does not explain which desk neighborhood people use afterward. ### Waffle for small spaces and individual versus group use [Density Waffle](https://density.io/waffle) reports zero, one, two or three-plus people. Those categories support decisions about phone booths, small meeting rooms and whether a space serves an individual or a group. A workplace can need more than one of these signals. Choose the output for each decision, then design the measurement plan with Density. ## Begin with a decision you can test Consider this hypothetical planning example. A workplace team is deciding whether to convert part of a desk neighborhood into collaboration space. Employees report difficulty finding somewhere to meet, while the floor's overall attendance appears modest. Measure the desk neighborhood and existing collaboration areas as separate spaces. Compare their patterns during the same working hours, including busy periods. Ask whether the proposed change would address a recurring mismatch between the available space and the way teams actually work. If you test a layout change, keep the before-and-after boundaries, capacity assumptions and reporting periods clear. Review the observed use alongside employee feedback before extending the change to another floor. Density's [published workplace examples](https://density.io/resources/space-utilization) describe a customer reallocating existing space after examining how rooms were used. Inspect use within the office before assuming the answer is more square footage. ## After the layout changes, check what the report describes A current floor plan helps the team connect a count to the right part of the office. Density's [floor-plan swap guidance](https://support.density.io/hc/en-us/articles/10427273288347-Floor-Plan-Swaps) says significant furniture or floor-plan changes may require an updated plan in Atlas. Send the revised plan and the affected location and floor to your Density contact, and confirm the current process for your deployment. Keep a short change record when desks become a collaboration area or a room boundary moves. Record the effective date, the old and new space purpose, the usable capacity and any changes to the measured boundary. Have Density review whether the physical change calls for a coverage or configuration check; uploading a drawing alone should not be treated as proof that the measurement still matches the space. Before comparing periods, decide whether the question concerns the same physical area or the same function. A former desk neighborhood and its replacement collaboration area can share a footprint while serving different needs. Keep that change visible in the report rather than presenting the two periods as an unchanged desk-use series. Review the updated map and one reporting period with the person responsible for the space decision. Confirm that the intended areas, names and capacity assumptions are represented, then use comparable hours and observation coverage for the next review. Ask how the layout change will appear in historical comparisons before combining the periods. ## Prepare a coverage review with Density Bring a current floor plan and the decisions you want it to support. Prepare these details for the deployment discussion: - Mark the areas you want to compare and state each area's purpose. - Record the capacity assumptions you will use when interpreting counts. - Identify ceiling conditions, furniture and other features relevant to placement. - Confirm the applicable Open Area model, mounting, coverage, power and network requirements with Density. - Agree how layout changes will be reflected in the measured spaces. A sensor count should follow the reviewed coverage design. An advertised maximum area is not a substitute for that plan. ## Compare periods with valid measurement Confirm when each area is ready for reporting. Density's [Atlas heatmap guidance](https://support.density.io/hc/en-us/articles/17230241385115-Atlas-Why-does-my-heatmap-not-show-up) notes that Open Area heatmaps begin after commissioning. Keep that start point in mind when comparing spaces or time periods. Keep the coverage and reporting window beside the result so your team can judge which workplace investment the pattern supports. [Book a demo](https://demo.density.io) or email [sales@density.io](mailto:sales@density.io) to plan Open Area measurement around your office decisions. The [utilization metrics guide](https://density.io/resources/4-space-utilization-metrics-to-measure-and-optimize) explains the denominators behind a chart. The [building-comparison guide](https://density.io/resources/compare-buildings-hours-time-zones) covers consistent hours and reporting windows.