Whistle Enterprise for HR and people teams

HR work involves meetings where the documentation is the record that decisions are defended on. A grievance hearing, a disciplinary meeting, an investigation interview, a settlement discussion: each one produces a written record that has to be defensible if an employment tribunal or the employee’s solicitor asks questions about it later. The documentation matters more than the meeting itself in some sense; the meeting happens and is forgotten, but the record is what governs what comes next.

This piece is for HR managers, employment lawyers, people team leads and in-house counsel who handle the most sensitive HR meetings. It covers what Whistle Enterprise gives the HR documentation workflow, why an on-machine tool fits HR’s data-protection posture better than a cloud one, and the questions that come up most often in procurement.

The HR meeting types Whistle Enterprise is designed for

Five meeting types between them cover most of the cases where high-quality, defensible documentation is the point:

• Investigation interviews. A complainant, a respondent and possibly witnesses. Each interview is a meeting that produces a structured statement. The documents from each interview combine into the investigator’s report.
• Grievance hearings. The employee, their companion, the chair of the hearing, possibly an HR observer. The document of the meeting is part of the formal grievance file.
• Disciplinary meetings. Same pattern, different framing. The document is part of the disciplinary record and informs the outcome letter.
• Settlement and exit conversations. The terms have to be recorded precisely and the document needs to be the basis for the formal agreement that follows.
• Performance and capability meetings. The documentation supports the formal process if it later becomes contested.

In each case, the recording is the source of truth, the transcript is searchable, and the structured document is what goes into the formal HR file. The pattern is the same as legal or charity work, but the regulator (in this case employment law and the wider tribunal system) has a particular interest in how the documentation was produced.

Why “nothing leaves the HR machine” matters

A grievance about another employee’s behaviour. A disciplinary about misconduct. A settlement that mentions named individuals. An exit conversation with sensitive complaints. Each of these is a meeting whose contents the organisation has a duty not to disclose to people who do not need to know. The standard list of “people who do not need to know” includes vendors of meeting AI tools.

The cloud meeting AI tools all work in a way that breaks this duty quietly. Audio uploads, transcription and document generation happen at the vendor, copies of the artefacts are kept in the vendor’s storage. The vendor’s data-processing addendum tries to manage this through contract, but the contract does not change the fact that the audio of a confidential HR meeting has been heard by people outside the organisation.

Whistle Enterprise does not create that disclosure. The audio is captured on the HR officer’s laptop. The transcription model and the writing model both run there. The output is written to a local workspace that can be encrypted with a password. There is no vendor in the processing chain.

For the wider data-protection framework, meeting recording and UK GDPR covers the controller-processor analysis. The result for HR work is that the standard processor-of-personal-data step in any DPIA disappears, because there is no processor.

Subject Access Requests and tribunals

Two specific points come up in HR procurement that are worth flagging.

Subject Access Requests. An employee can ask for the personal data the organisation holds about them. If a meeting was recorded, the recording is personal data of the people whose voices are on it. With a cloud tool, the SAR response has to include both the local copy and the vendor’s copy. With Whistle Enterprise, the SAR response covers the local files only; there is no vendor copy to retrieve.

Disclosure in tribunal proceedings. If an HR matter goes to tribunal, the documentation produced in HR meetings can become disclosable. The chain of custody for that documentation matters. A document produced entirely on the HR officer’s own machine has a clearer chain of custody than one that travelled through a vendor’s infrastructure and back. The vendor’s logs, the vendor’s processing terms, the question of who at the vendor saw the audio: all of those become potential disclosure questions in a contested case. None of them apply to a tool that ran the whole pipeline locally.

Workflow integration

Whistle Enterprise integrates with HR workflow at the export step. The HR officer records and processes the meeting in Whistle Enterprise, then exports the structured document to PDF, Word, Markdown or plain text, and saves it to the employee file in the HR system through the same workflow used for any other document.

There is no specific integration with HR information systems (Workday, BambooHR, Cezanne, etc.). The export is the boundary. This is by design: the data-protection story stays simple because there is no integration that introduces another data flow.

For HR teams that handle a lot of these meetings, the per-seat licence model fits. The pricing page has the tier table; the FAQ on the pricing page covers per-person versus per-device.

Where to start

The free 30 day trial is the right way to test the fit. Run a recording of a recent investigation interview (with the employee’s consent, in line with your organisation’s policy) and look at the structured document Whistle Enterprise produces. That document is the foundation for the formal record; the HR officer’s professional judgement is what turns it into the formal interview note that goes onto the file. If that pattern fits the way your team works, the pricing page covers the licence tiers, and for HR functions above the public slider’s range the licensing email handles invoicing and enterprise terms.

Back to all articles