HR & People package

Probation review

Every morning, employees whose probation ends within three weeks get a manager review; the outcome is confirmed, extended or ended and recorded.

ScheduledIntermediate~15 min setupv1.0.0

About this package

What it does

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.

Scheduled

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

Step by step

  1. 1

    Daily check

    At 08:00 the scheduler lists employees whose probation ends within the look-ahead window.

  2. 2

    One review each

    For every employee a Probation review sub-workflow starts in the background, so reviews run independently.

  3. 3

    Manager review

    The manager rates performance, recommends confirm, extend or end, and adds development notes before the end date.

  4. 4

    Decide the outcome

    The Probation outcome decision table sets the action, the HR status and any extension weeks.

  5. 5

    Record and tell people

    The HR system is updated, the people team gets the outcome and next step, and confirmed employees are congratulated.

Probation review scheduler — Every morning, find employees whose probation ends within the look-ahead window and start a Probation review for each one. The same canvas you get in the designer after installing.

Sub-workflow: Probation review

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.

Forms

Inputs and task forms

The inputs a caller passes when it starts a run, and the forms people complete when the process needs a decision.

Start inputs

Probation review scheduler

Passed by the calling system

Look-ahead (days) lookahead_days · number0Start reviews this many days before the probation end date
HR email hr_email · emailname@company.comPeople team mailbox that receives each outcome

User Task · Probation review

Review probation

Probation review for {{employee_name}} (ends {{probation_end_date}})

Performance rating * performance_rating · choice
exceeds expectationsmeets expectationsbelow expectations
Recommendation * recommendation · choice
confirmextendend
Development notes * development_notes · text
Submit review

From your code

Start a run over the API

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

shell
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

shell
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 --wait

What's included

8 assets, ready to adapt

TypeNameDetails
Email templateProbation passedSent to the employee when their probation is confirmed.
Email templateProbation review outcomeSent to the people team when a manager completes a probation review.
IntegrationHR system
API referenceList probations ending soonGET /employees — Employees whose probation ends within the given number of days and has no review recorded yet.
API referenceUpdate probationPATCH /employees/{{employee_id}}/probation — Record the probation outcome: passed, extended (with the new end date) or ended.
Decision tableProbation outcome5 rules — Turns the manager's recommendation and rating into the probation action, the HR status and any extension. First matching rule wins.
WorkflowProbation review11 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.
WorkflowProbation review scheduler10 steps — Every morning, find employees whose probation ends within the look-ahead window and start a Probation review for each one.

Requirements

What you connect it to

Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.

Needs

  • REST API — A REST API integration: set its base URL and credentials on install.
  • Assignees — People in your workspace to receive the User Tasks (picked on install).
  • Email — Email delivery configured for the instance (EMAIL_PROVIDER), used for notifications.

After installing

  1. HR system integration: set the base URL and API token. The references expect GET /employees?probation_ends_within=21 (returning data[] with manager and probation_end_date) and PATCH /employees/{id}/probation; adjust them to your HR system.
  2. Assignees: pick the default reviewing manager. To route each review to the real manager, map reviewer_id in the Start probation review step from a field your HR system returns.
  3. Set hr_email on the scheduler to your people team mailbox, and lookahead_days if three weeks is not right.
  4. Edit the Probation outcome rules (extension lengths, HR follow-ups) to your policy.
  5. Email: configure EMAIL_PROVIDER on the instance so the HR and employee emails are delivered (the steps continue on error).

Asked for on install

  • Integration “HR system”Required

    • Tokenconfig.auth_config.token
    • Base urlconfig.base_urldefault https://hris.example.com/api· optional
  • Workflow “Probation review” assigneesRequired

    • User for step “Review probation”nodes.3.config.assignee_id

Install

Install it in your workspace

Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.

In the app

  1. Download probation-review-1.0.0.utpkg.
  2. Open Automations → Packages and drag the file onto the page (or choose Import package). Browse gallery there lists every gallery package without downloading by hand.
  3. Pick the file. The wizard verifies the checksum, every file hash and the signature, and shows the readme.
  4. Review the changes (what is created) and the data rows.
  5. Fill in the requirements, or tick Keep incomplete and finish later with Complete setup.
  6. Done: the workflow is published and active once setup is complete.

With the CLI

shell
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.yaml

Verify the download

File SHA-256
fce3a417b05e4dc00669ea1f8bba815175e39170d351043c27c8844b8e120ea2
Package checksum (what is signed)
sha256:0979f843e183fc52c9476260819ffeb7d59aa691c2f3f859557bd36a45c88da4
Signer
Unsigned preview build — compare the SHA-256 above

shasum -a 256 probation-review-1.0.0.utpkg should print the file SHA-256. How gallery packages are signed.

Versions

Version 1.0.0

  1. v1.0.02026-10-26First release.

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

Related

Browse the whole gallery