How to read this documentation
This documentation is built for two types of use: read-through learning when you start with Lumos, and point lookup when you are searching for the answer to a specific question.
Organization in parts
The documentation follows the learning path of an inspector adopting Lumos:
- Part I — Foundations: welcome, account configuration, platform tour.
- Part II — Native apps: Lumos Capture (iOS, Android coming).
- Part III — The inspection cycle: engagement preparation, field capture, writing, compliance, delivery.
- Part IV — Business management: contracts, invoicing, project management.
- Part V — Customization and team: libraries, team, preferences.
- Part VI — Reference: subscription, privacy, troubleshooting, glossary.
If you are just starting with Lumos, follow the order of the parts. For a specific question, use the search bar or the Lumos chatbot integrated in the documentation; it answers your questions based on this content.
Levels
Each page carries a reading level label:
- Beginner — you are discovering Lumos. No prerequisite.
- Intermediate — you master the basics and explore more advanced features.
- Advanced — for experienced inspectors who customize deeply or manage a team.
Most pages are beginner level. Advanced pages are flagged at the top.
Page types
Three formats coexist:
- Tutorial — a step-by-step flow, often paired with a video, to learn a procedure (for example: Configure your profile).
- Concept — an in-depth explanation of the why and the how of a feature or principle (for example: AI philosophy, BNQ standard).
- Reference — a descriptive sheet (glossary, keyboard shortcuts, release notes) consulted occasionally.
Visual conventions
- Bold terms in prose: interface elements or official terms (example: Narrative Bank, Severities).
- Italic terms: literal quotes from interface elements or screen titles.
- Links: cross-references to other pages of the docs, or external resources (BNQ, RBQ, AIBQ, etc.).
- Callouts: Info (useful note, non-critical), Warning (frequent pitfall), Error (irreversible action).
- Screenshots: illustrate elements described in the text; organized by surface (Web, Web Mobile, Capture).
The glossary
For any term unfamiliar to you (BNQ 3009-500, client, severity, narrative, narrative bank…), the glossary at the end of the documentation lists all definitions, in French and English.
How to report an error or a gap
If you find an error, a poorly defined term, an outdated procedure, or a missing topic: use the Comments button available in Lumos, or write to us at support@lumos.property. The documentation evolves with the product; your feedback helps us keep it up to date.