Documents
A document management system that knows what each file is for.
A property business runs on documents with deadlines: energy certificates, mandates, leases, inventories, insurance policies, invoices, identity papers. Stored in folders they are just files. Stored against an object with a type and an expiry date they become a compliance system.
In REOS every document is attached to a property, a unit, an owner, a tenant, a mandate or a ticket. It has a type, a version, permissions and, where relevant, an expiry date that produces alerts before it becomes a problem. Electronic signature closes the loop so a mandate can be signed without leaving the platform.
What it does
- Attachment to any object, with the type driving the required fields.
- Versioning, so a superseded lease is kept without confusing the current one.
- Expiry dates and renewal alerts for certificates and policies.
- Electronic signature requests with status tracking.
- Granular permissions, including what an owner or tenant can see.
What it automates
- An energy certificate expires in sixty days and a renewal task is created on the unit.
- A signature request is completed and the mandate becomes active with the signed file attached.
- A required document is missing when a listing is about to publish and the publication is held.
Records behind this module
These are the actual tables in the platform. Every other module reads the same rows, which is why nothing needs reconciling.
Metrics it produces
- Documents expiring
- Signature turnaround
- Compliance coverage
- Storage per unit
Frequently asked questions
Where are the files stored?
Can we bulk import an existing folder structure?
Ready to see it on your own portfolio
A demo runs on a structure that looks like yours: your unit count, your mandate model, your portals. Forty five minutes, no slide deck.