This looks like the work of a bit of a control freak. It seems odd to codify so many things in so much detail. It seems they are a pretty small and young company (the handbook has multiple references to being less than 10 employees, their Twitter account joined in 2012), so why do they feel the need to specify how many weeks of vacation you should have taken in the year leading up to the sabbatical you earn in <i>your fifth year of employment</i>?<p>Some of these things seem ripe for deviating from before they even see their first legitimate use:<p>&quot;It makes Clef look great when our employees speak at industry conferences&quot; -- so employees are allowed to go four times a year, spending $1000 each time, subject to approval, oh, and this is a &quot;benefit&quot;? Anyway, it&#x27;s nice -- but does this mean that if there&#x27;s a conference somewhere, everybody agrees it&#x27;s a great opportunity, but it&#x27;s my fifth, and it will cost $1100, then we just shrug and don&#x27;t go? No, I thought not, so why have the rule at all? What, exactly, is the problem they are solving by writing this stuff down?<p>I get it at a larger company, where you need to align expectations across a larger body of employees, but when you&#x27;re &lt;10 employees, you can literally just raise your voice in the room and say &quot;Any reason we shouldn&#x27;t send Joe to FooCon to speak about the FizzBuzz? It&#x27;s a bit pricey, probably $1100, but it&#x27;s it worth it right?&quot; -- that&#x27;s a much more transparent decision than anything written in a handbook.