The Wand has been one of those tonearms that has intrigued me for years, largely because it never looked like it was designed by committee, or by someone trapped in front of a CAD workstation after midnight with too much confidence and something much stronger than coffee. They do it differently in New Zealand. Its wide to narrow carbon fiber arm profile helped make it instantly recognizable, and the design has built a real following over time. The latest chapter arrives next week at HIGH END Vienna 2026, where Wand will unveil its new 12-inch Dark-Light tonearm, a longer version of the 10-inch Dark-Light that first appeared at Munich High End 2025.

Long tonearms are not new, and neither is the argument over whether the added length is worth the extra real estate and setup demands. Wand already offers 9.5-inch, 10.3-inch, 12-inch, and 14-inch arms, and the company claims a 12-inch arm can reduce distortion by roughly 30% compared to a 9-inch design. That matters if the arm can keep resonance, rigidity, and bearing behavior under control, which is where Wand has always tried to separate itself from the usual aluminum tube and prayer routine.

My own curiosity goes back to some oddball tonearms I tried years ago, including the Japanese RS Labs RS-A1, a rotating headshell design that looked faintly mad but made a persuasive case for thinking differently about geometry and tracking. I also came across The Wand while looking at restored idler drive Lenco turntables, including the Dutch PTP Audio projects built around classic Swiss Lenco decks from the 1970s. PTP adopted The Wand for some of its turntables back in 2014, which only made the rabbit hole deeper. Naturally, I fell in. That is how these things happen.

The new 12-inch Dark-Light is not just about making the arm longer because the internet needs another argument. It is about whether Wand can preserve the speed, low noise, and musical flow that made the shorter model interesting, while taking advantage of the lower tracking distortion that a properly executed 12-inch arm can deliver. For vinyl listeners with the deck, space, cartridge, and patience to make it work, this could be one of the more interesting analog debuts at HIGH END Vienna 2026.

Handmade in New Zealand, Designed by Simon Brown

Design Build Listen is not just another boutique analog brand making pretty bits for expensive turntables. Based in Aotearoa / New Zealand, the company hand builds The Wand Tonearm along with other audio accessories, including its “No Ring Rings” tube dampers designed to reduce unwanted vibration.

Created by designer Simon Brown and launched in 2011, The Wand Tonearm has earned multiple design awards and five star reviews for its distinctive carbon fiber arm design. Its large diameter arm tube is claimed to be at least four times stiffer than traditional tonearms, which helps explain why The Wand has always felt less like a retro accessory and more like a serious rethink of how a tonearm should work.

Longer Reach, Tapered Stiffness, Serious Vibration Control

The new Wand Dark-Light 12-inch tonearm is not just a longer version built for people with more plinth real estate and stronger opinions. Its core advantage is Wand’s Musical Taper design, which increases the arm tube diameter toward the pivot as length increases. That larger rear section is intended to preserve stiffness rather than sacrifice rigidity, while also allowing more internal brass mass near the bearing assembly.

The added mass lowers the center of gravity and gives vibrational energy a more controlled path away from the cartridge and arm tube. For a 12-inch tonearm, that matters: the longer geometry can help reduce tracking distortion, but only if the arm remains stable, rigid, and free enough to trace the groove properly. The Dark-Light’s appeal is that it tries to balance those demands without turning the design into another heavy analog science project with nicer photography.

Will The Wand Tonearm Work With Your Cartridge?

The Wand Tonearm should work with a wide range of cartridges, which is one reason it has attracted attention from both high end analog users and listeners building more sensible vinyl systems. Design Build Listen says The Wand has been used with cartridges from Lyra, Transfiguration, Koetsu, Kiseki, Dynavector, Denon, Ortofon, Hana, and others, which covers a pretty broad slice of the cartridge world.

The standard Wand Tonearm is considered a medium mass design, with a claimed effective mass of 12.5g, while the 12-inch version is listed at 15g. The Master Series arms add roughly another gram.

Very high compliance cartridges still need some care, but Design Build Listen notes that even a Shure V15Vx measured at a 7Hz resonance, which remains usable. Lower compliance moving coil cartridges are also considered a good match.

Denon DL-103 and Ortofon 2M models appear to be among the most popular cartridge choices with Wand users, which makes sense. One is a classic low output moving coil with a long history, and the other is a widely used moving magnet family that covers a broad range of budgets. Wand also recommends Hana moving coil cartridges, especially the Hana ML.

