Content basis 15 October 2026 · manuals issued 16 October · official-source checks 17 October 2026

ACLASA methodology by countryLocal language first, English translation, governed company access

SK/EN, IT/EN, GR/EN and ES/EN provide a public online preview and a direct 10-page PDF. LT/EN is private and paid only. Full files remain protected by the exact country program and server grants; Latvia is not published because the enacted legal basis is not yet sufficient for a controlled document.

ACLASA rule: employer wording may sit above the ACLASA default text, but the ACLASA default remains preserved, traceable and exportable.

Preview, sign in, use governed outputs

Public packs expose a controlled online preview and a direct 10-page PDF. Full reading and downloads use separate exact country grants. Lithuania has no public preview; the current static production portal does not save or export an employer layer.

01

Start

Choose country

Select a public SK/EN, IT/EN, GR/EN or ES/EN pack, or review the private LT/EN access conditions.

Browse countries
02

Then

Read preview

Use the controlled online preview or download the direct public 10-page PDF for a public pack.

Read preview
03

Next

Company access

Use only a server-verified PAY session with the required company entitlement and grant.

Access requirements
04

Finish

Prepare a governed employer layer

A labelled localhost demo is available for UI testing; the production editor stays fail-closed until tenant-bound persistence is deployed.

Review access conditions

One controlled core, 27 legal overlays and 35 presentation languages

The presentation language and the applicable jurisdiction are selected independently. The country overlay records legal status, employer actions, dates and official sources without changing the ACLASA 1,200-point core.

Loading the governed methodology library…

Controlled public and protected country packs

Slovakia, Italy, Greece and Spain provide public previews. Lithuania remains private and entitlement-controlled. Latvia is shown only as an explicit exclusion and has no document.

ACLASA keeps the method owned and traceable.

The public method is a governed ACLASA standard. A future tenant-bound workspace may add employer wording, but the ACLASA default, source layer and change history must stay separate. The current production portal does not persist employer wording.

Public methodWork of equal value
Review basisISCO-08, EIGE and ACLASA factors
OwnerACLASA methodology owner
Company layerVisible employer wording

Check the work before using pay.

Use skills, responsibility, complexity, authority, effort and working conditions to confirm the ACLASA band and the ISCO context before any pay decision.

Skills

What the role needs

Look at knowledge, practical skill, problem solving and learning required by the real work.

Responsibility

What the role owns

Check decision authority, people impact, financial scope, risk and accountability.

Complexity

How hard the work is

Review ambiguity, coordination, independence, judgement and stakeholder pressure.

Evidence

Why the result holds

Keep the source, reviewer, date, exception and approval path visible for later audit.

Country methodology reader with a public preview boundary

Public packs expose their controlled preview without login. Protected country-pack content requires the exact read grant and program; electronic files require the separate download grant. Employer-specific production editing remains disabled pending the tenant-bound backend.

Legal

Slovak and EU aligned

The text keeps the hierarchy of law, collective agreement, employment contract and internal employer rules explicit.

Employer

Adoptable wording

The methodology can be adopted as an internal rule, directive or annex while keeping ACLASA ownership clear.

Portal

Company layer

The target backend records employer wording by stable section ID. The current production portal does not persist that layer; only a labelled localhost demo does.

PAY access

Access contract

The target model accepts only signed, short-lived PAY access assertions and then rechecks the ACLASA company entitlement and scoped grant. The current static deployment remains fail-closed until that backend is live.