Platform
Construction projectsCAPEXFinancePreventive maintenanceCorrective maintenanceInternal auditsEnergyLegal & shareholdingSuppliers & procurement See all modules
Industries
HospitalityRestaurantsServiced residencesHealthcareFranchise networksIndustry & logisticsReal estate funds See all industries
Roles
ExecutivesCFOAsset ManagerTechnical DirectorProject ManagerSite ManagerTechnicianLegal CounselProcurement Manager See all roles
Let's talk AI About Contact Request a demo

Module

Reported in a few taps,resolved and logged.

Housekeeping, front desk or maintenance: anyone can report an issue from their phone or the web, with a photo. The technical team is notified, takes it on and closes it, and every lead time is measured.

Request a demo
GET17 · Corrective maintenance
New work request: illustrated quick actions, zone, sub-zone, equipment and photo.
iOS · Androidmobile reporting app that also works offline
5color-coded statuses, from Requested to Closed
18statistical groupings: zone, equipment, hour, lead time…

The problem

A breakdown reported by word of mouthis a breakdown forgotten.

  • Issues go through the logbook, a phone call or a chat app, and get lost between shifts.
  • Nobody knows who is handling an issue, or how long it has been waiting.
  • Repeat failures in a room or on a piece of equipment go unnoticed.
  • Without history, there is no way to measure the technical team's workload or justify a replacement.

Features

Corrective maintenanceReported from a phone, handled, resolved and logged: every breakdown counts.

Android / iOS mobile app

Requests filtered in one tap (open, my tasks in progress, on hold, my reports…), with creation, pickup and closing right from the field.

Instant reporting

Illustrated quick actions pre-fill the request; you just add the origin (guest or staff), zone, sub-zone and a photo.

Even without a network

Offline, the request is kept on the phone, flagged as pending sync, and sent at the next sync once the connection is back.

Technical team notified

On creation, the property's designated members are notified. No dispatching needed: the technician who takes the request becomes its owner.

Resolution tracking

Requested, In progress, On hold, Closed, Cancelled: every change is timestamped, and response and resolution times are calculated automatically. Reopen if the issue comes back.

Work history

Photos, files and comments stay attached to each request, even after closing, and the filtered list can be exported at any time.

Analytics view and statistics

Breakdown by status, origin and equipment type; statistics by property, zone, equipment, day, hour or lead time, normalized per room.

Configurable zones and quick actions

Zones and sub-zones imported from Excel, quick actions enabled per property, and a maintenance, front desk or housekeeping designation for each member.

The video

Corrective maintenancein 86 seconds.

No voice-over; on-screen text in French.

How it works

From breakdown to decision,with nothing lost on the way.

Report

From the app or the web: quick action, zone, sub-zone, comment and photo.

Alert

The request is set to Requested and the property's technical team is notified.

Fix

A technician takes it on, comments, puts it on hold if a part is missing, then closes it.

Log

Every step is timestamped; response and resolution times are calculated.

Analyze

The analytics view and statistics reveal peak times and team responsiveness.

Decide

Recurring issues by zone or equipment guide preventive maintenance, replacements and CAPEX requests.

On screen

The application,as your teams see it.

GET17 · Corrective maintenance
A closed request: timestamped steps, response and closing times, photo and comments.
A closed request: timestamped steps, response and closing times, photo and comments.
GET17 · Corrective maintenance
The analytics view: requests by status, origin and equipment type, with their timeline.
The analytics view: requests by status, origin and equipment type, with their timeline.
GET17 · Corrective maintenance
Work request statistics, compared by property and by year.
Work request statistics, compared by property and by year.

Our approach

Built for the field,used by head office.

Reporting takes a few taps for teams on the move, yet every request is structured: property, zone, equipment, origin. That is what lets head office analyze every request across the group and connect breakdowns to the rest of the portfolio.

01

Shared master data

Zones, equipment families and users are those of the whole platform: a breakdown connects to the equipment inventory and its renewal plan.

02

No dispatching to manage

The property's whole technical team sees the requests; whoever takes one becomes its owner, and statistics track each person's activity.

03

From patterns to decisions

A room or piece of equipment that concentrates failures stands out in the statistics, supporting a preventive inspection or a CAPEX request.

What makes the difference

What matterswhen you choose.

Field adoption

Illustrated quick actions, mobile entry, photos taken from the phone: reporting is within reach of every team.

Full audit trail

Requester, owner, dates and lead times of each step, photos and comments: a reliable history, useful for disputes or guest complaints.

Measured responsiveness

Response and resolution times calculated automatically and analyzed by property, day, hour or user.

Property-level permissions

Reporting, handling and configuration rely on permissions specific to each property.

Comparable across sites

A per-room ratio to compare properties of different sizes, exports of lists and statistics. 100% web, in 6 languages.

Frequently asked questions

Corrective maintenanceyour questions.

Do we need to install an app?

Not for the web version, which runs in any browser. The GET17 mobile app for iOS and Android is recommended for field teams: direct photos, simplified entry and offline use.

Who is notified when a request is created?

Property members with the relevant designation, such as the technical team, are notified. New requests also appear in the home-page tasks of the users concerned.

Can a request be assigned to a specific technician?

There is no named assignment: the whole technical team sees the request, and the technician who clicks “Take charge” becomes its owner.

How do we spot a room with repeated failures?

Filter the list by zone or sub-zone, or group statistics by zone, sub-zone or equipment: recurring issues stand out immediately.

Are requests linked to the rest of the portfolio?

Yes: a request can specify the equipment family and item concerned. The report is thus linked to the equipment inventory and informs preventive maintenance and CAPEX decisions.

Can quick actions be customized?

Yes. Default quick actions are provided; your managers adapt them and enable them for the whole group or property by property.

Follow a request end to end

We'll show you the full journey, from reporting on a phone to analysis at head office, with your own zones and teams.