Record vs register vs log

An individual record holds information about a particular item, transaction or event. A register brings items together in an organized list with consistent details. A log records a sequence of events: what happened, when it happened and, where relevant, who was involved. These are common working distinctions, not rigid naming rules: a document can serve more than one purpose.

For office equipment maintenance, think of a repair report as an individual record, the equipment list as a register, and the dated maintenance history as a log. They answer different questions about the same equipment.

An individual record captures the particulars

An individual record might describe one printer, document one repair visit or preserve one inspection result. It need not be a separate paper document: a saved form or an entry in a software system can do the job.

Consider this illustrative example. An office has a shared printer identified as PR-014. After repeated paper jams, a technician replaces its feed roller. The completed maintenance record, MR-082, contains:

• The equipment identifier, PR-014.
• The service date, 7 October.
• The reported fault and the technician’s findings.
• The work completed and the replacement part used.
• The technician’s name and the test result.
• A reference or link to the supplier’s service report.

This record answers: “What exactly was done during this repair?” A short note saying “printer fixed” would not provide the same detail.

There could also be an individual equipment record for PR-014, holding its model, serial number, purchase details and warranty information. “Individual record” therefore does not mean “repair report” specifically. It means a particular unit of recorded information; what that unit covers depends on the task.

A register gives an organized overview

A register brings entries together using a consistent structure so people can identify, find and compare them. The Society of American Archivists includes this consistent-format sense in its definition of a register.

In our illustrative office, an equipment register might contain this simplified view after the printer repair:

Equipment ID	Item	Location	Responsible team	Current status
PR-014	Shared printer	Second-floor copy room	Office services	In service
SH-006	Shredder	Finance office	Finance	In service
PJ-003	Projector	Meeting room 2	Office services	Awaiting repair

This answers: “What equipment are we tracking, where is it, and what is its current status?” A fuller version could include serial numbers, last-service dates and next-service dates, with links to detailed equipment and maintenance records.

In this register, each entry represents a piece of equipment. One printer appears once, even if it has been repaired several times. Its status can change without creating another printer entry.

A different register could list maintenance jobs instead. Each entry would then represent a job, not a machine. The word register alone does not tell you what is being listed; its title and column headings should make that clear.

A log gives the sequence of events

A log is organized around occurrences rather than just the latest status. In the same illustrative example, the printer’s maintenance log could show:

Date and time	Equipment ID	Event	Supporting reference
6 October, 09:10	PR-014	Repeated paper jams reported	Ticket MT-081
6 October, 09:25	PR-014	Printer taken out of service	Ticket MT-081
7 October, 14:30	PR-014	Feed roller replaced; test passed	Maintenance record MR-082
7 October, 14:45	PR-014	Printer returned to use	Ticket MT-081

This answers: “What happened, and in what order?” The repeated equipment identifier is intentional: there is one printer but several events.

The log preserves the fact that the printer was unavailable, even though the equipment register now says “In service.” Simply replacing yesterday’s status with today’s status would lose that sequence unless the system kept a separate history.

A log can cover one machine or the whole office. Its distinguishing feature here is the event history, not the number of machines included. It might display newest events first or oldest events first. For entries made later, distinguish the time an event happened from the time someone entered it.

How the three work together

The shared equipment identifier connects the overview, the history and the supporting detail. Someone investigating PR-014 can find it in the register, follow its events in the log, then open MR-082 to see the repair findings.

For this repair, the updates would be:

1. Complete the maintenance record with the work performed and its result.
2. Add the relevant log entries so the repair and return to use appear in the history.
3. Update the equipment register so its current status and service details reflect the completed work.

These steps need not mean typing the same information three times. The record, register and log could be separate documents or different views of the same underlying data. A system could generate the history and update the overview from a saved maintenance record. In a simpler arrangement, a spreadsheet could link to a service report.

The important point is that readers can move between the overview and its supporting information without confusing current status with past events.

Why the labels overlap

“Record” also has a broader meaning than an individual entry. A whole register or log can itself be a record, while its entries are records too. The Society of American Archivists’ record entry illustrates this use at both the individual-item and whole-container level.

Software labels can mix these levels. In its help article dated 25 June 2026, Access Assets describes its Asset Records screen as a way to browse the asset register. The same article describes adding a maintenance record and viewing an asset’s maintenance log. These are the provider’s documented labels, not three universally prescribed document types. See Access Assets: The Asset Records Screen.

An organization might call a dated list of repair requests a “maintenance register”; another might call it a “maintenance log.” Local procedures and the way a software system groups information can influence the name.

A register can also be chronological: the archivists’ definition includes registers of events arranged by date or number. Conversely, sorting an equipment register by purchase date does not, by itself, make it a maintenance history.

When a label is unclear, ask what one entry represents and what question the collection answers. Is it information about a particular item or action, an organized overview of items, or a sequence of events? Use the organization’s established name, but make that purpose explicit.