JML Workflow Design Specification Template

A specification template used to design Joiner-Mover-Leaver workflows before any platform configuration begins. Its main purpose is structural: it forces mover logic to be specified with the same rigor as joiner and leaver logic, rather than being treated as an afterthought — see Why Mover Events Are Where JML Automation Actually Breaks for why that matters.

Structure

• Authoritative source mapping — which HR attributes drive which lifecycle events, and their effective-dating behavior.
• Joiner specification — birthright role assignment logic, target systems, and SLA.
• Mover specification — explicit grant and revoke logic: what’s added for the new role, what’s removed from the old one, and how overlapping or ambiguous transitions are handled.
• Leaver specification — deprovisioning timing, any grace-period exceptions and their approval/audit trail, and handling for non-employee identities that don’t originate from the same HR feed.
• Disconnected application handling — manual fulfillment process and SLA for target systems without a native connector.
• Reconciliation and audit requirements — what gets logged, and specifically why an event happened, not just what changed.

Why a template, not just a diagram

A reference architecture diagram shows the intended flow; it doesn’t force anyone to answer the harder questions — like what happens to entitlement X when someone transfers from department A to department B with partial overlap in responsibilities. The template’s section-by-section structure exists specifically to surface those questions during design, before they turn into access certification findings eighteen months later.