What Building Features does in Proplix
Building Features is part of Proplix Property & Portfolio Management and is designed to capture building-level characteristics in a reusable structured form. The capability sits against the live property operating context, so staff can work from a controlled record rather than recreating the same information in personal notes, inboxes or local spreadsheets.
In practical terms, Building Features supports structured property and room information. Proplix gives that requirement a defined place in the workflow, making the current position easier to understand for the next person who opens the record.
Because Building Features lives in the same operating environment as the wider property record, it can support cleaner handovers. The user who updates the information and the colleague who relies on it later are working from the same context, even when they sit in different parts of the business.
Why this capability matters in day-to-day property operations
Property operations depend on many small decisions being interpreted consistently. When building features is handled informally, two members of staff can look at the same property and reach different conclusions about what the current record means or what should happen next.
That inconsistency grows with portfolio size. A workaround that feels manageable across a handful of properties becomes expensive when managers have to reconcile hundreds or thousands of records, explain differences, correct copied information or rebuild reports from local spreadsheets.
Using Building Features inside Proplix reduces that ambiguity by keeping the relevant information close to the property record. The objective is not to add another administrative step; it is to make the existing work more dependable, easier to hand over and easier to review later.
Where Building Features adds operational value
This section focuses on the practical operating context for this specific capability.
What the attribute tells the team
Building Features is a structured part of the physical property description. It should capture one clear fact about the room, building, lot, amenity or accessibility context so that another user can understand the property without relying on a long narrative note.
Where it adds value
This detail can matter at different moments: preparing a listing, answering an applicant question, reviewing suitability, checking imported property data or handing the record to another colleague. A structured value is easier to reuse than a fact buried in correspondence.
Quality check
Record only what is known, keep the terminology consistent and update Building Features if the property changes. If the information is uncertain, it is better to leave a controlled gap for review than to turn an assumption into a permanent portfolio fact.
How Building Features fits into the workflow
The exact screens and permissions depend on the user's role and the surrounding Proplix workflow, but the operating pattern remains controlled and property-centred.
- 01
Start from the correct property context
Open the property, relationship, request or workflow where building features belongs so the action starts from the right source record.
- 02
Confirm the required information
Review the fields, state or supporting context needed before the action is applied. This reduces avoidable corrections later.
- 03
Use the structured Proplix control
Carry out building features through the relevant workflow rather than relying on a free-text note or an external spreadsheet.
- 04
Check connected outcomes
Review any property, client, portfolio, document or reporting view that relies on the result so the wider record remains coherent.
- 05
Retain a reviewable history
Keep significant changes connected to the source record, making handover, audit and later operational review easier.
What this feature helps the team control
Structured attribute capture
Record building features as a reusable property attribute instead of burying it in narrative notes.
Listing reuse
Make the information available to listing and presentation workflows where appropriate.
Property review
Give managers a quicker understanding of the property's layout, amenities or physical characteristics.
Consistent terminology
Reduce different staff describing the same property feature in incompatible ways.
Downstream context
Keep the attribute available to other property workflows that rely on room or building detail.
Portfolio data quality
Improve the consistency of comparable property information across the portfolio.
What this looks like in practice
Imagine a team preparing a property for marketing while another colleague is checking suitability for a prospective occupier. Building Features gives both people the same structured fact from the property record. The listing team does not need to copy a note from one system, and the property manager does not need to ask the same question again.
Later, if the property details are reviewed or migrated, the attribute remains easier to validate because it has a defined place and meaning. Across a large portfolio this reduces repeated interpretation and helps the organisation keep property information more consistent.
Built for the people responsible for the property record
Building Features is designed for the authorised people who need to create, review, progress or rely on this part of the property operating context. Access should match the responsibility each role holds.
Use the feature with clear ownership and reliable source data
Building Features should be configured and used in a way that matches the organisation's operating model. Property businesses differ in how they define ownership, status, review responsibilities and handover points, so teams should agree the business meaning before applying the capability at scale.
Data quality remains important. A structured feature does not make inaccurate source information correct by itself. The strongest results come when authorised users keep property records current, use consistent terminology and correct exceptions close to the point where they arise.
Permissions should reflect responsibility. Staff who can change significant property information or workflow state should have the access required for their role, while stakeholders and other users should see only the information appropriate to their relationship with the property.
When Building Features feeds another workflow, teams should test the normal case and the main exceptions so downstream documents, reports and user views behave as expected.
Related features in Property & Portfolio Management
These related pages cover capabilities that sit close to Building Features in the wider property operating model.
Technical flow & related Help Centre guides
Start with the primary guide for this capability, then use the related maintained guides for the surrounding workflow, evidence, access or handoff.
Questions about Building Features
Where is Building Features used?
It is part of the structured property record and can provide context to relevant listing, management, applicant or review workflows where that attribute is needed.
Should the team also repeat this information in notes?
Notes can add context, but the core fact should be kept in its structured field where possible. That makes the information easier to find, compare and reuse.
What if the property detail is not known?
Do not turn an assumption into a property fact. Leave the value for review or follow the organisation's data-quality process until the information can be confirmed.
Does Building Features replace an inspection or professional assessment?
No. It records property information. Where an inspection, accessibility assessment or other professional judgement is required, the appropriate process still needs to be completed.
Explore how this capability fits your property operation
Proplix connects property records, people, workflow, evidence and management visibility. A walkthrough can focus on the areas that are relevant to your portfolio rather than a generic software tour.