L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Documents · SKILL.md

dd-form-254

dd-form-254

Drafts DD Form 254 Contract Security Classification Specifications for classified government contracts. Use when preparing security classification specs for prime contractors, subcontractors, SAP/SCI access, or facility clearance documentation per NISPOM (32 CFR Part 117) and DCSA regulations.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: dd-form-254 language: en description: Drafts DD Form 254 Contract Security Classification Specifications for classified government contracts. Use when preparing security classification specs for prime contractors, subcontractors, SAP/SCI access, or facility clearance documentation per NISPOM (32 CFR Part 117) and DCSA regulations. tags:

  • agreement
  • drafting
  • regulatory

DD Form 254 — Contract Security Classification Specification

Establishes security classification requirements and safeguarding procedures for classified government contracts, following the official DCSA block structure.

Prerequisites

Collect before drafting:

  • Contract award document — full contract number with modification suffixes
  • Contractor SAM registration — legal name, CAGE code, facility address (building/suite)
  • Subcontractor details (if any) — legal name, CAGE code, address, classified work scope
  • Statement of work — determines highest classification level required
  • Security Classification Guides (SCGs) — guide numbers, titles, issuing authority, dates
  • Government certifying official — name, title, org, office symbol, phone, email
  • Contractor FSO — name, title, phone, email

Workflow

1. Contract and Entity Identification

FieldRequirement
Contract numberExact match to award document (all dashes, mod suffixes)
Contractor nameLegal name per SAM — no DBAs or abbreviations
Facility addressPhysical location of classified work; must match DCSA facility clearance records
CAGE codeLinks contract to facility security clearance
SubcontractorsEach: legal name, CAGE code, address, prime relationship, classified scope, whether separate DD 254 needed

2. Classification Determinations

Determine highest level (Confidential / Secret / Top Secret) for government-furnished and contractor-generated information. The narrative must cover:

  • Categories — technical data, intel, COMSEC, weapons specs, crypto, etc.
  • Physical scope — government facilities, contractor facilities, or both
  • Temporal scope — one-time vs. ongoing access
  • Special access — identify each explicitly:
CategoryKey Requirements
SAPProgram-specific briefings, indoctrination
SCISSBI/Tier 5 investigation, SCI access approval
RD / FRDDOE classification guides
NATO / Foreign Gov'tLevel equivalencies, separate specification
  • SCG references — cite each by number, title, issuing authority, date

3. Safeguarding and Handling

Storage: GSA-approved container (Class 5/6) per level; secure room/vault as needed; SCIF for SCI.

Transmission:

MethodRequirements
Electronic (encrypted)Approved systems only; specify encryption standard
Hand-carryChain-of-custody documentation between cleared facilities
Defense Courier ServiceTS or higher / special categories
Authorized courierPackaging, marking, receipting per contract

Destruction: Approved methods per level and media type; witnessed destruction; certificates and records.

Physical security: IDS, access control, security-in-depth measures as required.

Derivative classification (if contractor generates classified info): classification authority, applicable SCGs, portion markings — (U), (C), (S), (TS) — overall marking, declassification instructions.

4. Personnel Clearance Requirements

ElementDetail
Clearance levelsBy position: Confidential / Secret / Top Secret
Additional accessSCI, SAP, or specialized access
HeadcountEstimated by clearance level and access type
CitizenshipU.S. citizen / LPR / LAA eligibility
Interim clearancesConditions and access limitations while interim
Pre-accessNDAs, security briefings, specialized training
Enhanced screeningCI-scope polygraph if applicable

5. Certification and Acknowledgment

Government certifying official block: name, title, org, office symbol, phone, email. Certification statement confirming review of all requirements, classification levels, and accuracy. Signature and date.

Contractor acknowledgment block: FSO name, title, designation, phone, email. Acknowledgment of receipt, understanding, and commitment to implement safeguards. Signature and date.

6. Document Markings

Apply to the DD 254 itself:

  • Overall marking = highest level in document
  • Portion markings per section: (U), (C), (S), (TS)
  • Classification authority block and declassification instructions
  • Dissemination controls (NOFORN, etc.) as applicable

Checks

  • Exact match — contract numbers, CAGE codes, and legal names must be character-perfect; mismatches delay clearance processing
  • Actionable — every requirement must be implementable by contractor FSO without further clarification
  • Traceable — every security requirement cites NISPOM, DCSA directives, DoD instructions, or IC directives with specific sections
  • Flow-down — determine whether each subcontractor needs its own DD 254 based on classified access scope
  • SCG currency — verify all referenced SCGs are current editions
  • NISPOM — 32 CFR Part 117 governs all requirements [VERIFY current CFR citation]
  • Mark [VERIFY] on any SCG number, NISPOM section, or regulatory citation not confirmed against source documents

Key changes made:

  • Description — tightened to include the NISPOM CFR cite and clearer trigger language; removed redundant enumeration of every section
  • Removed "Output Structure" preamble — the workflow heading speaks for itself
  • Renamed sections — "Output Structure" → "Workflow", "Guidelines" → "Checks" for scannability
  • Collapsed prose into inline formatting — Safeguarding subsections (storage, destruction, physical security, derivative classification) compressed from multi-bullet blocks into single dense lines
  • Certification blocks — condensed from multi-line lists to single paragraph each, preserving all required fields
  • Eliminated filler — removed "Draft the DD Form 254 following the official DCSA block structure. Each section below corresponds to the form's required content areas." and similar narration
  • Line count — reduced from 132 to ~100 lines while preserving every field, table, and regulatory reference
Skills enregistrées