The Exception Manual: Log Edge Cases, Recover Worker Knowledge, and Decide When to Write a Rule, Use Judgment, Escalate, or Refuse

Written procedures cover normal cases. Real work includes duplicate records, missing permissions, conflicting instructions, unusual customer requests, and cases where following the steps would produce the wrong result. If everyone says, "Ask the person who knows," this book shows how to record that knowledge without pretending every answer can be reduced to a rule. The Exception Manual starts with an exception log. You reconstruct each case from records, actions, decisions, delays, and consequences. You interview experienced workers about specific incidents, compare how they handled them, group similar cases, and choose one of four routes: write a rule, preserve qualified judgment, escalate to someone with authority, or refuse work that should never enter the process. Worksheets and inspection procedures help you separate true exceptions from defects, incidents, missing prerequisites, ordinary variation, and uncontrolled scope. You will test proposed rules against cases that do not fit, set evidence thresholds, prepare complete escalation packets, write refusal criteria, and connect each decision to the forms, permissions, training, prices, and software that must change. The book maps the people, records, objects, states, permissions, decisions, histories, and consequences involved in each case. It shows where local facts, laws, prices, and professional duties must be checked instead of guessed. AI is limited to comparison, synthesis, and drafting. It does not become the source of truth or gain authority over people or records. The book also makes access, logs, review, correction, export, recovery, and stop controls visible before software handles a live case. You will also learn how to test a bounded exception-repair service before building software, and how to reject an AI product when the work lacks stable rules, review, correction, or a safe way to stop. This is for workers inside undocumented processes, small process owners, technical generalists, and independent builders who need to decide what to standardize, what to leave manual, what to escalate, and what to refuse.