Start
Choose country
Select Slovakia SK/EN, Italy IT/EN or another verified country methodology.
Browse countriesACLASA methodology library - first 10 sections free
ACLASA methodology by countryLocal language first, English translation, governed company access
SK/EN and IT/EN methodologies live in one country library. The first 10 sections are public. Full reading and electronic downloads require separate exact grants. Production employer editing remains disabled until the tenant-bound company-layer backend is deployed.
ACLASA rule: employer wording may sit above the ACLASA default text, but the ACLASA default remains preserved, traceable and exportable.
How to use this methodology
Preview, sign in, use governed outputs
The first 10 sections are public. Full reading and downloads use separate grants. The current static production portal does not save or export an employer layer.
Then
Read preview
Use the first 10 sections without login to understand the ACLASA default method.
Read previewNext
Company access
Use only a server-verified PAY session with the required company entitlement and grant.
Access requirementsFinish
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 conditionsCountry methodologies
One ACLASA methodology library, organised by country
Each country methodology starts in the local language and includes an English governance translation. Public users can read the first 10 sections; full reading and downloads require separate paid grants. Production employer editing is not yet deployed.
Company access
Sign in with a company PAY account
ACLASA.pro does not create a separate password island. Protected access requires a server-verified company identity, active entitlement and scoped grant; a public product link or browser-local state never grants access.
Access rule
Free preview stops after 10 sections
- Sections 1-10: public preview without login.
- Full reader: paid ACLASA company program and
aclasa.methodology.read. - Electronic PDF/DOCX/data:
aclasa.methodology.downloadplus the paid country program and active period. - Employer drafting requires
aclasa.methodology.draftand publicationaclasa.methodology.publish; production remains disabled until tenant-bound persistence is deployed.
Method governance
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.
Job evidence factors
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.
What the role needs
Look at knowledge, practical skill, problem solving and learning required by the real work.
What the role owns
Check decision authority, people impact, financial scope, risk and accountability.
How hard the work is
Review ambiguity, coordination, independence, judgement and stakeholder pressure.
Why the result holds
Keep the source, reviewer, date, exception and approval path visible for later audit.
Online methodology
Country methodology reader with a public preview boundary
The first 10 sections are readable without login. Remaining sections require the read grant and downloads require the separate download grant. Employer-specific production editing remains disabled pending the tenant-bound backend.
Slovak and EU aligned
The text keeps the hierarchy of law, collective agreement, employment contract and internal employer rules explicit.
Adoptable wording
The methodology can be adopted as an internal rule, directive or annex while keeping ACLASA ownership clear.
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.
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.