Clause 8 · Title coverage

Deletion classes

Clause 8 makes the rule set manageable. It defines abstract starting points, builds a matrix of deletion classes, and shows how a cluster is allocated to a class and given a specific deletion rule.

Citation: ISO/IEC DIS 27555, Clause 8. Held: Contents only.

What the draft asks of an organisation

The clause takes the standard periods from clause 7 and pairs them with abstract starting points to form deletion classes. An abstract starting point is a type of event, not a dated instance: end of contract, last activity, closure of a case. The matrix is the set of combinations the organisation uses. Allocation is the act of placing each cluster in one cell, then writing the specific deletion rule that names the actual event for that cluster. The clause is deliberately narrow. It does not decide the periods or the events. It gives the organisation a small, auditable structure so that hundreds of record types do not need hundreds of hand written rules, and it shows how each cluster is placed in one cell and given its own specific rule. The output is a matrix a reviewer can read and a rule sheet that maps every cluster into it.

What the public sample holds

The DIS contents lists three parts for clause 8, covering abstract starting points, the class matrix and the allocation step. The clause text is not in the public sample and is not held, so this page states the method and the buyer's work, not the draft's sentences.

What this clause covers, in our reading

A deletion class matrix is a compression device, and like every compression it loses something. The point is to lose the right things. A class combines a standard period with an abstract start. If the organisation has six standard periods and five abstract starts, the matrix has thirty cells at most, and most will be empty. Every cluster then points to one cell. The specific rule adds the real event, such as the date the contract ended or the date the last invoice was paid. That two layer design is what makes the framework maintainable. A change to a standard period updates one row and every cluster in it, while a change to one cluster's event updates one rule. The matrix also exposes nonsense early. If a cluster lands in a cell with an abstract start that cannot apply to it, the allocation is wrong. A reviewer can test the matrix by picking a cell and asking which clusters sit in it and why. An empty matrix with a note that says every cluster is unique is a sign that the organisation has not done the compression, and the clause exists to prevent exactly that. The allocation record should name who decided, when, and which evidence was used, because the decision is a judgement about purpose and law, not a technical default.

Subclauses named in the contents

• 8.1 Abstract starting points: abstract deletion rules
• 8.2 Matrix of deletion classes
• 8.3 Allocation of deletion classes and definition of deletion rules

What to prepare

1. List the abstract starting events the organisation actually uses, and merge the near duplicates.
2. Build the matrix from the standard periods and the abstract starts, and mark the empty cells.
3. Allocate every cluster to one cell and write the specific rule with the real event named.
4. Record the decision maker and the evidence for each allocation.

The evidence an auditor or regulator asks for

Tests to run

• Pick a cell and list every cluster in it; confirm the purpose fits the abstract start.
• Change one standard period on paper and confirm the affected clusters are obvious.
• Check that no cluster has a specific rule without a matrix allocation.

What the public text does not settle

• The clause text is not in the public sample and is not stated here.
• The draft does not prescribe the number of classes.
• The draft does not say how to handle a cluster that fits two abstract starts.

Next

• Publish the matrix as a one page control the business can read.
• Link every cluster row to its cell and its specific rule.

Other clauses

• Clause 1: Scope
• Clause 2: Normative references
• Clause 3: Terms and definitions