Social landlords and in-house maintenance teams

A leak reported by a tenant, handled and tracked end to end

In one minute, follow a leak reported by a tenant: the job linked to the home, the plumber’s calendar, the job report signed on site, even with no signal, then the report in the landlord’s format. This is G-ordon, in action.

  • 1 min 05 s video
  • Subtitles available
Book a demo

Step by step

What you have just seen

From the tenant’s call to the report sent to the landlord: five steps, one tool for the office and the field.

  1. Log

    The request is logged

    The job is created at the office and linked to the right home, with its history.

  2. Schedule

    The visit is scheduled

    The scheduler drops the job into the technician’s calendar. The visit notice is generated automatically.

  3. Go on site

    The technician arrives prepared

    He has his calendar, the home’s history and the route, even without a network.

  4. Do the work

    A guided report, right the first time

    Questions adapt to the answers. Annotated photos and the tenant’s signature are collected on site.

  5. Deliver

    The report goes out by itself

    G-ordon fills in the landlord’s template and produces the PDF. Every action is tracked: who did what, and when.

What you gain

An in-house team that keeps its promises to tenants

What the film shows in one minute, your teams experience on every job.

The home, and its whole history

Every request is linked to the right home. The manager sees previous visits at a glance: a leak that keeps coming back is spotted before the technician is sent out.
A request linked to the home, and the job report filled in on the technician's phoneAssetsLes Tilleuls EstateBlock BUnit 214Leak under the sinkTenant requestUrgentOFFLINEJob reportVisible leak?Part replacedNo access?Submit

Even deep in a cellar

Calendar, history, route and job report remain available with no signal. Everything reaches the office as soon as the connection returns.
The network is back: the job report, photos and signature are sent automatically and reach the officeBACK ONLINESyncingJob reportSentPhotosSentSignatureSentAll up to dateOffice · job reports receivedManhole no. 12InspectionReceivedUnit 214InventoryReceivedPumping stationVisitReceived

The unexpected, handled on site

A loose wall tile, a seal to redo? The technician creates the job himself, already linked to the home: the office gets it at the next sync.
The message thread of a job between the office and the technician, and a new job created on site from the phoneJob threadOfficeDoor code: 4512TechnicianAnother leak on 2nd floorOfficePlease create it on siteONLINENewjobLocationBlock B, 2nd fl.TypeLeak detectionReported byTechnicianCreate

A report the landlord recognises

The report is produced from your Word templates, in Word or PDF, with the annotated photos and the signature. Every action is tracked: who did what, and when.
The job report filled in on the phone becomes a service report built on the organisation's template, with photos and signature, in Word or PDFJob reportWork carried outSeal replacedLeak fixedYesNext visitIn one yearYour templateService reportUnit 214 · Block BCustomer signatureWordPDF
01

The same process, with your documents

The film shows a leak. For you, it might be a front door, a ventilation unit or a lift. In G-ordon, a trade is a job type, a field form and a report template: they are configured from your documents, with no development.

The form follows the trade, not the other way round.

02

What we look at together during the demo

  1. Your assets: estates, buildings, homes and equipment, and how to bring them in from your files.
  2. Your job reports: conditional questions, annotated photos, signature, and the report produced from your Word templates.
  3. Your schedule: the in-house team’s calendar, visit notices, technicians working with no signal.
  4. Your data exchanges: the REST API and the imports and exports that let G-ordon talk to your housing management software.
Read the video transcript
  1. IntroductionA leak reported by a tenant. Let’s see how G-ordon handles it, from the call to the report.

  2. The request is loggedAt the office, the job is created in seconds, and linked to the right home, with its full history.

  3. The visit is scheduledThe scheduler drops it into the plumber’s calendar. The visit notice is generated automatically for the tenant.

  4. The technician arrives preparedThe technician has his calendar, the home’s history and his route. Even without a network.

  5. A guided report, right the first timeOn site, the report guides him. Questions adapt to his answers, he annotates his photos, and the tenant signs on screen.

  6. The unexpected is handled on siteSpotted another problem? He creates the job himself, already linked to the home. The office gets it at the next sync.

  7. The report goes out by itselfThe report goes out in the landlord’s format, as a PDF. And every step is tracked: who did what, and when.

  8. Ready to make the move?So, ready to take the next step? Book your demo at g-ordon.io.

Frequently asked questions

How does a tenant request become a job in G-ordon?
The manager creates the job at the office, in a few seconds, and links it to the relevant asset: estate, building, home or equipment. The tenant and the visit history appear straight away.
Does the visit notice follow if the job is moved?
Yes. The visit notice is generated automatically when the job is scheduled. If the job is moved or removed, the notice is replaced or withdrawn accordingly.
Can the technician report another problem during the visit?
Yes. From the field app, they create a new job, already linked to the home, with their photos. The office gets it at the next sync and schedules it like any other.
What does the landlord receive once the job is done?
A report in the landlord’s format, built from their Word templates and produced in Word or PDF. Reports can also be sent in bulk (ZIP archive or merged PDF), and the history of actions remains available.
Can we see this process with our own jobs?
Yes, that is the whole point of the demo: we start from your job types, your field forms and your report templates, and show you the process with your own use cases. Request a demo.

G-ordon, every day in the field

A platform that runs, every single day

Field teams and back offices rely on it every morning, with or without a network. Here is what that adds up to over a year.

1,500 different users every day
  • 250,000 requests processed per day
  • 90M requests processed per year
  • 20,000+ logins per month
  • 1 in 3 exchanges sent from the field app
  • 70 GB of field data received in one month

Measurements from the logs of the G-ordon production platform, all customers combined, from October 2025 to September 2026. Rounded values. Different users per day: all customer platforms combined.

Sovereignty

Your data in France, backed up in the EU

G-ordon has been designed and developed in Toulouse by Agiléo Solutions since 2018, and runs on French infrastructure.

Scaleway

Production in France

Hosted by Scaleway (iliad group) in its Paris region, on a hybrid infrastructure: Elastic Metal dedicated servers and Scaleway Elements cloud services.

One database per customer

Each customer has its own dedicated database; documents and photos are kept separate.

Backup in the EU

Backups are kept in Paris, with an emergency copy in the European Union.

Self-hosted maps

The OpenStreetMap base map is served from our own servers, as vector tiles.

A hosting provider committed to more sustainable digital services

  • Wind or hydro electricity, certified by guarantees of origin
  • Average energy efficiency (PUE) of 1.37, against an industry average of 1.55
  • No drinking water in the cooling towers
  • Refurbished servers, used for up to 10 years instead of 5 to 6

Source: Scaleway, 2024 environmental indicators for its data centres. scaleway.com

Our commitments on personal data

Ready to make the move?

Book your G-ordon demo, built around your own use cases.

Book a demo Agiléo Solutions · software publisher based in Toulouse · production in France, emergency backup in the EU