Vigenza

Policies and resolutions: bringing internal commitments into a compliance calendar

· Redazione Vigenza

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

To bring a commitment from a policy or resolution into a compliance calendar, extract the required action and link it to the document establishing it. Assign an owner, determine when it must be performed and identify the evidence that will document execution. A date without its source reference becomes difficult to update when the original text changes.

Internal activities can be more frequent or more detailed than the minimum required by applicable rules. This does not mean every policy sentence automatically creates a new statutory deadline. Distinguish legal requirements, conditions in an official decision and the business's organisational choices, assessing their status and the possibility of changing them separately.

Collect the versions actually approved

Start with documents in force rather than the folder containing the most files. For each policy identify its title, version, approval date and competent approving body. For a resolution, locate the passage containing the commitment and any referenced attachments. If minutes refer to a missing document, record the gap before extracting an apparently complete calendar.

Keep approved text separate from proposed updates. A draft may help prepare work, but should not silently replace the current source. If the business decides to follow a new procedure early, document the decision and check that this is permitted. A filename is insufficient to establish which rule is in force.

Look for actions, conditions and recurrence

Read passages assigning activities to a function or requiring periodic checks. Do not restrict the search to sentences containing a date. Wording such as “following a significant change” describes an event to identify, rather than a deadline automatically set at year end. Determine who recognises that event and who opens the corresponding task.

For recurring commitments, establish when the period starts and how completion is documented. “Every quarter” may be ambiguous if the calendar basis or reporting point is unclear. Where the text does not support a reliable reading, ask the procedure owner to clarify it. Do not resolve an interpretative uncertainty by inventing a date and presenting it as already approved.

Keep the origin of the commitment visible

Use a calendar field distinguishing legislation from policies and resolutions. A monthly check chosen by the company may sit alongside reporting required by sector rules, but they are different activities. Connect them where they share documents or owners without erasing the differences.

If a commitment arises during an authorisation process, examine the relevant document and its actual status. Do not assume that every preparatory statement is a condition of the authorisation; equally, do not assume a policy can override a binding condition. The calendar records a verified classification rather than deciding it independently.

Resolve overlaps without losing content

Two documents may require similar activities at different frequencies. Before combining them, compare their subject, recipient and required evidence. An annual report to the board is not necessarily replaced by four quarterly checks by an operational owner. Where preparation overlaps, relevant material can be reused, but the recipient and approval may remain separate.

When the company changes an internal frequency, retain the decision authorising that change. Do not merely move the next dates. Commitments already due and future commitments may need different treatment. Review legislative, contractual or official-decision restrictions before implementing the new calendar. This prevents an apparently simple scheduling edit from obscuring a substantive change to an approved commitment.

An invented example of a more frequent commitment

The fictional company “Argine Tecnologie” has a policy requiring quarterly access reviews. A working group proposes moving to six-monthly reviews because user numbers are low. The calendar, however, continues to derive from the approved policy rather than the proposal in a presentation.

The owner collects the proposal and submits it through the required approval process. Only after applicable constraints are assessed and the competent body decides are future activities updated, with a link to the new version. Quarterly checks already due do not disappear from the history. This example describes an organisational method without claiming that a particular frequency suits everyone.

Allocate the work and its review

For each activity identify a responsible person or function and cover arrangements. Specify who receives the outcome and who acts if problems emerge. Naming only “Compliance” may conceal dependence on another function holding the information. Preparatory requests should leave enough time to perform the actual check rather than making completion dependent on materials delivered at the final moment.

Calendar review must also follow document changes. When a new policy is approved, check which entries need adding, removing or rewording. Keep a link to the previous version, within applicable retention rules, so it is possible to explain why an activity existed in one period and not another. A handover should include these source changes as well as the dates of outstanding tasks.

Sources and limitations

The DORA Regulation, EU 2022/2554, provides a sector-specific example of the importance of responsibilities and a documented ICT risk framework. It is not extended here to businesses outside its scope. AgID's document management resources help distinguish organisation from preservation; applicability must be checked for the entity and document concerned.

This guide does not classify particular authorisation commitments or replace examination of the source by competent functions. A calendar helps carry out properly understood decisions; it is not an independent source of obligations or extensions. When the underlying text remains uncertain, that uncertainty should remain visible until the appropriate review resolves it.

To compare this method with a calendar linking commitments to their source documents, you can view Vigenza.