An office IT equipment checklist should connect each room and role to a device quantity, a technical requirement and a named dependency owner. Count personal computers separately from shared displays, document equipment and connectivity. A list becomes an orderable bill of materials only when the supporting power, connections, software and responsibility decisions are recorded.
Start with a floor plan and the work expected in each space. A reception desk, finance room and meeting room can need different equipment even when they serve the same employees. This guide builds that mixed-device requirement. For a hiring-led laptop plan, use the startup fleet and hiring guide alongside the room inventory.
Map rooms and roles before counting devices
Give each space an identifier that appears on the floor plan and the equipment sheet. Record its purpose, occupied work positions, shared activities and current reusable equipment. Then assign roles to the positions: reception, administrative work, finance or other approved workloads. Ask each application owner to describe the task and operating-system constraints before selecting a computer.
Use separate counts for employees, simultaneous desk users and visitors. A meeting room used by people who already have laptops does not automatically require another laptop for every chair. Record whether participants bring their devices or the room needs dedicated compute. Keep uncertain requirements visible as decisions, rather than inserting an arbitrary spare percentage.
Separate personal equipment from shared room equipment
Personal equipment follows a role or a fixed workstation. Shared equipment follows a location and an operating owner. Use separate rows for laptops, desktops, desk monitors, docks, meeting displays, audio/video equipment and document devices. Record accessories included with a quoted bundle so they are not ordered twice.
For meeting spaces, Microsoft’s Teams Rooms planning guidance separates room inventory, device selection, site readiness, network readiness and resource accounts. It also considers room layout, acoustics and camera views. Use that dependency approach for your chosen meeting platform; it does not establish that a particular room system, licence or installation service is included in a hardware enquiry.
Resolve power, connection and application dependencies
A monitor and dock line needs more than matching connector shapes. Record the host model, supported display connection, required display arrangement, dock power supply and charging requirement. Dell’s docking guide distinguishes USB-C video support through DisplayPort Alternate Mode from other port capabilities. Ask IT to validate the exact host, dock, cable and monitor combination instead of assuming every USB-C connection does the same job.
Facilities should confirm the physical power and placement requirements; IT should own the connectivity design. List wall connections, wireless coverage or cable routes as dependencies requiring approval. Device counts alone cannot establish switch capacity or access-point quantities. Schneider Electric’s UPS guide distinguishes equipment load from battery runtime. Have the responsible reviewer assess the actual connected load and required operation or shutdown period before selecting backup equipment.
Software accounts, licences, security controls and configuration also need named owners. Describe those tasks in the requirement without assigning them to an equipment supplier by default. A room can receive every box on the list and still remain blocked by an unavailable account or unfinished power connection.
Copy this editable office bill of materials
Create one row per distinct device requirement, even when several rows serve the same desk. Duplicate the blank rows as needed. Give each row an asset source such as existing owned equipment, proposed rental or purchase. In a spreadsheet, add row identifiers, separate quantity columns, ready-by dates and approval status so decisions remain editable.
| Room / role | Device requirement | Quantity reconciliation | Dependency | Owner / readiness | Custody / acceptance |
|---|---|---|---|---|---|
| Personal work positions | Computer / display / dock: ___ | Total ___ / reuse ___ / source ___ | Connection / power / app: ___ | Dependency owner ___ / ready by ___ | Custodian ___ / acceptance ___ |
| Reception | Device and purpose: ___ | Total ___ / reuse ___ / source ___ | Connection / power / app: ___ | Dependency owner ___ / ready by ___ | Custodian ___ / acceptance ___ |
| Meeting room | Display / AV / compute: ___ | Total ___ / reuse ___ / source ___ | Platform / location / power: ___ | Dependency owner ___ / ready by ___ | Custodian ___ / acceptance ___ |
| Document area | Print / capture device: ___ | Total ___ / reuse ___ / source ___ | Workflow / access / space: ___ | Dependency owner ___ / ready by ___ | Custodian ___ / acceptance ___ |
| Network / backup location | Design-approved component: ___ | Total ___ / reuse ___ / source ___ | Approved design / load: ___ | Dependency owner ___ / ready by ___ | Custodian ___ / acceptance ___ |
Reconcile total required minus reusable quantity to the quantity still to source. Reuse should mean a checked, suitable asset, not merely something in storage. List an unresolved model, supply category or dependency as pending; do not turn it into an approved order by filling a quantity cell.
Check a filled office example
Hypothetical planning example, not a customer deployment: An office has 20 people: 16 in an open work area, two in finance and two at reception. Assume the planned roles require 14 laptops and six desktops. Each work position has one external monitor; each laptop position has one dock. These are example choices, not recommended ratios or confirmed stock.
| Space | Illustrative equipment requirement | Dependency owner |
|---|---|---|
| Open work area: 16 people | 12 laptops; 4 desktops; 16 desk monitors; 12 docks | IT: application and host/display combinations |
| Finance: 2 people | 2 desktops; 2 desk monitors | Finance owner and IT: approved applications and access |
| Reception: 2 people | 2 laptops; 2 desk monitors; 2 docks | Operations and IT: desk placement and role access |
| Meeting room: 6 seats | 1 room display; 1 audio/video kit; participant laptops reused | AV/IT: kit components, platform and room test |
| Shared document area | 1 MFP; 1 document scanner, both provisional | Administration and IT: separate print/capture needs |
| Network and backup locations | Quantities TBD pending design and load review | IT and facilities: approve before ordering |
The desk totals reconcile to 20 computers, 20 desk monitors and 14 docks. The meeting display is an additional shared display, not one of the 20 desk monitors. Its six seats do not add six employees or laptops. The audio/video kit is one provisional kit line; its eventual component list must prevent duplicate camera or speaker orders.
For this example, reusable quantities are assumed to be zero. Network and backup quantities remain blank until reviewed, and the two document devices remain provisional until the process owner confirms the need. The example therefore illustrates a reconciled requirement, not an order-ready equipment package.
Assign an owner to every opening-day dependency
| Decision | Responsible owner | Evidence required |
|---|---|---|
| Role applications, accounts and access | Customer application owner and IT | Approved task, permissions and configuration plan |
| Electrical readiness and physical placement | Customer facilities team | Suitable power and installation arrangements approved |
| Network design and connectivity | Customer IT or its appointed specialist | Required locations and connectivity validated |
| Room audio/video and shared-device workflow | Customer room or process owner with IT | Representative task passes agreed checks |
| Equipment source and commercial scope | Customer procurement and the confirmed supplier | Exact quoted items, inclusions, exceptions and responsibilities |
Add a ready-by date and status to each dependency. Before release, review one complete work position, the meeting-room task and the document workflow with their owners. Confirm that the quoted equipment matches the reviewed combinations. Keep substitutions and unresolved exceptions visible so the person approving the order understands what still needs to happen.
Frequently asked questions
Does an office need one of every device for each employee?
No. Personal computer quantities follow the approved work positions and roles; shared equipment follows room and process needs. Count monitors and docks separately, and state whether a meeting room uses participant laptops. A headcount alone does not specify the office-wide equipment mix.
Should networking and backup power appear on the checklist?
Yes, as requirements with named design and readiness owners. Leave quantities pending until IT and facilities review them. Their appearance on a checklist does not confirm that a rental supplier offers those categories or performs cabling, electrical work or network installation.
How do we avoid ordering monitors or accessories twice?
Give shared equipment a location identifier and record bundle inclusions against the relevant row. Count an item once, then reference it from the desks or rooms that use it. Reconcile reusable, included and separately sourced quantities before approving the final list.
When is the bill of materials ready for a quote or order?
A draft BOM can support an initial enquiry with unknowns clearly labelled. An order needs exact offered items, confirmed inclusions, reconciled quantities and agreed responsibilities. Application, power, connection or room-fit questions should have an owner and decision date before the requirement is treated as ready.