Every employee file checked in one pass: no signed contract, expired right-to-work document, missing probation decision, attendance records with impossible hours. Names and dates, not a completeness score.
European HR admin has a texture. Probation end dates needing a decision two weeks early, absence approvals sitting with a manager who is themselves absent, and a document folder per employee where completeness is theoretical.
A companion reads employees, absences, attendances and documents, and reports what is missing before somebody asks. What it can read is what the connected account can read, which for employee data is the important sentence.
01
What does a completeness check find?
Employees with no signed contract on file, expired right-to-work documents, missing probation decisions, attendance records with impossible hours. Each category comes back as a list of names and dates.
None of that is clever. It is the check anybody could run and nobody does, because it takes an afternoon and produces an uncomfortable list. The list existing is most of the fix.
02
Can it help with absence approvals?
It finds the ones that are stuck and says why.
Requests waiting more than five days, requests whose approver is on leave themselves, overlapping absences inside one team that nobody noticed when approving them separately.
A companion drafts the nudge to the approver and, where a team would be left uncovered, says so plainly so somebody can make a call. Approving stays with the approver.
03
The reporting nobody wants to build
Absence by team and month, attendance anomalies, probation decisions due next quarter, headcount by contract type. The awkward requests are the ones needing Personio plus the recruiting pipeline or a payroll export.
A companion works your signed-in browser sessions as well as the connection, so those cross-system questions become one pass instead of three exports and a spreadsheet. See ai for hr teams and automate weekly reporting.
04
Probation dates and the decisions they need
A probation period ends on a date somebody set nine months ago, and the decision needs to exist two weeks before it. Missing the date lets the decision default, which in several jurisdictions is not what anyone intended.
A companion reads employment records, reports probation ends inside a window you choose with the manager attached, and drafts the reminder. Whether somebody passes carries employment-law weight and stays with the people accountable.
Within the permissions of the account you connect, yes. Employees, absences, attendances and documents are the readable core, and a restricted account restricts the companion identically.
Ask for employees with no signed contract on file, expired right-to-work documents and missing probation decisions. Each category comes back as names and dates rather than a completeness score.
Approval stays with the approver. A companion finds the requests that have been waiting, the ones whose approver is themselves away, and the overlapping absences in one team, then drafts the nudge.
Yes. Connect the account and a companion reads employees, absences, attendances and documents, and reports what is missing before somebody asks for it. The credential is stored encrypted outside Strawberry, and the available actions follow the Personio public API.
A companion reads the entitlement Personio computed and reports the gaps around it, by name and date. Your policies, carry-over rules and country holidays stay in Personio, which is where the calculation belongs.