You can guess the rest: Calls for help because "we just tried such-and-such" ...
Only last week I got called out to a hotel I put a wireless system in a couple of years ago. Guests had reported being able to see the office computers which when I left was just not possible. I had my thoughts about what had been done, but "no, nothing's been changed" - yeah right, no one has every changed anything
Needless to say, when I got on site, stuff had been changed. Because the hotel weren't prepared to buy a new router back when I installed the wireless kit, and couldn't give me any login details for the routers that were there, nor ADSL details to setup a router again if I blew it's config - I'd had to cascade two routers, one connected to the internet and with all the wireless kit attached, and a second one segregating the office network. Well actually, that's the setup they already had for some unfathomable reason and it happened to be convenient.
When I got there, one router had been replaced as they now have FTTC (VDSL with an OpenReach modem), and everything had just been plugged into the one router - so yes, all the guests had access to the office network, which was (not by us) setup with zero security on file shares. This wasn't just accidental either - the IP subnet had changed as well.
It got blamed on a previous manager who "knows a bit about IT" but doesn't work there any more. Still, it's a couple of hours of billable time for me
EDIT: And just for good measure, judging from logs in the WiFi management software, it looks like it was done over a year ago, and a guest mentioned it around Christmas but they dismissed it as "can't be, it was all set up securely" and never looked into.
if you must have a few sockets for general use, a possible way forward if the wiring is all in earthed trunking or conduit, or SWA, is to fit sockets with a built in RCD but NOT to have one at the circuit origin - that way only defective kit goes off, which is after all the idea.
Well given how few sockets there are (late 80's build, back when they only expected the vacuum cleaner and perhaps an electric typewriter), in our office it would probably be cheaper to swap them all out that replace the DB.
Equally one can risk asses the RCDs away in many commercial cases by having a regime of inspection/test or user training.
Sadly, given that some of our users do nothing to dispel the stereotype of the "la la la can't hear you" attitude to safety and care of equipment, I doubt that any regime of user training could risk assess away the issue. We have a vacuum cleaner with a fairly short lead because during PAT inspection it was found to be worn through to the copper in several places - due to having had the cleaner head "parked" on the cable with the brush bar running - and the "fix" was to shorten the cable to remove the damaged bits. But several times, after having pointed out to people why the cable is so short, I still heard the familiar buzzing sound of the brush bar chewing at the flex while someone is using the hose to remove dust bunnies from PCs - completely oblivious to the racket even after I've pointed it out to them
And then there was the time I 'had words" with someone who picked up an insulated driver off my desk, said "that'll do the job" and started to walk off with it. "Excuse me chappie, what do you plan to use that for" was a polite translation of what I said - he only wanted to use it to lever up the seat position locking bar in one of the cars where the normal operating cable had broken
Needless to say, he didn't get to use my driver, nor has he borrowed tools again without asking