Furniture and Room Condition Reports Overview

Furniture tracking in Housing.Cloud is a foundational part of maintaining accurate records for room condition reports (RCRs), especially during the key transition periods of student move-in and move-out. Admins configure Furniture Types and generate Furniture Items to create detailed, location-specific condition logs that can be submitted by student staff or residents and reviewed by administrators. This overview explains how Furniture Types are established, how they connect to Room Condition Reports, and what admins should consider when preparing their inventory for inspection workflows.

When to Set Up Furniture Types

Furniture Types are configured in the Inventory Management section of the Admin Portal. While critical to the RCR workflow, Furniture Types are not usually established during the initial implementation or go-live process. Instead, admins are encouraged to complete their onboarding, evaluate their space layouts, and take inventory of room contents before initiating this setup.

Once this post-onboarding assessment is complete, admins can begin creating their Furniture Types. Each type represents a unique, physical item, such as a desk, chair, mattress, or towel rack, and must be created individually. These types function as templates and are not directly tied to conditions or student profiles until they are transformed into Furniture Items.

Room Parts

Room Parts are older furniture type variations and are being phased out. They lack key features like condition history, ownership tracking, and submission interaction. Housing.Cloud strongly encourages schools to transition to Furniture Types and leverage their full capabilities. A unified Furniture Item system ensures consistent condition tracking and improved admin and student experience.

Furniture Types and Assignment Levels

Each Furniture Type must be assigned an intended assignment level that determines how the item will be distributed across housing spaces. Assignment levels indicate the type of usage and help clarify ownership:

• Bed-level: Item is assigned to one student (e.g. desk, mattress)
• Room-level: Shared by all residents in the room (e.g. closet shelf, mini fridge)
• Suite-level: Shared by all residents in a suite (e.g. shower rod, towel rack)

While the assignment level itself is not stored in the platform, this data is added during Housing.Cloud’s propagation process. When submitting a schema to bulk generate Furniture Items, admins must indicate the assignment level and the applicable buildings.

We recommend naming Furniture Types in a clear and student-friendly way. This ensures that when students complete their RCRs, they can easily recognize and assess each item in their space.

Furniture Item Setup and Tracking Strategy

Furniture Items are unique, trackable entities in Housing.Cloud. Like applications and profiles, each Furniture Item has its own record, URL, and status history. These records allow for precise condition logging over time and are used in Room Condition Reports.

When setting up Furniture Types, admins should decide how specific they want to be. For example:

• If the institution prefers simplicity, a universal label like “Dresser” can be used for all dressers, even if they differ slightly.
• If variation matters for tracking and replacement (e.g. 3-drawer vs. 4-drawer), each variation should be created as a separate Furniture Type.

This naming strategy impacts student usability and reporting accuracy. Admins should choose the approach that aligns best with institutional practice.

Furniture Items live under the Furniture sub-section of the Inventory section in the Admin Portal.

From Types to Items

Furniture Types do not automatically appear in rooms. Admins must request Housing.Cloud to perform a bulk propagation of Furniture Items using a completed schema. This schema includes the assignment level and building mapping, and allows the platform to efficiently create and place Furniture Items throughout the housing inventory.

Without this propagation, Furniture Items must be added one by one—an extremely time-consuming task not suitable for most institutions.

Once created, Furniture Items exist within individual room, bed, or suite records and serve as the backbone for Room Condition Reports. Each item becomes a trackable object with a condition history that can be updated through student or staff interaction.

To learn more about the schema format, visit: CSV Integration Schema: Furniture

How Room Condition Reports Use Furniture

Room Condition Reports are built from the Furniture Items assigned to a bed, room, or suite. Each report reflects the current state of those items, creating a standardized process for condition tracking. These reports provide a snapshot of space condition tied directly to student occupancy and are required to document move-in or move-out inspections accurately.

For a Room Condition Report to function correctly, the corresponding Furniture Items must already exist in the space. Without this inventory setup, RCRs cannot be generated. Admins can choose to initiate RCRs manually at any time or trigger them automatically through student check-in and check-out processes.

Room Condition Report Roles and Flow

Institutions can customize how Room Condition Reports are completed by defining who submits and validates reports. The standard workflow includes two roles:

• Submitter: The individual who first records the condition of the space and its contents. This is most commonly the student during move-in, but it can also be a staff member.
• Validator: The person who reviews and approves the initial submission. This role is typically filled by student staff or administrators during move-out.

Once a Room Condition Report is submitted and validated, the data is stored with each Furniture Item. Admins can review condition history in the Admin Portal at any time. This process ensures transparency, accountability, and consistent documentation over time.

RCRs are stored under the Room Condition Reports tab in the Inventory section of the Admin Portal. Admins can view all submissions, including notes, images, and condition updates from both the submitter and validator. RCR data is tied to the student’s occupancy record and the inventory items in their assigned space.

Setup Overview

To establish a working Furniture and RCR workflow, admins should follow this structured process:

• Configure Furniture Types in the Inventory Management section
• Prepare a Furniture Schema with assignment levels and building assignments
• Submit schema to Housing.Cloud to generate
• Furniture Items in bulk
• Ensure Furniture Items are visible within room, bed, and suite records
• Generate Room Condition Reports manually or via automated check-in/check-out flows
• Students or staff submit initial RCRs; validators review and finalize
• Finalized condition data is recorded on each Furniture Item for future reference

This setup allows institutions to conduct thorough, structured inspections while maintaining a digital record of all furniture-related conditions tied to each space and student. For more information on setup, reach out to your Housing.Cloud representative.