The practical takeaway is that The Wand is not a one-cartridge science project. It should work with many common MM and MC cartridges, provided setup is done properly and the turntable is not being asked to rescue warped records from the witness protection program. As always, compliance, cartridge weight, counterweight range, and phono stage compatibility still matter, but for most users, The Wand should not create a matching crisis.

Will The Wand Fit Your Turntable?

The Wand is designed around Rega-style mounting dimensions, but that does not mean it is the obvious upgrade path for every Rega Planar 3, Pro-Ject Debut PRO, or other sub-$1,000 turntable. This is a serious tonearm, and not an inexpensive one, so the better question is whether the turntable, cartridge, plinth, and overall system justify the move. Bolting a high-end tonearm onto an entry-level deck can work mechanically, but it may not be the smartest use of the budget. Vinyl has enough ways to separate you from your money without handing it the keys.

Where The Wand makes more sense is on turntables with the space, adjustability, and mechanical foundation to take advantage of it. Design Build Listen offers mounting information and kits for a wide range of decks, including the Linn LP12, Technics SL-1200 and SL-1500 family, including newer GR models, Lenco L75 family turntables, Thorens TD-160 and TD-150 models, Thorens TD-318 family turntables, Michell turntables, and SME-style armboards.

The 10.3-inch Wand is especially interesting because it was designed to deliver much of the appeal of a 12-inch arm in a more compact footprint. Design Build Listen describes it as the longest arm intended to fit on a Linn LP12 or Technics SL-1200 family turntable, which gives owners of those decks a way to go longer without needing a battleship-sized plinth.

Suspended turntables should not be ruled out automatically. The Wand weighs roughly 500g, which is in the same general territory as an SME 3009 and somewhat heavier than many Rega arms. That means most properly adjustable suspended decks should be able to accommodate it, but setup matters. Arm height, lid clearance, suspension adjustment, mounting geometry, and counterweight clearance all need to be checked before anyone starts drilling holes and pretending this is IKEA furniture.

The Bottom Line

At €8,900, the Wand 12-inch Dark-Light tonearm is not a casual upgrade. It is built for serious turntables, serious cartridges, and vinyl listeners who care about geometry, stiffness, resonance control, and setup precision.

Its appeal is the way Wand tackles the 12-inch tonearm problem: lower tracking distortion, a tapered carbon fiber arm tube designed to maintain rigidity, internal brass mass for vibration control, and, finally, headshell lifts for better day-to-day usability.

This is for experienced Linn, Technics, Lenco, Thorens, Michell, and custom plinth users, not someone trying to turn a budget deck into an analog miracle. It is available now and can be heard at Vienna High End in Halle 5, S15.

For more information: designbuildlisten.com

Related Reading

Dirac Live Active Room Treatment is coming to miniDSP’s new Tide16, giving the 16 channel multi-channel processor access to Dirac’s full room optimization suite, including Dirac Live Room Correction, Dirac Live Bass Control, and ART.

That matters because Tide16 is aimed at systems where channel count, bass control, and acoustic correction are not afterthoughts. Designed for audiophiles, integrators, and system designers, the processor gives users a more flexible path to managing complex playback systems without turning the room into the villain of the story.

Introduced in 2023, Dirac Live ART takes the concept beyond traditional room correction by using the speakers in a system as a coordinated acoustic control network. The goal is to reduce low frequency resonances and improve bass consistency across the listening area, especially in rooms that do not behave nicely because, naturally, rooms rarely do.

“miniDSP has built a global reputation for flexible, high-performance DSP tools that empower enthusiasts and professionals alike,” said Rikard Hellerfelt, VP & Head of BA Consumer Electronics. “By integrating Dirac Live Active Room Treatment into the new Tide16, miniDSP is making cutting-edge room optimization accessible to a wider audience, unlocking studio-grade performance in real-world listening rooms.”

What Does the miniDSP Tide16 Actually Do?

The miniDSP Tide16 is not a receiver in the usual living room sense. There are no amplifier channels inside, and it is not designed to be an all-in-one box for someone plugging in five speakers and calling it a day. Think of it as the control center for a more advanced stereo, home theater, immersive audio, or custom installation system.

Its job is to accept audio from sources, process that signal, apply room correction, manage bass, decode formats such as Dolby Atmos and DTS:X, and then send the corrected signal out to external power amplifiers or active speakers. That is where the 16 balanced XLR outputs matter. Tide16 can support complex layouts, including 9.1.6 systems, depending on the source material, speaker layout, and the rest of the system.

