Lookup instead of typing
Building, unit and tenant are searched in your database and carried over into the form. No retyping, no transposed digits.
Integration
Connected to your database, not locked into an ecosystem
A handover app that does not know your data simply moves the typing from paper to a tablet. What matters is access to the records you already keep, independently of which vendor supplied them.
- Lookup directly from Oracle, MS SQL and MySQL
- Sign-in via Active Directory / SSO
- No lock-in to a particular management suite
- Reports return as PDF and as an Excel export
- Runs on-premise or online
- Form logic reads your own master data
Technical facts
3
database systems supported: Oracle, MS SQL, MySQL
AD / SSO
sign-in through your existing directory
100 %
of data in your own house when run on-premise
Why the database connection is the real differentiator
There are plenty of forms apps, and most of them can take photographs and capture signatures. The difference shows up at the third step: where does the data come from, and where does it go back to?
Without integration, the manager types the address, unit number and tenant name into a tablet on site. That is the same effort as on paper, only in better handwriting, and it carries the same risk of error. What comes out is a PDF that somebody then has to file into the tenancy record by hand.
With integration, the manager picks the property from a list that comes out of your own system. Tenant details are prefilled, the unit is unambiguously identified, and the finished report returns as structured data. That is the point at which digital capture actually saves effort rather than merely relocating it.
Supported databases
The lookup function reads directly from common relational databases:
- Oracle, widespread in larger housing companies and established ERP systems
- Microsoft SQL Server, the standard in many mid-sized management firms
- MySQL, frequently found behind web-based and smaller systems
Access is read-only, against views or tables you define. Which fields are carried over is your decision, typically the property name, address, unit number, floor, tenant name and contract details.
Because the integration happens at database level it is not tied to a particular management product. What matters is that you have access to your own database, not which application sits on top of it.
Sign-in via Active Directory and SSO
A separate user administration is a reliable source of errors in practice. Accounts get created and then forgotten when people leave. That is exactly why sign-in can be tied to the directory you already run.
Staff sign in with their familiar credentials. Permissions follow the groups you maintain anyway. And when an account is disabled, access to reports and tenant data ends with it, without anyone having to think about it.
For firms working with external service providers, such as caretaking companies, access can be scoped accordingly.
What comes back out of the app
The return path matters as much as the way in. Completed reports are available in two forms.
The PDF is the document for the tenant, the file and the archive, with every entry, photograph and signature in its final state. It is generated and distributed automatically.
The Excel export delivers the same content as analysable data. That answers questions a PDF archive cannot: how many handovers took place this quarter, which categories of defect keep recurring, how long an inspection takes on average.
This is precisely what separates documentation from data capture. A folder of PDFs answers no questions. Structured data does.
What the integration actually delivers
Central user administration
Sign-in via Active Directory or SSO. When someone leaves the company, access ends with the account.
Structured return path
Reports come back not only as a PDF but as data you can analyse, via Excel export.
Vendor independent
The integration works at database level rather than through a proprietary module. Changing management software does not force you to change systems.
Data-driven forms
Dropdowns and prefilled fields feed from your master data instead of from maintained copies.
Encrypted transmission
Data exchanged between device and server is encrypted, whichever operating model you choose.
Frequently asked questions
Do we need a particular management software?
No. The integration works at database level rather than as a module of one specific product. The requirement is read access to your records in Oracle, MS SQL or MySQL. Which application sits on top is largely irrelevant.
Does eMODAT write back into our database?
The lookup is read-only. How finished reports flow back into your systems, as a PDF in the tenancy file, as a data export or through an agreed route, is defined during setup. Your leading system stays the leading system.
Does the lookup work offline?
Capture itself needs no connection. Data is stored locally and synchronised later. A live lookup against the database naturally requires connectivity, which is why the master data needed for an appointment is loaded onto the device beforehand.
Is the lookup included in every package?
The lookup function is part of the Ultimate edition and of the on-premise variant. It is not included in the smaller packages.
Let us look at your environment
Which database, which fields, which sign-in route. We clarify that in a short technical conversation before anything gets installed.