• I compared my Operations Manual with the Table of Contents of this template, and it is nearly complete. But I am very interested in the Chapter "Application Interfaces".

In this case we recommend our product

"Application Interface Checklist"

The part two, the Documentation Template for Application Interfaces is identically with this chapter in our template for an IT Operations Manual.

• My Systems are running stable even without Operating Manuals, and my staff members do know those systems in and out.

Congratulations! - Many of your colleagues would love to have such systems and employees. - But...

1. An Operations Manual is a mandatory Requirement in all Auditing Standards!
2. More and more laws and regulations require mandatory external audits. For the case that none of such laws or regulations apply (not yet) to you, there are several more reasons why you really should have a comprehensive operations manual:
3. It is good practice to have an Operating Manual. We intentionally don't use "best practice", because an Operations Manual you should already have on a maturity level of "good practice", long time before you achieve "best practice"! And latests after something very unpleasant happened, the investigators will ask for the operating manual.
4. An voluntary audit (if successful) can reduce your Insurance costs!
5. Each Quality Standard requires an unambiguous assignment of all duties direct to persons or via roles. But this requires that all tasks are detailed listed.