Connectivity includes HDMI, Toslink, USB Audio, balanced XLR and unbalanced RCA stereo analog inputs, plus Bluetooth for wireless playback. That gives Tide16 enough flexibility to work in a serious two channel system, a dedicated theater, an immersive audio room, or a professional listening space. A calibrated microphone is sold separately, so buyers should factor that into the final cost and setup process.

The headline feature is the inclusion of the full Dirac Live suite out of the box: Dirac Live Room Correction, Dirac Live Bass Control, and Dirac Live Active Room Treatment. That matters because Dirac licenses are often an added expense on competing products, and those costs can add up quickly.

Dirac Live Room Correction addresses frequency and timing issues caused by the room and speaker placement. Dirac Live Bass Control focuses on integrating subwoofers with the main speakers so the low end is more consistent across more than one seat. Dirac Live ART goes further by using multiple speakers in the system as a coordinated acoustic control network. Instead of treating each speaker and subwoofer separately, ART uses Dirac’s MIMO technology to help reduce low frequency decay and room resonances.

That does not mean Tide16 replaces smart speaker placement, competent setup, or physical acoustic treatment. Anyone expecting software to turn a bad room into Abbey Road by Tuesday is going to need a chair and a quiet moment. But for systems with multiple speakers, subwoofers, and enough complexity to make manual setup painful, Tide16 gives users a powerful DSP platform with the Dirac tools already included.

The Bottom Line

The miniDSP Tide16 matters because it brings 16 channel immersive audio processing, Dolby Atmos and DTS:Xdecoding, advanced bass management, and the full Dirac Live suite into a $3,500 processor. That price is not pocket change, but it is aggressive for a processor that includes Dirac Live Room Correction, Dirac Live Bass Control, and Dirac Live Active Room Treatment rather than treating them like toll booths.

Tide16 is not a traditional AVR. There are no amplifier channels inside, so buyers still need external amplification, speakers, subwoofers, and a calibrated microphone. Its strength is control: 16 balanced XLR outputs, support for complex layouts like 9.1.6, multi subwoofer integration, and Dirac ART’s ability to use the speaker system as a coordinated tool to reduce low frequency room issues.

The right buyer is an enthusiast, integrator, or system designer building a dedicated theater, active speaker system, advanced stereo setup, or multi subwoofer room where precision matters more than plug and play convenience. At $3,500 before amps, cables, microphones, and setup time, Tide16 is not cheap. But for users who want Dirac ART and 16 channel flexibility without jumping into far more expensive processor territory, it could be a very important box.

For more information: minidsp.com

Related Reading:

Your browsing habits may not be as private as you think, even with all the right precautions in place. According to Ars Technica, security researchers have uncovered a new attack technique that lets a malicious website figure out which other sites and apps you have open. You do not need to click anything, download anything, or grant any permission; just visiting the page is enough.

How can websites spy on your browsing activity through hard drive?

The technique is called FROST, short for Fingerprinting Remotely using OPFS-based SSD Timing. Every website and app you use generates its own unique pattern of activity on your SSD, the storage drive inside your computer.

FROST exploits a browser feature called the Origin Private File System, or OPFS, which quietly lets websites store files on your local drive without asking permission first.

The attacker’s page creates a large file on your drive and then listens to the tiny speed fluctuations that happen when your SSD is busy handling other tasks. Those fluctuations are fed into an AI model that has been trained to recognize the telltale patterns of specific websites and apps.

According to the research paper, the technique correctly identified which websites a person had visited with about 89% accuracy, and which apps were running with about 96% accuracy, when tested on an Apple M2 Mac.

The attack also works across different browsers simultaneously, meaning visiting the attacker’s page in Chrome can still expose what you are doing in Safari.

The browsers won’t fix this, but you can protect yourself

FROST has not been spotted in the wild yet, which is reassuring. It also only works while the offending tab is open, so closing it immediately stops the attack.

Google, Apple, and Mozilla were all informed, but none have committed to a fix. Your best defense right now is keeping an eye on your available disk space. A sudden, unexplained drop in storage is a red flag worth investigating immediately.

Browser-level fixes have been proposed, including capping how much disk space OPFS can claim, but given the browser makers’ responses, those changes are not coming any time soon.

Dealing with text streams is a fundamental skill for the Linux power user. You can sort, merge, and search text files easily from the command line. What if you could do the same thing with video? Well, you can. Maybe you want to add a logo to a webcam feed before sending it to a conference app. Maybe you want to blur, color-correct, or annotate video in real time. Or perhaps you want to inject prerecorded video into Zoom while pretending it is a live camera. Linux can do all of this, and the key ingredient is usually the same: a loopback video device.

