Pick your role first. Then we'll guide you by learning goal and learner mode.
Application mode
Choose a straight certification route or switch into research mode for broader topic exploration.
Learning goal
Choose the outcome you want first. We will guide the next step around that goal instead of showing everything at once.
Learning mode
Choose how much guidance, pacing, and explanation you want.
Are you familiar with the relevant Zalaris standards?
Standards
ZASAM is data-first: we analyze customer payroll data before any workshop. Configuration decisions are made from evidence — not from workbooks filled out by the client.
ZASAM uses a lean, highly accountable team. Each role owns outcomes end-to-end — from data analysis through go-live. No handoffs, no intermediaries.
Six phases with formal quality gates (A1–A5): Pre-Project → Discover → Prepare & Build → Optimize & Test → Deploy → Run. Every gate requires evidence, not documentation.
Accountability is defined by RACI. One accountable owner per activity. Meetings are focused on decisions — not status. Client involvement is high only where it genuinely matters.
No data, no start. Required inputs include legacy payslips, legal reports, master data, and integration samples — delivered before kickoff. Outputs are a validated payroll system and an operational handover package.
ZAPSE (project management, RAID logs, templates) and the ZASAM Data Analysis Tool (AI-supported data mapping, payslip extraction, migration export) are the two core platforms across the project.
Knowledge Check
5 questions on methodology, roles, phases, responsibilities, and tools.
These principles are the operational contract of ZASAM. They define how we run projects, how we work with clients, and how we protect speed, quality, and margin.
01 · Start from evidence
We reduce ambiguity early: first secure the data package, then analyze it, then align with the client on facts instead of assumptions.
02 · Deliver with ownership
Delivery stays fast when experienced people own outcomes end-to-end, validate incrementally, and escalate only the decisions that truly need client authority.
03 · Protect focus and control
Meetings, documentation, and change control exist to protect delivery quality. They are tools for control, not theatre for the project.
Operating Rules
Each card is one non-negotiable rule. Together they show how ZASAM protects speed, quality, and margin.
01
Start from evidenceThe operational project does not begin before the agreed customer data package is fully delivered.
02
Deliver with ownershipHighly skilled consultants own delivery areas end-to-end. If a role needs a messenger, the setup is wrong.
03
Start from evidenceAnalyze first, then engage with concrete client questions. No broad workbook-driven discovery sessions.
04
Start from evidenceThe Data Analysis Tool structures customer reality quickly and consistently, reducing dependency on subjective explanations.
05
Deliver with ownershipConfiguration and testing run iteratively. Feedback loops are short, and quality is proven continuously through cycles like CIPC.
06
Protect focus and controlDocumentation exists to enable BAU operations. We document what is needed to run the client, not what is traditional.
07
Deliver with ownershipZalaris configures based on expertise and data. Client decisions are requested only where client authority is required.
08
Protect focus and controlClient meetings are decision-focused, prepared, and small. Status reporting is asynchronous unless dialogue is necessary.
09
Protect focus and controlAgility inside contractual boundaries, formal change control outside. This protects timeline, budget, and delivery quality.
Knowledge Check
5 questions covering the 9 operating rules across data, delivery, and governance.
Interactive process map of all ZASAM phases. Click any node to see its goal, responsibilities, tool support, and gate checks.
Knowledge Check
5 questions on the six phases, quality gates A1–A5, and process responsibilities.
Before workshops, build, or detailed discovery start, the customer package must be uploaded through the portal, checked, and formally accepted against the A1 gate.
Critical Start Gate
This is foundational project input, not background material. It determines whether delivery may start at all.
Portal-Led Process
Gate Acceptance
Coverage
The delivery hub narrows requirements by country and source system, so the team sees the exact package that matters for the current customer context.
Knowledge Check
5 questions on the customer data package, gate checks, and portal-led process.
Four section-specific quizzes generated from the onboarding content plus optional global-standard bonus quizzes. Start with the topic you've just read, or work through the full set.
Section Quiz
Methodology, roles, phases, responsibilities, inputs & outputs, and tool support.
Section Quiz
The 9 operating rules across data, delivery, and governance clusters.
Section Quiz
The six ZASAM phases, quality gates A1–A5, and process responsibilities.
Section Quiz
Customer data package, gate acceptance checks, and the portal-led process.
Optional Quizzes
Optional deep-dive checks from the consultant and sales standard areas. These are open to everyone and do not replace the four core onboarding quizzes.
Once delivery intake is secured, use Deep Dive for role-guided journeys, topic detail, and process hotspots across methodology, phases, testing, tools, RACI, and support.
Fast Start
Pick your role once and open the role journey with the same filter pre-applied.
Choose a role to get a guided pathArea Entry
Choose by topic and jump into the detailed view with tasks, tools, and responsibilities.
Process Entry
Open critical process points directly and review goals, interactions, and tool support.
