Operational expertise can mask structural pressure

In DVE’s survey, respondents described duplicated work, multiple calendars and spreadsheets, incomplete information, local variations in data entry, unclear responsibilities and difficulty producing a coherent institutional view. They also emphasised the value of discipline knowledge and established academic and host relationships.

WIL teams routinely bridge these interfaces. They repair handovers, interpret exceptions, locate missing information, and draw on relationship knowledge to prevent disruption for students and hosts. That expertise protects students, partnerships and institutional reputation. It can also make the underlying pressure less visible.

From an institutional perspective, continued delivery may look stable. At team level, the same continuity may depend on repeated rework, manual coordination and knowledge held by a small number of experienced people. Assessing sustainability requires a separate view of capacity, dependency, risk, and the human effort needed to keep the model functioning.

Scale compounds coordination

Adding more WIL opportunities doesn’t simply mean processing more of the same thing. New disciplines, delivery models, industry partners, student cohorts and locations create different requirements, relationships, exceptions and risks.

Two programs managing the same number of placements can require vastly different levels of staff effort. One may use established partners, standardised documentation, predictable calendars, and bulk allocations. Another may involve individually negotiated opportunities, complex eligibility requirements, dispersed hosts, travel or accommodation challenges, frequent changes, extensive student intervention, and information held across several systems. A simple placement count can’t show that difference.

This is why capacity conversations need to move beyond volume alone. The real workload includes both activity volume and coordination intensity. If institutions don’t understand both, the work absorbed by WIL teams remains largely invisible – until service quality drops, staff leave, an issue escalates or a new obligation exposes the gaps. It’s also a sufficiency question: the HESF expects staffing to meet the educational, academic support, and administrative needs of student cohorts (Section 3.2), and coordination intensity is where that need is most easily underestimated.

Quality and assurance are carried through everyday work

Under the HESF, WIL experiences and their supervisory arrangements must be quality assured (HESF Standard 5.4.1). TEQSA’s WIL Guidance note also makes clear that providers remain responsible for student safety and welfare, and must monitor and support wellbeing and safety throughout WIL. The HESF also expects WIL to sit within coherent course design, with assessment suited to its learning outcomes (Sections 1.4 and 3.1), and within the provider’s wellbeing, safety and complaints arrangements (Sections 2.3 and 2.4). WIL must be educationally sound, and appropriately supported and monitored.

A policy can describe the expected outcome, but the operating environment determines how consistently that outcome is achieved and whether the institution can produce reliable evidence of it.

This is where the experience of WIL teams becomes strategically important. They know where controls work as intended, where the same issue repeatedly returns, where the information trail breaks, which processes create avoidable risk, and which parts of the model depend on informal intervention.

Leadership needs access to that knowledge before an incident, audit or reporting deadline turns an underlying weakness into an institutional problem. Under Standard 6.2.1, governing bodies must be able to assure themselves that risks to higher education operations are identified and managed, critical incidents are monitored and compliance lapses are identified and corrected. That assurance is only as good as the information flowing up from WIL.

The GBV National Code brings the WIL interface into sharper focus

The National Higher Education Code to Prevent and Respond to Gender-based Violence applies to Table A and B providers from 1 January 2026 and commences for other existing TEQSA-registered providers on 1 January 2027.

Its reach is not confined to campus. Department guidance specifically identifies work experience, professional placements, internships and fieldwork as settings in which gender-based violence can occur.

That creates a practical interface for WIL. Students need clear pathways into institution-wide disclosure, support and reporting arrangements. Staff need to understand how information can be transferred safely and appropriately. Institutions also need to consider how host organisations and other third-party settings connect with those arrangements.

Once the Code applies, providers must collect data for annual reporting, including the location of each experience, disclosures involving third parties, and the number of risk assessments undertaken and support plans implemented. After the applicable initial reporting date, governing bodies must also receive reports at least every six months against the institution’s outcomes framework.

These are institution-wide responsibilities, not responsibilities WIL teams should be expected to own alone. But institutions cannot meet them reliably if disclosures, support, risk management, and evidence from off-campus settings remain disconnected from institutional systems.

Visibility depends on connected information

One of the most useful distinctions in DVE’s survey is between systems being present and institutions having usable visibility.

Respondents commonly reported being able to centralise documents, but reported capability was much lower for flagging individual risks, monitoring support needs, and mandatory government reporting.

Formal placement platforms, institutional systems, spreadsheets and local tools often operate alongside one another. The practical question arising from this is whether placement status, documentation, host information, agreements, risk, student support, location, communications and reporting can be connected into a reliable institutional view – and importantly, how much human effort is required to create it.

Knowing how many students have a placement is useful. Knowing which students, hosts or requirements need action today enables the institution to respond.

Operational teams need visibility that supports timely follow-up. Leaders need visibility that reveals patterns, pressure points and emerging risks across disciplines and organisational boundaries. The institution needs an evidence trail that can be relied upon without asking staff to reconstruct the story after the fact. That’s also the practical test of Standard 7.3.3, which expects information systems and records to be maintained so the provider can document critical incidents and demonstrate compliance with the HESF.

Technology works best when the work is understood

Technology can connect information, automate routine work, support communication, surface exceptions and strengthen reporting. But it cannot determine ownership, decide what should be standardised, resolve justified local variation, or define where human judgement is required.

A new platform can streamline a well-designed operating environment. It can also embed unclear processes and fragmented responsibilities more efficiently. Understanding the work first allows technology to support the right operating model, information flows and decisions.

Five questions leadership should ask now

For institutions considering the future of WIL, I would start with five questions:

1. Where does delivery currently depend on individual knowledge?
   Which processes rely on particular people knowing the workaround, the history, the contact or the location of the evidence?
2. Are responsibilities and handovers clear in practice?
   Especially where work moves between faculties, central teams, academics, professional staff and external partners.
3. Do we understand coordination intensity as well as volume?
   What work, judgement, intervention and relationship management sits behind the placement count?
4. Can we demonstrate how quality, safety and compliance controls operate?
   Can the institution produce reliable evidence across different disciplines, placement types, partners and locations – in a form the governing body can rely on?
5. Can the current environment absorb change?
   Can it respond to growth, policy reform, regulatory requirements, technology change, curriculum developments, workforce pressure and changing student need?

The case for leadership attention is stronger

WIL teams have already done much of the diagnosis. Their day-to-day experience shows where pressure accumulates, responsibilities become unclear, information fails to travel and delivery relies too heavily on informal knowledge and intervention.

DVE’s survey brings those voices together. The conference reinforced how widely the challenges are shared, and the current governance, compliance and reporting environment is making their institutional implications more visible.

This creates a timely opportunity for leadership to bring WIL expertise more directly into institutional planning, investment and assurance.

The next step is to convert operational knowledge into durable institutional capability: appropriate capacity, clear governance, connected data, reliable processes, and technology aligned with the work.

Treating WIL as institutional infrastructure doesn’t require unnecessary bureaucracy. It requires intentional design across governance, people, processes, partnerships, data and systems – so that quality delivery is supported by the institution rather than sustained primarily through individual effort.

Over the next few weeks, I’ll explore several parts of that operating environment more closely: the risks that remain invisible while the work continues, the capacity that placement numbers don’t show, the questions institutions should answer before replacing a system, and why reporting begins long before a report is due.

For a concise view of what WIL and placement practitioners told us about current delivery conditions, you can read DVE’s 2025 WIL and Placements Sector Snapshot.

If the people who know how your WIL arrangements really work were unavailable tomorrow, could your institution still see, support and evidence what was happening?