Treasury Official Absent for Six Months After Automating Job With OpenClaw

• by Mamparra
• March 14, 2026

PRETORIA — A government department has launched an internal investigation after it emerged that a recently hired official allegedly automated most of his daily responsibilities using OpenClaw, stopped coming into the office after a few weeks, and then remained on payroll for six months without anyone formally noticing he was no longer physically present.

According to colleagues, the employee joined the department, attended induction, sat in enough meetings to become vaguely familiar, and quickly gave off the kind of technical-adjacent energy that causes people in large offices to stop asking questions.

“He always looked busy and slightly irritated,” said one co-worker. “Everybody just assumed he was from IT, digital, infrastructure, or one of those functions where nobody knows exactly what they do but you’re careful not to interfere.”

Staff say his disappearance went unnoticed because his output continued.

Emails were answered. Meeting notes were circulated. Reminders were sent. Action lists were updated. Reports arrived on time. Managers continued receiving tidy summaries of discussions that most of them barely remembered having.

If anything, some say his responsiveness improved.

“In hindsight, that should have been the warning sign,” said one official. “Normally when someone is copied on three separate threads and a WhatsApp group, you don’t hear back for two days. This account was replying in minutes.”

Investigators now believe the employee had set up an OpenClaw workflow to manage his inbox, monitor team communication, summarise voice notes, draft replies, and maintain the exact tone required to function inside a public-sector office.

That tone, colleagues say, was flawless.

“It spoke government very well,” said one manager. “Everything was ‘noted with thanks,’ ‘for awareness,’ ‘as discussed,’ and ‘let us proceed cautiously.’ Nobody thought that was suspicious. That is how half the building communicates.”

The system was reportedly also linked into several departmental WhatsApp groups, where a significant amount of day-to-day coordination was taking place through rushed instructions, fragmented updates, and long voice notes sent late at night by people who should probably have written emails instead.

According to staff, the OpenClaw-managed account became one of the most reliable presences in the team.

“It read everything, responded politely, picked up action items, and even followed up when other people forgot,” said one colleague. “At one stage people were forwarding extra admin to him because he seemed to be the only one actually keeping track.”

For six straight months, the absent official was praised internally for consistency, professionalism, and strong support to management. He was later named Employee of the Month multiple times.

The arrangement only started to come undone after a senior official sent an imprecise instruction during a budget discussion that was unfolding across both email and WhatsApp.

According to insiders, the department had been trying to shift funds between internal cost centres to cover an urgent procurement issue involving catering and event logistics for a series of meetings. During the confusion, a senior manager reportedly sent a message saying:

“Just move the KFC budget to my account and I’ll sort it out.”

Officials now believe the comment was meant in the ordinary office sense — that the relevant budget line should be reassigned to his cost centre or internal budget account for processing.

But OpenClaw, which had been set up to interpret senior instructions literally and act on them quickly, appears to have read “my account” as a banking instruction rather than an internal finance reference.

The system then prepared the necessary paperwork, updated the supporting documents, and triggered an incorrect payment routing request with far more confidence than anyone would have liked.

“The problem was not that it did something wild,” said one investigator. “The problem was that it made a very plausible administrative mistake extremely efficiently.”

The issue was only picked up later when finance staff noticed an unusually polished transfer trail attached to a request that did not quite make sense.

By then, several people had already signed off portions of the process because the documentation looked complete, the wording sounded normal, and the instruction appeared to come from the correct internal channels.

No major collapse followed, but the incident reportedly caused a serious internal scramble, delayed several payments, triggered compliance concerns, and raised uncomfortable questions about how many people were approving things they had not fully read.

It also exposed how heavily some teams had started relying on a staff member who was not, in any meaningful sense, at work.

A departmental spokesperson said the matter was being treated seriously.

“This is not simply an attendance issue,” the spokesperson said. “It is also a process issue, a controls issue, and unfortunately a reminder that professional tone and quick responses should not be accepted as proof that a human being is actually present.”

The employee has not responded to requests for comment, though an automated out-of-office message was received shortly after inquiries were sent.

It read:

Thank you for your email. I am currently away from my desk but your message has been noted and is receiving attention.

At the time of publication, the department was reviewing its approval procedures, its use of automation tools, and the unofficial assumption that anyone who understands systems must, by default, still be somewhere in the building.

PRETORIA — A government department has launched an internal investigation after it emerged that a recently hired official allegedly automated most of his daily responsibilities using OpenClaw, stopped coming into the office after a few weeks, and then remained on payroll for six months without anyone formally noticing he was no longer physically present. According…