Skip to content
Try an example
Early preview Nothing here is released yet. Pages marked Garden are drafts that no person has reviewed. How review works

Track onboarding obligations to closure

← Explore patterns and cases

Reference eligibility: eligible — Institutional or method-author operating guidance documents this procedure; no tool-seller customer-success claim is admitted.

This is a retained audit record, not an eligible reference example. Inspect source eligibility.

people/HR / svc-16

Track onboarding obligations to closure

A shared issue distributes general and role-specific onboarding work and supports compliance follow-up.

documented-procedure · · Source account, not a validated implementation

What goes in

  • Onboarding template
  • Role and start date

What comes out

  • Completed checklist
  • Follow-up requests

Documented sequence

Order described in the source account; not a sequence between pattern families.

  1. Create the onboarding issue before the start date.
  2. Assign manager and People Operations tasks.
  3. New starter completes general and role-specific tasks.
  4. Use buddy or team support where needed.
  5. Audit open issues monthly.
  6. Follow up on outstanding tasks and close the issue.

Checks described

  • Monthly audit checks tasks and compliance obligations.

What changes with context

  • General tasks have a 30-day due date; bot closes issues after 60 days.
  • Temporary service-provider onboarding belongs to Procurement.

Shared patterns · provisional interpretation

  • Coordinate commitments to closure

    An objective involving people or teams → accountable next actions, handoffs, tracking, and agreed closure

Fit: direct. Exploratory analyst coding of collected source summaries; not independently tested

Could this transfer?

Hypothetical: A membership service could track new-member setup across departments.

Limit: Automatic closure is not evidence of actual completion.

Evidence limits and unknowns

  • Audit exception outcomes
  • Completion quality

Source eligibility and effectiveness

Allowed use: process reference with explicit limits . Source eligibility is not proof of effectiveness, safety or transferability.

Review attribution: AI-assisted source review · 2026-10-18T03:26:44.526806+00:00.

  • Eligibility, where granted, permits a process reference only; it is not proof of usefulness, causal effectiveness, safety, or transferability.
  • No workflow software executed, no video playback independently observed, and no outcomes independently measured by this audit.
  • Audit exception outcomes
  • Completion quality
  • Automatic closure is not evidence of actual completion.

Source and dates

GitLab Onboarding ↗ · First-party public handbook

Published
Unknown
Updated
2026-09-13
Checked (UTC)
2026-10-18T03:00:27Z

Original handbook footer explicitly states Last modified 2026-09-13. Original publication date is not provided in retrieved text. This is page-level modification, not proof that this workflow changed on that date; several entries concern handbook-wide renaming.

verified updated only · Date evidence ↗

Permanent case link · Download source records