Skip to content
INDEPENDENT PERSPECTIVES. CLEARER PATHWAYS.
Australian flagAustralia PATHWAYS

A new perspective.
A clearer direction.

Get in touch
Menu

Immigration · RPL

ICT Project Manager Skills Assessment: Why Managing a Team Is Not Enough

A large team does not automatically make someone an ICT Project Manager for ACS.

A person can supervise twenty engineers, approve leave, hire staff and own an operating budget without managing a defined ICT project. Another person may have no direct reports but be accountable for scope, schedule, dependencies, resources, milestones and delivery across a major technology implementation. An ICT Project Manager skills assessment is easier to substantiate when schedules, delivery milestones, resource decisions and dependency controls can be traced to real project records.

For occupation mapping, those are different professional stories.

The broader rule is that duties matter more than titles in an ACS assessment.

ACS currently describes ICT Project Manager 135112 as planning, organising, directing, controlling and coordinating quality-accredited ICT projects, with day-to-day accountability for resourcing, scheduling, prioritisation, task coordination and meeting milestones, objectives and deliverables within agreed timeframes and budgets. See the ACS IT occupation descriptions.

Project management is not the same as line management

Line management is about people and ongoing organisational responsibility. Project management is about delivering a defined change within constraints.

Agile leadership is another boundary case: a Scrum Master is not automatically an ICT Project Manager.

Evidence that may point mainly to line or operations management

  • recruitment and performance reviews;
  • leave approval and team development;
  • general department budgeting;
  • continuous operational responsibility without a defined project boundary;
  • routine prioritisation of support or maintenance work.

Evidence that points more strongly to ICT project management

  • defined project scope and objectives;
  • schedule and milestone ownership;
  • project resource planning;
  • dependency management;
  • risk, issue and change control;
  • vendor and stakeholder coordination tied to delivery;
  • budget control tied to project deliverables;
  • acceptance, transition or go-live governance.

A career can contain both. The question is whether the project-management function is substantial and provable.

The “ICT” part also has to be real

Consulting titles create the same mapping problem; a Salesforce Consultant may map differently depending on the actual duties.

Managing a complex project does not automatically make it an ICT project.

A corporate office relocation may involve laptops, networks and conferencing equipment, but the occupation case depends on whether the applicant’s project is substantively about technology systems, software, infrastructure or ICT services — not merely whether technology appears in the background.

A useful test is to describe the project without the words “project manager”.

What system changed? What technology was implemented or migrated? What technical workstreams depended on each other? What ICT risks were being controlled? What would fail if the coordination was poor?

If those answers are vague, the ICT element may be too weak.

Accountability matters more than attendance

Many professionals participate in project governance without owning the project.

A Business Analyst may maintain requirements and support UAT. A Scrum Master may facilitate delivery routines. A PMO analyst may produce dashboards and track actions. A Team Lead may coordinate engineers. Those activities can be important without automatically becoming ICT Project Manager work.

Look for accountability:

  • Who owned the integrated schedule?
  • Who allocated or negotiated resources?
  • Who maintained the risk and issue position?
  • Who made or escalated priority decisions?
  • Who was responsible for milestones and delivery outcomes?
  • Who controlled change against scope, time or budget?

The answer does not have to be “one person did everything”. Real projects distribute responsibility. But the employment evidence should show what the applicant personally owned.

What a strong employment reference can prove

“Managed IT projects” is not enough detail.

A more assessable reference can identify:

  • the types of ICT projects managed;
  • project scale or complexity without disclosing confidential values;
  • the applicant’s responsibility for scheduling, resources, dependencies, risk and budget where applicable;
  • major technology workstreams or vendors coordinated;
  • governance responsibilities;
  • the stage of delivery owned by the applicant;
  • whether the role was project-specific or a continuing operational-management position.

If the person was promoted from Analyst or Engineer into Project Manager, separate the role dates and duties. Do not backdate project accountability to a period when it did not exist.

Useful evidence beyond the reference letter

ACS skills assessment evidence requirements should control the application, but internal career artefacts can help an applicant reconstruct an accurate role before asking for a reference.

Examples include:

  • project charters;
  • schedules or milestone plans;
  • RAID logs;
  • change-control records;
  • steering-committee packs;
  • vendor plans;
  • project budget or resource plans;
  • implementation and cutover plans;
  • acceptance or closure records.

