Leonardo247 Glossary of Terms
Keep reading to learn more about some of the most commonly used Leonardo247 terms.
| Leonardo247 Terms | |
|---|---|
| Assigned User | A user who has been assigned via the menu option on an individual task OR a user who has been assigned via the template and is always assigned that task when it appears. |
| Attributes | Property characteristics such as location, amenities, and equipment. Attributes drive the Leo247 automation. |
| Automation | Leo247 matches the right tasks to the right properties at the right time automatically using several proprietary back-end codes, including attribute matching. |
| Category | Each template is put into a category for filtering and reporting purposes. The master categories are Accounting, Asset Management, Code, Commercial, Compliance, Leasing, Maintenance, Marketing, Operations, Risk Management, and Training. |
| Code Task | A task that has been created by the Leo247 proprietary AI tool that has scraped municipality’s websites for code updates related to a particular property based on geography. |
| Company Template | A template that is created at the company level to be used for that company’s properties. |
| Conditional Questions | A function of the dynamic form. Conditional questions can be delivered to the user based on answers to a previous question. |
| Dashboard Map | Map of the user portfolio with pin colors to identify properties that are compliant (green), working on compliance (yellow), or not compliant (red). |
| Document Manager | Library of all Dynamic Forms completed, sorted by Portfolio and Property, then based on type of form (action items), contracts, etc. |
| Due Diligence | Inspections performed before buying a new property. Typically, comprised of Unit-by-Unit inspections, Lease File Audits, and Exterior and Common Area inspections. |
| Dynamic Form | Digital form created to allow users to populate the fields on the form via Leo247 desktop or Leo247 mobile app. |
| Integration | Software components that “talk” to each other are said to “integrate”. Leo247 has active integrations with other software solutions. |
| Messenger | Chat functionality. |
| Mobile App | Leonardo247 app for smart devices (phone/tablet), available in the Google Play or Apple App Stores. |
| Code Task | Patented machine learning algorithm that sources and catalogs federal, state, and city municipal codes that govern real estate operations. |
| My Reports | Reports located in Leonardo247, run with filters that a user can save to run again later on demand. |
| On Demand | A section of Leonardo247 for resources on demand, such as Leonardo247 training materials, recordings. Can be updated with SDS sheets, and any other resource client would like to have available for users. Searchable by key word. |
| Permanence | How long the task will stay on the workspace if left incomplete. Based on criticality and importance. Pre-set when creating templates. |
| Pin Color | Green is compliant and current on tasks, Yellow is working towards compliance and behind on some tasks, and red is not compliant and behind on most or all critical tasks. |
| Portfolio | A portfolio is how the properties are primarily organized within Leo247. Each property is assigned to 1 portfolio. A portfolio is created for each RPM. This is the required organization. |
| Priority | Task templates have a priority pre-set, the options are “critical”, “normal”, “minor”. This priority is taken into consideration in the Leo247 automation. |
| Property Group | A property group is another way to organize properties, outside of portfolios. A property can be included in any number of property groups. This is optional organization. |
| Property Template | A customized template that is created at the property level to be used. |
| Quick Reports | Various reports pre-set by the Leo247 team for on-demand reports. |