Establishing secure connection…Loading editor…Preparing document…

Standard Form 299

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

APPLICATION FOR TRANSPORTATION AND UTILITY SYSTEMS AND FACILITIES ON FEDERAL LANDS

STANDARD FORM 299 (6/99)    Prescribed by DOI/USDA/DOT    OMB NO. 0596-0082

NOTE: Before completing and filing the application, the applicant should completely review this package and schedule a preapplication meeting with representatives of the agency responsible for processing the application.

1. Name and address of applicant (include zip code)

2. Name, title, and address of authorized agent if different from item 1 (include zip code)

3. Telephone (area code)

4. As applicant are you? (check one)

Individual

Corporation*

Partnership/Association*

State Government/State Agency

Local Government

Federal Agency

* If checked, complete supplemental page

5. Specify what application is for: (check one)

New authorization

Renewing existing authorization No.

Amend existing authorization No.

Assign existing authorization No.

Existing use for which no authorization has been received *

Other*

* If checked, provide details under item 7

6. If an individual, or partnership are you a citizen(s) of the United States?

Yes    No

7. Project description (describe in detail)

8. Attach a map covering area and show location of project proposal

Map attached

9. State or Local government approval:

Attached    Applied for    Not Required

10. Nonreturnable application fee:

Attached    Not required

11. Does project cross international boundary or affect international waterways?

Yes    No

12. Give statement of your technical and financial capability to construct, operate, maintain, and terminate system for which authorization is being requested.

13a. Describe other reasonable alternative routes and modes considered.

13b. Why were these alternatives not selected?

13c. Give explanation as to why it is necessary to cross Federal Lands.

14. List authorizations and pending applications filed for similar projects which may provide information to the authorizing agency.

15. Provide statement of need for project, including economic feasibility and items such as cost of proposal, estimated cost of next best alternative, and expected public benefits.

16. Describe probable effects on the population in the area, including the social and economic aspects, and the rural lifestyles.

17. Describe likely environmental effects that the proposed project will have on air quality, visual impact, water quality, noise, and land surface conditions.

18. Describe the probable effects that the proposed project will have on fish, plantlife, wildlife, marine life, threatened and endangered species, and marine mammals.

19. State whether any hazardous material will be used, produced, transported or stored on or within the right-of-way or any of the right-of-way facilities.

20. Name all the Department(s)/Agency(ies) where this application is being filed.

I HEREBY CERTIFY, That I am of legal age and authorized to do business in the State and that I have personally examined the information contained in the application and believe that the information submitted is correct to the best of my knowledge.

SUPPLEMENTAL

NOTE: The responsible agency(ies) will provide instructions. Check appropriate block.

I - PRIVATE CORPORATIONS

Articles of Incorporation

Corporation Bylaws

Certification from State showing good standing

Copy of resolution authorizing filing

Shareholder and affiliate information

Oil or gas pipeline related applications

Federal lands impacted by proposal

II - PUBLIC CORPORATIONS

Copy of law forming corporation

Proof of organization

Copy of Bylaws

Copy of resolution authorizing filing

Oil or gas pipeline information required by item I-f and I-g

III - PARTNERSHIP OR OTHER UNINCORPORATED ENTITY

Articles of association, if any

Resolution authorizing action

Name and address of each participant, partner, association, or other

Oil or gas pipeline information required by item I-f and I-g

NOTICE

Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number. The valid OMB control number for this information collection is 0596-0082.

This information is needed by the Forest Service to evaluate the requests to use National Forest System lands and manage those lands to protect natural resources, administer the use, and ensure public health and safety.

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What Standard Form 299 Is and when organizations use it

Standard Form 299 (SF-299) is a standardized U.S. government administrative form used to capture structured details for a specific agency process, such as requests, approvals, or project-level data. The form provides consistent fields for party identification, concise descriptions of the subject matter, signature and date blocks, and space for attachments or exhibits. Agencies and their vendors use SF-299 to reduce variation in submissions, speed internal routing, and maintain a uniform record for compliance and archival purposes across offices and jurisdictions.

Why Standardizing on SF-299 helps process consistency

Using a single, well-completed Standard Form 299 reduces processing delays, lowers the chance of missing information, and creates a uniform audit trail for approvals and reviews across teams and agencies.

Why Standardizing on SF-299 helps process consistency

Primary users and stakeholders for Standard Form 299

