Internal Operations Manual Template
Four documents and two sheets that check every licensed tool against the meeting calendar and policies, so an unexplained one becomes a named finding.
Free download · No account needed
Every operations manual template on page one is the same fill-in-the-blank outline: How We Work, Roles and Ownership, Operating Standards, a Core SOP Library. None of them tell you where the content comes from, so writing it means interviewing the whole company from a blank page. Whitfield Consulting Group, a 37-person management consulting firm, tried a different starting point: the policies already on file, a meeting calendar export, and the identity export naming every tool the firm pays for.
Of the firm's 34 licensed applications, 21 turned up by name somewhere in that policy-and-calendar corpus. Thirteen did not, and six of those were single-seat, individually elected tools nobody needed to explain. The other seven were team-wide licenses nobody's meetings or policies ever mentioned, costing $870.50 a month combined, $10,446 a year, with no explanation reachable by anyone who didn't already know to ask. GAO found the identical failure at federal scale, tracing it to agencies that never checked license inventories against what they had purchased in the first place.
The same cross-check works on decisions, not just tools. Whitfield's org chart named the COO as compliance owner, but the committee's own minutes showed the operations manager chairing every session for four months straight, with the COO attending none of them. That gap becomes a row in Decision Norms instead of a surprise for whoever routes the next compliance question. The output sits next to the procedure library it deliberately does not replace, and next to the handover that names a successor once someone in one of these rows actually leaves.
What's in the pack
Operating Handbook
The narrative itself: how departments actually hand off work, and where the other three docs and two sheets fit, built from what a new hire's second week actually needs answered.
Cadence Guide
Every recurring meeting checked for whether it actually decides anything or just informs, with the total person-hours it costs summed across attendees so the real weekly load is a number, not a guess.
Tool Guide
Every licensed application checked against the meeting and policy corpus for a real mention, splitting the unexplained ones into individually-elected tools and genuinely orphaned team-wide licenses with a dollar figure attached.
Decision Norms
Who actually chairs or decides each recurring topic, checked against meeting minutes rather than assumed from the org chart, with the two recorded as separately checkable facts wherever they disagree.
Team and Ownership Map
One row per function naming who actually owns it day to day against who the org chart says owns it, flagging the same single-person concentration a continuity plan treats as risk.
System Register
Every tool from the identity export scored against every meeting agenda and policy for a real mention, so an unexplained team-wide license becomes a named finding instead of an assumption.
How it works
- 1
Send what already exists
Any written policies, a calendar export of your recurring meetings, and an identity or SSO export listing licensed tools. Missing pieces get named rather than guessed at.
- 2
Every tool gets checked
The System Register cross-references each licensed application against every meeting agenda and policy for a real mention, splitting the unexplained ones into individual elections and team-wide orphans.
- 3
Decisions get mapped to reality
The Team and Ownership Map records who actually chairs or decides each recurring topic, checked against the meeting record rather than assumed from the org chart.
- 4
The handbook gets written
Operating Handbook, Cadence Guide, Tool Guide and Decision Norms get drafted from what the two sheets show, in the voice of someone explaining the place to a smart new hire.
Frequently asked questions
Isn't this the same as the SOP library?
No. The SOP library documents individual procedures step by step. This handbook explains the operating rhythm those procedures sit inside: which meetings actually decide something, which licensed tools are load-bearing, and who really makes each kind of call, none of which a single procedure captures.
What if we don't have a full SSO export?
Send whatever identity list exists, even a spreadsheet of logins IT maintains manually. A partial list still finds real gaps; it just cannot rule out a tool paid for outside that list entirely, which the handbook says plainly rather than implying completeness it doesn't have.
How does the System Register decide a tool is unexplained rather than just under-used?
By checking two different sources, not one. A tool absent from meeting agendas could still be documented in a policy, and vice versa. Only a tool missing from both counts as unexplained, which is a stricter bar than a single search would apply.
What happens after a tool is flagged as unexplained?
Nothing automatic. The register hands the finding to whoever holds the budget for that team. They confirm whether it's quietly load-bearing for something the corpus doesn't capture yet, or genuinely idle, and cancel it with a real dollar figure attached instead of a vague note to audit software spend someday.
Does this replace an org chart?
No, it corrects it where the two disagree. The org chart states who reports to whom; Decision Norms states who has actually chaired or decided each recurring topic in the recent record, and the two frequently drift apart without anyone updating either document.
What format are the downloaded files?
Word (.docx) for the four documents, CSV (.csv) for the two sheets, zipped together and needing no conversion. Excel, Numbers and Google Sheets open the sheets directly, and the format documents open in Word or Pages.
What does 'Edit with AI' actually do?
It opens a private workspace with this exact pack installed, then asks for your policies, meeting calendar and identity export. River checks every tool against every meeting and policy for a real mention, drafts the two sheets from what it finds, then writes the four docs from those.
Find the tool nobody can explain
Send your policies, meeting calendar and identity export, and see which licenses, and which decisions, don't match what's on file.
Edit with AI