When HR and marketing systems should share audiences under controls

Sharing people data with marketing starts with a purpose

HR and marketing systems should share audiences only when there is a clear purpose the people on the list would expect, a recorded consent or other lawful basis for that purpose, and access controls limiting what marketing can see. Without all three, keep the lists apart and let HR send the messages itself.

The requests arrive naturally. Marketing wants staff to share a campaign. The careers team wants a newsletter for past applicants. Someone suggests inviting former employees to a product event. Each sounds harmless, and each uses personal data that HR collected for employment rather than marketing.

Employees, candidates and alumni sit on the boundary

Current employees are the most common case. An advocacy programme asks staff to share company posts, and marketing needs to know who has opted in. It needs names, a work email and the opt-in, and nothing from the employment file.

Candidates and past applicants form a talent pool. HR collected their data for a recruitment process. Sending them company news or future openings needs a basis covering that use, and many candidates will never have agreed to it.

Former employees are the third group. An alumni network can bring referrals and goodwill, but their records sit with HR for employment and statutory reasons. Using those records for marketing without fresh consent carries the most risk of the three.

PDPA principles on purpose, notice and consent apply to all three groups. Check the current requirements against the Personal Data Protection Commissioner's guidance or with your adviser before building any shared list.

Controls to put in place before any list changes hands

Each control below answers a question an auditor or an unhappy former employee could ask.

• A written purpose for each shared audience, approved by the HR head and reviewed by whoever handles data protection
• A separate opt-in captured for that purpose, with the wording and date recorded
• A minimum field set, usually name, contact address and opt-in status, with no employment, salary or performance data
• Named people in marketing who can open the list, reviewed whenever someone joins or leaves the team
• A clear withdrawal route, and a process for HR to remove anyone who withdraws
• A rule that the list is refreshed from HR and never edited or extended by marketing
• A record of what was sent to the list and when, kept for review

Cases where HR should keep the list and send the message

Often, sharing the list is unnecessary. HR can send the alumni newsletter itself using content marketing prepares. HR can invite past candidates to a career fair from its own recruitment records. Marketing supplies the design and the words, and HR keeps the data.

This suits audiences where consent is uncertain or the list is small. It also suits sensitive moments, such as staff communication during a restructuring, when the message must come from HR's own channels. Event invitations are another example: if marketing wants staff ambassadors at a customer event, HR can ask for volunteers through its own channels and pass marketing only the names of those who said yes.

Sharing makes more sense when marketing needs to measure results across campaigns, reach the same audience through several channels, or combine opted-in staff with external contacts for an event. Even then, share only the opted-in subset.

Setting up the two systems in the right order

Begin with HR's records and consent capture. Without a reliable opt-in field there is nothing safe to share. Next, define each shared audience and its purpose on paper. Then structure marketing's contact lists so shared audiences stay separate from customer and prospect lists, labelled with their source.

Only after those steps should the teams decide how a list moves: a controlled export each time, a scheduled refresh, or a link scoped between systems. Start with the simplest method that serves the purpose and review it after the first few campaigns.

Plan the withdrawal path at the same stage. When someone opts out through marketing, HR needs to hear about it so the master record agrees, and when someone withdraws through HR, marketing's next refresh must drop them. Test both directions with a dummy record before the first real send.

Where each list should live

Employee and candidate records belong in HR's system, such as BukuHR. Marketing's audience and contact lists, including any opted-in subset, can sit in BukuReach with clear labels showing where each contact came from. Data exchange between the two is not automatic; it is scoped with Fasttrade around the purposes and controls you have agreed.

Frequently asked questions