What a log should represent
A log should represent a repeatable category of records. Examples include equipment inspections, vehicle maintenance, safety checks, incident follow-ups, generator readings, facility walkthroughs, or recurring compliance reviews.
Log names and slugs
Each log has a display name and a URL-friendly slug. Use clear names that your users will recognize. Avoid creating multiple logs for the same process unless the records truly need to be separated.
Editing and deleting logs
Log changes should be handled carefully. Logs with existing fields, metadata, or entries may be protected from deletion so historical records are not accidentally removed.