Google Union Access in the UK: What the New Law Means

What Prospect can do at Google

Under the agreement, Prospect can talk with Google employees in person and online, and hold workplace sessions explaining how to join a union. That matters because organising often goes more smoothly when workers can ask questions directly, instead of relying only on messages shared outside the workplace.

Google has more than 7,000 employees in the UK, spread across roles and teams with different working patterns. The access agreement gives Prospect a clearer way to reach people in that setup. It also turns a broad legal right into something that can work day to day - covering where conversations take place, how online sessions are run, and how staff learn what membership involves.

The reported agreement covers Google's UK offices, including its King's Cross headquarters. It does not, based on the information available, create a union presence in every team or guarantee access to every employee at any moment. The practical details still have to be coordinated around office security, employee schedules, and normal day-to-day operations.

Access is not formal recognition

Prospect's goal is to recruit enough members to seek formal recognition from Google. That distinction matters. Recruitment gives a union a chance to build membership; recognition is a separate step that could give it a formal role in workplace negotiations.

Prospect says recognition would give it a say over issues such as pay, flexible working, and the company's rollout of AI. The access deal itself doesn't settle those questions, create collective bargaining arrangements, or require Google to accept Prospect as the recognised representative. What the agreement does provide is a channel for employees to decide whether they want the union involved.

For employees, the immediate choice is whether to learn more or join. For Google, the immediate responsibility is to implement the agreement and follow the law that applies. Anything beyond that depends on what employees choose and whether the recognition process is followed.

Why that distinction matters

When access and recognition get treated as interchangeable, expectations can get inflated. The agreement is important because it removes a practical barrier to organising. But it isn't proof that Google has agreed to negotiate over every issue Prospect raises, and it doesn't show that the union already represents the workforce.

That clearer framing helps both sides. Employees can consider the union's case without assuming a specific outcome. Google can make room for workplace access without treating the agreement as a transfer of decision-making power. The next milestones - membership, any recognition process, and then (only if recognition happens) the scope of further discussions - are where the real change would follow.

Workplace access makes organising more practical

The agreement follows a change in UK law under the Labour government's Employment Rights Act. As reported, the law gives unions a right to enter workplaces to recruit members. It came into force on the Friday before the agreement was announced on Monday.

That shifts the practical position for employers and unions. If access depended entirely on whether a company chose to host organisers, the company controlled an important part of how easily workers could hear from a union at work. With a legal access right, employers have to plan for union visits rather than treating them like a discretionary courtesy.

This is operational, not just symbolic. Workplace conversations can reach employees who don't follow union communications elsewhere, or who want to ask questions directly. Online sessions also matter when teams are spread out or when employees don't share the same office schedule. The Google agreement includes both in-person and online access, giving Prospect more than one way to reach staff.

The consequences of refusing access

The source report says employers that keep refusing access can face fines of up to £500,000. That makes access compliance, not just "employee relations" management.

The reported maximum shouldn't be read as an automatic fine for every dispute. The information available doesn't spell out the full legal process, exceptions, or how penalties would be decided. Companies should check the Act and relevant guidance for their specific situation rather than treating a headline number as the complete story.

That caveat doesn't remove the bigger point. The law raises the cost of a blanket refusal and gives a clearer framework than handling requests case by case without consistency. Google's negotiated arrangement is one example, but other employers will still need to understand the legal requirements that apply to them.

Why an agreed process still matters

A legal right doesn't remove the need to coordinate access. Employers still have to make practical arrangements for lawful union activity - protecting employees' ability to work and keeping normal site operations running. A written process can set out how visits are requested, where sessions happen, how online access is organised, and who answers questions.

That doesn't mean making access difficult on purpose. If processes add friction to the point where employees can't realistically take part, they undermine the point of the right and damage trust. The real test is whether the process is clear, consistent, and workable for both organisers and staff.

The issues Prospect wants to discuss

Prospect wants enough members to seek formal recognition, with a potential role in talks about pay, flexible working, and how Google rolls out AI. Those issues sit right at the intersection of technology and day-to-day working conditions. AI decisions can affect the tasks employees are asked to do, how teams are structured, and what skills the company expects staff to develop.

