A company operations manual is the reference document that collects and organizes, within a single architecture, the rules, policies and procedures that govern how a business runs. It is not the individual procedure, and it is not the process map: it is the organized container that holds them together and makes them easy to find.
In Italy, the issue is far from marginal. Labor productivity in the private sector has fallen for the second year in a row after a long period of growth [3], and Italian micro-enterprises are about 30% less productive than their European peers [4]. Public statistics do not isolate how much of that gap depends on the quality of organizational practices — operational documentation included; still, it is one of the few levers you can pull without changing scale.
This guide offers a phased path for building the manual: from choosing the content to designing the structure, from writing to putting it into daily use, through to maintaining it over time. It also points out the most common confusions — between manual, SOP, job description and handbook — and the mistakes that hollow out the tool.
One question that often comes up among those trying to get started remains open: where should you begin when the risk is writing a book that will stay closed?
Recognize the scope of the company operations manual
The word "manual" covers very different things: a collection of files in a shared folder, a 200-page PDF frozen in 2019, an internal wiki updated every week. Understanding where the manual ends and neighboring tools begin (SOP, job description, process map, HR handbook) is the precondition for the tool to work. ISO 9001:2015 provides the formal framework [1], but the distinction plays out mainly at the operational level.
How many of a company's documents today carry a version, a date and an owner? Without these three pieces of information, any document becomes indistinguishable from a personal note — and stops being a manual.
The ISO 9001:2015 standard, in clause 7.5 ("Documented information"), sets the minimum requirements: the creation, updating and control of system documentation must be organized and traceable [1]. The operations manual is the container in which documented procedures find a coherent structure. Without this container, documents remain orphans: each one lives on its own, without being connected to the others.
Operations manual vs. SOP (standard operating procedure). The SOP is the individual instruction that says how to do one thing. The manual is the system that connects SOPs to one another, places them in the context of policies and governs their versioning. As early as 1993, Hammer and Champy distinguished between process, procedure and activity [5]: the SOP is the part, the manual is the whole. An SOP without a manual is a valid but isolated tool; a manual without SOPs is an empty frame.
Operations manual vs. company procedure. The procedure is the rule for a single flow; the manual is the system in which that rule lives alongside other rules, roles and context. A procedure without a manual remains an orphan; a manual without procedures remains empty.
Operations manual vs. job description. The job description describes the position: a person's role, responsibilities and expected outputs. The manual describes how the company works: how activities are carried out, regardless of who performs them. They complement each other but do not overlap.
Operations manual vs. employee handbook. The handbook is an HR tool: it governs conduct, rights, duties, benefits and the code of ethics. The operations manual is a process tool: it describes how outputs are produced. They coexist in the company but answer different questions.
Operations manual vs. process map. The map is a visualization: graphic, concise text that does not replace explanation. The manual is the full text that explains, contextualizes and regulates. A good map belongs inside the manual, but does not replace it.
Being clear about the manual's scope is not an academic exercise: it is the prerequisite for not building overlapping or incomplete tools, and for knowing exactly what to include and what to leave out.
Design the manual's architecture: the three main sections
Most abandoned manuals share the same flaw: they were born without an architecture. Structure is not an aesthetic detail; it is the condition for anyone looking for information to find it in under a minute. An analysis of established practice (ISO 9001:2015 [1]; Hammer-Champy [5]) suggests a three-section architecture — identity, core processes, mandatory safeguards — on which to build the detail.
How many sections should the manual of a 10-person company have? The answer depends less on headcount and much more on the variety of processes and the number of external counterparts — customers, suppliers, authorities.
Section 1 — Identity and rules of the game. This first section contains what orients people who work in the company: the organizational chart, summary job descriptions, internal policies (expense reimbursements, communications, access), operating values. It is not a "philosophical" section but an orientation one: a new team member who reads it knows who decides what, on what basis and with what authority.
Section 2 — Core processes. This is the heart of the manual: the SOPs for the main processes, organized by operating area (sales, operations, administration, customer service). For each process, the manual does not replicate the SOP's detail but indicates where it is, who owns it and how it fits into the wider flow. Reading it alongside the guide to standard operating procedures (SOPs) clarifies the micro level of each instruction.
Section 3 — Mandatory safeguards. Occupational health and safety, GDPR, IT and cybersecurity, emergency procedures: these are non-negotiable contents that are often missing from the manual or enter it in a disorganized way. Having them in a dedicated section, with explicit owners and review intervals, reduces exposure to regulatory risk.
Example of a minimal table of contents (independent professional / practice with 2-4 people):
- Section 1: roles and responsibilities, internal communication policy, tool access
- Section 2: client acquisition process, service delivery process, invoicing and collection process
- Section 3: privacy and data processing (GDPR), backup and information security
Example of an extended table of contents (company with 50-100 employees):
- Section 1: up-to-date organizational chart, summary job descriptions by role, HR policies (reimbursements, leave, tools), operating values and code of conduct
- Section 2: sales (leads, proposal, contract), operations (planning, production/delivery, shipping, quality control), customer service (complaints, support, renewals), administration (accounts receivable, accounts payable, reporting)
- Section 3: workplace safety, GDPR (policies and record of processing activities), IT security, emergency management
The architecture chosen at this stage should not be changed midway without a specific reason: every structural change requires revising the tables of contents and cross-references. Better to choose carefully and then populate than to populate and then restructure. To visualize the overall structure graphically, the cluster on the business flowchart provides visual tools to integrate into the manual.
Gather and organize the content: the 4-phase process
Filling a manual starts with a choice many people skip: which processes to document first and at what level of detail. ISTAT reports that 48.8% of Italian SMEs use an ERP and only 21.1% a CRM [2]: process data often already exist, but are fragmented across different tools. The gathering phase is therefore, above all, an exercise in consolidation.
How long does it take to reach the first usable version of the manual? A minimal working version can be produced in 30-60 days; a complete version takes months. Confusing the two leads to early abandonment.
Phase 1 — Inventory. Before writing, map what exists: which processes are in place, who performs them, where they are already documented (if they are). The inventory does not need to be exhaustive: its purpose is to produce a rough list of all the company's processes as a starting point for prioritization. The guide to process mapping describes the detailed method.
Phase 2 — Priorities. Hammer and Champy teach that you do not document chaos: you redesign first, then write [5]. The criterion for choosing what to document first combines three variables:
- Frequency: how often the process is performed (a daily process is worth more than a monthly one)
- Criticality: how costly a mistake in that process is (a mistake in handling a complaint or in the collection cycle has a direct impact on cash and reputation)
- People turnover: how much the process depends on knowledge concentrated in one person (if a key person leaves, does the process stop?)
The priority checklist works like this: for each process, assign a score from 1 to 3 on each of the three variables. Processes scoring 7-9 are documented in the first phase; those scoring 4-6 in the second; those scoring 1-3 can wait.
Phase 3 — Writing. The SOPs for priority processes are written in a consistent format: title, purpose, scope, owner, sequence of activities, reference documents, version and date. The format does not need to be sophisticated; it needs to be consistent. The guide to standard operating procedures (SOPs) provides the working template.
Phase 4 — Integration. The SOPs are assembled into the manual: you build the table of contents, add cross-references between sections and create a glossary of the terms used. The table of contents is not an ornament: it is the navigation tool that lets anyone consulting the manual find what they need without reading everything.
Keep the manual alive: from publication to daily use
The manual that wins is not the best-written one but the most consulted one. The difference between a manual that sits on the server and one that becomes part of daily work depends on concrete choices: where it lives, how it is searched, at what moments it is called upon. Among the management practices that the Bank of Italy finds associated with higher productivity is the systematic collection and use of information to monitor and improve the production process: information that someone must be able to find when it is needed [8].
How many minutes does a new team member take to find the returns-handling procedure the first time they need it? If the answer is more than five, the manual exists only on paper.
Format and medium. The choice of medium depends on two variables: the size of the business and how often staff turn over.
- A shared Word/PDF file is adequate for organizations of up to 10-15 people with low turnover: simple to manage, accessible to everyone, easy to update. The risk is a proliferation of outdated versions.
- An internal wiki (even a free, simple tool) is preferable for growing organizations or those with high turnover: searchable, linkable, updatable without distributing new copies. It requires a minimum of discipline in its structure.
- A document management platform is justified when processes include approval steps, formal versioning or access differentiated by area. ISO 9001:2015 assumes one [1]; for companies without certification, it is often oversized in the early phase.
Indexing and searchability. Whatever the medium, the manual must be searchable: an analytical index, keywords for each section, explicit cross-references. If someone looking for "how to handle a complaint" has to leaf through thirty pages, the manual will soon be abandoned.
Embedding it in company rituals. Three moments when the manual must be explicitly called upon:
- Onboarding a new team member: the manual is the first document to read, with a session guided by their direct manager. Employee onboarding is the process in which the manual proves, or fails to prove, its value.
- Operational meetings on standard processes: when a process that has a procedure is discussed, the manual is opened. Effective business meetings become the moment when the documentation system enters daily work.
- A change of tool or supplier: every time a structural element of the process changes (a piece of software, a supplier, an owner), the manual is opened and updated before the new way of working becomes informal practice.
Imai describes standard work as the daily operational baseline: before improving, every operator must know the current standard [6]. The manual is that standard: not an archive of the past but a description of the current way of working.
The manual owner. In small organizations, this role can be part-time or rotate: what matters is that there is an explicit owner, tasked with receiving update requests, approving changes and communicating them to those who must apply them. Without an owner, the manual ages without anyone noticing.
Update the manual without rewriting it from scratch: versioning and review
The manual starts aging the day after it is published. Imai describes standard work not as a finish line but as a baseline: every standard is the basis for the next improvement [6]. The question is not "when to redo the manual" but "how often and with what method to update it, so that it stays aligned with operational reality."
How often should a chapter of the manual be reviewed? An annual review is a prudent threshold; off-cycle changes make sense when a concrete event justifies them.
Versioning. ISO 9001:2015 §7.5 sets the requirements for controlling documented information: each document must show a version number, update date and owner [1]. The simplest numbering is "v1.0," "v1.1" (minor change), "v2.0" (substantial revision). A change log — even as a short table at the end of the document — shows what has changed without rereading everything.
Review schedule. A sample schedule for a small or mid-sized company:
- Full annual review: at the start of the year or the end of the previous one, all sections of the manual are reviewed. You check that procedures are still aligned with reality, that owners are up to date and that regulatory references are still valid.
- Six-monthly reviews for the most variable sections: sales processes, customer service procedures, pricing policies. Because they change more often, they need a shorter cycle.
- Off-cycle reviews for specific events: a change of management software, a relevant regulatory change (GDPR, safety), a key person joining or leaving, a recurring error traceable to an outdated procedure.
Who proposes and who approves. Update proposals come from whoever performs the process: the person closest to operational reality is the first to notice when the document no longer reflects how the work is done. The manual owner (or the function manager) evaluates the proposal, approves the change and communicates it to those who must apply it.
Communicating changes. An approved change that is not communicated has the same effect as a change never made. Communication must be direct (not left to the hope that someone rereads the document), proportionate to the impact (for a minor change, an entry in the log is enough; a substantial change requires explicit communication) and tracked (who received the communication, who read the new version).
For the recursive philosophy that drives the continuous updating of the manual, the reference is the cluster on continuous improvement in the company.
5 common mistakes that hollow out the operations manual (and how to avoid them)
Most abandoned manuals share a few recurring mistakes. European data help frame what is at stake: EU micro-enterprises are projected to operate in 2025 at about half the productivity of large enterprises [7]. Recognizing the typical mistakes is the fastest way not to repeat them.
Which of these mistakes is most common? ISTAT data on Italian companies' adoption of document software [2] suggest that the first mistake avoided — building the architecture before the content — is also the least practiced.
Mistake 1 — Photographing chaos instead of redesigning it. Warning sign: the manual is written in a hurry, copying the way things are done now, without asking whether that way is the right one. Immediate fix: apply the Hammer-Champy principle [5] — first simplify and redesign the process, then document it. A manual that crystallizes disorganization perpetuates it.
Mistake 2 — A "monumental," unreadable manual. Warning sign: the document runs over 100-150 pages, uses technical jargon that is not shared, and has no summary or analytical index. Immediate fix: rewrite it in simple operational language, use bullet points, limit each procedure to strictly necessary information, add a glossary. The usability test is simple: if a new team member cannot find the answer to their question in under five minutes, the document needs revising.
Mistake 3 — No versioning and no owner. Warning sign: the file shows no date, no version and no owner's name. Several copies are in circulation. Immediate fix: immediately add a control template (version, date, owner, change log) and archive or delete previous versions — as required by ISO 9001:2015 §7.5 [1].
Mistake 4 — A manual that never enters the rituals. Warning sign: the manual has been published, but nobody consults it; operational questions keep going straight to the founder or the manager. Immediate fix: define three explicit triggers for consulting it ("when a customer asks this question, open the manual at section X"; "when a new team member joins, the first three days follow the manual"; "when a supplier changes, the manual is updated before switching to the new way of working") and build them into onboarding and operational meetings.
Mistake 5 — Confusing the manual with other tools. Warning sign: the manual contains detailed SOPs, job descriptions, contractual material and HR policies all together, without a clear structure. Immediate fix: define the architecture (the three main sections described above), move out-of-scope content into the right document (job description, HR handbook, process map) and add explicit cross-references between related documents.
Limits and conditions of applicability
The path described in this article is calibrated on companies with relatively stable processes and between 5 and 150 people. Some conditions may reduce the applicability of the guidance:
- Highly variable sectors: in contexts where processes change rapidly (tech startups, companies going through product transformation), a "heavy" manual risks aging faster than it can realistically be updated. In these cases, lightweight, modular documentation focused on the most stable processes is preferable.
- Startup-stage businesses (1-3 people): at this size, the cost of building a structured manual can exceed the benefit. It is better to start with 2-3 SOPs for critical processes and build up gradually.
- Correlation vs. causation: neither the OECD [4] nor the JRC [7] measures the quality of companies' documentation practices. The only survey cited here that touches on the topic is the Bank of Italy's study of structured management practices [8], which documents a positive association with productivity while explicitly stating that the analysis is descriptive and does not establish a causal link. The operations manual is a necessary but not sufficient condition for improving company productivity.
- ISTAT data [2]: the references to ERP and CRM adoption among Italian SMEs point to the gap in management tools, not directly to the quality of operational documentation. The link is inferred, not documented by the source itself.
FAQ
Is an operations manual required by law? Generally no, except in specific regulated sectors (food, pharmaceutical, safety) or for ISO 9001-certified companies. In all other cases, the manual is a voluntary internal governance tool.
What is the difference between an operations manual and a quality manual? The quality manual is a specific document of the ISO 9001 management system: it describes how the company meets the standard's requirements. The operations manual is broader and less formal: it describes how the company works as a whole, regardless of certification.
How long should an operations manual be? There is no right length. A 30-page manual used every day is worth more than a 300-page one nobody consults. The criterion is functionality: the document must allow anyone who needs it to find the answer in under five minutes.
Who should write the manual? Ideally, whoever performs the process: they are the most accurate source of operational information. The manual owner's job is to coordinate, structure and approve, not to write the whole document alone.
Can the manual be in digital format? Yes, and for most companies it is preferable: it is easier to update, distribute and make searchable. What matters is that there is a clearly identifiable "current" version and that obsolete versions are archived or removed from circulation.
Operational summary
A company operations manual works when it meets four conditions: it has a clear scope (it is not everything, and it is not nothing), it has a three-section architecture (identity, core processes, mandatory safeguards), it becomes part of daily operational rituals (onboarding, meetings, system changes) and it is kept alive by a review cycle with explicit intervals and owners. The build process follows four phases: inventory, priorities (frequency × criticality × people turnover), writing the SOPs, integration into the overall document. The most frequent mistakes — photographing chaos, producing an unreadable document, skipping versioning, leaving it in a drawer, confusing it with other tools — are all predictable and can be corrected before they show up.
Conclusion
Building a company operations manual is not an editorial project: it is an exercise in architecture. The sequence that works is clear — first the scope (what it is and what it is not), then the three-section structure, then the four phases of content gathering, and finally daily use and versioning. Without architecture, even the richest document remains dead weight.
The manual is also the point where other organizational tools meet. For its prerequisite — knowing which processes exist — read the guide to process mapping. For the detail of the individual instructions the manual contains, how to write standard operating procedures (SOPs) covers the micro level. For the overall framework — roles, flows, safeguards — the pillar article on company procedures sets out the system in which the manual lives.
A company that truly has a living manual is recognizable by a few simple things: people who join find answers on their own in their first days, people who leave do not take the only copy of how things work with them, and people who stay do not improvise the same answer twice. The productivity gap that separates smaller businesses from larger ones [4][7] will not be closed by a document; but if part of it can be recovered without changing scale, it goes through here: through the simplest — and most underrated — document a business can give itself.
Sources and references
[1] International Organization for Standardization, "ISO 9001:2015 Quality management systems — Requirements", ISO, 2015. Available at: https://www.iso.org/standard/62085.html
[2] ISTAT, "Imprese e ICT, Anno 2025", Istituto Nazionale di Statistica, 2025. Available at: https://www.istat.it/comunicato-stampa/imprese-e-ict-anno-2025/
[3] Banca d'Italia, "Relazione Annuale sul 2024 — Sintesi", Banca d'Italia, May 2025. Private-sector labor productivity fell for the second year in a row, after a long period of growth. Available at: https://www.bancaditalia.it/pubblicazioni/relazione-annuale/2024/sintesi/index.html
[4] OECD, "Economic Surveys: Italy 2024", OECD Publishing, January 2024. Italian micro-enterprises are about 30% less productive than their European peers; the report attributes to small family-run businesses a lack of scale for research, of management skills and of incentives to adopt technology. Available at: https://www.oecd.org/content/dam/oecd/en/publications/reports/2024/01/oecd-economic-surveys-italy-2024_18011b9d/78add673-en.pdf
[5] Hammer, M., Champy, J., "Reengineering the Corporation", HarperBusiness, 1993.
[6] Imai, M., "Kaizen: The Key To Japan's Competitive Success", McGraw-Hill, 1986.
[7] European Commission, JRC, "Annual Report on European SMEs 2024/2025, SME Performance Review", Publications Office of the European Union, 2025. In 2024 the EU non-financial business sector counted about 26.1 million SMEs (99.8% of enterprises); SMEs' real value added fell by 0.2% in 2024, with a projected recovery of +1.6% in 2025, and micro-enterprises are projected to operate in 2025 at about half the productivity of large enterprises. Available at: https://publications.jrc.ec.europa.eu/repository/handle/JRC142263
[8] Baltrunaite, A., Formai, S., Linarello, A., Mocetti, S., "Proprietà, governance, management e performance delle imprese", Banca d'Italia, Questioni di Economia e Finanza n. 678, March 2022. Invind 2019 survey of about 3,200 manufacturing and service firms with at least 20 employees; the section on monitoring covers the collection and use of information to monitor and improve the production process. Structured management practices are positively associated with productivity, with the analysis stated to be purely descriptive. Available at: https://www.bancaditalia.it/pubblicazioni/qef/2022-0678/QEF_678_22.pdf