Transparency

Before making promises, we show how the work is held.

Alzette is built around a simple operating rule: every matter needs a source, an owner, a status, and a next action. This page shows the framework, screens, and reporting examples using anonymized sample data.

Frame

What can be checked without relying on sales copy.

Credibility is not only references. It also shows in how an organization documents commitments and makes operations legible.

Clear legal identity

The company is published as Alzette sàrl, with RCS Luxembourg number B308795.

Insurance available

The professional liability certificate can be shared as part of a takeover file.

Anonymized examples

The screens and extracts below use sample data. They are not customer references.

Resident app

The Alzette One iOS app shows residents what is happening.

Owners, occupants, and representatives can view their buildings, incidents, announcements, documents, notices, and proof of opening according to their rights. The screens below are native iOS screenshots using demo data.

Real iOS screenshot of Alzette One showing the resident portfolio

Resident portfolio

Residents choose the relevant building before opening incidents, documents, and access rights.

Real iOS screenshot of Alzette One showing the building home screen

Building home

Open incidents, announcements, documents, and quick actions are grouped in the native building view.

Real iOS screenshot of Alzette One showing incident follow-through

Incidents

Open reports, statuses, and exchanges remain visible inside the iOS resident space.

Real iOS screenshot of Alzette One showing resident documents

Documents and proof

Rules, notices, minutes, and proof of opening are available according to the resident's rights.

Alzette operations

On the operator side, matters are handled as work queues.

The goal is not to respond from a scattered mailbox. Incidents, AGMs, finances, and calls need structure so the team knows what is blocked and what should move next.

Anonymized screenshot of the Alzette operator incident view

Incident follow-through

Each matter keeps priority, status, source, and next action.

Anonymized screenshot of the Alzette operator financial view

Financial operations

Treasury, arrears, budget, and next actions are grouped in an operating view.

Reporting

Reporting models make follow-through readable again.

The examples below come from Alzette documentation models and have been turned into anonymized public extracts.

Anonymized extract from the annual syndic report

Annual syndic report

Commitment indicators, highlights, active contracts, claims, arrears, and outlook.

Anonymized extract from the annual statement

Annual statement

Cover letter, contents, indicators, and next steps before the AGM.

Anonymized extract from the incident ledger

Incident ledger

Source, category, priority, status, and next action to keep matters followed.

Operating targets

Concrete targets, stated conservatively.

These commitments are operating targets. They can be adapted in the mandate depending on size, urgency, access, and building constraints.

Urgent incident

Acknowledgement target within 2 business hours, with triage and first action based on criticality.

Standard incident

Acknowledgement target within 1 business day and documented next action.

Administrative request

Acknowledgement target within 2 business days, with routing to the right channel or document.

Board reporting

Monthly note on open matters for active mandates where a board is in place.

Every tracked matter should keep an owner, status, source, and next action. That is the basis of how we work.

Want to see how this would work for your building?

The transition diagnostic turns this method into your real context: available documents, open incidents, AGM, finances, and priorities.