Can I sign SF 294 electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states if the signer shows intent, consents to electronic records, attribution is established, and a reproducible record is retained.

What if a name on the form doesn't match ID?

Mismatched names can delay verification. Use the legal entity or individual name that matches government-issued ID and document the reason for any variance before signature.

Is notarization required for this form?

Not typically required unless the specific agency or contract demands it. Check contract clauses and state rules for notarization or witness requirements before executing.

How do I correct an error after signing?

Prepare an amended form, mark it as an amendment with explanation, and route it through the same approval chain. Keep both versions for audit purposes.

What authentication strength is recommended?

Email plus SMS OTP is common; use higher-assurance options (multi-factor or certificate-based) for high-risk or regulated submissions per agency policy.

How long must signed copies be retained?

Follow the longest applicable retention rule: federal financial records three years minimum (IRC §6501(a)); healthcare documents six years (45 CFR §164.530(j)); state rules may extend these periods.

Electronic Signature
Templates
Legal
Standard Form 294

Standard Form 294

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

SUBCONTRACTING REPORT FOR INDIVIDUAL CONTRACTS

(See instructions on reverse)

Public reporting burden for this collection of information is estimated to average 9 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to the FAR Secretariat (MVP), Acquisition Policy Division, GSA, Washington, DC 20405.

OMB No.: 9000-0006

Expires: 04/30/2004

1. CORPORATION, COMPANY OR SUBDIVISION COVERED

a. COMPANY NAME

b. STREET ADDRESS

c. CITY

d. STATE

e. ZIP CODE

3. DATE SUBMITTED

4. REPORTING PERIOD FROM INCEPTION OF CONTRACT THRU:

MAR 31 SEPT 30

2. CONTRACTOR IDENTIFICATION NUMBER

5. TYPE OF REPORT

REGULAR FINAL REVISED

6. ADMINISTERING ACTIVITY (Please check applicable box)

ARMY NAVY AIR FORCE

GSA DOE DEFENSE CONTRACT MANAGEMENT AGENCY

NASA OTHER FEDERAL AGENCY (Specify)

7. REPORT SUBMITTED AS (Check one and provide appropriate number)

PRIME CONTRACTOR SUBCONTRACTOR

8. AGENCY OR CONTRACTOR AWARDING CONTRACT

a. AGENCY'S OR CONTRACTOR'S NAME

b. STREET ADDRESS

c. CITY

d. STATE

e. ZIP CODE

9. DOLLARS AND PERCENTAGES IN THE FOLLOWING BLOCKS:

DO INCLUDE INDIRECT COSTS DO NOT INCLUDE INDIRECT COSTS

SUBCONTRACT AWARDS

TYPE

CURRENT GOAL

WHOLE DOLLARS

PERCENT

ACTUAL CUMULATIVE

WHOLE DOLLARS

PERCENT

10a. SMALL BUSINESS CONCERNS (Include SDB, WOSB, HBCU/MI, HUBZone SB, and VOSB (Including Service-Disabled VOSB))

10b. LARGE BUSINESS CONCERNS (Dollar Amount and Percent of 10c.)

10c. TOTAL (Sum of 10a and 10b.)

100.0%

11. SMALL DISADVANTAGED BUSINESS (SDB) CONCERNS (Include HBCU/MI) (Dollar Amount and Percent of 10c.)

12. WOMEN-OWNED SMALL BUSINESS (WOSB) CONCERNS (Dollar Amount and Percent of 10c.)

13. HISTORICALLY BLACK COLLEGES AND UNIVERSITIES (HBCU) AND MINORITY INSTITUTIONS (MI) (If applicable)

14. HUBZone SMALL BUSINESS (HUBZone SB) CONCERNS (Dollar Amount and Percent of 10c.)

15. VETERAN-OWNED SMALL BUSINESS CONCERNS (Include Service-Disabled Veteran-Owned SB Concerns) (Dollar Amount and Percent of 10c.)

16. SERVICE-DISABLED VETERAN-OWNED SMALL BUSINESS CONCERNS (Dollar Amount and Percent of 10c.)

17. REMARKS

18a. NAME OF INDIVIDUAL ADMINISTERING SUBCONTRACTING PLAN

18b. TELEPHONE NUMBER

AREA CODE

NUMBER

GENERAL INSTRUCTIONS

This report is not required from small businesses.