The basic idea is simple. Instead of an application reading directly from /dev/video0, you create a fake camera device using the v4l2loopback kernel module. Your software pipeline writes processed video into the fake camera, and applications read from it as if it were a normal webcam. The result is surprisingly powerful.

Loopback Cameras

The first step is to install the loopback driver. On many distributions, this is packaged already. On Debian or Ubuntu, you’d install the v4l2loopback-dkms package. On OpenSUSE it’s probably v4l2loopback-kmp-default if you’re using the usual kernel.

Unless your distro automatically loads the module, you’ll do it yourself and tell the driver how many fake cameras to make. You’ll also need to tell it where to put them. Here, I’m asking for a single camera at /dev/video10 named VirtualCam:

sudo modprobe v4l2loopback devices=1 video_nr=10 card_label="VirtualCam"

After you’ve done this, you can verify it:

v4l2-ctl --list-devices

Applications can now see the fake camera, but there’s nothing coming out of it yet.

Basic Pipeline

Suppose you have a USB webcam at /dev/video0. You can read from it and send the stream directly into the loopback device with FFmpeg:

ffmpeg -f v4l2 -i /dev/video0 -vf format=yuv420p -f v4l2 /dev/video10

Now applications can use /dev/video10 as a webcam source. This alone is useful because it decouples applications from the physical camera. For example, I had an old Intel Lifecam that would randomly throw an error when used with a browser video conference app, but ffmpeg had no problems with it. A similar pipeline lets me videoconference with this camera. But the real fun starts when you insert filters. A fun test site is webcamtoy.com.

Adding a Watermark

FFmpeg’s filter graph system is quite flexible. A watermark is just another video source composited over the main image. Suppose you have a PNG file named wrencher.png with transparency. This command overlays it in the lower-right corner:

ffmpeg -f v4l2 -i /dev/video0 -i wrencher.png -filter_complex "overlay=W-w-20:H-h-20,format=yuv420p" -f v4l2 /dev/video10

Or, you could be more explicit:

ffmpeg -f v4l2 -video_size 1024x720 -framerate 15 -i /dev/video0 -i wrencher.png -filter_complex "overlay=x=main_w-overlay_w-20:y=main_h-overlay_h-20,format=yuv420p" -f v4l2 /dev/video10

Now the logo appears 20 pixels from the bottom-right edge. However, note that if your software “mirrors” your image for local display, the watermark will go to the other side in your view. That makes sense.

If your video fails, or it looks like color garbage or a green screen, you may have to pick a different video conversion other than yuv420p.

Injecting Video

You are not limited to webcams. You can inject a prerecorded video:

ffmpeg -re -stream_loop -1 -i intro.mp4 -vf format=yuv420p -f v4l2 /dev/video10

The -re flag tells FFmpeg to play in real time instead of as fast as possible. The -stream_loop -1 repeats forever.

This is useful for demonstrations, test feeds, signage, appearing awake in meetings, or foiling security cameras in low-budget action movies.

Multiple Filters

Once you understand the filter graph concept, you can stack effects endlessly.

For example:

-filter_complex "eq=contrast=1.2:brightness=0.05, hue=s=0, overlay=W-w-20:H-h-20, format=yuv420p"

This:

• Adjusts contrast
• Brightens slightly
• Converts to grayscale
• Adds the watermark

FFmpeg contains hundreds of filters, including blur, sharpen, edge detection, chroma keying, denoise, LUTs, stabilization, and even AI-assisted processing if built with the right libraries.

At some point, though, you may want a more modular architecture. That is where GStreamer becomes interesting.

Enter GStreamer

FFmpeg excels at direct command-line media processing, but GStreamer is more like a traditional Unix/Linux pipeline. You construct a pipeline out of interconnected processing blocks. The learning curve is steeper, but it enables extremely sophisticated workflows.

A simple camera-to-loopback pipeline looks like this:

gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! v4l2sink device=dev/video10

That simply duplicates the webcam into the virtual device.

Suppose you want to add text:

gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! textoverlay text="Hackaday!" valignment=bottom halignment=right ! v4l2sink device=/dev/video10

Inspecting GStreamer

One thing that intimidates new GStreamer users is how enormous the framework feels. Fortunately, there’s a tool specifically designed to explore what is available: gst-inspect-1.0

Run without arguments, it dumps every installed plugin and element on your system. The list can be surprisingly long. Using grep on the output can help.

