The Disciplinary Pattern Nobody Can See Because It's Not Written Down
The employee who has been late four times in eight weeks is not a disciplinary problem on any individual morning. Each instance, taken alone, is a conversation. Taken together, they're a progressive discipline pattern that establishes the factual record for a Performance Improvement Plan or, if it comes to that, a termination that survives an unemployment challenge. The problem is that "taken together" requires that someone wrote down each individual instance, dated it, noted who handled it, and kept it accessible.
The HR Situation Log in Memento Database is the system that makes that record exist. Not in a filing cabinet. Not in someone's head. In a searchable, filterable database indexed by employee name and situation type.
What the Situation Type Field Includes That Most Systems Don't
The Situation Type field carries eleven categories. Most HR software logs discipline. This template also explicitly includes Employee Idea, Employee Recommendation, Employee Reward, and Employee Commendation—the positive side of the employee record.
That design choice is not accidental. An employment attorney reviewing a termination record that contains only discipline entries for an employee looks at a one-sided file. The same record with a commendation from March and a documented employee idea from February that was implemented looks like a real management history—one where the employee received genuine feedback in both directions, and the discipline record is not manufactured in retrospect.
Employee Call Off and Employee Late are separate types from Employee Discipline, which matters for attendance tracking. Logging an absence as Discipline when it was an unexcused call-off misclassifies the event. The type field creates the distinction.
Status, Follow-Up, and the Open Record That Gets Forgotten
Status—Open, Pending, Closed—is the queue management field. Open records are active situations. Pending records are waiting on something: a follow-up meeting, documentation from the employee, an HR decision from above. Closed records are resolved.
The Follow-up Required boolean paired with Follow-Up Date and Time is the accountability mechanism. An HR manager who handles a concern on Tuesday and schedules a follow-up for the following Monday creates a record that surfaces in a date-sorted filter on Monday morning. Without that structure, follow-ups are calendar events that get bumped and eventually forgotten, and the employee who raised a concern three weeks ago and never heard back is now talking to an employment lawyer about retaliation.
Situation Handled By and Names of other employees involved create the witness and responder record. When a situation involves two employees and was handled by a shift supervisor, all three names are in the record. When the matter surfaces again three months later—as it often does, in a different form—the people who were present are named.
The Fee Fields and What They're For
The Fee, Amount Charged, Payment, and Amount Paid fields are present because some HR situations involve financial components: wage adjustments, cash handling discrepancies, damage assessments, or settlement amounts in cases involving HR vendors or external consultants. These fields are not relevant to every record; they're available when the situation requires them.
An HR log that captures the discipline conversation but not the $200 cash register shortage that prompted it is an incomplete record at the hearing. The financial fields close that gap without requiring a separate system.
The boolean fields—Fee and Payment—function as presence flags. If Fee is false, Amount Charged is irrelevant and can be ignored. If Fee is true and Payment is false, the outstanding amount is visible on the record and can be filtered against all employees with unresolved financial situations attached to their log.