What Dardaris is
The job Dardaris does, the job it leaves to you, and how to tell the two apart.
Updated
On this page
Dardaris does the work a property manager does. It chases rent, reconciles the bank feed, triages repairs, answers tenants in their own language, indexes leases, runs short-stay turnovers and files the paperwork. You supervise. You do not operate.
That distinction is the whole product. Everything below follows from it.
What it does on its own
Most of the day-to-day runs without you. Rent reminders go out, receipts are issued, a payment that arrives with a structured reference is matched to its invoice, a guest gets the check-in instructions at the right hour, a cleaning slot is booked between two bookings.
Each of those is a workflow, and each workflow has a trust level you set. See what runs on its own.
What it brings to you
Anything that spends your money above your cap, ends a tenancy, sends a formal notice, deducts from a deposit or raises a rent stops and waits. It arrives on the front desk with the reasoning attached and the record it came from.
Read autonomy tiers and spend caps for how that line is drawn, and change it whenever you like.
What it will never do
It will not tell you something it cannot trace to a record in your portfolio. If a figure is not in the data, Dardaris says so rather than estimating. A manager who rounds up a quiet morning is one you stop believing on a loud one.
What it is not, and what stays yours
Dardaris is software, not an estate agency. It holds no professional licence, nothing it produces is legal or financial advice, and the responsibility for your property stays with you.
It is not a managing agent, a syndic, a lawyer, an accountant or a tax adviser either. Where the law where your property sits regulates letting or property management, the person doing that regulated work is you, or the professional you engage. A jurisdiction pack applies a rule consistently; it does not decide anything about a person, and a screen that shows you a figure has not chosen anything on your behalf.
The product is built around that rather than in spite of it. Every workflow carries a trust level, anything with real consequence stops and waits for you, and every step is written down with the rule that fired it. You supervise, which is another way of saying the decisions and the responsibility for them are yours.
So set the limits to match what you are willing to answer for. The defaults are a starting point, not a recommendation. Decide how much a repair may cost before you want to see it first. Decide whether a reminder reaches a tenant without you reading it. Decide what should never move on its own. Anything you leave running unattended runs on your instruction, and the audit record will say exactly that.
Two things follow from this and are worth reading before the first real tenancy goes in. The practical version is autonomy tiers and spend caps. The contractual version is clause 3 and clause 12 of the terms.
Where to start
- Put a building in. Your first building.
- Put a lease on a unit. Your first lease.
- Walk in the next morning and read the briefing. The front desk.