Establishing secure connection…Loading editor…Preparing document…

Miscellaneous Form SF312

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

MISCELLANEOUS FORM SF312 — GENERAL BUSINESS AGREEMENT

This General Business Agreement (the Agreement) is made and entered into as of Effective Date: by and between Client Name: and Contractor Name: .

WHEREAS

WHEREAS, Client Name: desires to retain Contractor to provide certain services described below; and

WHEREAS, Contractor Name: represents that it has the skill, personnel, and resources necessary to perform such services in accordance with the terms and conditions set forth in this Agreement.

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, the parties agree as follows:

SCOPE OF WORK

PAYMENT TERMS

Total Contract Amount: $

Late Payment Fee:   — Late fees accrue on unpaid balances from the date payment is due.

Invoices shall be submitted in writing to the billing contact designated by Client, and Client shall remit payment within days of invoice receipt unless otherwise agreed in writing.

TERM AND TERMINATION

Term Commencement Date:   Term Expiration Date:

Either party may terminate this Agreement for convenience upon providing written notice to the other party at least days prior to the intended termination date. Either party may terminate immediately for material breach that remains uncured for thirty (30) days following written notice of breach.

CONFIDENTIALITY

Each party (Receiving Party) will hold in confidence and not disclose to any third party any Confidential Information of the other party (Disclosing Party). "Confidential Information" means non-public information disclosed in any form that is identified as confidential or that, under the circumstances, should reasonably be understood to be confidential. Confidential Information does not include information that is (a) publicly available without breach of this Agreement; (b) already rightfully in the Receiving Party's possession; (c) rightfully received from a third party without restriction; or (d) independently developed by the Receiving Party without use of the Disclosing Party's Confidential Information.

The Receiving Party shall use Confidential Information solely to perform its obligations under this Agreement, shall restrict access to employees and contractors who have a need to know, and shall take reasonable measures to prevent unauthorized disclosure. Upon termination or request, the Receiving Party shall return or destroy the Disclosing Party's Confidential Information and certify in writing that such return or destruction has been completed.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of law principles. The parties consent to the exclusive jurisdiction of the state and federal courts located within that State for the resolution of any disputes arising under this Agreement.

ENTIRE AGREEMENT

This Agreement, together with any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous negotiations, proposals, representations, and understandings, whether written or oral. Any amendment to this Agreement must be in writing and executed by authorized representatives of both parties.

ADDITIONAL PROVISIONS

Assignment: Neither party may assign its rights or delegate its duties under this Agreement without the prior written consent of the other party, except that either party may assign to an affiliate or in connection with a merger or sale of substantially all of its assets.

Remedies: The parties agree that a breach of the confidentiality obligations or unauthorized use of intellectual property will cause irreparable harm for which monetary damages may be insufficient; accordingly, the non-breaching party shall be entitled to seek injunctive relief in addition to any other remedies available at law or in equity.

PARTY CONTACT INFORMATION

Client — Printed Name:

By:

Date:

Contractor — Printed Name:

By:

Date:

Enter text✕

What the Miscellaneous Form SF312 Is and When It Applies

Miscellaneous Form SF312, commonly known as Standard Form 312, is the U.S. government nondisclosure agreement used to govern access to classified information. The form documents the signer’s legal obligations not to disclose classified material and typically appears in federal personnel and contractor onboarding, assignment changes, and security clearance processes. Agencies use SF312 to establish continuing duties of confidentiality, to record each individual’s acknowledgment of those duties, and to provide a consistent written basis for administrative or security actions if an unauthorized disclosure occurs.

Why the SF312 Matters for Security and Compliance

SF312 defines legal confidentiality obligations that protect national security information, creates a record of informed consent to nondisclosure, and supports agency personnel and contractor security programs under federal policy and agency regulations.

Why the SF312 Matters for Security and Compliance

Who Typically Completes or Signs SF312

Use SF312 whenever an individual is granted or continues access to classified information or when agency policy requires re-acknowledgement.

  • Cleared employees assigned to classified duties who must affirm nondisclosure responsibilities.
  • Contractors or subcontractors with adjudicated clearances providing services to a federal program.
  • Security office staff and human resources personnel who maintain and store signed forms.

Representative Roles and Responsibilities

Security Officer

Security officers receive and retain signed SF312s, verify completion before clearance-based access, and maintain chain-of-custody and retention according to agency record schedules.

Cleared Contractor

Contractors sign SF312 to acknowledge nondisclosure duties; they must understand reporting obligations for potential breaches and coordinate with their sponsoring agency or facility security officer.

Core Elements Found on a Professional SF312

