There are several queries and answers for technical reference manuals, user guides etc. and I've found enough places on the net that have these templates along with detailed descriptions of their scope. But where can I find a TeX template for Standard Operating Procedures specifically? The template should typically have:

  • A standard-looking Header and footer for the procedure numbers, company name etc.
  • Uniform formatting for headings, bullets and sub-bullets
  • Simple placeholders for images (not a priority).

The guys at my workplace typically write this sort of thing in Word 2007, but I feel the stuff I'm working on now is quite is quite well suited to and will benefit greatly from using TeX.

P.S. I am at a beginner level when it comes to LaTeX, but I'm very comfortable using it. Also, if it makes any difference to your answers – I prefer to write it completely by hand in a simple editor (rather than using something like LyX, for example). The output is in pdf.

Here are two examples of the look I'd like:

migrated from stackoverflow.com Jul 7 '11 at 14:21

This question came from our site for professional and enthusiast programmers.


This isn't everything you're looking for, but it's a start, and hopefully will give you an idea of how easily document class customization can start out. Mind you, I'm not going to worry much about emulating bad habits from the Word document, but focus on simple semantic content and formatting.

Let's start with some minimal content from your PDF:

\title{Personal Protective Clothing Level}



\subsection{Structure Fires}
\item All firefighters operating in the ``hot zone'' of a structure fire will be in
full turnouts to include coat, pants, helmet, hood, gloves and boots. When operating
in an IDLH atmosphere an SCBA shall be worn.

\item Engineers when operating close to the incident and exposed to products of
combustion shall also be in full PPE including SCBA. If outside the ``hot zone''
engineers will be allowed to modify their PPE accordingly. If the Engineer is
considered to be a part of the RIT team, then full PPE including an SCBA shall be


Using the standard article class as given, you get page content that looks like

enter image description here

After writing a (relatively) simple document class based off article, the same content (with \documentclass[12pt]{sop} and \approved{Chief Harper} instead of \documentclass[12pt]{article}, you get page content that looks like

enter image description here


enter image description here

The file sop.cls that created this layout is:

\ProvidesClass{sop}[2011/07/08 v0.2 Modified article class for standard operating procedures]
% https://stackoverflow.com/questions/581916/how-do-you-extend-article-document-class-in-latex

% Passes and class options to the underlying article class

% Redefine the page margins

% Modifications to the section titles

% Modification of title block
% Ref: http://tex.stackexchange.com/questions/3988/titlesec-versus-titling-mangling-thetitle
\begin{tabular}{|c|p{2in}|l|l|} \hline
\multirow{3}{*}{logo} & \multicolumn{1}{p{2.5in}|}{\centering Mammoth Lakes Fire Protection District } & Date: \thedate & Number: \\ \cline{2-4}
& \multicolumn{1}{p{2.5in}|}{\centering Standard Operating Procedure } & \multicolumn{2}{p{2.5in}|}{Title: \mythetitle} \\ \cline{2-4}
& Approved By: \theapproved & \multicolumn{2}{l|}{Revision Date: \quad / \quad / \quad} \\ \hline

% For "Page N of M"
% For easier construction of page headers/footers
\fancypagestyle{plain}{ % for first page
\fancyfoot[L]{\framebox{Author: \theauthor}\\ \jobname{}.tex} 
\fancyfoot[R]{\framebox{Page: \thepage{} of \pageref*{LastPage}}}

\pagestyle{fancy} % for other pages
\begin{tabular}{|c|c|} \hline %
Revision Date: & Number: \\
\quad / \quad / \quad & \\ \hline
\fancyfoot[L]{\framebox{Author: \theauthor}}
\fancyfoot[R]{\framebox{Page: \thepage{} of \pageref*{LastPage}}} % \pageref* if we use hyperref, \pageref otherwise

% For easier customization of itemized, enumerated, and other lists
% For hyperlinked cross-references
% Ensure first page is correct style
% That's all, folks!

See this SO question for where I got started with this.


Regarding the body: There is a lot of goofy, inconsistent formatting going on there. The text in Section I (Scope) is indented, the text in Section II (Purpose) has a start of paragraph indent and is in bold, Section III (Definitions) has no indent period, Section IV (Responsibilities) has no start of paragraph indent but the whole paragraph is indented, and so on. The only consistency I see in that SOP is an utter lack of consistency. Replicating that utter lack of consistency is a piece of cake with microstuff word. Doing that is going to be a bit tough with LaTeX.

On the other hand, getting rid of that goofy crap (and it is crap) would, in the end, be a good thing.

The cute little box around the page content will also be a bit challenging, but someone else here will be able to solve that problem. What is going to be challenging is setting up that cute little title box. I've done that for a document that requires three cover pages (a pretty front cover, a less pretty inside front cover, and a signature page). It involved some down and dirty TeX nastiness. Something like

% \SOPtitlebox: Create the title for an SOP
% #1 - Date (format: mm/dd/yy)
% #2 - Number (format: Unknown. The example has a blank number.)
% #3 - Title (e.g. {Personal Protective Clothing Level})
% #4 - Approved by (e.g. {Chief Harper}, but probably a macro)
% #5 - Revision date (Hmmm. Example is / /, so presumably mm/dd/yy, but with blanks)
    % Contents of this macro left as an exercise for the user

I've asked a similar question over here: LaTeX for SOPs? with mixed results so far.

Also; while I don't want to speak for the original poster, I doubt they're interested in replicating the crappy, inconsistent formatting in the sample document.

What I'd assume they want to preserve would be:

  1. Box around the header (box around body optional)
  2. Box around the footer
  3. Logo in the header

The body style could probably be entirely cleaned up without anyone caring at all. SOPs seem to be typically produced by MS Word, resulting in this kind of crap.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy