A hybrid professional can use SQL, Power BI, Jira and stakeholder workshops in the same week and still face a real ACS occupation question: is the work primarily Data Analyst or ICT Business Analyst? The Data Analyst versus ICT Business Analyst ACS distinction becomes clearer when you identify the principal work outputs: insights and datasets on one side, business requirements and system specifications on the other.
The answer is not the toolset. ACS currently describes Data Analyst 224114 as gathering, processing, analysing and interpreting data and communicating findings through reports and visualisations. ICT Business Analyst 261111 is centred on identifying user needs, analysing business processes, formulating requirements and producing specifications for system and software solutions.
If the role combines business analysis with deeper systems-analysis work, test where a technical business analyst crosses into Systems Analyst territory.
Start with the output of the work
| Question | Data Analyst direction | ICT Business Analyst direction |
|---|---|---|
| Primary problem | What does the data show? | What should the system/process do? |
| Core output | Analysis, trends, statistics, dashboards, visualisations, decision insight | Requirements, process analysis, functional specification, system behaviour, acceptance criteria |
| Stakeholder value | Explains evidence and implications from data | Translates user/business needs into system change |
| Technical context | Data collection, validation, transformation, analysis and visualisation | System/process analysis, requirements, functional design and solution validation |
| Testing role | May validate data quality and analytical outputs | Often supports functional testing/UAT and acceptance of system behaviour |
The same keyword can belong to both occupations
SQL is not an occupation. A Data Analyst may use SQL to prepare and analyse datasets. An ICT Business Analyst may use SQL to validate requirements, reconcile system behaviour or investigate a process problem. Power BI is not an occupation either: the question is whether the professional output is primarily analytical insight or system/process requirements.
Jira, Agile and stakeholder meetings are equally non-determinative. These are work environments and tools. ACS assesses the professional function shown across the career evidence.
Use percentage thinking for hybrid roles
A title such as “Data & Business Analyst” can hide a dominant function. Take a representative six- or twelve-month period and estimate where the professional effort went. An approximate breakdown is not a legal formula; it is a diagnostic tool.
- If most work is data collection, quality, transformation, analysis, interpretation and communicating findings, Data Analyst deserves serious comparison.
- If most work is eliciting needs, analysing processes, defining functional behaviour, writing specifications and supporting system acceptance, ICT Business Analyst may be more coherent.
- If most work is building pipelines, platform services or engineering data infrastructure, neither comparison may be sufficient; a Data Engineer/software occupation analysis may be required.
Evidence should change when the occupation changes
For Data Analyst, strong employment evidence can make analytical methods, dataset quality, interpretation, visualisation and decision support visible. For ICT Business Analyst, evidence should expose the system context: users, process gaps, requirements, functional specifications, testing and implementation.
The employment reference does not need to mimic ACS wording. ACS explicitly warns against duties copied directly from occupations/ANZSCO. Describe the real work and then test the occupation fit.
RPL makes occupational inconsistency easier to see
If an RPL applicant nominates ICT Business Analyst but both project reports are almost entirely about statistical analysis and dashboards, the evidence may communicate a different profession from the label. The reverse problem exists when a Data Analyst nomination is supported mainly by requirements and UAT narratives.
RPL reports must also remain the applicant’s own work. Occupation mapping should happen before project narratives are drafted so the applicant is not pushed toward artificial wording.
Three hybrid scenarios
Scenario A — reporting and insight
The applicant gathers data from multiple sources, validates quality, builds analysis, identifies trends and presents findings to management. Requirements meetings are mainly about what should be measured. This profile points more strongly toward Data Analyst.
Scenario B — system change
The applicant maps current processes, elicits user needs, writes functional requirements, works with developers, defines acceptance criteria and coordinates UAT. SQL and dashboards are used for validation, not as the main professional output. This profile points more strongly toward ICT Business Analyst.
Scenario C — data platform engineering
The applicant builds ingestion pipelines, orchestration, distributed transformations and deployment automation. The problem is no longer simply Data Analyst versus ICT BA; broader occupation mapping is needed.
The decision rule
Choose the occupation that requires the least rewriting of the career. The title, tools, employment reference, project evidence and work output should converge on the same professional function.
If more than one occupation remains genuinely defensible after this mapping, ACS allows applicants to nominate up to three occupations—but each still needs support from the evidence record.
Outputs tell you more than the position title
Data Analyst and ICT Business Analyst can sound interchangeable on a résumé, especially in companies where ‘analyst’ covers every person who works with information. The assessable difference lies in the principal occupational function. A data analyst may extract and clean datasets, build measures and explain patterns in customer behavior. An ICT business analyst may elicit system requirements, model processes, define functional specifications and translate business needs into technical changes. Real roles overlap, so map a representative working week rather than cherry-picking attractive tasks. If a candidate spent most of the year maintaining dashboards, a few requirements workshops cannot necessarily justify describing the whole role as systems analysis.
Use a deliverable-led occupational comparison
For each substantial project, list the problem, decisions and outputs the employee personally owned. SQL pipelines, experiment analysis and statistical findings indicate one cluster of activities. Process models, user stories, requirements traceability and acceptance criteria may indicate another. No single deliverable automatically fixes an occupation code; the pattern across projects matters. Ask what the candidate was employed to achieve and who consumed their work. Did business stakeholders use the analysis to set a marketing budget, or did a development team use a formal specification to change software? These questions often clarify ambiguous titles better than a job description drafted for immigration purposes.
Evidence must align across the whole file
A CV that emphasizes machine learning while the employer reference describes documenting system-change requests can raise a mapping problem. Employment letters should reflect actual duties, and portfolio materials should support—not replace—those claims. The ACS General Skills pathway explains the need for documented qualifications and work experience; the Home Affairs occupation list provides the migration framework. These sources answer different questions: assessment of work relevance and eligibility of an occupation for a particular visa.
Keep the borderline cases honest
A hybrid professional might split time across requirements gathering, database design and reporting. Rather than inventing a perfect fit, make a dated allocation of primary responsibilities and distinguish long-term duties from a one-off assignment. Identify which nominated occupation gives the most faithful account of the majority of assessable work, considering the authority’s current definitions. An applicant who changes occupations between assessment and visa planning should not assume the first positive result covers the second. A well-supported choice may be less fashionable than a popular ANZSCO label, but it is easier to defend when documents are compared side by side.
Compare the occupation descriptions in ACS occupation mapping with the index at ACS occupation index, then verify how professional duties must be evidenced using ACS employer evidence. The resulting analysis should be based on what the candidate delivered, not which title looks more advantageous.
