Practical guide
How to set up a log of condominium owner requests
A request log is the orderly register in which every owner query, report or complaint is recorded at the moment of receipt, with an identifier, a date and the essential data. It is the tool that turns a chaotic flow of calls, emails and messages into a searchable archive where nothing is lost and everything can be reconstructed. For the manager, the log is not bureaucracy: it is the basis of traceability, the proof of diligence in management and the starting point for assigning priorities, monitoring times and communicating progress. Setting it up requires a few clear rules, applied consistently from the very first contact.
Checklist for setting up the log
- Assign each request a sequential number or a unique identifier
- Record the date and time of receipt and the channel of origin
- Note the owner, the building and the unit concerned
- Describe the subject concisely and understandably
- Funnel scattered channels towards a single collection point
- Update the record at every change of status through to closure
What logging requests is for
Logging means giving every request a stable identity from the moment it arrives. Without a log, the same report may be remembered by one collaborator and ignored by another, or handled twice, or forgotten entirely. The sequential number and the date of receipt fix a reference point everyone can return to.
The log also has evidential value. If an owner claims to have reported a problem months earlier, the register says exactly whether and when the request arrived. This certainty protects the manager from accusations of inertia and, at the same time, lets them recognise the requests that have genuinely fallen behind, in order to recover them.
The essential fields of the register
An effective register need not be complicated, but must be complete in the data that matters. Each record should contain a unique identifier, the date and time of receipt, the channel the request came from, the owner's name, the building and unit concerned, a concise description of the subject and the processing status.
To these basic fields are added, as the case advances, the person responsible, any supplier involved, the intervention dates and the closure date. The rule is to note at the moment, not from memory: a field filled in when the request arrives is worth far more than a reconstruction attempted days later.
- Unique identifier or sequential number
- Date, time and channel of receipt
- Owner, building and unit
- Concise subject of the request
- Processing status and person responsible
- Supplier, intervention dates and closure
Funnelling channels towards a single point
The enemy of the log is the dispersion of channels. If requests arrive on three different emails, on a personal phone, on messaging apps and verbally during meetings, logging everything becomes impossible and something always slips through. The first step is to reduce the entry points and funnel them towards a single collection channel.
This is not about banning the other routes, but about establishing that every request, from whatever channel, is entered in the register before being worked on. A received phone call is noted, a message is transcribed into the log. The single collection point does not eliminate the channels, it makes them converge into a single shared memory.
From register to priority management
A well-kept log is the precondition for everything else: assigning priorities, monitoring response times, communicating progress, measuring satisfaction. Without a complete register, these steps rest on partial data and produce unreliable results. With the register, instead, every analysis stands on a solid and continuous basis.
The log also lets you read the activity as a whole: how many requests arrive in a period, how long they stay open, which themes recur. This information helps organise the work and justify any requests for resources or fee adjustments, anchoring them to real figures rather than impressions.
The digital log with management software
A paper register or a spreadsheet works for a few buildings, but struggles when requests grow and must be consulted by several people. Management software turns the log into a digital archive that automatically numbers requests, tracks their status and keeps the history per building and per owner.
AmministraPro lets you record each request as a traceable case, with status, person responsible and chronology, so the log becomes a natural part of the workflow rather than a separate obligation. The features are described on the /funzioni page and the plans on the /prezzi page, with solutions suited to portfolios of different sizes.
Frequently asked questions
Is the manager legally obliged to log requests?
The Italian Civil Code does not impose a formal log of ordinary requests, but the duties of diligence and accountability set out in Articles 1129 and 1130 make traceability a highly advisable practice. An orderly register demonstrates correct management and protects the manager in the event of disputes, as well as making the work more efficient.
What is the difference between a log and a simple list of emails?
A list of emails is scattered and hard to consult, whereas the log assigns each request a unique identifier, a certain date of receipt and an updatable status. The log unifies different channels into a single structured register, making every request reconstructable, while emails remain fragments scattered across inboxes and folders.
Should I log requests received verbally or by phone too?
Yes. A request received verbally or by phone should be entered in the register like all the others, noting the date, owner and subject. It is precisely on informal channels that most requests are lost: transcribing what arrives verbally straight into the log is the most effective way not to forget it and to keep a record.
How many statuses should the register include?
Few and clear. An effective scheme distinguishes receipt, taking in charge, processing, any wait for third parties and closure. Too many statuses confuse and discourage updating; a few well-chosen ones suffice to say where the case stands and who has to make the next move, keeping the register simple to maintain.
Does software make a paper register unnecessary?
Management software not only replaces it but improves it: it numbers requests automatically, tracks their status and keeps a history consultable by several people. AmministraPro records each request as a traceable case with status and chronology. The features are described on the /funzioni page and the plans on the /prezzi page.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.