Don’t forget that your JDex should do the heavy lifting for you. When you save your ops manual[1] for ‘deactivating the alarm system’ at 12.22+30 perhaps you should also drop a quick note in your JDex. Just a bullet point will do, but enough to help you get to this thing quickly when you need it.
Tangent: if there’s a reason for me to want to write software, which I do, it’s this sort of thing. Imagine JDex.app monitoring your file system and noticing a new file. Perhaps it prompts you if you want to make a note. Perhaps it makes that note itself, extracted from your OS’ metadata for the file. Or, these days, an on-device AI-generated summary. Perhaps it’s enough for you to make the note manually but have every ID in the JDex be one click away from the file system folder? So many possibilities…
12.40 is something else. Let me see … 12.40 ■ Getting around 🚚.
No, there are two assigned premises-types: back, and front. If a furniture maker only has a workshop, that’s just back-office.
Many of you will only need back-office. That’s okay. There will be other examples where you don’t need a whole section. As an IT contractor and then Johnny.Decimal I have no need for 12.40, for example.
This one’s a judgement call. If occasionally you have someone over, it might not be worth the mental burden of classifying some things as front-office, yeah.
As you noted above, the rule of use-the-first-thing-you-hit applies. So if you do have security guards and they’re for both your staff and your customers, use 12.22.
This ops manual can be as simple as a .txt file with a couple of bullet points. Something else we’re going to be emphasising: simple documentation is better than no documentation and might even be better than complicated documentation. ↩︎