Do not upload confidential company material merely because it exists. The point is to use contemporaneous records to write truthful, specific evidence and to identify what can lawfully and appropriately be supplied.

Three profiles that often get confused

People manager with no defined project ownership

The person manages a software support department, staff performance, operational budget and daily incidents. Unless separate project-delivery evidence exists, the profile may be stronger as an ICT management or operational role than as ICT Project Manager.

Project coordinator or PMO specialist

The person tracks actions, prepares reports and organises meetings, while another manager owns budget, scope, risk and delivery decisions. The work supports the project, but the accountability level may be different.

ICT delivery manager with no direct reports

The person coordinates internal engineers, vendors and business stakeholders, owns milestones and risk, controls delivery changes and is accountable for implementing a new platform. A lack of direct reports does not weaken the project-management nature of that work.

RPL applicants have a natural project narrative — but must still show ICT knowledge

For an RPL applicant, ICT Project Manager can be well suited to career-episode reporting because a project naturally contains chronology: problem, constraints, scope, decisions, dependencies, risk, resources and outcome.

The danger is writing a generic management story. The report still needs to demonstrate ICT knowledge and the applicant’s understanding of the technological context.

Before building RPL project reports, confirm whether RPL is actually the right ACS pathway for the qualification and experience profile.

A project manager should not pretend to have written code or designed architecture if those responsibilities belonged to engineers. Equally, the report should not reduce the technology to “the technical team handled it”. Explain enough of the system, dependencies and technical risk to show why the management decisions were informed ICT work.

The title-removal test

Delete the words “Project Manager” and “Manager” from the CV and read only the duties.

If those duties plausibly support more than one code, apply the up-to-three-occupation evidence test rather than nominating alternatives speculatively.

Do the remaining duties still show:

  • a defined ICT project;
  • accountable delivery;
  • resource and schedule control;
  • risk and dependency management;
  • milestones and outcomes;
  • professional technology context?

If yes, the occupation has a much stronger foundation.

Managing a team can support an ICT Project Manager profile. It cannot replace the evidence of managing an ICT project.

Managing a project is not always managing an ICT project

A delivery manager may organize timelines, budgets and meetings for a website rollout while the actual technical project management sits with someone else. Assessing an ICT Project Manager role requires examining accountability for ICT delivery: scope, resources, technical dependencies, risks, supplier coordination and project outcomes. The central challenge is not adding the phrase ‘ICT’ to a business-management position. It is showing that the projects were genuinely technology projects and that the applicant carried substantial responsibility for their delivery. Distinguish corporate seniority from occupational relevance; a highly paid general manager may have less directly relevant ICT project evidence than a hands-on technology delivery lead.

Follow one project from approval to handover

An effective account can trace a migration of a legacy customer platform: identifying stakeholders, sizing the delivery, defining a dependency plan, handling vendor interfaces, controlling scope changes and managing cutover risk. Explain decisions the applicant made rather than listing project-management software. If an engineer chose the architecture, acknowledge that boundary. If the project manager negotiated sequencing, managed budget exposure and resolved cross-team blockers, detail those responsibilities. The difference between observing progress and owning delivery can be shown through actual governance artifacts, approvals and project-specific decisions. Avoid disclosing confidential client information.

Make employment proof consistent with project claims

Projects may involve consulting arrangements, temporary secondments or matrix reporting lines. Describe the legal employer, host organization where relevant, position dates and the authority held during each project. Payment records prove remuneration; project summaries support the substantive duty claims. The ACS General Skills guidance identifies these distinct classes of evidence. A résumé that calls someone a project director while the employer confirms a coordinator role will need a credible explanation of what the titles meant, not an inflated letter drafted for the assessment.

A failed project can still demonstrate skill

Professional competence does not require that every project was delivered perfectly. Delays caused by dependency failures, vendor problems or changing regulation can reveal strong management judgment if the candidate identified risks early, documented options and led a proportionate response. An honest account explains the consequence and the adjustment made. Claims such as ‘completed every project on time and under budget’ without supporting detail often read like marketing. Relevant skills are shown by accountability and problem solving, even where the outcome involved compromise or cancellation.

Assess actual management duties against the occupation descriptions in ACS ICT occupations index. Use employment-reference criteria to document responsibility and role dates, while verification of payment shows why proof of remuneration is a separate question from evidence of complex ICT project delivery.

Explore
Drag