Comment Re:Meh (Score 1) 301
Terms of a person's firing are almost always non-public. A company as large as Staples can't publish to ALL it's employees that they fired Bob over $5.00 misappropriated on an expense report. That's malicious. It's appropriate to say we will (and have) terminated over expense reports being wrong without giving the offenders name.
I can't think of any company I've worked at that's attached names to memos like that. Even companies that actually call the cops on somebody don't typically inform the employees of the person's name, or particular details of the infraction beyond the company "rule book" for just this reason.
Um, the easy solution would be to list the reason for every firing on the corporate website as a matter of store policy. See the thing isn't if you think something's right or not. It's that a policy exists and is followed. If they don't have a policy, then opps. Now, if they go outside their normal policy, opps. Now, if they change their policy to say everyone being fired is going to have their final evaluation posted and the reason that they were fired, it becomes magically o.k.
Never say that a large company can't do something like this. It'd actually be easier for a large company to post it on their web site under their employee terminations section and reasons. Usually at small businesses, or single stores, it's pretty much known amongst everyone within 5 seconds if some one had the cops called on them for something. It's only larger stores with multiple shifts and enough people that everyone didn't get the gossip within 5 seconds and it was taking the gossip more like 5 weeks and wasn't as accurate. That's when it's understandable that someone would like to set the record straight per se. Now if they just had a simple form to fill out that basically has the employee's name and dates of employment and reason for separation from the company they could just have some peon enter into a DB and it all show up on the internet for any interested parties to find out.
I'm more surprised that this isn't currently done rather than the current setup.