The best method to do this kind of thing is to use existing tools in SQL Server, such as Change Data Capture , and SQL Auditing .

However, if you really want to roll your own logging, the following should get you started.
It's unclear what some of your logging columns are supposed to represent so I've omitted them. It also seems like overkill.

CREATE TRIGGER dbo.LogChanges ON dbo.Employee
FOR INSERT, UPDATE, DELETE
AS

SET NOCOUNT ON;

IF NOT EXISTS (SELECT 1 FROM inserted) AND NOT EXISTS (SELECT 1 FROM deleted)
    RETURN;    -- bail early if no rows
    
INSERT dbo.Logs (
    TimeStamp,
    WinUser,
    Computer,
    Action,
    OldValue,
    NewValue,
    ParentID
)
SELECT
    GETUTCDATE(),
    SUSER_NAME(),
    HOST_NAME(),
    IIF(i.ID IS NOT NULL, IIF(d.ID IS NOT NULL, 'U', 'I'), 'D'),
    v.oldVal,
    v.newVal,
    ISNULL(i.ID, d.ID)
FROM inserted i
FULL JOIN deleted d ON d.ID = i.ID    -- full join on primary key
CROSS APPLY (VALUES
    (i.FirstName, d.FirstName),    -- unpivot all columns
    (i.LastName, d.LastName),
    (i.[Current], d.[Current]),
    (i.Password, d.Password)
) v(newVal, oldVal)
WHERE EXISTS (SELECT v.newVal EXCEPT SELECT v.oldVal);    -- null-aware comparison

If the column types are mixed then you should cast at least the first value in the CROSS APPLY (VALUES to sql_variant .

db<>fiddle

I note that some of your data types are questionable, such as nullable columns, lengths, and object and username columns should be sysname . Plain-text passwords are also a bad idea.