Traditional and Non-Traditional Cycles

Not every housing timeline follows the academic calendar. While most housing cycles align with traditional terms like Fall or Spring, many offices also manage programs that don’t, such as summer camps, commuter meal plans, or visiting faculty housing.

Housing.Cloud supports both, allowing you to create cycles that either connect to your institution’s Student Information System (SIS) through a term code or operate independently.

This flexibility gives your team control over how each housing cycle interacts with your SIS. Whether a cycle syncs automatically or stays separate depends on how your institution’s integration is configured and how your IT team chooses to handle the data.

How Term Codes Work with Cycles

A term code identifies an academic period in your institution’s SIS. When a term code is attached to a cycle, it tells both systems how to categorize assignments, meal plans, and billing.

When a cycle has a term code, Housing.Cloud includes that information when sending data through the integration. Your SIS then maps those records to the correct academic term for billing, enrollment, or reporting. When a cycle does not have a term code, Housing.Cloud still generates and sends the data. However, your SIS may not have a matching location to store it. Your IT or integration team decides whether to process, redirect, or exclude that information.

In other words, Housing.Cloud will always generate and share housing data when an integration is active, but the presence of a term code determines how (or if) your SIS uses it.

Traditional Cycles (With Term Codes)

Traditional cycles align with your academic calendar and include a term code. They are used for housing activity that should sync directly with your SIS and appear in institutional billing, assignments, and student records.

Attaching a term code ensures that all applications, assignments, and charges from the cycle are categorized under the correct academic period across campus systems.

Common examples

• Fall Returning Student Cycle 
• Fall New Student Cycle 
• Spring Housing Cycle 
• Summer Session 1 or 2 Cycle 
• Commuter Meal Plan Cycle

These cycles form the foundation of your housing year. They connect directly to your SIS for reporting, financial reconciliation, and student record accuracy.

Non-Traditional Cycles (Without Term Codes)

Non-traditional cycles manage housing activity that operates outside the academic calendar or doesn’t require automated billing through your SIS.

These cycles use the same structure as traditional ones but are intentionally left without a term code. Doing so allows your IT or finance team to keep the data separate from institutional term-based records or handle it manually instead of through automated posting.

Common examples

• Summer or athletic camps 
• Visiting faculty or researcher housing 
• Partner or exchange programs on different academic calendars 
• Conferences or event housing 
• Short-term or interim housing not tied to academic billing

If billing is still needed, data from these cycles can be exported manually or mapped by your IT team to a custom destination in your SIS. The key difference is that these cycles are not tied to a specific institutional term unless your team chooses to link them.

Choosing the Right Setup

Before creating a cycle, confirm how your institution handles data coming from Housing.Cloud.

• Include a term code if the cycle will send housing, billing, or meal plan data that your SIS should associate with an academic term. 
• Leave the term code blank if the cycle manages short-term programs, guests, or populations that should not post to institutional term data by default.

Many institutions use both types of cycles year-round: traditional cycles for academic housing and non-traditional cycles for specialized or external programs. The right approach depends on how your integrations and financial workflows are structured.

Best Practices

• Confirm active term codes with your IT or registrar before creating a cycle. 
• Coordinate with your integration team to define how cycles without term codes should be handled. 
• Use clear naming conventions such as “Summer 2026 – Soccer Camp Housing” for non-traditional cycles. 
• Keep billing configurations separate to avoid posting non-traditional charges to the SIS unintentionally.
• Apply eligibility tags to ensure only the intended participants can access each cycle. 
• Review data exports regularly if your team processes charges or reconciles off-term billing manually.

Integration and Data Handling

Term codes guide how housing data is categorized once it leaves Housing.Cloud.

• With a term code: Data sent through the integration includes the official term identifier, allowing the SIS to route records to the correct academic term. 
• Without a term code: The data is still generated and sent, but your SIS may not have a mapped location to store it. Your IT team determines whether it’s imported, redirected, or excluded.

This setup gives housing teams flexibility. Each cycle can either align fully with institutional systems or remain independent for short-term or external housing needs, all while maintaining consistent data in Housing.Cloud. Institutions using an Ellucian Ethos integration experience this behavior differently.

Ethos Integration Behavior

Ethos acts as a structured data pipeline between Housing.Cloud and your SIS (Colleague or Banner). Because Ethos enforces strict alignment with academic term structures, every transaction, assignment, and meal plan record sent through Ethos must include a valid term code.

If a cycle does not have a term code, the data will still be created in Housing.Cloud but will not successfully post through Ethos. The SIS will not know which academic term to associate it with, so the data will either fail validation or remain unprocessed within the Ethos pipeline.

What this means for Ethos clients

• Cycles without a term code will not deliver assignment or transaction data through Ethos. 
• Housing activity from those cycles will remain in Housing.Cloud unless exported manually or sent through a supplemental SFTP integration. 
• Attach a term code to any cycle intended for billing, reporting, or SIS synchronization. 
• Non-traditional or short-term cycles can still be used but will require manual export or custom handling outside of Ethos.

Clients using non-Ethos integrations or custom API connections have greater flexibility. Their integrations can typically accept and store data even when no term code is attached, allowing more freedom to manage non-traditional or off-term housing operations.

Coordinating with IT

Before launching a new cycle, especially one without a term code, check with your IT or integration team to confirm how your SIS will handle that data.

• Agreeing on rules early helps prevent failed data transfers, missing records, or duplicate billing.
• If your institution uses Ethos, plan to include a term code for every active housing term.
• For non-Ethos clients, confirm whether your SIS can accept off-term housing data or if manual export is required for reconciliation.