Knowledge base for garden and landscape constructionwhen someone out on site asks about the planting list and the irrigation plan.

You can ask about what is on that night’s job slips — property, date, time, driver, gritting material — and the answer cites the slip as its source. If the system finds nothing for that night, it says so; you can work with that too, it is just less pleasant. The time is the point here: in built-up areas, the duty to clear and grit the pavements along a property under § 93 of the Austrian Road Traffic Act (StVO) falls in the first instance on the owner, between 6 a.m. and 10 p.m.; it can be transferred by contract. What you actually took on is in the winter service contract — if it is in the knowledge base, it can be queried at the same time.

Once the pages are scanned, they can go in; how well the handwriting is read, a demo with a few real pages will show. Anyone who uses plant protection products professionally must keep records of every application and retain them for at least three years: product, time, quantity, area treated and crop. Since the beginning of 2026, the authorisation number, the EPPO code of the crop and the growth stage have been added, and from 2027 the records must be kept electronically. The knowledge base is not record-keeping software and doesn’t pretend to be one: it makes the pages you already have searchable, and if the system finds no entry for a property and period, it says so. Add the plant protection certificate of competence while you are at it — it is valid for six years, and who is due for further training when is otherwise yet another question nobody can answer.

The argument usually starts one step earlier, with the question of who owes it at all: under the contract standard ÖNORM B 2241, establishment maintenance and development maintenance are two different services, and whether they are yours has to be agreed. What was agreed is in the bill of quantities and the handover record; what was actually done is on the job slips and the photos. Asked about the property, the answer gives both, with the dates of the individual visits and the source for each, as far as it is in the knowledge base. The contract is not assessed — what is shown is what it says, and from there on you discuss with something in hand.

Through what happens anyway: photos from the property and voice notes from the vehicle. A spoken note after a job — which valve is sticking, which shrub needs replacing, where the shaft lies under the lawn — is transcribed and assigned to a property; how well that works with engine noise and dialect, you try out in the demo. Someone in the office confirms the document type once, because visibility depends on it: the winter service contract isn’t everyone’s business, the planting plan is. When a foreman leaves, his role is withdrawn, and with it his access ends.