How does onboarding differ for contractors versus permanent employees?

• A. Contractors have longer review cycles than permanent staff.
• B. Different lifecycle, access durations, approvals, and review frequency; revocation at end of contract.
• C. Contractors should be given permanent access to all apps.
• D. Permanent employees do not require any access reviews.

Answer: (B)

Onboarding for contractors is driven by the contract lifecycle, so the access you grant is time-bound and tightly controlled. You design the process to fit the contractor’s duration: specific access windows, approvals that reflect contractor status, and review cycles that align with project needs. Crucially, access is revoked automatically or promptly at the end of the contract to prevent lingering privileges. That combination—distinct lifecycle, defined access duration, approvals tied to contractor status, review cadence, and end-of-contract revocation—best captures how onboarding differs for contractors.

Giving permanent access to all apps or skipping reviews for permanent staff isn’t correct. Contractors should only receive what they need and their access should be removed when the contract ends; permanent employees still require access controls and periodic reviews, not indefinite, unreviewed privileges. The idea that contractors have longer review cycles also doesn’t fit typical practice, which tends to align reviews with project timelines and contract details rather than extending them.