The form is typically completed and signed by administrative owners, project leads, and compliance personnel responsible for formal requests or authorizations.

  • Federal program managers and agency clerks responsible for intake and approvals
  • Contractors and vendors submitting requests, change notices, or deliverable details
  • Compliance, legal, and records teams ensuring enforceability and retention

Core parts of a professional Standard Form 299

A complete SF-299 groups standardized fields into clear sections so reviewers can find identity, scope, authority, and supporting materials quickly. Formatting and consistent field usage reduce manual follow-ups and rework.

Header / ID

Form identifier, agency code, and tracking number fields that ensure correct routing and record association across systems.

Party Information

Names, legal entity type, title, contact information, and organizational identifiers used to verify authority and reach signers or approvers.

Request Summary

A concise description of the action requested or the item reported, limited to the specified character or line count for consistent review.

Dates and Term

Effective date, expiration or review dates, and any milestone dates that determine when obligations or approvals take effect.

Authorization

Signature block, printed name, title, and date fields that record who authorized the submission and under what role.

Attachments

Exhibits, supporting documentation, or certifications referenced on the form and listed with filenames and version numbers for traceability.

Essential data elements that must appear on SF-299

Full legal name: Primary signer’s legal name
Title / authority: Signer role and signing authority
Mailing address: Street, city, state, ZIP
Effective date: MM/DD/YYYY format
Summary description: One-line request summary
Signature block: Signature and date fields

Step-by-step: completing Standard Form 299

Follow these sequential steps to prepare and submit a complete SF-299 that meets typical agency expectations.

  • 01
    Gather documents: Collect IDs, authorizations, and attachments
  • 02
    Populate header: Enter form ID and tracking information
  • 03
    Complete main fields: Fill party, description, and dates
  • 04
    Review and sign: Validate entries and apply signature

Configuring an online SF-299 workflow

When digitizing SF-299, configure field behavior and routing so reviewers receive the right version in the correct order.

Field validation Require MM/DD/YYYY for dates and exact-length TINs
Authentication Email verification or SMS code for signer identity
Conditional fields Show extra fields when certain checkboxes are selected
Routing order Sequential signer order with reminders
Accepted formats PDF, DOCX attachments accepted

Where to send or file the completed SF-299

Follow the receiving agency’s instructions for submission; routes commonly include secure portals, email to a designated inbox, or physical delivery.

  • Agency portal: Upload signed PDF to the agency online portal
  • Designated inbox: Email to the official intake address if allowed
  • Physical filing: Deliver paper copies when the agency requires originals
  • Recordkeeping: Keep a local copy and confirmation of receipt

Technical formats and authentication options for eSubmission

Choose platform settings that preserve field formatting, attachments, and an audit trail when eSubmitting SF-299.

  • File formats: PDF and DOCX supported
  • Signer authentication: Email, SMS code, or stronger methods
  • Integrations: Connectors for cloud storage and ERPs

Typical timelines and processing expectations

Processing times and deadlines for SF-299 vary by agency; prepare for internal review cycles and allow time for corrections or requests for more information.

Agency submission window:

Follow the deadline published by the receiving agency

Internal review time:

Allow 7–30 business days for standard reviews

Correction period:

Respond to requests within the timeframe specified

Retention start date:

Retention usually begins on the effective date

Expedited processing:

Confirm availability and any extra fees

Common mistakes that delay SF-299 processing

  • Missing or inconsistent names between the form and supporting ID cause verification delays and possible rejection
  • Incomplete attachment lists or omitted exhibits require re-submission and slow approvals
  • Incorrect date formats or blank effective dates create questions about when obligations begin
  • Unsigned or incorrectly signed signature blocks invalidate the form for processing

Consequences of an incorrect or incomplete SF-299

Processing delay: Submission may be returned for correction
Denial: Request can be denied for noncompliance
Administrative fines: Agencies may impose penalties under their regulations
Contract risk: Incorrect forms can affect contract milestones
Record inconsistency: Poor records complicate audits or disputes
Re-execution: May require re-signing or notarization

Typical eSignature vendor comparison for SF-299 workflows

For electronic execution and routing of SF-299, platform selection affects costs, bulk sending capability, and compliance features important for agency submissions.

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
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

Frequently asked questions about completing and submitting SF-299

Answers to common issues encountered when filling, signing, and submitting Standard Form 299.


Need help? Contact support

Explore Templates

Notice to Landlord of Refusal to Allow Sublease Notice to Vacate Form Notice to Landlord of Insufficient Notice of Change in Rental Agreement Amended Nineteenth Year Action Plan Installment Purchase and Security Agreement Installment Sale and Security Agreement
be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.