PUXORA 360 · PEOPLE OPERATIONS

A request. A clear rule. A recorded outcome.

Follow one representative leave request from an employee conversation through policy review, management approval, and an auditable result.

Illustrative P360 HR interface using representative data.

P360 HRPeople operations workspace
Pilot

Start where work already happens

A private, fictional Connect-style conversation gathers the request.

Step 1 · Employee

Private conversation · P360 Connect

Hi HR, I’d like annual leave from 14–18 September.Amara Mensah · 09:12
Thanks, Amara. That is five working days. Who will cover your active responsibilities while you’re away?P360 HR · 09:12
Kojo Owusu can cover the weekly site report.Amara Mensah · 09:14
Thanks, Amara. I’ll contact Kojo Owusu to confirm he can cover the weekly site report while you’re away. Once he accepts, your request will move to management for approval.P360 HR · 09:14
Awaiting Kojo’s confirmation

Make the rule visible

Recorded facts and deterministic checks explain why the request can proceed.

Step 2 · P360 HR

Rule path

1
Balance check12 days recorded before this request
Passed
2
Working-day countFive chargeable days in the selected range
Passed
3
DelegationAwaiting Kojo’s acceptance
Pending
4
Management decisionRoutes after delegation is accepted
Next

Keep authority with the right person

The management queue presents only the context needed for a decision.

Step 3 · Management

Restricted approval queue

Annual leave · Request LV-2048

Amara Mensah · 5 working days · Delegate accepted · Balance after approval: 7 days

Ready for decision

Illustrative controls — no record will be changed.

Close the loop with evidence

The employee sees the outcome while HR retains a clear workflow record.

Step 4 · Recorded

Outcome timeline

LV-2048

Request authorised
Decision recorded by the designated authority

BALANCE

Leave balance updated
12 days → 7 days

CONNECT

Employee notified
Outcome delivered in the private conversation

Built by < / Pux Devs >