Start inputs
Probation review scheduler
Passed by the calling system
HR & People package
Every morning, employees whose probation ends within three weeks get a manager review; the outcome is confirmed, extended or ended and recorded.
About this package
Probation review makes sure no probation period ends without a decision. Every morning the scheduler asks your HR system for employees whose probation ends within the look-ahead window (21 days by default).
For each employee it starts the Probation review sub-workflow in the background. The manager gets a task due on the probation end date with a performance rating, a recommendation (confirm, extend or end) and development notes. The Probation outcome decision table turns that into the action, the HR status and any extension; a "confirm" with a below-expectations rating becomes a short extension.
The outcome is written back to the HR system, the people team is emailed the result and next step, and confirmed employees get a congratulations email. Adapt the look-ahead, the outcome rules and the API paths; your HR system should stop returning an employee once their review is recorded so they are not picked up twice.
Daily at 08:00 (UTC). You can also start it any time from the Run dialog, the API or the CLI.
Runs on a schedule (daily, weekly, monthly) in your time zone.
The flow
Daily check
At 08:00 the scheduler lists employees whose probation ends within the look-ahead window.
One review each
For every employee a Probation review sub-workflow starts in the background, so reviews run independently.
Manager review
The manager rates performance, recommends confirm, extend or end, and adds development notes before the end date.
Decide the outcome
The Probation outcome decision table sets the action, the HR status and any extension weeks.
Record and tell people
The HR system is updated, the people team gets the outcome and next step, and confirmed employees are congratulated.
Forms
The inputs a caller passes when it starts a run, and the forms people complete when the process needs a decision.
Start inputs
Passed by the calling system
User Task · Probation review
Probation review for {{employee_name}} (ends {{probation_end_date}})
From your code
Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.
REST
curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
-H "Authorization: Bearer $USERTASKS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"workflow_id":"<workflow id>","variables":{"lookahead_days":21,"hr_email":"people-team@example.com"}}'CLI
usertasks workflows inputs <workflow id> # the start form: keys, types, required
usertasks workflows run <workflow id> --input lookahead_days=21 --input hr_email=people-team@example.com --waitWhat's included
| Type | Name | Details |
|---|---|---|
| Email template | Probation passed | Sent to the employee when their probation is confirmed. |
| Email template | Probation review outcome | Sent to the people team when a manager completes a probation review. |
| Integration | HR system | |
| API reference | List probations ending soon | GET /employees — Employees whose probation ends within the given number of days and has no review recorded yet. |
| API reference | Update probation | PATCH /employees/{{employee_id}}/probation — Record the probation outcome: passed, extended (with the new end date) or ended. |
| Decision table | Probation outcome | 5 rules — Turns the manager's recommendation and rating into the probation action, the HR status and any extension. First matching rule wins. |
| Workflow | Probation review | 11 steps — Sub-workflow for one employee: the manager reviews the probation, the outcome table decides confirm / extend / end, the HR system is updated and HR is emailed. |
| Workflow | Probation review scheduler | 10 steps — Every morning, find employees whose probation ends within the look-ahead window and start a Probation review for each one. |
Requirements
Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.
Integration “HR system”Required
Workflow “Probation review” assigneesRequired
Install
Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.
curl -fLO https://usertasks.com/gallery/probation-review-1.0.0.utpkg
usertasks packages inspect probation-review-1.0.0.utpkg # offline: checksum, hashes, signature
usertasks packages install probation-review-1.0.0.utpkg --dry-run
usertasks packages install probation-review-1.0.0.utpkg # prompts for each requirement
usertasks packages install probation-review-1.0.0.utpkg --keep-incomplete --yes # in CI; finish with:
usertasks packages complete probation-review -f values.yamlVerify the download
shasum -a 256 probation-review-1.0.0.utpkg should print the file SHA-256. How gallery packages are signed.
Versions
Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work
More packages
HR & People
A manager submits a leaver; access is revoked on the right day, equipment recovered, final pay scheduled, the exit interview held and the termination recorded.
Needs:REST APIAssigneesEmail
HR & People
HR enters a new hire; the HR record, laptop, accounts, buddy and first-week plan are all arranged before day one, with a 30-day check-in.
Needs:REST APIAssigneesEmail
HR & People
Employees request kit from an equipment catalogue; a cost and role policy routes approval, IT fulfils the request and the asset is registered.
Needs:REST APIAssigneesEmail