Record relevant changes when they happen.
A furnished property changes over time.
A stain appears. A remote goes missing. A hinge is repaired. An appliance is replaced.
These changes become important later, when someone needs to know what happened, when it was recorded, and what evidence exists.
Mono follows a simple principle:
Anything that may later affect the understanding of the property, an issue, or responsibility should be put on record when it happens.
Chats and tasks lose context.
A task app can show that an inspection was completed. A chat can contain a photo of damage.
But neither automatically connects that information to the item, its earlier condition, the person who recorded it, and the inspection in which it was found.
As conversations grow and tasks are closed, that context becomes difficult to recover.
Mono records relevant changes where they belong: on the property, the item, and the inspection.
The inventory records each change.
The record begins when an item is added to the inventory.
Each space, fixture, surface, and movable item has its own entry.
When an administrator edits an item or an inspector updates it, Mono adds a new entry to its status history instead of replacing the previous state.
Condition, cleanliness, quantity, notes, evidence, date, and source remain connected to that change.
The current value can evolve without erasing how it reached that state.
Let evidence accumulate.
Evidence is most useful when it remains connected to the exact observation it supports.
Photos and notes should not sit separately in a chat, folder, or maintenance ticket while the inventory shows only the latest rating.
Mono keeps them together inside the item’s status history.
Evidence can accumulate across inventory work and inspections.
When an item returns to its best rating, evidence attached to its current status can be reset because it no longer describes the present condition.
The earlier history remains. The old rating, note, and evidence stay connected to the entry in which they were recorded.
Every inspection creates a condition report.
The status history records changes item by item.
The condition report records the complete inspection.
It identifies the property, inspection type, participants, completion date, and scope. It shows what was confirmed or updated across condition, cleanliness, and quantity, together with issues, notes, photos, timestamps, signature, and available location information.
The report does not merely show that the inspection was completed.
It shows what the inspection established.
Ratings describe. Issues require attention.
Ratings record the observed state of the property.
Issues isolate what may require action and distinguish between problems that already existed and those first identified during the current inspection.
That difference matters when responsibility or costs are discussed.
Mono does not deduct deposits, assign liability, or decide who should pay.
It records the condition before and after, the issue, the timing, and the evidence so the responsible people can decide what follows.
Keep the report connected and usable.
Inspection results become part of each item’s status history, and history entries link back to the reports that created them.
Someone can begin with an item, see when its condition changed, and open the relevant inspection.
Or they can begin with the report and review the complete property at that moment.
Every Mono report is available as an interactive web report and as a downloadable, print-ready PDF that can be shared, printed, archived, or used when facts are disputed.
Completed reports must remain intact.
Mono will continue to change.
The interface, terminology, inspection rules, and inventory configuration may develop over time. Completed reports should not change with them.
Each report preserves the inventory state, photos, evidence, and inspection configuration used to create it.
Reports are stored in the cloud using Google Firebase, while Mono’s architecture keeps the interactive report and its underlying data independent from future product changes.
The PDF provides an additional fixed copy outside the application.
Nothing relevant should disappear.
A property may be inspected at every move-in and move-out, once per quarter, or when it first enters management.
The frequency can vary.
What matters is that each inspection adds a clear, dated record to the property’s history—one that can still be opened, understood, and used later.
Put everything on record.