Who is responsible for declaring and classifying a record at the moment it's created — the employee, IT, or the records team?

The short answer is that responsibility is shared, but the person who actually creates or receives the information carries the first and most important duty. Declaring and classifying a record at the moment of creation is not a single department’s job; it works best as a coordinated effort across the employee, IT, and the records or information governance team.

The Employee: The First Line

In most organizations, the employee who authors, sends, or receives information is the one who effectively declares it as a record. Only that person knows the business context: what the document is, what activity it documents, and why it matters. Whether a draft email, a signed contract, or a dataset, the creator is best positioned to recognize that the item has evidential or business value and should be captured into a recordkeeping system. Good programs make this easy and, increasingly, automatic so that the burden on individuals is low.

IT: The Enabling Layer

IT rarely decides what is a record, but it builds and maintains the systems that make reliable capture, classification, and protection possible. That includes repositories, metadata fields, security controls, retention enforcement, and the integrations that let classification happen automatically or with minimal user effort. IT executes policy; it does not set it.

The Records / IG Team: The Authority

The records management or information governance team owns the policies, the file plan or classification scheme, and the retention schedules. They define the categories into which records are sorted, train staff, and provide the rules everyone else applies. When automated classification is used, it is the records team’s scheme and business rules that the technology enforces.

How It Fits Together

• Records/IG sets the rules (what counts as a record, how it is classified, how long it is kept).
• IT provides the tools and enforces controls technically.
• Employees apply the rules at the point of creation.

International guidance such as ISO 15489 frames recordkeeping as an organization-wide responsibility supported by clear roles, while NARA similarly treats records management as a program-level duty rather than one owned by any single individual.

The practical takeaway: classification should happen as close to creation as possible, by the person who has the context, supported by systems and rules others provide. Learn more on the information governance hub.