This report is not required for commercial items for which a commercial plan has been approved, nor from large businesses in the Department of Defense (DOD) Test Program for Negotiation of Comprehensive Subcontracting Plans. The Summary Subcontract Report (SF 295) is required for contractors operating under one of these two conditions and should be submitted to the Government in accordance with the instructions on that form.

This form collects subcontract award data from prime contractors/subcontractors that: (a) hold one or more contracts over $500,000 (over $1,000,000 for construction of a public facility); and (b) are required to report subcontract awards to Small Business (SB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), HUBZone Small Business (HUBZone SB), Veteran-Owned Small Business (VOSB) and Service-Disabled Veteran-Owned Small Business concerns under a subcontracting plan. For the Department of Defense (DOD), the National Aeronautics and Space Administration (NASA), and the Coast Guard, this form also collects subcontract award data for Historically Black Colleges and Universities (HBCUs) and Minority Institutions (MI).

DISTRIBUTION OF THIS REPORT

For the Awarding Agency or Contractor:

The original copy of this report should be provided to the contracting officer at the agency or contractor identified in Block 8. For contracts with DOD, a copy should also be provided to the Defense Contract Management Agency (DCMA) at the cognizant Defense Contract Management Area Operations (DCMAO) office.

For the Small Business Administration (SBA):

A copy of this report must be provided to the cognizant Commercial Market Representative (CMR) at the time of a compliance review. It is NOT necessary to mail the SF 294 to SBA unless specifically requested by the CMR.

What Standard Form 294 Is and when it applies

Standard Form 294 is a standardized U.S. government form used by agencies and contractors to report contract-related administrative and financial information. Agencies may adopt a specific SF‑294 layout for periodic reporting, reconciliation, or closeout tasks. This guide explains the form's typical structure, the information commonly requested, and practical steps for accurate completion, secure storage, and compliant electronic submission under U.S. e-signature law.

Why using a correct Standard Form 294 matters

Using the Standard Form 294 consistently reduces processing delays, supports audit readiness, and preserves contract payment accuracy. Proper completion creates a clear record for contract administrators and legal review while enabling compliant electronic signature and retention under ESIGN (15 U.S.C. ch. 96) and applicable state law (UETA or equivalent).

Typical users and stakeholders for Standard Form 294

The form is commonly completed by contract administrators, finance staff, and authorized signers tied to federal or agency contracts.

Contracting officers and CO representatives responsible for oversight and acceptance.
Prime contractors and contract administrators preparing periodic financial and performance reports.
Authorized signers and contract finance teams responsible for certification and retention.

Distribution usually includes the contracting officer, prime contractor records, and the agency payment office for reconciliation.

Step-by-step completion: a practical checklist

Follow these four core steps to prepare a complete, auditable Standard Form 294 ready for signature and filing.

01

Gather details: Collect contract number, period, and supporting financial records.
02

Enter data: Populate each field carefully; use agency-specified formats.
03

Review & certify: Confirm totals, attach backup schedules, and verify signatory authority.
04

Sign and file: Execute signatures and submit per the agency routing requirements.

How submission and routing typically flow

Standard Form 294 generally moves from preparer to reviewer to approving official and then to the agency payment or records office.

Prepare: Preparer compiles data and supporting documents.
Internal review: Supervisor or finance reviewer validates entries.
Approval: Authorized official certifies accuracy and signs.
File: Submit to contracting office and retain a copy for records.

Configuring an electronic workflow for consistent submissions

Set up the form workflow to match agency routing, required fields, and signer authentication to avoid manual handoffs and delays.

Field	Configuration
Required Fields	Mark contract ID, amounts, period, and certifier as mandatory.
Authentication	Use email plus SMS or stronger methods for key signers.
Routing	Create sequential routing for preparer → reviewer → approver.
Retention	Store completed PDFs with embedded audit trails.

Technical considerations for eSubmission and signature

Configure the platform to accept the form file types you use and to capture an audit trail and signer authentication.

File formats: PDF, DOCX, HTML, Excel
Integrations: Salesforce, NetSuite, Google Workspace
Audit data: IP, timestamps, signer emails

Security, encryption, and compliance essentials

In-transit encryption: TLS 1.2/1.3

At-rest encryption: AES-256

Authentication standards: Multi-factor and SSO available

Certifications: SOC 2 Type II

Regulatory support: ESIGN and UETA compliant

Health data: HIPAA available with BAA

Common preparation pitfalls to avoid

Using inconsistent contract identifiers across attachments, causing reconciliation errors.
Entering dates in multiple formats leading to reporting period confusion.
Omitting required backup schedules and delaying reviews or payments.
Allowing unauthorized signers to certify without documented authority.

