01 Overview
Reporting is a by product, not a project
Most property reporting is archaeology. Someone exports a list from the CRM, another from the property management system, pastes both into a spreadsheet that has been inherited twice, reconciles the differences by hand, and produces a picture of a month that ended two weeks ago. By the time it is read, it describes a portfolio that no longer exists.
The problem is not the spreadsheet. It is that the underlying work was never recorded in a consistent form in the first place, so the numbers have to be reassembled from fragments.
When Fashti is running the workflows, the recording happens at the moment of the action. An inquiry answered, a viewing confirmed, a document received, a work order closed, a payment reconciled: each one writes a dated, structured record against a unit and a tenancy. The portfolio view is a direct read of that, not an interpretation of it.
- Centralised portfolio metrics drawn from every workflow, not re entered.
- Current rather than monthly, so a problem is visible while it is still small.
- Drill down from portfolio to unit without changing tool or export.
- Owner reporting on a schedule, in a format you have approved.
Portfolio overview
Current
Occupancy
Tracked live
Time to lease
Trending down
Open work orders
12 active
Rent position
Reconciled
Portfolio activity, this week
Written as the work happens
Exportable
An illustrative portfolio view
02 The views
Four altitudes, one set of numbers
The same records, read at the level the question is being asked at. Nothing is recalculated differently between views.
01
Portfolio
Occupancy, pipeline, arrears position, open maintenance and workload across everything you manage, with the trend behind each figure.
02
Property
The same measures for one building or scheme, which is where differences in performance actually show up and where an owner's questions land.
03
Unit
One timeline per unit: every tenancy, inquiry, viewing, repair, inspection and payment, in order, with the documents attached.
04
Team
What was handled automatically, what was escalated, how long exceptions waited and where the remaining manual load sits.
03 What is measured
Definitions matter more than dashboards
Every measure below is defined once, in writing, and calculated the same way every time it appears. Most reporting arguments are really definition arguments.
| Measure | How it is defined |
|---|---|
| Occupancy | Units with an active tenancy as a share of lettable units, measured daily, excluding units you have flagged as deliberately held back for works. |
| Days on market | From the date a unit becomes available to advertise to the date an agreement is signed, not to the date a viewing happened. |
| Time to first reply | From the arrival timestamp of an inquiry to the first substantive response, counted around the clock rather than in office hours. |
| Inquiry conversion | Inquiries progressing to a confirmed viewing, and viewings progressing to a completed application, reported as two separate steps. |
| Renewal rate | Tenancies renewed as a share of those that reached a renewal decision in the period, with the reason recorded where a resident declined. |
| Arrears ageing | Outstanding balance by tenancy, bucketed by age, with the next scheduled action and the date of the last contact attempt. |
| Time to resolution | From a maintenance request being reported to the resident confirming it is resolved, not to the contractor marking it complete. |
| Automation share | The proportion of inbound interactions closed under policy without a person, reported alongside the escalation rate so the two are always read together. |
04 Owner reporting
The report that used to take two days
If you manage property on behalf of owners or investors, reporting is not an internal nicety. It is the product.
On a schedule
Monthly, quarterly or on a date each owner prefers, produced automatically from the same records your own views read. No separate export, no second version of the truth.
In your format
Your template, your sections, your commentary headings and your branding. The structure is agreed once during onboarding rather than negotiated every month.
With the detail attached
Occupancy and rent roll, leasing activity, maintenance spend by category, open items, and the unit level history behind any figure an owner asks about.
Reviewed before it is sent
Owner reporting is a relationship, so it is drafted and queued rather than sent blindly. A person reads it, adds the commentary that needs a human, and releases it.
05 Honest numbers
What we will not do with your data
Reporting is where software is most tempted to flatter itself. These are the rules we hold the reporting layer to.
01
No vanity measures
We do not report messages sent or tasks touched as though volume were an outcome. Every measure has to connect to vacancy, cost, resolution or risk.
02
Escalations reported in full
The share of work Fashti could not handle is shown as prominently as the share it could. A rising escalation rate is information you need, not a number to hide.
03
Baselines taken first
Your own figures are measured during the shadow period before any workflow goes live, so improvement is compared against your actual starting point.
04
Gaps shown as gaps
Where a connected system cannot supply a field, the view says so rather than estimating. An empty cell is more useful than a confident guess.
05
Your data stays yours
Your operational data is not pooled into a benchmark product, sold on, or used to train models for other customers. It is exportable at any time.
06
Definitions published
Every measure in your views carries its definition. If a figure moves because a definition changed, the change is dated and visible.
06 Questions
About analytics and reporting
Can we get the data out?
Yes. Everything Fashti records is exportable in a structured format, on request or on a schedule, so you can load it into your own analysis, warehouse or board reporting. There is no commercial reason for us to make your records difficult to retrieve, and we do not.
Does it replace our property management reporting?
No, and it is not meant to. Your property management system remains the financial system of record, and its statements remain authoritative for accounting. Fashti reports the operational layer: speed, conversion, workload, resolution and the activity behind the financial figures.
What if our two systems disagree on a number?
The disagreement is surfaced rather than resolved silently. Fashti shows both values, where each came from and when each was last updated. Reconciling a conflict is a decision about your records, which means it belongs to a person.
How far back does reporting go?
From the day the relevant workflow goes live, in full detail. Historic data held in your existing systems can be read for context during onboarding, but we are deliberately careful about presenting reconstructed history as though it were measured, because the collection method was not the same.
Start the conversation
Bring us your month end
Show us the report your team assembles by hand and the sources it comes from. We will tell you which parts would write themselves and which would still need a person.
We read every message and reply within one business day