If you are searching for how to translate ICSE-18 codes, how to translate employment status categories, how to translate employer, own-account worker, dependent contractor or permanent employee correctly, or how to preserve labour-statistics meaning across languages, the first rule is to translate the category label without changing the work relationship it represents. ICSE-18 is a statistical classification of status in employment, not a list of ordinary job titles.
This matters in labour force surveys, employment statistics, census data, social-protection research, platform-work studies, labour-market dashboards, policy reports, household surveys, HR analytics, informality research and international comparisons. A translation can be fluent and still be wrong if an employer becomes a manager, if an own-account worker becomes a generic freelancer, if a dependent contractor is translated as an employee, or if a fixed-term employee is collapsed into a broad temporary-worker label that loses the statistical boundary.
This guide explains how to translate ICSE-18 safely: what status in employment measures; how authority and economic risk create two analytical hierarchies; why dependent contractors are important; how employer, owner-operator, own-account worker, employee and contributing family worker differ; how to handle survey questions and national mappings; and how to protect codes and category meaning in multilingual datasets. It stays deliberately narrower than the broader eduKateSG translation architecture and does not compete with the existing ISCO occupation-code owner.
1. Status in employment is not occupation
Occupation describes the kind of work a person does; status in employment describes the type of work relationship the person has in a job. A software developer can be a permanent employee, a dependent contractor, an own-account worker or an employer. The occupation can remain the same while employment status changes. Translators must keep ICSE-18 separate from ISCO occupation language so “what work?” and “under what relationship?” do not collapse into one field.
2. ICSE-18 replaced the older ICSE-93 framework for new standards
The International Labour Organization adopted the revised International Classification of Status in Employment in 2018. Compared with ICSE-93, ICSE-18 provides more detail and explicitly introduces dependent contractors as a separate category. Historical datasets can still use ICSE-93, so translation should preserve the version used by the source rather than silently modernizing every old label.
3. ICSE-18 can be organized by type of authority
ICSE-18-A organizes employed persons according to the type of authority they can exercise in relation to the work performed. At the top level it distinguishes independent workers from dependent workers. This is not merely a wording preference. The hierarchy reflects whether the worker controls the economic unit and work relationship or is dependent on another actor for key aspects of the work.
4. ICSE-18 can also be organized by economic risk
ICSE-18-R provides an alternative analytical arrangement based on economic risk, including the distinction between employment for profit and employment for pay. The same detailed categories can be grouped differently depending on the analytical perspective. A translation must therefore preserve not only the category label but also which hierarchy the table or report is using.
5. Independent worker does not simply mean “self-employed”
Everyday language often uses self-employed as an umbrella term, but ICSE-18 makes finer distinctions. Independent workers can include employers and independent workers without employees, with further detail according to whether the enterprise is incorporated or a household market enterprise. Translating all these categories as one general self-employed label destroys the classification’s analytical purpose.
6. Employer is a relationship category, not a seniority title
In ICSE-18, employers are independent workers who own the economic unit in which they work and regularly employ one or more employees. The word does not mean supervisor, executive, boss or hiring manager. A corporate manager can be an employee rather than an employer. Translate employer according to ownership and hiring relationship, not workplace rank.
7. Employers in corporations are distinct from employers in household market enterprises
ICSE-18 distinguishes employers according to whether they operate incorporated enterprises or household market enterprises. That distinction matters because the legal and economic relationship between worker and enterprise differs. A target-language translation should preserve “corporation” versus household market enterprise rather than replacing both with a generic business-owner label.
8. Independent workers without employees form a separate group
These workers operate an economic unit without regularly employing employees. They are not automatically contractors, freelancers or sole traders in every legal system. The statistical category is defined by the work relationship and enterprise characteristics, not by a local tax label. Use national legal terms only if the official survey mapping explicitly supports them.
9. Owner-operators of corporations without employees are not ordinary employees
A person can work in an incorporated enterprise that they control while having no regular employees. ICSE-18 recognizes this as a distinct status. Translation can fail if “owner-operator” becomes employee because the person draws income from the corporation, or if “corporation” is omitted because the target language prefers simpler business wording.
10. Own-account workers in household market enterprises are another distinct category
Own-account workers in household market enterprises operate unincorporated market enterprises without regularly employing employees. This category is narrower than everyday phrases such as independent professional or freelancer. Preserve the household-enterprise and no-regular-employees meaning when the source provides that detail.
11. Dependent contractor is a core ICSE-18 concept
Dependent contractors have commercial contractual arrangements to provide goods or services for or through another economic unit, but they depend on that unit for organization and execution of work, income or market access. They are one of the important additions in ICSE-18 because traditional employee-versus-self-employed language often fails to describe modern dependent work accurately.
12. Dependent contractor is not automatically “gig worker”
Platform work provides useful examples, but the statistical category is broader than app-based work. A dependent contractor can exist in construction, transport, sales, professional services, home work or other sectors. Translating dependent contractor as gig worker can make the category sound narrower and more technologically specific than the standard intends.
13. Dependent contractor is not automatically employee
Dependence can exist without the worker being classified as an employee under ICSE-18. That is precisely why the category exists. A target language that commonly uses one broad word for worker or contractor needs careful phrasing so the statistical distinction remains visible.
14. Dependent contractor is not automatically independent worker
A person may call themselves self-employed or operate under a commercial contract yet still be economically dependent on another unit. Translation should not take self-description as final classification. Survey instruments often ask additional questions about clients, control, price-setting, market access and organization of work to identify dependency.
15. Employees form several detailed categories
ICSE-18 distinguishes permanent employees, fixed-term employees, short-term and casual employees, and paid apprentices, trainees and interns. These categories are not stylistic variants of employee. They capture differences in expected duration and form of employment relationship, so each needs a precise target-language equivalent.
16. Permanent employee does not mean lifetime employment
Permanent usually means the employment arrangement is not limited to a specified end date in the way a fixed-term contract is. Translators should avoid target-language words that imply an absolute guarantee of employment for life. The statistical concept concerns contract or arrangement duration, not a promise that the job can never end.
17. Fixed-term employee needs a defined end condition
Fixed-term employment is characterized by a contract or arrangement limited by a specified period or event. A language that uses temporary broadly for all non-permanent workers can erase the distinction between fixed-term and casual or short-term work. Preserve the more specific concept when the source does.
18. Short-term and casual employees are not necessarily fixed-term in the same sense
Casual and short-duration arrangements can be organized differently from formal fixed-term contracts. Translation should reflect the source statistical definition rather than assume that all time-limited work belongs to one category. Survey metadata is especially important because national labour-law terminology can differ from international statistical terminology.
19. Paid apprentices, trainees and interns are employees in ICSE-18
Paid apprentices, trainees and interns work for pay in an economic unit to gain workplace experience or skills. Translators should preserve the paid element and should not collapse this category with unpaid trainee workers in the broader status-at-work framework. The difference is substantive, not merely linguistic.
20. Contributing family workers are dependent workers
Contributing family workers help in a market-oriented enterprise operated by a household or family member without receiving regular pay. The category should not be translated as volunteer, unpaid employee or family business owner. The relationship to the family enterprise and the absence of regular remuneration are central.
21. Contributing family worker is not simply “family helper”
In ordinary speech, family helper can describe many unpaid activities. ICSE-18’s employment category concerns work in a market-oriented household or family enterprise. Broader unpaid family work can appear elsewhere in the status-at-work framework. A translation should preserve the employment context instead of using a vague domestic-help phrase.
22. ICSE-18 sits inside the wider Classification of Status at Work
The broader International Classification of Status at Work includes categories beyond employment, such as certain unpaid trainee workers and volunteers. ICSE-18 covers the employment subset. This boundary matters when translating reports about all work rather than employment only. Do not assume every status-at-work code is an ICSE-18 employment category.
23. ICSE-18-A and ICSE-18-R can regroup the same detailed categories
Under the authority hierarchy, owner-operators of corporations belong among independent workers. Under the economic-risk hierarchy, they can be grouped with employment for pay. The detailed category does not change, but its analytical parent can. Translators must therefore check table headings and hierarchy labels rather than assuming one parent structure.
24. “Independent” is a statistical concept, not a personality trait
Some languages use independent to suggest autonomy, freelance identity or personal freedom. In ICSE-18, the concept is defined through authority in the work relationship. Translate it in a way that preserves that technical sense and does not drift into motivational or legal language unrelated to the classification.
25. “Dependent” does not mean unskilled or powerless in every respect
Dependency in the classification refers to the employment relationship, not a judgment about competence, income or social status. A highly paid specialist can be a dependent worker. Avoid target-language terms that carry unnecessary stigma or imply personal incapacity.
26. Economic risk is different from job insecurity
ICSE-18’s economic-risk perspective concerns how remuneration and enterprise outcomes affect the worker. It should not be translated as the everyday idea of having a risky or unstable job. A permanent employee can face job insecurity, while an independent business owner can have strong market demand. Keep statistical economic risk distinct from subjective insecurity.
27. Authority is different from supervisory responsibility
A manager can supervise many employees while remaining a dependent employee of the organization. ICSE-18 authority concerns control over the economic unit and work relationship, not simply authority over colleagues. Translators should avoid words that make the independent-versus-dependent distinction sound like organizational rank.
28. Incorporation is a structural variable
Whether an enterprise is incorporated helps distinguish some ICSE-18 detailed categories. The translation must therefore preserve corporation or incorporated-enterprise terminology accurately. Do not replace it with generic company or business if the target language uses those words for both incorporated and unincorporated units.
29. Regularly employing workers matters
The employer distinction depends on employing one or more employees on a regular basis. Occasional help or one-off subcontracting does not necessarily have the same statistical meaning. Survey questions and national implementation manuals define how to operationalize this. Translators should preserve qualifiers such as regularly rather than deleting them as stylistic detail.
30. Client dependence can matter for dependent contractors
Survey instruments may examine whether a worker depends on one main client, receives clients or inputs from another unit, lacks control over prices, or depends on another actor for market access. These are not merely business-description questions. They help identify the work relationship. Translate them with consistent controlled vocabulary so the classification logic survives.
31. Price-setting control needs precise wording
A question about who sets the price of goods or services can help distinguish economic dependence. Translating “set,” “determine,” “negotiate” and “accept” loosely can change respondents’ answers. Survey translation should preserve the decision-making distinction and be cognitively tested where possible.
32. Work organization is another dependency signal
Who determines schedules, methods, clients, inputs or access to work can matter to classification. These concepts are culturally and legally sensitive. Avoid replacing several distinct questions with a broad phrase such as “who is your boss?” because that can force respondents into an employee frame even when the relationship is commercial but dependent.
33. Employment status is job-specific
A person can hold more than one job with different statuses at the same time. Someone may be a permanent employee in a main job and an own-account worker in a second job. Translation should preserve whether a variable refers to the main job, second job, previous job or all jobs. Do not convert a job-level classification into a person-level label without explanation.
34. Main-job and second-job fields must remain distinct
Labour-force microdata often repeat employment-status variables for several jobs. A translation memory can easily carry a correct label into the wrong variable name. Keep job-number suffixes, questionnaire references and field keys protected so the same respondent’s different work relationships do not become mixed.
35. Survey wording is not the same as classification wording
Respondents may never be asked “Are you a dependent contractor?” Instead, surveys derive the category from several questions about ownership, employees, contracts, clients, control and payment. Translators should distinguish interviewer-facing classification labels from respondent-facing questions. Technical precision and natural survey language have different requirements.
36. Questionnaire translation needs cognitive equivalence
A literal translation can fail if respondents interpret corporation, employee, business owner, client or family enterprise differently in the target culture. Good survey translation preserves the decision path respondents need to follow. Back-translation alone is not enough; expert review and cognitive testing can reveal whether terms trigger the intended concepts.
37. National legal categories may not map one-to-one
Domestic labour law can define employee, contractor, sole proprietor, director or apprentice differently from international statistical standards. A translation should not assume that the nearest legal term is automatically the correct ICSE-18 equivalent. Keep national status and international statistical status as separate dimensions where necessary.
38. Tax status is not automatically ICSE-18 status
Workers can be registered for tax in ways that do not fully describe the authority and dependency of the job. A person taxed as self-employed can still show characteristics of a dependent contractor under statistical standards. Translators should not replace ICSE terminology with local tax labels unless the source explicitly does so.
39. Informality is a separate dimension
ICSE-18 status and formal-versus-informal employment are related but not identical. Employees, dependent contractors, independent workers and contributing family workers can have different formalization conditions. Translating an ICSE category as “formal worker” or “informal worker” changes the variable and should be avoided.
40. Platform work should not be forced into one status
Digital platforms can organize work through different contractual and economic arrangements. Some workers can be employees, some dependent contractors, and some genuinely independent. A translated report should preserve the evidence-based status rather than use platform worker as a substitute classification.
41. Freelancer is not an ICSE-18 code
Freelancer is an everyday market term used for many kinds of independent or contract work. It can describe people with very different dependency, incorporation and hiring arrangements. When a source says freelancer, translate the term naturally, but do not infer a precise ICSE-18 category without additional evidence.
42. Contractor can be dangerously ambiguous
Contractor can refer to an independent business, a dependent contractor, an employee on a fixed-term contract or even a company supplying services. The phrase “dependent contractor” must therefore be translated as a defined statistical category rather than shortened to contractor if the target language would lose the dependency meaning.
43. Employee and worker are not synonyms in every dataset
Worker is often the broader term. Employee is a specific status category. Translating every worker as employee can exclude employers, own-account workers, dependent contractors and contributing family workers. Build a glossary that distinguishes person-in-work terms from status-in-employment terms.
44. “Not elsewhere classified” is a technical residual
Operational datasets can include residual categories such as employers not elsewhere classified, own-account workers not elsewhere classified, employees not elsewhere classified or workers not classifiable by status. Do not simplify these to “other” unless the source itself does. Residual labels communicate why the case is outside more specific categories.
45. Codes should be stored as reference data
ICSE-18 codes such as 11, 12, 21, 22, 30, 41, 42, 43, 44 and 51 are machine-facing category identifiers. Translate the label, not the number. Keep codes as text where formatting matters, and never allow spreadsheet cleaning or localization routines to replace them with ordinal numbers or target-language abbreviations.
46. Spreadsheets can preserve codes but still break relationships
Because ICSE codes are short, they are less vulnerable to scientific notation than long identifiers, but rows can still shift during sorting. A correct translated label can become attached to the wrong code. Use stable keys and validate every code-label pair after translation import.
47. APIs should separate code and localized label
A multilingual labour-statistics API should expose a canonical status code and return localized labels through language resources. Do not create a French code, Arabic code or Chinese code. The statistical identifier remains constant while the label changes.
48. Databases should not join on translated status names
Terminology can be revised as national statistical offices improve translations. If data joins depend on the label text, a terminology update can break the system. Use ICSE code plus version as the stable key and store language labels as attributes.
49. Translation memories should treat category names as controlled terminology
Near matches are risky because permanent employee, fixed-term employee and short-term employee share many words. A CAT tool can suggest the wrong status with high confidence. Lock the code and maintain an approved terminology base keyed to the classification version.
50. Machine translation should not classify respondents
Machine translation can help render survey text, but it should not infer status from free-text job descriptions unless the statistical workflow explicitly validates that approach. Classification requires variables about ownership, hiring, incorporation, clients, control and remuneration that may not appear in narrative text.
51. Generative AI can explain categories but should not guess missing status
A model can describe the difference between employee and dependent contractor, but a real respondent may sit near the boundary. If key survey answers are missing, preserve missingness or uncertainty. Do not fabricate a definitive category because one label sounds likely.
52. Worked example: delivery-platform worker
A driver uses their own vehicle and is called self-employed in marketing materials. The platform controls customer access and important terms of the work. The statistical survey asks dependency questions and classifies the person as a dependent contractor. The translation keeps the platform’s self-description in narrative context but preserves the official ICSE category in the data.
53. Worked example: incorporated consultant with no employees
A consultant owns and controls an incorporated company and does not regularly employ anyone. Translating the record simply as freelancer would lose the incorporated owner-operator distinction. The target keeps the detailed ICSE category and can use a plain-language explanation beside it.
54. Worked example: family shop
One household member owns the shop and regularly employs staff, while another family member helps without regular pay. They do not share one employment status. The owner may be an employer; the unpaid helper may be a contributing family worker. Translation must classify each job relationship separately rather than apply “family business” as one category.
55. Worked example: fixed-term researcher
A university researcher has a two-year employment contract. The occupation is researcher; the industry is education or research depending on the coding system; the status in employment is fixed-term employee. Translating all three fields as a single phrase such as temporary academic worker would destroy the multidimensional data structure.
56. Search intent: “translate ICSE-18 employer code”
The useful answer identifies whether the code refers to an employer in a corporation, an employer in a household market enterprise or another detailed category. Translate the official label and explanation while preserving the numeric code. Do not replace it with a local occupational title such as director or manager.
57. Search intent: “dependent contractor meaning”
This query usually needs more than a dictionary definition. Explain that the worker has a commercial arrangement but depends on another economic unit for important aspects of work organization, income or market access. Then distinguish the concept from employee, independent contractor and generic freelancer terminology.
58. Search intent: “ICSE-18 vs ISCO”
ISCO classifies occupation; ICSE-18 classifies status in employment. The same person needs both codes in many labour datasets. A nurse can be an employee or independent worker; a driver can be an employee, employer or dependent contractor. Translation should preserve both dimensions instead of choosing one.
59. A practical ICSE-18 translation workflow
Identify the source version and whether the table uses the authority or economic-risk hierarchy. Extract code, label, definition, survey variable and job reference. Protect codes. Translate category labels with an approved labour-statistics glossary. Translate respondent questions separately, preserving decision logic. Reassemble by stable keys, then validate code-label relationships, hierarchy, job number, version and national mapping.
60. Reference route: International Labour Organization
The ILO’s ICSE-18 Manual explains the revised classification and its implementation in household surveys. ILOSTAT resources also document how detailed categories are derived from survey questions. Use current ILO definitions for production translation rather than relying on generic employment dictionaries or local legal terminology alone.
61. Connection to the eduKateSG language ecosystem
This specialist article sits beneath the Master Art of Translation — Technical Translation System. Its narrow owner problem is work-relationship meaning. It also connects conceptually to the protected Vocabulary Learning Hub because words such as worker, employee, contractor, employer and independent have everyday meanings that differ from their technical statistical use.
62. Final rule: translate the relationship, not just the worker label
ICSE-18 translation succeeds when a reader in another language understands the same authority, dependency, enterprise structure, economic risk and contract-duration relationship as the source. Preserve the code and hierarchy, distinguish occupation from employment status, respect survey logic, and validate the data structure after translation. The goal is not merely to find a plausible word for worker. It is to preserve the exact kind of work relationship the statistics are measuring.