Position Descriptions to Standard for Visa 482
Why the position description matters in a 482 application
When an employer lodges a nomination for a Subclass 482 visa, one of the most important documents is the position description (PD) — the description of the role. DHA (the Department of Home Affairs) relies on the PD to assess whether the nominated position genuinely corresponds to the ANZSCO occupation code declared.
This is a key factor in the Genuine Position Test — the test of whether the nominated position is a real, necessary role that suits the business. A weak PD that is written too generically or does not match the ANZSCO is one of the leading causes of a nomination refusal.
The 50% rule for ANZSCO main tasks
The most basic and important rule: at least 50% of the duties in the PD must match the main tasks of the nominated ANZSCO code.
Each ANZSCO code on the ABS (Australian Bureau of Statistics) website has a specific list of “Tasks”. For example, ANZSCO 261111 (ICT Business Analyst) includes tasks such as analysing business requirements, designing system solutions, producing technical documentation and so on.
If your PD mainly describes sales or customer support work with only a few lines about systems analysis, DHA will determine that the position does not meet the ANZSCO 261111 requirement and may refuse the nomination.
The structure of a standard position description
A complete, valid PD for a 482 application usually includes the following sections:
1. Position Title It must match or be very close to the occupation name in ANZSCO. Do not give the role an overly creative title that has no basis in industry practice — for example “Digital Solutions Wizard” instead of “Software Engineer”.
2. Employer name and address State the company name and the specific work address clearly. If the employee works across multiple locations, state the main one.
3. Reporting Line Whom does this position report to? This helps DHA understand the organisational structure and the role’s real place in the business.
4. Salary State the annual salary before tax clearly. It must meet or exceed the current TSMIT (AUD $70,000 a year from July 2023) and meet or exceed the market salary rate for an equivalent role in Australia.
5. ANZSCO code State the nominated ANZSCO code clearly, for example: ANZSCO 261111 — ICT Business Analyst. This lets the officer cross-check quickly.
6. Key Duties / Responsibilities This is the most important section. List at least 8–12 specific, detailed duties, and make sure more than 50% of them match the ANZSCO Tasks list directly. Use specific action verbs (analyse, design, develop, manage, coordinate, and so on).
7. Skills & Qualifications State the minimum qualification, required experience, and technical and soft skills clearly. This supports proving the position is at the right ANZSCO Skill Level 1 or 2.
8. Contract type and working hours Full-time or part-time, permanent or fixed-term contract, and hours per week.
Common mistakes that lead to nomination refusal
Based on how applications are assessed in practice, the following are the most common PD mistakes:
Mistake 1: duties that are too generic For example: “Perform various administrative and technical tasks as required.” This provides no specific information about the actual work. DHA needs detail, not vague description.
Mistake 2: duties that do not match the ANZSCO Declaring the occupation as “Accountant” but having the PD mainly describe data entry, invoicing and answering phones — this is a bookkeeper’s work, not an accountant’s.
Mistake 3: a position that does not fit the size of the business Nominating a “Chief Technology Officer” for a business with three employees. DHA will doubt the genuineness of the position.
Mistake 4: salary below market Even where it meets TSMIT, if the salary is significantly below the market salary rate for an equivalent role, the application may be asked to explain it or be refused.
Mistake 5: a position title that does not correspond to the ANZSCO Using the title “Social Media Manager” but declaring ANZSCO 225113 (Public Relations Manager). This inconsistency raises questions from the outset.
Advice for writing an effective PD
Before writing the PD, look up the ANZSCO code on abs.gov.au, read the “Tasks” section carefully, and use it as the backbone for the duties section of the PD. Adjust the language to reflect the real work at the company, but do not stray from the essence of the occupation. A good PD both reflects the reality accurately and is strong enough to demonstrate the position is worth sponsoring under the Subclass 482 visa.