Designing a compensation-change process people can audit

A number without a state is ambiguous

A compensation change is not just a value. It has a proposer, reason, effective date, approval state, publication state, and payroll handoff. If those live in a spreadsheet, the spreadsheet becomes the permission system by accident.

Perelan Compensation presents this as a compensation workspace, not a statutory payroll engine.

Keep reason and effective date

The reason gives context. The effective date makes downstream work possible. Both should sit beside the number rather than in a detached comment thread.

Separate approval from publication

Approval means the change is allowed. Publication means the employee can see it where appropriate. Keeping those states separate prevents accidental disclosure and makes the process easier to audit.

Mask sensitive values by default

Sensitive values should not appear just because someone opened a table. Reveal controls, role checks, and finance/HR scope help the product treat compensation as consequential data.

Record actor and outcome

Every decision should show who acted, when, and what changed. Slack approvals should still update the Perelan record and preserve the acting employee identity.

Be precise about the payroll boundary

A compensation workspace can prepare clean payroll handoff data. That does not mean it calculates taxes or files statutory payroll. The boundary should be visible in product copy and implementation planning.