Consequences and risks from incorrect or late submissions

Processing delays: May defer payment or correction requests

Audit exposure: Incomplete records increase audit risk

Contract holds: Administrative holds until reconciled

Financial adjustments: Retroactive corrections or recoupment

Legal review: Material misstatements prompt deeper inquiry

Reputation impact: Repeated errors can harm contractor standing

Typical timing and processing expectations

Timing varies by agency and contract; confirm the schedule in your contract or agency reporting instructions before submission.

Reporting frequency:

Often monthly or quarterly per contract terms

Internal review time:

Allow 3–7 business days for supervisor review

Agency processing:

Agency reconciliation timelines vary widely

Correction window:

Respond promptly to agency inquiries to avoid holds

Record retention:

Keep originals per regulatory retention rules

Key milestones in the SF 294 lifecycle

Track these sequential stages from preparation to archive to maintain an auditable chain of custody.

01

Prepare records

Compile ledger entries, invoices, and supporting schedules.

02

Internal validation

Supervisor verifies figures and completeness.

03

Sign and submit

Authorized official signs and forwards to contracting office.

04

Comparison of eSignature options for completing and signing forms

Choose an eSignature provider that meets your agency's security and compliance needs; the table below lists typical plan starting prices and selected features for comparison.

	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	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Illustrative scenarios showing common uses

These brief examples show how organizations use the form to streamline contract reporting and reconciliation.

Optica Ventures

Optica compiled monthly contract reconciliations into a single SF 294 package

Saved approval cycles through consolidated attachments
The result reduced review queries and shortened payment reconciliation time by eliminating duplicate submissions.

Martin Properties

A property management firm standardized reporting across projects

Used a template to enforce consistent field entry
This consistency improved internal audits and made external contract closeouts faster and less error-prone.

Practical tips for accurate and efficient completion

Adopt repeatable procedures and templates to reduce errors, speed review, and ensure compliance with signature and retention rules.

Standardize inputs

Use a master template and controlled pick lists to prevent inconsistent values across reports.

Validate arithmetic

Run automatic checks on totals and cross-reference attached schedules before routing for signature.

Designate signers

Keep an up-to-date roster of authorized certifying officials and documented delegation.

Preserve audit data

Store final PDFs with timestamps, IP logs, and signer identity metadata.

Comparing electronic vs. cryptographic signatures for form execution

Choose the signature type required by contract or agency policy; the legal distinction affects authentication strength and non-repudiation.

Criteria	Electronic Signature	Digital Signature
Definition	any electronic mark	pki-based cryptographic seal
Legal validity	yes under esign/ueta	yes, cryptographic evidence stronger
Use cases	routine approvals	high-assurance regulatory filings
Non-repudiation	audit trail dependent	certificate-based, stronger

Representative signers and preparers

Contracting Officer

A federal contracting officer or their delegate typically reviews and accepts the completed form. They verify compliance with contract terms, ensure required attachments are present, and record acceptance for the official contract file.

Prime Contractor Signer

An authorized finance or program official at the prime contractor certifies accuracy and signs. Their signature confirms the report matches company records and may trigger payment processing or reconciliation steps.

Frequently asked questions and quick solutions

Answers to common questions about completing, signing, and storing the Standard Form 294, including eSignature and legal validity concerns.

Need help? Contact support

Can I sign SF 294 electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states if the signer shows intent, consents to electronic records, attribution is established, and a reproducible record is retained.
What if a name on the form doesn't match ID?
Mismatched names can delay verification. Use the legal entity or individual name that matches government-issued ID and document the reason for any variance before signature.
Is notarization required for this form?
Not typically required unless the specific agency or contract demands it. Check contract clauses and state rules for notarization or witness requirements before executing.
How do I correct an error after signing?
Prepare an amended form, mark it as an amendment with explanation, and route it through the same approval chain. Keep both versions for audit purposes.
What authentication strength is recommended?
Email plus SMS OTP is common; use higher-assurance options (multi-factor or certificate-based) for high-risk or regulated submissions per agency policy.
How long must signed copies be retained?
Follow the longest applicable retention rule: federal financial records three years minimum (IRC §6501(a)); healthcare documents six years (45 CFR §164.530(j)); state rules may extend these periods.

Explore Templates

Mortgage Deed of Trust Clinical Affiliation Agreement Notice of Breach of Lease Alabama Notice of Breach of Lease California Notice of Breach of Lease Breeding Agreement

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now