How it works
From a request to a completed transaction.
Describe an off-cycle promotion in your own words, refine the proposal and follow it through the sample approval process. See the result in the sample HR and payroll records. No live system connections.
01
Describe what needs to change.
Start with the example or write a promotion request for Maya Chen. Name the new title, salary or percentage increase, and effective date. If a detail is missing, the demo asks for it before preparing the proposal.
Try: “Promote Maya Chen to Senior Product Designer with a 10% raise, effective October 1.”
02
Review and refine the proposal.
See the current and proposed title and pay, annual cost, effective date and sample policy checks together. Change your request in plain language, such as “Actually, make that 12%.” The proposal and its checks update before you send it for approval.
The initial example moves annual salary from $150,000 to $165,000. Your request determines the proposed amount and date.
03
Send it for approval.
The sample employee and payroll records stay unchanged while approval is pending. A salary above the band first needs a Head of People exception approval. Then simulate the Finance and HR decisions to schedule the promotion.
Try a $200,000 salary to see the exception path. Revised terms need a new review.
04
Inspect the completed transaction.
Open the employee record, payroll change and approval history to inspect the saved terms. Each view belongs to the same transaction, including any salary-band exception. Current pay stays unchanged until the effective date.
All records and notifications stay in your browser. No live systems are changed or messages sent.
Beyond the promotion example
The decision changes.
The questions stay useful.
For a raise: what changes, when does it take effect, and who can approve a budget exception? For a bonus cycle: who is included, how is the fixed pool allocated, and which awards are approved, payable or paid?
For a review: which evidence supports the draft, and what still needs the manager’s judgment? For an employee answer: which record can this person see, and where can they check the detail?
These are separate workflows in the guided sample company. Each has its own rules and completion criteria.
Implementation
Exports first.
Production connections after validation.
In the separate guided sample company, the implementation preview accepts permitted synthetic CSV or JSON exports. An operator reviews columns, missing values, money units, identity links and field authority, then publishes a versioned setup. That comparison describes the uploaded rows; it does not establish complete coverage of a source system.
An eligible difference can become a separate synthetic working copy for a reviewed correction. Original uploads remain unchanged, and manually recorded sample approval evidence is identified as such.
A production rollout needs an agreed data scope, approved access and retention, tested provider operations, and verification of the customer’s business processes. Those connections and operational commitments require validation before real writes are enabled.
See the decision, then follow the result.
Start with the public promotion example, or bring a workflow to a guided conversation.