That doesn't mean every AI deployment would automatically become a union negotiation. And it doesn't mean Prospect already has a say in Google's decisions. It does mean the union is putting AI on the list of issues that could matter for employee representation if recognition is achieved. The difference between raising an issue and agreeing an outcome should stay clear.

For employees thinking about membership, the key question isn't whether a union can promise a preferred result. It's whether collective representation could help employees raise concerns, share information, and negotiate on issues that affect their work. The answer will vary by role, team, and personal priorities.

Google is not the first major tech company involved

Prospect also reached a similar access agreement with Meta in September, covering about 5,000 UK employees. That's a useful comparison: workplace access is becoming a live issue for more than one large technology company, but each access deal still has to be understood on its own terms. Getting a structure for access doesn't automatically produce recognition - or the same negotiating setup - at another employer.

Google also has a history of employee organising. In April, DeepMind researchers voted to unionise amid concerns about Google's Pentagon AI work. In the United States, Alphabet Workers Union members rallied in July for job protections. Taken together, these examples show that questions about representation and technology decisions aren't confined to a single office or single country.

The legal context still differs across countries. The UK access right here comes from UK legislation, while US developments are better treated as background, not proof that the same rules apply to Alphabet employees under US law. For multinational employers, that gap matters: global policies have to work alongside local rights and processes.

A useful way for employees to assess the change

Employees don't have to treat access as either a guaranteed victory or a guaranteed threat. They can look at it in steps:

• What can I ask? Find out what membership involves, what the union is seeking, and how it plans to represent different roles.
• What is already agreed? Separate the access arrangement from any future recognition or bargaining process.
• Which issues affect my work? Consider pay, flexible working, AI deployment, and other conditions in light of your own team.
• What happens next? Watch for clear information on membership and any path to seeking recognition.

This way of thinking avoids treating the presence of organisers as proof of a specific outcome. It also gives employees a grounded basis for deciding whether collective representation is relevant to them.

Build a process before the next request

For technology companies, the practical takeaway is to put a consistent access process in place rather than treating every request as an exception. A workable plan should spell out who owns the request, how the company checks the relevant rules, what arrangements are needed for office visits or online sessions, and how employees will be informed.

A simple checklist can help, such as:

1. Confirm the legal requirements. Use current UK guidance and get advice if the situation is unclear.
2. Name an accountable contact. Don't let requests bounce between facilities, HR, and legal teams without a clear owner.
3. Set neutral logistics. Decide timing, space, online access, and security measures without adding unnecessary barriers.
4. Communicate accurately. Explain what access means - and what it doesn't - especially the difference between recruitment and recognition.
5. Review the process. Make sure sessions are accessible across offices, roles, and different working patterns.

The goal isn't to create a complicated programme. It's to avoid inconsistent decisions that create compliance risk and leave employees wondering whether the rules are being applied fairly.

Separate compliance from employee relations

Meeting a legal obligation isn't the same as understanding why workers may want representation. And an employer doesn't have to treat a union access agreement as proof that existing internal forums have failed.

Internal groups can offer one kind of feedback channel. A union can offer independent representation and seek collective recognition. Whether employees feel one or both meet their needs is something for the workforce to decide - not a label a company can settle on.

A credible response therefore has two parts: comply with the access rules, and also take time to understand the underlying concerns without assuming a communications effort will fix them automatically. If employees are worried about pay, flexibility, or AI-related changes, the company needs a way to hear those worries and explain its decisions. Otherwise, access may become the visible part of a deeper trust problem.

Plan for the next step, not just the visit

The bigger operational question may come after recruitment: what happens if Prospect seeks formal recognition? Companies should understand the recognition process and be ready to respond through the right channels. That doesn't require betting on whether recognition will succeed. It requires knowing who makes decisions and how employee questions will be handled.

For a global technology business, planning should be jurisdiction-specific. The UK law in this case can't just be transplanted into a US policy or treated as a universal rule for every office. A consistent company principle - clear, respectful communication - can travel across borders; the legal mechanics cannot be assumed to be the same.