Role-based SOP assignment

Role-based SOP assignment means a person receives procedures because of the job they hold — via assignment and distribution rules — not because someone dumped a PDF folder on the all-hands list. The object is the audience: which roles see which procedures. Owner of the rules is usually HR operations with the procedure owner naming who must follow the job. Product surface is Dayzen SOP management: categories, assignment and distribution rules, My SOPs receipts, compliance reports, revision control, and welcome SOP assignment on activation. Job and directory data that make “role” real live on Dayzen employee management. The joiner special case is welcome SOP for new joiners (assigned at activation). This page is assignment strategy. It does not reprint the SOP template, does not teach writing craft, and is not an inbox-forward protocol.

Why the PDF dump fails

A shared drive with fifty procedures looks complete and is unread. People who punch attendance receive the vendor-onboarding SOP. People who onboard vendors never see it because it sat in last year’s zip. Compliance reports then show either empty audiences or 100% outstanding. The dump is not generosity; it is how you train everyone to ignore SOPs.

Assignment by role (or equivalent responsibility you actually maintain on the employee record) makes My SOPs a short list of jobs this person might do. Short lists get read. Endless lists get a bored click if you even require a receipt.

What a distribution rule is

A rule maps a procedure (or a category of procedures) to a population: designation, department, location, employment type, or another attribute you keep clean. The artefact is the rule plus the resulting assignment. The done definition is that a new person who matches the population receives the current procedures without a personal email from HR, and a person who leaves that population stops being chased for those jobs.

Dayzen SOP management includes assignment and distribution rules and categories. Use categories so you are not maintaining fifty identical audiences by hand when five procedures share a shop-floor population. Use rules so a transfer can pick up the new job’s procedures when the employee record changes — which depends on employee management holding a trustworthy role, department, and status.

Rules are not AI matching. Nobody searches a knowledge base to “find what you need.” You name the audience. If the directory says the wrong designation, the rule will faithfully assign the wrong SOP. Fix the record; do not add a second informal list.

Role means the job on the record

For assignment to work, “manager,” “packer,” and “HR executive” must mean the same thing on the employee profile that the rule reads. Employee management is where those attributes are maintained: identity, organisation, and the fields you use to slice audiences. This page will not become a data-dictionary for every employee field. It will say: if SOP rules key off designation, treat designation changes as assignment events, not as cosmetic badge text.

Contractors, interns, and multi-entity staff need an explicit choice: in the population or not. Vague “all staff” rules are how you assign a warehouse packing SOP to a visiting intern in finance. Prefer the narrow population, then add a second rule if a second population truly does the same job.

Do not invent a nationwide mapping of Indian designations to SOP packs. Your catalogue is yours. Keep it small enough that owners can name every procedure in a category.

Welcome SOP is the joiner case, not the whole strategy

Dayzen can assign welcome SOP material when a joiner is activated. That is a verified onboarding-adjacent behaviour: day-one procedures without a scavenger hunt. The welcome SOP sibling owns that story — pipeline versus SOP, what not to stuff into a welcome pack, and that this is not IT provisioning. This page only places it on the map: joiners get a starter assignment at activation; role-based rules should cover the job they were hired to do, which may be more than the welcome set.

If the welcome SOP is the only assignment you ever configure, people will have day-one reading and nothing for the job they do in month three. If you assign the entire library at welcome, you have reinvented the PDF dump with a nicer timestamp. Combine a short welcome set with ongoing rules by role.

A comparison you can paste into a RACI

	Role-based rule	Welcome SOP	All-hands PDF dump
Object	Population ↔ procedures	Activation-time starter set	Folder or zip to everyone
Typical owner	HR ops + procedure owner	Onboarding / HR ops	Whoever last forwarded the drive link
Trigger	Record matches the rule (role, dept, …)	Employee activated	Email, hope
Done when	Right people see current SOPs in My SOPs	Joiner has the starter list	Never, operationally
Dayzen role	Assignment/distribution rules, categories	Welcome assignment on activation	Not a product behaviour to copy

Keep the catalogue small enough to assign

Every procedure should have an audience you can say in one phrase. If you cannot, you wrote a handbook chapter. Categories help you browse; they are not a substitute for a rule. A category “Finance” with no distribution rule is a folder. A category plus a rule that maps Finance department employees to those procedures is assignment.

When two roles share most steps but not all, prefer two SOPs or a clearly scoped SOP with an exception line — not one mega-SOP assigned to both plus a verbal “ignore section 7 if you are in Pune.” Assignment cannot encode hallway caveats.

Review the rule list when you review the catalogue — a planned cadence, not only after a complaint. Dead rules that still include a closed site will chase people who cannot do the job. Missing rules for a new designation will show a clean report because nobody was assigned. Both look like success if you only glance at percentages. Count assigned heads against headcount for that job.

Revision control still applies: rules should point people at the current version. Re-read after a material change is a versioning and receipts decision. Assignment answers who is in the population; receipts answer who has confirmed. Do not merge those questions into “we assigned it, so they know.”

Transfers, exits, and dual hats

A transfer that updates department or designation should change the SOP list. If HR changes the manager in conversation but not on the employee record, distribution rules will not notice. That is an employee-management hygiene issue with SOP symptoms.

Exits should stop adding to outstanding receipt chases for job SOPs they no longer hold. How status flows is a lifecycle and directory concern; assignment rules should not be maintained by deleting people from a spreadsheet after they have gone.

Dual hats (a store manager who also runs local hiring) may need two populations or an explicit second rule. Do not rely on “they will know to open the other folder.” If both jobs are real, both assignments should be real.

Acting roles and temporary cover need a written choice: does the delegate receive the SOP assignment for the cover period, or only a named exception in the procedure? If the directory never shows the acting designation, a rule cannot see it. Either update the record for the cover window or assign the extra procedure by a second, explicit population you are willing to maintain. Informal “you are manager this week” without a record change is how receipts stay on the person who is on leave.

Locations and entities are roles’ cousins. A packing SOP for Site B should not auto-assign to Site A packers unless the steps are actually the same. If they share a designation but not a method, split the SOP or split the rule. Categories can group Site B operations; they still need a rule that names Site B, not “operations” as a mood.

What this page will not become

It will not become the welcome SOP article. Link it for activation-time reading, IT-provisioning boundaries, and the join path. Mentioning activation here is only to place the special case.

It will not become employee-management field design. Directory roles are cited because rules read them. Identity collection and org charts have their own owners.

It will not become receipts, writing craft, or policy-versus-handbook taxonomy, except to say assigned people still need a written current SOP and a receipt process. It will not link helpdesk. It will not claim AI assignment, AI generation, or AI search. PMS is not this topic: project membership is not an SOP audience unless you have chosen to misuse both products.

What you must assign for a given topic may depend on applicable law, contract, policy, or company practice. Verify with your HR, legal, or SME team. This page is operational guidance, not a statutory audience list.

Language to use in status updates

Prefer:

• “Rules: packing SOPs → Packer designation, Site B; not all-company.”
• “Welcome SOP still assigned on activation; job SOPs follow department rules after the record is correct.”
• “Transfer last Thursday: designation updated Monday — SOP list lagged until the record caught up.”

Audience is the job on the record, expressed as a rule, visible in My SOPs. If your distribution method is a zip file, you have circulation, not assignment.

Keep Dayzen SOP management as categories and assignment rules. Keep employee management as the source of role and organisation attributes those rules read. Keep the welcome SOP sibling as the activation starter. Then stop flooding inboxes. A person should see the procedures for the work they are paid to do — current version, named owner — and not the entire history of HR’s shared drive.