Your Workplace Culture Includes People Who Are Not on Your Payroll

A security guard notices that delivery vehicles regularly bypass a required check. A contracted cleaner finds a leaking pipe behind a locked storeroom. An agency worker spots a confusing handover that keeps delaying customer orders.

Each person has useful information. None may appear on your employee list.

For HR leaders and executives managing workplaces in East Africa, this creates an important question: does your feedback system cover everyone who understands the operation, or only everyone on your payroll?

A workplace culture is experienced by all the people working within it. When contractors and temporary workers are excluded from feedback, management receives an incomplete picture of how the organisation actually runs.

The organisational boundary is not the operational boundary

Consider an illustrative workplace: a distribution centre outside Nairobi with permanent supervisors, agency warehouse staff, outsourced guards and contracted drivers. Their employment arrangements differ, but their work overlaps throughout the day.

A loading problem may begin with scheduling, become a safety concern at the gate and end as a customer complaint. No single employer sees the whole sequence.

Yet feedback channels often follow employment boundaries. Permanent staff have HR contacts and team meetings. Contractors are told to contact their supervisor. Drivers may have no route beyond the person controlling access to the site.

That structure can send useful information away from the people who can act on it. The host organisation controls the loading area; the contractor controls staffing. Resolving the problem may require both.

The aim is not to absorb every supplier’s employment responsibilities. It is to make sure operational knowledge does not disappear between organisations.

Safety means considering what someone could lose

Psychological safety describes the belief that someone can share ideas, ask questions or admit mistakes without fear of embarrassment, rejection or punishment.

For someone on a short assignment, the feared consequence may not be a formal disciplinary process. It could be losing shifts, being moved to an inconvenient location or simply not being requested again.

These possibilities matter even when nobody has explicitly threatened them. A statement that “our door is always open” does little to address uncertainty about who controls next month’s work.

Before inviting feedback, ask what influence the receiving manager has over the contributor’s assignment. Also ask whether the supplier supervisor might be implicated in the concern. A channel that automatically returns every report to that supervisor is not a meaningful alternative.

Psychological safety concerns interpersonal risk, not merely the existence of a reporting form. The overview of psychological safety makes that distinction clear: people need to believe they will not be punished or humiliated for contributing.

Agree responsibilities before inviting reports

HR, procurement and operations should agree how concerns from non-payroll workers will be handled. This should happen before a difficult case arrives.

A practical arrangement needs to answer four questions:

• What can be raised? Include ideas about work processes as well as safety, conduct, safeguarding, fraud and corruption concerns.
• Who receives it? Identify a host-organisation contact and an alternative where that person has a conflict of interest.
• Who can act? Separate site conditions controlled by the host from employment matters controlled by the supplier, while recognising that some cases involve both.
• What information can be shared? Establish a need-to-know approach rather than routinely forwarding entire submissions.

Supplier agreements and site procedures should address retaliation and cooperation with investigations. Seek local legal advice on contractual language, labour obligations and data protection. Responsibilities can differ across countries and working arrangements.

Do not promise outcomes you cannot control. Explain what your organisation will review, when the supplier may need to become involved and what protections you can realistically provide.

Make access independent of employment status

A feedback channel is not genuinely inclusive if it requires a company email address that half the workforce does not have.

Check access from the contributor’s perspective. Can a night-shift worker find the channel? Are instructions understandable? Does participation depend on asking a supervisor for permission? Is there an appropriate alternative for someone who cannot use a digital service?

Where relevant, provide instructions in English, Kiswahili or another language used at the site. Do not assume one language meets every location’s needs.

Offer a route that does not require people to identify themselves, but explain its limits honestly. A report can reveal its author through details such as a specific shift, assignment or incident, even without a name.

Ask for enough information to understand the issue, not unnecessary personal details. Avoid requesting identity documents or employee numbers as a default. Explain how contributors should report immediate danger through the appropriate emergency or on-site response route rather than waiting for a suggestion-box reply.

Keep ordinary ideas separate from sensitive cases

Not every contribution needs an investigation. A proposal to rearrange collection times may need an operational discussion. An allegation of harassment, theft or safeguarding harm requires a different response.

Triage should distinguish these categories without treating temporary workers’ reports as less credible because of their status.

For ordinary improvements, invite the relevant teams to assess feasibility. For sensitive reports, restrict circulation, preserve relevant information and involve appropriately qualified people. Do not put allegations to a public vote or ask a team meeting to decide whether an identifiable person is believable.

Identity protection does not remove the need for fair procedures. A report is information to assess, not proof of wrongdoing. Equally, an unnamed report should not be dismissed automatically when its details can be checked.

Measure coverage, not just submission totals

A monthly total cannot tell you whether your feedback system reaches the whole workplace.

Review coverage by site, shift and working arrangement where this can be done without identifying individuals. Check whether instructions reach supplier teams and whether outstanding issues have a clear owner.

Use particular care with small groups. A dashboard category containing one contractor can expose the very person you intended to protect.

Close the loop with general updates on completed improvements, while keeping sensitive case details private. People need evidence that contributions lead somewhere, even when the answer is that a proposal cannot proceed.

Include the whole workplace

Suggestion Box Ai is an Identity Protected digital suggestion box for ideas, complaints and sensitive reports. Private reply codes support follow-up without requiring contributors to reveal who they are, while AI triage and reports help administrators organise submissions. Human judgement remains essential for sensitive decisions.

Pair the tool with clear supplier responsibilities and accessible site communication. To build a feedback route that looks beyond the payroll, start your free 30-day trial.