Skip to main content
Humanities LibreTexts

18.5: Sample SSS and eSSS

  • Page ID
    180273
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    The guidance and examples that follow are derived from multiple sources and experience; however, check with your command officials for guidance or supplements to AFMAN 33-326.

    SSS Format Standards (AF IMT 1768)

    • Format:
      • Page setup, margins, font, point size and text wrapping: Set by the application for AF IMT 1768; cannot be changed by users.
      • Tabs: Center aligned in line with the signature block lines (see sample SSS, below).
      • Line spacing: Single space within paragraphs (no blank lines); double space between first-level paragraphs (one blank line) and before "//SIGNED//."
      • Paragraph numbering: Number or letter all paragraphs at the left margin. Paragraphs may be sub-divided using the same outline structure as for the official memorandum.
    • Content: The form-generating software limits the SSS to a single page. If additional coordination or summary space is needed, follow the "SSS Fundamentals" guidance repeated below:
      • Coordination Overflow: If more than ten offices need coordinate on the package, the first ten offices are listed on the original SSS form. Beneath the original SSS form, add a second AF Form 1768 that has the "TO" blocks renumbered from 11 to 20 and is completed through the subject. The second SSS is attached behind the original SSS.
      • Summary Overflow: Use plain bond paper if additional "Summary" space is needed.
    • Signature block: Use the signature block for the action officer or the official designated as the office of primary responsibility (OPR) for the SSS package. The signature block is placed flush with the left margin with "//SIGNED//" (to indicate official Air Force information) above the official’s name, rank, service affiliation, duty title, organization, and contact information (telephone and/or e-mail). The signature must match the signature block: do not sign "for" another official; and do not use an authority line. .

    SSS Sample (AF IMT 1768)

    clipboard_e7ceb87cfa96f9809b33ecd735b11945d.png

    Figure \(18.5.1\) Staff Summary Sheet Example

    eSSS Format (Body of an e-mail)

     

    The eSSS as the body of an e-mail serves the same purposes and has the same elements as the Air Force Form 1768. The primary difference is that you do not use a form to fill in the required coordination, identification and summary elements. If the eSSS format is chosen, the action officer or official designated as the office of primary responsibility (OPR) transmits package electronically (e-mail or other electronic staffing software) to the first reviewer to coordinate/comment. The first reviewer forwards the package, with any comments and all the attachments, to the next reviewer. This procedure is repeated until last reviewer listed in the eSSS coordination section has coordinated on the package. The last reviewer forwards the entire package back to the OPR for final action and/or to close the task. With this in mind, consider the following sample SSS and eSSS.

    • Format:
      • Page setup and margins: Typically set by the e-mail application.
      • Font/point size: Times New Roman font, 12 points.
      • Text wrapping: Text for all paragraphs wraps to the left margin.
      • Tabs: List Tabs flush with the left margin below the signature block with one blank line between the signature block and the Tabs list.
      • Line spacing: Single space within paragraphs (no blank lines); double space between first-level paragraphs (one blank line) and between elements (AO line to SUSPENSE line; RECOMMENDATION to "//SIGNED//," signature block to Tabs, etc.)
      • Paragraph numbering: Number or letter all paragraphs at the left margin. Paragraphs may be sub-divided using the same outline structure as for the official memorandum.
    • Content: All the sections of the SSS are combined in the body of the e-mail. The first section in the e-mail is the coordination section. The second section combines the staff summary with action officer contact information and the suspense date. While there are no page limits with the eSSS per se, action officers should strive to keep the eSSS summary concise-no longer than two pages when printed. Check with your local command section for further guidance.
    • Signature block: Use the signature block for the action officer or the official designated as the office of primary responsibility (OPR) for the SSS package. The signature block is placed flush with the left margin with "//SIGNED//" (to indicate official Air Force information) above the official’s name, rank, service affiliation, duty title, organization and contact information (telephone and/or e-mail). The signature block and the system-generated "From" information must match: do not sign "for" another official; do not use an authority line; do not add slogans, quotes, or other personalization to an official e-mail signature block.

    eSSS Sample (Body of an e-mail)

    clipboard_ece45f2014cc58c0f20022ebaa81d2bf0.png

    Figure \(18.5.2\): Electronic Staff Summary Sheet Example


    18.5: Sample SSS and eSSS is shared under a not declared license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?