More useful is inspecting a specific element:

gst-inspect-1.0 v4l2src

This shows:

• Supported capabilities
• Accepted formats
• Properties
• Pad types
• Configuration options

For example, inspecting textoverlay reveals options for font selection, alignment, shading, and transparency. Inspecting videobalance shows controls for brightness, hue, saturation, and contrast.

This becomes essential because GStreamer pipelines are often constructed experimentally. You discover an element, inspect its capabilities, then wire it into the pipeline.

Using Images in GStreamer

Overlaying an image is slightly more involved because GStreamer separates streams explicitly. One common approach uses gdkpixbufoverlay (here, placing a logo at the lower right):

gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! gdkpixbufoverlay location=logo.png offset-x=20 offset-y=20 ! videoconvert ! v4l2sink device=/dev/video10

You can keep adding modules until you get what you want. A more elaborate pipeline might:

• Read a webcam
• Add a logo
• Blur the background
• Encode H.264
• Stream over RTSP
• Simultaneously feed a loopback webcam

GStreamer can also integrate with many hardware codecs for hardware encoding and decoding.

Practical Considerations

There are several things that tend to trip people up.

Video applications can be extremely picky about formats. MJPEG, YUYV, RGB, and YUV420 all appear frequently. If things fail mysteriously, format conversion is often the culprit.

Tools like v4l2-ctl can help:

v4l2-ctl --list-formats-ext

Another issue is that many applications reject unusual sizes. Sticking with standard resolutions like 1280×720 or 1920×1080 avoids many headaches.

Real-time video processing can consume substantial CPU resources. Hardware acceleration helps, but some filters force software processing anyway. Similarly, virtual camera pipelines can accumulate delay. Low-latency flags and queue tuning sometimes become necessary for interactive use.

Beyond Watermarks

Once you have a loopback pipeline running, you can get creative. You could create a retro CRT simulation, a fake thermal camera, or detect motion. Maybe insert a timestamp or a live video feed from your oscilloscope or 3D printer. Because the output looks like a normal webcam, almost any Linux application can use it. They simply see another camera.

There are many more advanced techniques possible with GStreamer pipelines, including branching streams with tee, synchronizing multiple sources, GPU-accelerated effects, network streaming, and live compositing. If you want a deeper dive into practical virtual-camera workflows, this video provides an excellent starting point:

Another tip: if you write shell scripts, using things like /dev/video0 will get you in trouble unless your configuration never changes. Instead, use the stable symlinks:

ls -l /dev/v4l/by-id/

You’ll see things like:

usb-046d_HD_Pro_Webcam_C920-video-index0

Then use that path directly in FFmpeg or GStreamer.

Cleaning Up

When you are finished with the virtual camera, remember that the loopback device persists until the kernel module is unloaded. Stop any applications using the fake camera first, then remove the module:

sudo modprobe -r v4l2loopback

That tears down the virtual camera devices and removes them. If you created multiple fake cameras, unloading the module removes them all at once.

We’ve used Gstrteamer before for remote driving.

OSes

May security update trips over hostnames of a very specific length

Windows Server 2016 might be long in the tooth but that isn’t about to stop Microsoft breaking stuff.

The May 12 security update introduced another bug for administrators to worry about. According to Microsoft, if the server hostname is exactly 15 characters long (like, for example, THEY-NEVER-TEST), domain controller discovery might fail.

In the notes for the glitch, Microsoft wrote: “When the hostname is 15 characters long, DCLocator calls (for example, using nltest /dsgetdc: /pdc) will return ERROR_INVALID_PARAMETER, preventing applications and administrative tools from locating a domain controller.”

In other words, anything that depends on a domain controller lookup might stop working. As an example, Microsoft gave Distributed File System (DFS) Namespace management, which would certainly be inconvenient. DFS Namespaces is a Windows Server role that allows admins to group shared folders across different servers into a single namespace. A single path can lead to files located on multiple servers. Unless, of course, the domain controller lookup is broken.

Microsoft lists no workaround for affected users, though changing the server hostname to something other than 15 characters would presumably avoid the trigger. “The issue is under investigation, and additional information will be shared as soon as it becomes available,” it said.

Microsoft still officially supports Windows Server 2016. Mainstream support ended in 2022, but extended support will continue until January 12, 2027. Microsoft is offering up to three more years of support via the Extended Security Updates (ESU) program after that.