A complete SF312 contains structured provisions to identify parties, describe classification obligations, and record acknowledgements required by federal security policy and agency guidance.

Form Header

Form title, OMB control information, and agency-specific routing instructions that identify this as the government SF312 NDA.

Signer Identity

Full legal name, job title or contractor role, employer or sponsoring agency, and identifying information used for personnel records and audit trails.

Acknowledgement Text

Standard nondisclosure language describing continuing obligations, legal consequences, and duties after separation from classified access.

Signature Block

Live signature line, printed name, date signed, and organizational affiliation to create a clear attribution and effective date of obligations.

Witness or Official

Position for the security official or authorized representative who accepts the signed form and records custody.

Retention Instructions

Agency-specific guidance on where to file the original, who receives copies, and how long the record is retained for audit.

Step-by-Step: Completing and Submitting SF312

Follow these sequential steps to ensure SF312 is properly completed, acknowledged, and filed according to agency practice.

  • 01
    Prepare Form: Obtain blank SF312 and review instructions.
  • 02
    Fill Fields: Complete identity and employment fields carefully.
  • 03
    Sign and Date: Signer signs; security official accepts and dates.
  • 04
    File With Security: Submit original to sponsoring security office.

Typical SF312 Handling Workflow

This sequence summarizes how SF312 moves from signer to final record custody within an organization.

  • Issue: Agency or contractor issues SF312 before classified access.
  • Sign: Individual signs to acknowledge nondisclosure duties.
  • Accept: Security official accepts and documents receipt.
  • Store: Original retained in security or personnel file.

Digital Workflow Settings Commonly Used for SF312

Configure e-submission and authentication settings to meet agency identity, audit, and retention requirements.

Field Configuration
Authentication Use strong multi-factor authentication for signer verification
Signature Type Accept only wet or verified e-signatures per agency policy
Audit Trail Capture IP, timestamp, and action history for each signer
Retention Auto-archive signed originals to secure record system

Digital Signing Considerations for SF312

Confirm agency policy before using any eSignature platform and retain a detailed audit record for compliance and review.

  • Authentication Methods: KBA, SMS, or SSO combined with MFA
  • File Formats: Use PDF/A or PDF for tamper-evident storage
  • Integrations: Connect with HR or security case management

Security and Compliance Features Relevant to SF312

Encryption In Transit: TLS 1.2/1.3
Encryption At Rest: AES-256
Certifications: SOC 2 Type II
HIPAA Support: BAA available
Audit Trail: Detailed signer events
21 CFR Compliance: 21 CFR Part 11 support

Common Mistakes to Avoid When Preparing SF312

  • Incomplete identity fields that prevent clear attribution and delay processing.
  • Using personal or abbreviated organization names that do not match personnel records.
  • Signing before required training or before clearance adjudication is complete.
  • Failing to route the original to the security office for official custody and retention.

Potential Consequences of Incorrect or Missing SF312

Administrative Action: Access suspension or removal
Employment Sanctions: Discipline or termination
Criminal Liability: Prosecution under federal statutes
Contract Remedies: Loss of contract or claims
Civil Liability: Damages or injunctions
Recordkeeping Risk: Audit findings or noncompliance

When to Sign, Renew, or Return SF312

Timing is driven by access needs and agency policy; use these typical triggers to determine when SF312 must be executed or re-acknowledged.

Prior to Access:

Sign before any classified information is disclosed.

Upon Role Change:

Sign when duties or sponsoring organization change.

Clearance Renewal:

Re-acknowledge per agency periodic review schedule.

Separation:

Security office records SF312 at termination for follow-up.

Policy Updates:

Re-sign if agency modifies nondisclosure terms.

Comparing eSignature Vendors for SF312 Workflows

When selecting an eSignature vendor for SF312, compare pricing, security controls, and features that support strong authentication and retention.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies Varies Varies Varies
Bulk Send Yes (Business Premium) Varies Varies Varies Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Varies Varies Varies Varies
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Practical Examples of SF312 Use

Real-world scenarios illustrate how SF312 is used across agencies and contractor relationships.

Federal Onboarding

A new analyst signs SF312 before accessing classified files

  • SF312 is filed with the security officer
  • The security office retains the original and records the access authorization in the personnel security file for audit.

Contractor Clearance

A cleared subcontractor employee signs SF312 when assigned to a program

  • Program security official accepts the signed form
  • The prime contractor maintains the SF312 in contract security records and provides copies to the contracting officer as required.

Frequently Asked Questions About SF312

Answers to common questions about form use, electronic signing, and recordkeeping for SF312.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users