Welcome SOP for new joiners

A welcome SOP is required reading assigned when a new employee is activated, so day-one procedures are a named document with an owner — not a scavenger hunt across chat threads. Dayzen SOP management can automatically assign welcome SOP material on activation. Dayzen onboarding is the new-joiner pipeline that reaches that activation event. This page is the welcome-SOP swimlane: what goes in the pack, who receives it, what a read receipt means, and what it is not. It is not a second copy of hire-to-activate onboarding (offer through activation). It is not a reprint of the employee onboarding checklist (HR joining tasks). Document skeleton — purpose, scope, owner, steps — stays on the SOP template. Dayzen does not provision laptops, email tenants, badges, or SSO. Assignment of a procedure is not IT provisioning.

What a welcome SOP is for

New joiners need a small set of procedures they must actually follow in the first days: how to request leave, how attendance is captured, where to find the employee directory, how to raise a people-ops question, what “activated” means for login. If that set lives only in a manager’s memory, every cohort invents a different first week. A welcome SOP is the written, versioned pack assigned because the person became an employee in the system — not because someone remembered to forward a PDF.

Write one sentence of purpose before you author the pack: these are the procedures every new employee in this organisation (or this location, or this employment type) must read at activation. If you cannot finish that sentence, you are assembling a dump of every handbook chapter. Dumps do not get read. Role-specific procedures belong on role-based assignment after the person has a job that needs them. The welcome pack is the common floor.

Keep the pack short enough to finish in a sitting. A welcome SOP that takes a full day of reading is a handbook with a different filename. Point to longer policies by name and location; do not paste them in full unless the procedure cannot be followed without the excerpt.

Activation is the trigger, not the whole join path

Hire-to-activate owns stages from offer through forms, approval, joining date, ready-to-activate, and activated. The welcome SOP fires because activation happened. Do not treat the SOP as a substitute for those stages. A person who is still filling pre-onboarding details should not receive “you are now an employee; here is how to mark attendance” as if they already had an employee login.

Operational split:

• Before activation: candidate or joiner packet, documents, joining date, readiness. Owned by onboarding and the checklist.
• At activation: employee record is live; account setup emails the product actually sends; welcome SOP assignment if you configured it.
• After activation: the person works; they read and acknowledge the pack; managers still run human orientation. The SOP does not complete coffees, shadowing, or first assignments.

If activation slips, the SOP should wait. Assigning day-one procedures to someone who cannot log in produces false receipts or ignored mail. If the joining date moves, move activation with the same identity. Do not create a second employee row so you can “send the welcome pack on the old Monday.”

Dayzen onboarding can assign the welcome SOP automatically when the joiner is activated. That is a distribution rule tied to a lifecycle event. It is not a claim that the product completed onboarding for you.

What belongs in the pack

Use the SOP template’s fields. Then fill only what a new employee must do or know in the first days. Typical operational contents organisations put in a welcome pack:

1. How you exist in the company systems. Where the employee profile lives, who updates which fields, how to spell your name if payroll already locked a version.
2. Hours and presence. How punches or attendance work here, what grace means in plain language, how to raise a regularisation — without reprinting the full attendance feature guide.
3. Leave. How to apply, who approves, what not to do (chat-only leave with no record).
4. People-ops channel. Named inbox or form for HR questions. Do not invent an unpublished helpdesk product. If you only have email, write the address.
5. Conduct floor. Pointers to issued policies the company already published (attendance, leave, POSH communication if that is a separate assignment). Do not paste legal manuals.
6. What to do on day one if something is broken. Who to ping for login failure versus who to ping for a missing desk. IT remains IT.

What does not belong as the whole pack: the complete employee handbook, every departmental SOP, client-delivery playbooks, or IT runbooks for device imaging. Those audiences are narrower. Flooding every joiner with every procedure trains people to click “acknowledged” without reading.

Asset assignment, if you do it at join, is a separate swimlane: catalog to person. Mention “you will receive named kit; acknowledge it in the asset record” if that is true. Do not turn the welcome SOP into an asset register.

Who is in the audience

Default audience is every newly activated employee in the scope you chose: company-wide, location, employment type (for example intern versus employee), or a combination your assignment rules support. Interns may need a shorter pack. Contractors may be out of scope if they never become employees in your directory. Write the scope on the SOP. Silent “everyone” is how a vendor joiner receives leave-balance instructions that do not apply.

Managers are not the primary audience of the welcome SOP. Managers need a different calendar for first-week work. If you want managers to know that joiners received the pack, use a compliance report — do not CC managers on every receipt.

Rehires and internal transfers are not automatic welcome-SOP events unless you decide they are. A transfer already knows how to apply leave. Re-assigning the full welcome pack on every contract change trains people to ignore it. Activation of a new employee record is the default trigger this article describes.

Assignment, receipts, and versions

Dayzen SOP management includes rich-text authoring, categories, assignment and distribution rules, My SOPs read receipts, compliance reports, and revision control. For welcome material:

• Author the pack once. Name an owner who will review it when policy changes.
• Assign by the activation rule you configured, not by a recruiter attaching a file to an offer email and hoping.
• Collect a read receipt so you can see who has not confirmed. A receipt is dated acknowledgement of that version. It is not proof they can operate the job, not POSH legal compliance, and not a government filing.
• Report outstanding reads in the first week. Chase like any other onboarding open item. Do not wait for month-end.
• Version when the procedure changes. Decide whether people already activated must re-acknowledge. New joiners should get the current effective version, not last year’s PDF in a shared drive.

If the product assigned the SOP and the person never logged in, the outstanding receipt is a login or activation problem first. Do not treat unread welcome SOPs as a culture issue until the account exists.

What welcome SOP is not

Confusion	Owner instead
Offer to activated pipeline	Hire-to-activate guide; Dayzen onboarding stages
HR task list (bank, remaining papers, payroll-ready fields)	Employee onboarding checklist
SOP section headings and writing skeleton	SOP template; writing-craft sibling if you use it
Laptop, email, MDM, SSO	IT — not this product
Role-specific procedures after the person has a job	Role-based SOP assignment
First-week manager orientation	Manager calendar, not auto-completed by SOP assignment

Do not describe this work as Dayzen PMS. PMS in Dayzen is a Project Management System for delivery work. Welcome SOP is people-ops procedure distribution.

Operating the first-week chase

On the joining week, the onboarding owner (or SOP owner) should be able to answer: was this person activated, was the welcome pack assigned, has the receipt come in, which version did they get. Put those four facts next to the checklist’s remaining HR tasks. They are parallel, not substitutes.

If a joiner says they never saw the SOP, check assignment and login before rewriting the document. If they saw it and the steps are wrong (leave form named a tool you retired), that is a versioning defect — fix the SOP, do not only coach the person.

Local exceptions belong in the SOP’s exception section, not in a side WhatsApp: “site X marks attendance at the gate; follow that local instruction.” Global welcome packs that ignore sites produce receipts without behaviour.

A welcome SOP is the activation-time reading pack. Dayzen can assign it when the employee is activated. Activation is not IT provisioning, and this page is not a second hire-to-activate guide. Keep structure on the SOP template and joining chores on the onboarding checklist.

Stop this article at assignment, contents, receipts, and the boundary with onboarding. Full pipeline narrative, itemized HR tasks, and SOP writing craft stay on their owners. Use the product for authoring, rules, receipts, and reports — not as a claim that software completed the human first week.