Earlier this year, Esben Dochy of Lansweeper told The Register that the operating system accounted for just 2.2 percent of all Windows devices it tracks, but 20.3 percent of all servers. That figure is unlikely to have dropped dramatically in the months since, so there is a fair chance that an administrator with a 15-character hostname could be affected.

In addition to the Windows Server 2016 problems, the May 2026 security update has failed during installation on some Windows 11 devices when the EFI System Partition is insufficient in size.

It is reassuring to know Microsoft’s talent for breakage shows no bias toward any particular vintage.   ®

Susan Doris-Obando discusses the upcoming deadline and explores the potential challenges and opportunities for professionals amid the policy change.

The EU Pay Transparency Directive, which EU member states are required to implement by 7 June 2026, is a policy that will “significantly reshape employment law around pay transparency within the EU“, explained Susan Doris-Obando, an employment partner at Dentons Ireland.

“The intent is to reduce the EU gender pay gap, which currently stands at around 12pc, by having greater transparency around pay and making it easier for employees to bring equal pay claims,” she said.

Initially brought into effect in June 2023, EU member states were told that they would have until the upcoming 2026 deadline to implement the directive. This means employers will have to acknowledge a number of changes in hiring and the dissemination of employment-relevant information.

“During the hiring process, employers will be required to provide candidates with information on initial pay or pay ranges and ensure that job vacancy notices and job titles are gender-neutral and recruitment procedures are conducted in a non-discriminatory manner,” explained Doris-Obando.  

“They will be prohibited from asking candidates about their current or past pay and from using pay secrecy clauses. During the employment relationship, employees will have the right to request and receive, within a reasonable period and in any event within two months, information in writing about their individual pay level and average pay levels, broken down by gender for workers doing the same work or work of equal value.”  

It will also be the responsibility of the employer to ensure that the criteria under which an employee’s pay, pay level and pay progression are determined, is made easily accessible. Additionally, employers with more than 250 employees will be required to report annually on the gender pay gap in their organisation. 

Reporting is mandated every three years for employers with a workforce of more than 150 people but less than 250, starting with a first report in June 2027. Organisations with 100 or more employees and less than 150 employees will be required to first report in June 2031.  

Doris-Obando noted the main difference between the directive and the current gender pay gap reporting policies already in place in many EU member states is that the new regulations require reporting on the categories of workers – namely, those doing the same work or work of an equal value. 

She said: “If the report reveals a pay gap of more than 5pc within a category of the same work or work of equal value that cannot be justified by objective, gender-neutral criteria and not remedied within six months, employers will be required to take action in the form of a joint pay assessment carried out in cooperation with employee representatives.”

It is also important to note that the directive does not prevent employers from paying workers who perform the same work or work of equal value differently, provided that it is based on objective, gender-neutral and bias-free criteria, such as performance and competence.

Moreover, as Doris-Obando stated, many member states – including Ireland – are going to miss the implementation date and will have to take a phased approach to implementation. Ireland to date, has only draft legislation in place around the recruitment obligations.

Directive consequences

Of the potential consequences, she explained that the organisations that fail to implement the new rules will inevitably be faced with increased claims for equal pay, with the directive effectively shifting the burden of proof in claims to the employer in instances where the employee establishes a prima facie case. 

“If an employer does not comply with their gender pay reporting obligations or pay level information requests, then the burden would likely shift to the employer, unless the breach is manifestly unintentional and minor in character. Significant gender pay gaps may also attract adverse publicity, impacting on recruitment and retention.”

She also anticipates issues in building a robust gender-neutral job evaluation and classification system that can correctly categorise those doing the same work or work of equal value. This is not an easy exercise, she finds, but now is the time to start preparing. 

“Work of equal value is often not immediately obvious,” she said. “For example, in some cases, store employees have been found to do work of equal value to warehouse employees. The next step will be to understand the gender pay gap within each category of worker and consider any objective gender neutral justifications. Any remediation steps should then be addressed.

“Policies should be put in place outlining the criteria used to determine pay, pay levels and pay progression and how to deal with pay on recruitment and in responding to employee pay level information requests. Multinational employers will need to consider whether to adopt global policies and consider their approach to member states’ gold-plating the directive.”

Of the long-term effects of the directive, Doris-Obando stated employee representatives are going to have a much larger role to play, particularly, in conversations around joint pay assessments, where typically their role has been short-term around collective redundancy or Transfer of Undertakings (Protection of Employment) consultations.

Don’t miss out on the knowledge you need to succeed. Sign up for the Daily Brief, Silicon Republic’s digest of need-to-know sci-tech news.