Vigenza

Compliance calendars: when can an obligation be marked complete?

· Redazione Vigenza

Draft date: 8 November 2026. Author: Vigenza Editorial Team.

An obligation can be marked complete when the required activity has been performed and the file contains evidence consistent with that activity. A tick in a calendar only demonstrates that someone changed a status. Before closing an entry, check what its source required, who needed to act and which document allows the outcome to be reconstructed.

This guide proposes an organisational method for regulated and unregulated businesses. It does not introduce a single legal procedure or establish that a particular attachment is always sufficient. Requirements for form and retention depend on the obligation, the legislation and the commitments applying to the company.

Turn the deadline title into a verifiable activity

“Privacy” or “annual review” are too broad to establish whether work is finished. The entry should describe an action: review a procedure, approve a document or submit a communication. If different people own these stages, connect them without treating preparation and approval as the same event.

Associate the entry with its source: an applicable provision, clause, resolution or internal policy. Give the precise reference and version of the document from which the activity follows. This makes it possible to verify the content without relying on the memory of the colleague who entered it. If applicability is uncertain, keep the entry awaiting assessment rather than turning an assumption into a definite obligation.

Define the evidence before starting

Ask what document should remain after execution. For a submission, the text sent and evidence of the channel used answer different questions. For approval, a prepared draft does not demonstrate approval by the competent body. Select evidence according to the required action, without accumulating unrelated attachments to make the file look complete.

Also determine who checks closure. In small organisations this may be the person performing the activity where permitted; for more sensitive work the procedure may require a separate reviewer. Do not present an organisational separation as a universal legal requirement unless it has been verified in the relevant source.

Distinguish the external deadline from internal stages

A calendar may contain a statutory date and an earlier date chosen by the business for collecting materials. Keep them separate. Changing an internal preparation date must not appear to extend the external deadline. When a deadline depends on an event, record that event and the calculation method, checking the applicable rules.

Assign an owner and cover for absences or handovers. A reminder sent to a general address does not ensure anyone is working on the task. If the owner changes, preserve continuity in the file: the new person should find the actual status and missing items, rather than simply a list of notifications received.

Check the connection between activity and document

Before closure, open the attachment. Verify that it concerns the right company and period. Check whether it is the final version or a draft with unresolved comments. A correctly named file can contain information from another financial year. The existence of a link does not demonstrate that its contents are relevant.

If the evidence is a message or receipt, retain enough context to identify its subject and recipient. Avoid circulating unnecessary personal information in the calendar: a reference to a restricted file, accessible to those who need it, is often sufficient. Ease of retrieval must coexist with access limitations.

A fictional example of premature closure

The imaginary company “Lago Servizi” schedules a review of an internal policy. Its owner uploads a new text and marks the task complete. A check then reveals that the policy requires board approval and that the uploaded document is only the proposal for the next meeting.

The entry returns to its correct status: preparation finished, approval still open. After the meeting, the reference to the minutes is linked and the approved version identified. The example illustrates an operational distinction; it does not claim that every policy needs board approval. The required stage follows from the source applying to that fictional company.

Handle delays and errors without rewriting history

If an activity is completed after its deadline, preserve the actual dates. Retrospectively moving the calendar can make the delay and its cause impossible to understand. Record the corrective action and assess possible consequences under the relevant rules. An internal note does not erase non-compliance or replace a mandatory communication.

When an attachment is wrong, link the correction and explain which document should be used. Avoid parallel copies without identifying the current version. Periodic calendar review should sample some closed entries to establish whether the method works in practice and whether owners can actually find the documents referenced. Sampling is an organisational choice here, and its extent should reflect the activities concerned rather than a percentage presented as universally mandatory.

Sources and limitations

AgID's resources on document management and preservation help distinguish these subjects; rules addressed to public administration are not automatically extended to every business here. For documents containing personal information, the GDPR requires an assessment of measures and retention consistent with the processing, rather than one period for every file.

The method described improves reconstruction of activities but does not certify compliance or guarantee an inspection outcome. A review may require further documents or enquiries. The file should clearly show what exists and what remains to be completed, so an internal status does not conceal an unfinished step or an unresolved evidential gap.

To compare this approach with registers and deadlines that link their supporting evidence, you can view Vigenza.