Entry points
| Product or task | Production URL | Purpose |
|---|---|---|
| PayGapAnalyzer public portal | https://paygapanalyzer.pro/?lang=en | Public product information and synthetic demonstration |
| PayGapAnalyzer client entry | https://paygapanalyzer.pro/client-app?lang=en | Sign-in boundary for authorised client work |
| Company assessment request | https://paygapanalyzer.pro/request-assessment?lang=en | Structured company enquiry form |
| ACLASA PULSE | https://pulse.paygapanalyzer.pro/?lang=en | Public EU pay-transparency implementation view and controlled project entry |
| ACLASA Comp Manager | https://compmanager.paygapanalyzer.pro/?lang=en | Role, compensation and pay-review planning workflows |
| Current guides | https://paygapanalyzer.pro/guides?lang=en | Current public help and downloadable guide formats |
1 Start here
Choose the journey that matches the result you need. Public and demonstration journeys use synthetic or non-personal information. Client journeys require an authorised account and the entitlement agreed with ACLASA.
| Your goal | Start here | Expected result |
|---|---|---|
| Understand the portfolio | Open the PayGapAnalyzer public portal | A product overview and links to the three applications |
| Try pay-gap analysis safely | Select the synthetic demonstration | A worked analysis without uploading your payroll data |
| Review an existing analysis | Sign in through the PayGapAnalyzer client entry | A controlled review surface with deterministic metrics and an editable action plan |
| Plan EU pay-transparency implementation | Open ACLASA PULSE | A country, evidence, workstream and project view |
| Prepare role and compensation work | Open ACLASA Comp Manager | A structured draft, comparison or pay-review plan |
| Discuss a client implementation | Submit the company assessment form | A structured request that ACLASA can review and follow up |
- Select your language in the portal header before starting a task.
- Confirm whether you are using a public synthetic journey or an authorised client journey.
- Do not enter employee names, employee identifiers, payroll rows or other personal data into public, trial or transient workflows.
- Use the result only for the purpose stated on the screen and keep the displayed limitations with any exported evidence.
- Escalate legal, methodological and remuneration decisions to an appropriately qualified human reviewer.
2 Accounts access and data boundaries
The portfolio uses different access boundaries because the three applications do different work. A visible link is not proof that your account includes that product or that persistent team storage is enabled.
| Mode | What you can do | Data rule |
|---|---|---|
| Public | Read product information, view public PULSE content and open guided demonstrations | Use only information already published by ACLASA and synthetic examples |
| Synthetic demonstration | Run the provided example and inspect results and exports | The dataset is supplied by ACLASA; you cannot replace it with your own payroll data |
| Authorised PayGapAnalyzer client | Open the client review journey supported by your entitlement | Follow the agreed local-processing and aggregate-receipt boundary |
| Controlled PULSE workspace | Work with approved project metadata, evidence references, tasks and review states | Do not enter payroll rows or employee personal data |
| Comp Manager transient workflow | Prepare and download a draft during the current session | Assume the public workflow is transient unless a separate persistent service is explicitly confirmed |
- If a sign-in action returns you to the client entry, your identity may be valid while the requested product entitlement is not yet active.
- If a controlled workspace denies access, do not create a second account to bypass the boundary. Submit the company assessment form or contact your named ACLASA implementation lead.
- Logging in does not convert a public synthetic workflow into an approved environment for payroll or employee data.
- External AI execution is not assumed. Deterministic analysis and recoverable drafts remain the authoritative fallback when an external provider is unavailable or not configured.
3 Language and navigation
The language selected in the header applies to the whole portal journey. A country selection changes the applicable methodology or project context; it must not silently change the interface language.
- Open the language control in the header and choose the full language name.
- Confirm that the page title, navigation, form labels, validation messages and accessible names use the selected language.
- Continue through links, sign-in, validation and safe return. The selected language should remain active.
- If one surface changes to another language, stop before entering data and report the route, selected language and visible text.
Protected names, identifiers, formulas, signed evidence and source quotations can remain in their original language. That is not an interface-language fallback.
4 PayGapAnalyzer public portal and synthetic demonstration
Use the synthetic demonstration to understand the analysis flow without sending your payroll data to the server.
- Open https://paygapanalyzer.pro/?lang=en and select Show demo or the equivalent action in your chosen language.
- Review the demo notice and confirm that the company, workforce and payroll records are synthetic.
- Choose the available core metric only when the demonstration asks for it. Do not treat a demo choice as a statutory reporting decision for your company.
- Start the demonstration and wait for the deterministic analysis to finish.
- Review the observed result and model views separately. A measured difference, a model estimate and an explanation are not the same conclusion.
- Open the methodology and limitation information before sharing a result.
- Download only the exports offered by the demonstration and retain the synthetic-data label with them.
- Use Request company assessment when you want ACLASA to evaluate a real implementation need.
| Result element | How to read it |
|---|---|
| RAW | The observed unadjusted difference in the stated population and period |
| OLS | A model estimate conditional on the variables and diagnostics used |
| Oaxaca Blinder | A decomposition view subject to the stated model and data limitations |
| Suppressed result | A result intentionally withheld because the evidence boundary or small-group rule does not permit disclosure |
| Action suggestion | A proposal for human review, not an automatic decision or legal conclusion |
The public demonstration is not the paid country-specific statutory workflow. It does not certify compliance and it does not accept your own payroll files.
5 PayGapAnalyzer client review and action plan
The authorised review journey combines deterministic evidence with an editable explanation and action plan. Numerical authority stays with the deterministic engine; the reviewer controls what is accepted for export.
- Open https://paygapanalyzer.pro/client-app?lang=en and sign in with the account supplied or approved by ACLASA.
- Open the case available to your entitlement. Confirm the company scope, population, period, purpose and mapping before reviewing results.
- Verify the receipt identity and the displayed deterministic metrics. The review layer should receive a sanitised aggregate receipt, not payroll rows, employee identifiers, residuals or protected attributes.
- Read each statement by category: observed result, model estimate, hypothesis, limitation, recommendation and required human decision.
- For every proposal, choose Accept, Edit or Reject. Edit wording without changing the underlying metric identity or value.
- Resolve warnings about insufficient data, suppression, rank deficiency, missing mapping or stale evidence before approval.
- Approve only the statements and actions you are authorised to own.
- Generate PDF, XLSX or JSON evidence only after the review state is correct. The export contains the approved state and audit information, not rejected draft text.
- Store the export under your company retention rules and record the human approver and decision date outside the public demonstration environment.
- If AI is unavailable, continue with the deterministic analysis and exports. Do not repeat the upload or recreate the case merely to obtain narrative text.
- If the receipt digest or metric identity does not match the case, stop and reopen the authoritative case rather than copying numbers manually.
- Never convert a hypothesis into a finding of causation or discrimination without the required evidence and qualified review.
- Server payroll upload remains disabled on the accepted production release. Use only the approved local-processing and aggregate-handoff method.
6 ACLASA PULSE public view
The public PULSE view helps a team understand EU pay-transparency implementation topics and move from a country overview to an implementation discussion. Public content is not a complete legal opinion and must show its evidence and freshness limits.
- Open https://pulse.paygapanalyzer.pro/?lang=en.
- Review the decision cockpit and confirm the scope and last-observed information displayed for the item you are using.
- Open the country register and select the country relevant to your implementation programme.
- Review transposition, implementation, evidence and uncertainty as separate concepts. A parliamentary or procedural event is not automatically an employer deadline.
- Use the implementation workstreams and timeline to identify the evidence and owner questions that need qualified review.
- Open a cited source from its source record when a decision depends on the detail. Do not rely on a card title alone.
- Use the PayGapAnalyzer or Comp Manager handoff when the next task is analysis or compensation design rather than implementation tracking.
The current production release provides a rich synthetic and public PULSE surface. It does not by itself prove a daily qualified legal update service for every country. Check the displayed source and observation date before acting.
7 ACLASA PULSE controlled workspace
A controlled workspace is for approved non-personal project metadata, source references, workstreams, tasks, review questions and decisions. Access and persistent collaboration depend on the client service and entitlement actually activated for your organisation.
- Sign in through the portfolio client entry and open the PULSE workspace offered by your account.
- Confirm the tenant, project and role shown on screen before reading or changing a draft.
- Create or select the legal entities and countries that define the programme scope. Do not add employee-level information.
- For each country, record the source ID, source title, HTTPS location, source version, observation date and evidence-based explanation.
- Separate national transposition status from your organisation's implementation status.
- Create workstreams and milestones, assign an owner, add a due date and state the evidence needed to complete the task.
- Use comments and reviewer questions to document uncertainty. Do not mark qualified review, legal compliance or closure unless the authorised human reviewer has made that decision.
- Review proposed changes as drafts. Accept, edit or reject them with the current expected revision so a conflicting update is not silently overwritten.
- Export the available project brief or backup and verify that it can be read before relying on it for recovery.
- An access-denied page normally means the tenant, role or entitlement does not authorise that workspace. It is not a reason to bypass the boundary.
- If persistence is not explicitly enabled, treat the workflow as a preview and keep the approved backup in your own controlled environment.
- PULSE must not receive payroll rows, employee IDs or salary records. Use PayGapAnalyzer's approved local and aggregate boundary for pay analysis.
8 ACLASA Comp Manager
Comp Manager structures role, compensation and pay-review work. The public production workflow is designed as a professional draft and transient planning surface; it is not an automatic pay decision and it does not imply persistent team storage.
| Workflow | Use it for | Primary output |
|---|---|---|
| Role description | Create or review a role description from structured information or a supported document | Editable professional draft |
| Job evaluation handoff | Prepare role evidence for the ACLASA 14-factor method | Structured handoff for qualified evaluation |
| Pay mix | Compare fixed, variable and other compensation components | Scenario summary for human review |
| Relocation | Structure location and mobility assumptions | Comparable relocation draft |
| Pay review | Prepare a synthetic or approved review plan and supported workbook flow | Review plan and downloadable evidence |
| Catalogue and references | Inspect governed role or ISCO context | Source-bound reference context |
- Open https://compmanager.paygapanalyzer.pro/?lang=en and select the workflow that matches your intent.
- Read the purpose and data boundary before entering information.
- Use synthetic, redacted or otherwise approved inputs. Do not enter personal payroll data into the public transient workflow.
- Complete the minimum required fields. Reuse imported or inferred information only after checking its source and confidence.
- Review the draft, assumptions, exclusions and evidence prompts. A title or ISCO suggestion does not establish an ACLASA band or pay outcome.
- Edit the draft until it accurately represents the role or scenario.
- Download the available document, workbook or JSON result before leaving the page when the workflow says storage is transient.
- Use Return to PayGapAnalyzer for pay-gap analysis or PULSE for implementation programme work.
- Use the client entry when you need an authorised service. The portfolio sign-in link does not by itself prove that Comp Manager persistent collaboration is enabled.
CCNL mapping and reverse recommendation for Italian positions are not described as production-effective in this guide. Do not rely on a draft mapping as a statutory classification or collective-agreement determination until the relevant product owner and qualified reviewer accept that capability.
9 Moving between the applications
Use one application for each decision stage and carry only the minimum approved information to the next stage.
| From | To | Carry forward | Do not carry forward |
|---|---|---|---|
| PULSE | PayGapAnalyzer | Approved scope, country, purpose, population, period and evidence question | Country-card text as if it were payroll evidence |
| Comp Manager | PayGapAnalyzer | Approved role structure, mapping decision and documented assumptions | Unreviewed title suggestions as final classification |
| PayGapAnalyzer | PULSE | Approved aggregate finding, limitation, owner action and evidence reference | Payroll rows, employee IDs, residuals or protected attributes |
| PayGapAnalyzer | Comp Manager | Approved action requiring role or compensation design | A model estimate presented as an automatic pay decision |
- Finish the current review and export or save the approved state permitted by that product.
- Record the purpose of the handoff and the human owner.
- Use the product navigation link and confirm the destination domain before entering information.
- Reconfirm the language, tenant and data boundary on the destination product.
- Enter or import only the approved minimum information.
10 How a company becomes an ACLASA client
Use the structured assessment request instead of composing an unstructured email. The form gives ACLASA the minimum information needed to understand the company scope and arrange the next step.
- Open https://paygapanalyzer.pro/request-assessment?lang=en.
- Enter the company name and a business contact email that your organisation authorises for this enquiry.
- Select or enter the company country and workforce size requested by the form.
- Choose the evaluation scope that best describes the intended outcome.
- Use the optional note for countries, legal entities, target timing, existing systems and the result you need. Do not paste payroll rows, employee information, credentials or secrets.
- Review the privacy and purpose statement, then submit the form once.
- Keep the confirmation displayed after submission.
- ACLASA reviews the request and can contact the company to confirm scope, data boundary, methodology, roles, security, entitlement, commercial terms and implementation sequence.
- Do not treat submission as account activation, a quote, a binding order or confirmation that every requested feature is available. Those steps require explicit follow-up and acceptance.
| Prepare before contact | Why it matters |
|---|---|
| Countries and legal entities | Determines the statutory and organisational scope |
| Workforce size and populations | Supports proportionate processing and review design |
| Purpose | Separates statutory, EU PTD, global ESG, diagnostic and compensation-design use |
| Reporting period | Distinguishes calendar-year statutory work from a corporate financial-year ESG view |
| Available fields and source systems | Allows a safe mapping plan without sending payroll data in the enquiry |
| Decision owners and reviewers | Clarifies who may approve methodology, legal interpretation and remuneration action |
| Required outputs | Defines the evidence, export, language and handoff expected by the company |
11 Data preparation privacy and security
Apply data minimisation before processing. Public and transient portfolio surfaces are not a substitute for the approved local payroll-processing workflow.
- Use synthetic data for demonstrations, training and screenshots.
- Keep employee-level payroll data in the approved local environment unless a separately accepted contract explicitly states otherwise.
- Remove names, direct identifiers, free-text comments and unnecessary protected information before a governed handoff.
- Confirm the country, purpose, population, pay definition, currency, working-time normalisation and reporting period before calculating.
- Preserve source provenance, mapping decisions, exclusions, suppression rules and diagnostics with the result.
- Do not upload credentials, API keys, medical information, disciplinary records or unrelated HR documents.
- Use your organisation's approved storage, access, retention, backup and deletion controls for downloaded evidence.
A country-specific statutory workflow can require different source fields, periods and calculations from a global ESG view. Select the purpose first and do not reuse an ESG result as a statutory filing without the required country method and review.
12 Exports evidence and human approval
An export is useful only when its scope, source, method, limitations and approval state remain understandable after it leaves the application.
- Confirm the company scope, population, period, purpose and selected language.
- Confirm that the deterministic metrics and diagnostics match the case shown on screen.
- Resolve or retain every material warning. Do not remove a limitation merely to simplify the report.
- Accept, edit or reject draft narrative and actions before export.
- Generate the required PDF, XLSX or JSON format.
- Open the downloaded file and verify its title, values, labels, language, page or worksheet structure and approved-state audit.
- Record the human reviewer, decision and date under your company's governance process.
- Store and share the file according to its sensitivity and retention rule.
- A PDF supports readable evidence but is not the calculation source of truth.
- An XLSX supports structured review but formulas and values must remain bound to the accepted method.
- A JSON receipt supports machine verification but does not replace a human decision.
- If a download is incomplete or cannot be reopened, repeat only the export step. Do not recreate the underlying case unless its authoritative state is unavailable.
13 Accessibility and mobile use
The accepted interfaces support keyboard use, responsive layouts, right-to-left presentation where applicable and a protected mobile menu. Report a route-specific problem rather than working around an inaccessible control.
- Use Tab and Shift Tab to move through interactive controls and Enter or Space to activate a native button.
- Open and close the mobile menu with its labelled button. Escape should close it and return focus safely.
- At mobile widths, controls should remain usable without horizontal page scrolling and primary touch targets should be at least 44 by 44 CSS pixels.
- At 200 percent text zoom, content should reflow rather than overlap or become unreachable.
- The visible language name and accessible control name should identify the selected language.
- For an accessibility defect, record the product, route, language, device or viewport, browser, action, expected result and actual result. Do not include customer data in the report.
14 Troubleshooting and recovery
Recover from the smallest affected step. Avoid repeating data entry, creating duplicate cases or bypassing an access boundary.
| What you see | What to do |
|---|---|
| Access denied | Confirm the account, tenant, product and entitlement. Return to the client entry or submit the company assessment form. Do not create a second identity to bypass access. |
| Wrong interface language | Re-select the full language name in the header. If the mismatch remains, stop before entering information and report the route and visible text. |
| Provider or AI unavailable | Continue with deterministic results and the saved draft. Retry the narrative step later without rebuilding the analysis. |
| Insufficient data or suppression | Review the population, mapping and minimum-group rule. Do not infer a hidden value or disable suppression. |
| Rank deficiency or model warning | Review variables, reference groups and diagnostics with a qualified analyst. Preserve the warning in the evidence. |
| Conflict while saving a PULSE draft | Reload the current revision, compare the conflicting changes, then apply the intended edit once. |
| Comp Manager result may be lost | Download the current draft or export before navigating away. Treat the public workflow as transient unless persistence is explicitly confirmed. |
| Export does not open | Repeat only the export, then check file size and format. Keep the on-screen approved state and do not manually retype values. |
| Page layout is broken on mobile | Reload once, confirm text zoom and browser settings, then report the route, language, viewport and screenshot without customer data. |
15 Current production limits
These limits prevent a public or technically available surface from being mistaken for a fully contracted, legally approved or persistent client service.
- The public PayGapAnalyzer demonstration uses ACLASA synthetic data and does not accept customer payroll uploads.
- The separate paid Powered MultiMetrics application and complete set of country-authority adapters are not documented as production-active here.
- PULSE public content does not prove a daily qualified legal update service for every country. Source dates and review states must be checked.
- PULSE persistent private team collaboration depends on an explicitly activated client service and entitlement.
- Comp Manager public workflows are transient unless a separate persistent service is confirmed; team mode and external AI are not assumed.
- Italy CCNL forward mapping and reverse recommendation are not represented as production-accepted capabilities in this revision.
- Technical language rendering does not equal native, legal or methodological approval.
- A submitted assessment request is not a confirmed order, account, price, payment, invoice or entitlement.
16 Glossary
Use these terms consistently when discussing a result or implementation plan.
| Term | Meaning in this guide |
|---|---|
| Aggregate receipt | A sanitised, integrity-bound description of approved analysis inputs and outputs without payroll rows or employee identifiers |
| Deterministic metric | A value calculated by the governed analysis engine rather than invented by narrative AI |
| Draft only | A proposal that requires an authorised human to accept, edit or reject it |
| Entitlement | The product, role and scope an authenticated account is authorised to use |
| Human decision | A decision made by the accountable qualified person, not by the application |
| Purpose | The approved reason for processing, such as EU PTD statutory work, global ESG reporting or internal diagnostic analysis |
| Suppression | A rule that withholds a result when disclosure or evidence requirements are not met |
| Transient | Not promised to remain available after the current session; download the permitted result before leaving |
| Qualified review | Review by a person authorised and competent for the relevant language, methodology, legal or remuneration decision |
Document control
Author: ACLASA s. r. o.
Revision: 2026-11-14-R2
Effective date: 14 November 2026
Covered product release: 347b2996aafdce5979ee8c6b9e4e804c98f15fee
Covered product tree: b39b521eb024ceb16aaf1b446937408d4cb29a7c
Supersedes the public portfolio guide dated 3 November 2026.