Check new starters can do their essential tasks

What this means for your practice

Accept onboarding through practical role-appropriate checks rather than task creation alone. Give the receiving manager a clear view of unresolved dependencies and support contacts.

A practical conversation with your supplier

Ask a tester using a fictional role to complete an ordinary first-day task with the approved access. A failed step should remain visible with an owner. This gives the manager a practical acceptance decision instead of a checklist that closes when technical setup alone is finished.

Plan the first improvement

Agree a short set of practical acceptance tasks with the receiving manager. These should reflect the role, such as finding approved guidance, accessing the right working list or completing a routine administrative action. They should use authorised test arrangements and avoid giving extra permissions simply to make the demonstration succeed. The starter or appropriate tester needs to know where to report a problem and who will own it. Keep a distinction between ready to begin essential work and every optional onboarding item being complete.

That gives the manager a useful decision while allowing less urgent tasks to remain visible. Include the expected support contacts in the handover, particularly where different tools have different owners. When an access problem is found after the checklist closes, use it to improve the acceptance task that would have exposed it. Counting accounts created is a useful setup measure, but the receiving team's ability to work is the more meaningful completion check.

How to check the result

Count completed onboarding records with unresolved access problems.