Project Unit Management

When a development contains many similar units, a spreadsheet can quickly become a collection of competing versions. A floor changes, an area is corrected, or a typical apartment needs to be repeated with one different view. Project Unit Management in MLS RealtyHub gives a developer a structured way to create units inside a project, connect each unit to its parent project, clone repeatable records and change the details that make each unit distinct.

Build unit inventory around the project

Project Unit Management is a live tool in MLS RealtyHub for users working with developer projects. Its purpose is narrow and practical: turn a project into a set of connected Unit records that can be maintained individually without re-entering the shared project context every time.

In MLS RealtyHub, a Unit is a Listing created within a Project. It inherits part of the project-level information while retaining its own record and characteristics. This creates a clear Project-to-Unit structure instead of treating every apartment, office or other saleable space as an unrelated entry.

Use it when repeated units stop being identical

A development may begin with a recognisable set of unit types, but the commercial inventory is made up of individual spaces. Two apartments can share the same basic configuration and still differ by floor, area or view. If the team copies those details between separate files, small differences are easy to lose and later corrections become harder to trace.

The tool is useful when a developer needs to:

1. add the first units to an existing project;
2. create another unit from a typical record;
3. connect an existing Unit record with the correct Project;
4. change the characteristics of one unit without rebuilding the rest;
5. review project inventory as a group of linked, separate records.

Start with the project context

The primary user is a developer or a member of a developer team working in the project area of MLS RealtyHub. Project creation and management are provided for Developer users. Company-linked projects may also be available to colleagues within the same company context, depending on the account configuration.

The process starts from a Project that already provides the shared context. The user then supplies or reviews the details that belong to the individual unit, such as floor, area and view. Required fields vary by project and account configuration.

Turn one project record into structured units

The interaction takes place in Developer Tools under the projects area. The sequence is simple enough to repeat as inventory grows:

1. Open the relevant Project in the projects workspace.
2. Create a new Unit inside that Project, link a Unit to it, or choose an existing Unit as the basis for a clone.
3. Review the information carried from the Project context.
4. Enter or change the details that belong to this specific Unit.
5. Complete the Unit record so it remains connected to the Project and available as part of its inventory.

The user decides which Project the Unit belongs to and which unit-level characteristics need to change. MLS RealtyHub maintains the relationship between the records and reuses the relevant project information. The tool does not make commercial decisions for the developer or decide whether a price, status or specification is correct.

Clone the pattern without cloning the identity

Cloning is designed for developments with repeatable unit types. Instead of recreating the common structure from the beginning, the developer copies a typical Unit and adjusts the details that differ. This is especially useful when the same layout appears on several floors or when a group of units shares most characteristics.

The clone is not another view of the original. MLS RealtyHub creates a new independent Unit record with its own identifier and preserves its connection to the Project. Changes can then be made to the new Unit without turning the original and the clone into one shared record.

Follow one unit from template to inventory

Consider a developer sales manager preparing the inventory for a residential project. A typical apartment already exists in MLS RealtyHub. The next apartment follows the same basic pattern, so the manager clones the existing Unit rather than entering the common information again. The manager then changes the floor, area and view to match the new apartment.

The output is a separate Unit record linked to the same Project. The manager can repeat the process for other variations and edit any Unit when its own characteristics change. The team works with a project structure that reflects individual saleable spaces rather than a flat list of disconnected copies.

Keep the working record ready for the next task

Once a Unit has been created or updated, it becomes part of the Project inventory in MLS RealtyHub. That structured source can support later work across the developer module, including maintained availability, project price lists and project presentations. Those outputs are separate capabilities; Project Unit Management supplies the connected Unit records they depend on.

The practical results are direct:

1. shared project information does not need to be entered from scratch for every Unit;
2. repeated unit types can become separate records with their own identifiers;
3. each Unit stays connected to the Project that provides its context;
4. unit-specific characteristics can be changed at the record level;
5. downstream project materials can draw on the maintained Project and Unit structure where that connection is supported.

Separate user control from system processing

The developer controls the source information. The user chooses when to create, link, clone or edit a Unit and remains responsible for the accuracy of the unit-level details. Other users may see information made available to them, but they cannot alter the developer’s Project or Unit information through this tool.

MLS RealtyHub handles the structural work behind the interaction: it keeps the Unit associated with its Project, carries applicable project-level information into the Unit context and assigns an independent record when a Unit is cloned. It does not automatically validate market price or availability, and it does not guarantee that every external recipient or channel receives every change immediately.

Know what the tool does not cover

Project Unit Management manages the source structure of a development’s inventory. It should not be read as a promise of post-sale property management, building operations or transaction administration.

Its current boundaries are important:

1. a block or building may be represented as a Unit attribute;
2. the tool does not verify whether commercial information is correct;
3. live price and availability updates are a related capability, not a substitute for the user maintaining the source record;
4. a generated PDF remains static after download and is not updated by later changes;
5. role permissions, required Unit fields and package availability vary by account configuration.

Work within Developer and Project Management

Project Unit Management sits inside the Developer and Project Management module. The module covers a broader operating area: Projects, Units, commercial availability, project materials and supported output formats. This page focuses only on the point where the Project becomes structured inventory and where that inventory is maintained.

That boundary matters. Searching the project marketplace, changing live availability, generating a price list and creating an interactive presentation are separate tasks. They can use the Project and Unit structure, but they do not change the core job of this tool: creating and maintaining independent Unit records under the correct Project.

See the unit workflow in your own project

Contact the MLS RealtyHub team to discuss access to Project Unit Management and see how developers can create, link, clone and maintain Unit records within the correct Project.