Is a Pre SOG Agreement legally binding?

Yes, if it meets contract elements and e-signature validity tests: intent, consent, attribution, and record retention. Federal ESIGN (15 U.S.C. ch. 96) and state UETA rules generally treat properly executed electronic signatures as binding.

Can I use an electronic signature?

Electronic signatures are valid under ESIGN and UETA for most Pre SOG Agreements. For consumer-facing records, a consumer disclosure may be required under 15 U.S.C. §7001(c). Use an audit trail with timestamp and signer attribution.

When is notarization required?

Most Pre SOG Agreements do not require notarization. If the agreement controls transfer of real property or creates a power of attorney, state law may require notarization and witnesses; verify with state rules.

How do I correct an executed Pre SOG Agreement?

Document amendments in writing and obtain signatures from the same authorized representatives. Unilateral edits are invalid; use an amendment or replacement agreement to preserve enforceability.

How long should I keep the executed file?

Retain the executed Pre SOG Agreement for at least the active term plus applicable federal or industry retention periods (e.g., IRS 3 years, HIPAA 6 years). Consult counsel for longer holds.

What if the signer's name doesn't match bank or tax records?

Name mismatches can delay payment and trigger backup withholding for tax purposes. Correct the signature block to match legal entity names and collect supporting documentation when needed.

Pre SOG Agreement

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

Pre SOG Agreement

This Pre SOG Agreement (the Agreement) is entered into on by and between:

Service Provider Name: Service Provider Address: Client Name: Client Address:

Recitals

WHEREAS, Service Provider is engaged to perform preliminary assessment, planning and preparatory activities in advance of a formal Statement of Goals (SOG) or Statement of Work that the parties anticipate executing; and

WHEREAS, Client desires Service Provider to commence specified preliminary services on the terms set forth in this Agreement so that the parties may later define a comprehensive SOG; and

WHEREAS, the parties intend that this Agreement govern the performance, payment, confidentiality and early termination of those preliminary services until a formal SOG is executed.

Scope of Work

Service Provider shall perform the preliminary services described below. The parties acknowledge that the Scope below is preliminary and may be incorporated into or superseded by a later SOG.

Preliminary Scope of Work (describe in detail):

Payment Terms

In consideration for the preliminary services, Client shall pay Service Provider as follows.

Total Estimated Fee: Payment Schedule / Milestones:

Unless otherwise specified in the payment schedule, invoices submitted by Service Provider are due and payable within days of receipt. Late payments shall incur a late fee equal to per month on the outstanding balance, or the maximum permitted by law if lower. Client is responsible for reasonable collection costs, including attorney fees.

Term and Termination

This Agreement commences on the Start Date below and will continue until the earlier of the End Date below, mutual execution of a formal SOG, or termination as provided herein.

Start Date: End Date:

Either party may terminate this Agreement for convenience by providing the other party with written notice no fewer than days prior to the effective termination date. Termination for material breach by either party shall be effective upon written notice if the breach is not cured within 10 days of receipt of notice.

Confidentiality

Each party (Recipient) acknowledges that it may receive confidential information from the other party (Discloser). Recipient shall: (a) hold such information in strict confidence; (b) use such information solely for purposes of performing its obligations under this Agreement and preparing a formal SOG; and (c) not disclose such information to any third party except to employees, contractors, or advisors who have a need to know and who are bound by confidentiality obligations no less restrictive than those herein.

Confidentiality obligations shall survive termination of this Agreement for a period of three (3) years, except that trade secrets shall remain protected for so long as they qualify as trade secrets under applicable law.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state specified below, without regard to its conflict of law principles. The parties submit to the exclusive jurisdiction of the courts located within that state for any dispute arising out of or relating to this Agreement.

Governing State:

Entire Agreement; Miscellaneous

This Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral, regarding the preliminary services and preparation of a formal SOG. Any modification or waiver must be in writing and signed by authorized representatives of both parties.

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign its rights or delegate its obligations under this Agreement without the prior written consent of the other party, except to an affiliated entity or in connection with a merger or sale of substantially all assets provided that the assignee assumes the obligations of the assignor in writing.

Acknowledgments

Each signatory below represents and warrants that they have the authority to bind the party on whose behalf they sign, and that they have read and understood this Agreement.

Service Provider:

Printed Name:

By:

Date:

Client:

Printed Name:

By:

Date:

What a Pre SOG Agreement Is and when it is used

A Pre SOG Agreement is a short-form, preliminary contract used to capture core objectives, responsibilities, and basic commercial terms before a full Statement of Work (SOW) or Scope of Goods (SOG) is drafted. It establishes the parties, high-level goals, delivery windows, payment structure, and any interim obligations while parties finalize a more detailed SOW. Organizations use a Pre SOG Agreement to reduce ambiguity, preserve negotiating positions, and allow limited work or planning to begin under agreed conditions without committing to full contract language.

Why a clear Pre SOG Agreement matters for projects

A concise Pre SOG Agreement reduces misalignment early, preserves evidence of intent, and creates a predictable handoff to the later SOW. When signed electronically, it is enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and most state UETA statutes, provided intent, consent, attribution, and record retention are satisfied.

Teams and roles that commonly prepare or sign a Pre SOG Agreement

The Pre SOG Agreement sits at the intersection of operations, procurement, and legal review; multiple teams typically collaborate on it.

Procurement and Sourcing Teams: Coordinate vendor selection, preliminary commercial terms, and initial pricing confirmation prior to full contracting.
Project Managers and Program Leads: Define measurable goals, timelines, and acceptance criteria for the later SOW and track interim milestones.
Legal Counsel / Contract Managers: Review liability, IP, and termination language to limit exposure during the pre-contract phase.

Final approval often requires a designated authorized signer and a project lead to manage the transition to the full SOW.

Who can sign and why their role matters

Authorized Signer

An individual with corporate signing authority (title or board resolution) who binds the organization. The signer’s authority should be documented to avoid challenges to enforceability; absent that, counter-parties may require additional verification or an attorney opinion.

Project Manager

Operational owner responsible for delivery and acceptance criteria. Their endorsement of schedules and milestones ensures the Pre SOG Agreement aligns with project plans and reduces later disputes over scope changes.

Essential fields to include in every Pre SOG Agreement

Parties' Legal Names: Full registered entity names

Effective Date: MM/DD/YYYY format

High-Level Goals: Concise deliverable summary

Delivery Window: Start and end dates

Consideration: Price or payment terms

Signature Blocks: Signer name, title, date

Core components of a professional Pre SOG Agreement

A well-structured Pre SOG Agreement balances brevity with legal clarity so that interim work can proceed without unintended commitments.

Parties

Identify the legal entities (not trade names), their addresses, and the authorized representatives who can accept or amend the Pre SOG Agreement.

Purpose

A short paragraph describing the objectives or goals that the parties agree the supplier will pursue before a full SOW is executed.

Scope Summary

High-level list of deliverables or services permitted during the pre-SOW period, including any explicit exclusions to limit ambiguity.

Payment Terms

Amount, invoicing cadence, any deposit or milestone amounts, and whether payments are refundable if SOW negotiations fail.

Confidentiality & IP

Interim NDA language for shared materials and an express statement on ownership of pre-SOG work product or background IP.

Termination & Transition

Procedures for ending the pre-SOG arrangement, notice periods, and steps to transition accepted interim work into the later SOW.

Step-by-step: preparing and signing a Pre SOG Agreement

Follow a consistent sequence to reduce revision cycles and speed approval — prepare, review, sign, and store with an audit trail.

01

Draft: Populate core fields and attach any reference exhibits.
02

Internal Review: Legal and procurement review for liability and commercial terms.
03

Client Review: Share draft with counterpart and capture redlines.
04

Execution: Collect signatures and record execution date and audit trail.

Configuring an online Pre SOG workflow

An online workflow ensures consistent routing, required fields, and signer authentication before signatures are collected.

Field	Configuration
Template Upload	PDF or DOCX template with mapped fields
Signer Roles	Assign roles and signing order
Authentication	Email link, SMS code, or advanced methods
Conditional Fields	Show fields based on prior answers

Where to send the executed Pre SOG Agreement

Decide distribution points in advance to ensure compliance, accounting, and project teams have access to the executed record.

Internal Approver: Send executed copy to procurement and legal repositories
External Counterparty: Provide signed PDF with audit certificate
Contract Repository: Store in centralized contract management system
Project Platform: Attach to project plan or ticketing system

Technical considerations for eSigning and eSubmission

Ensure your platform supports required file formats, signer authentication, and audit trails before inviting signatures.

File Formats: PDF, DOCX, and editable templates
Integrations: Salesforce, NetSuite, Microsoft 365
Authentication: Email, SMS, or KBA options

Typical deadlines and timing expectations

Establish clear deadlines for negotiation, approval, and transition to a full SOW to avoid work without an agreed scope.

Negotiation Window:

7–21 days depending on project complexity

Effective Date:

Date specified in the Effective Date field

SOW Execution Target:

Usually 30–90 days after Pre SOG signature

Interim Deliverables Start:

As agreed — tie to milestone dates

Amendment Notice:

Typically 10–30 days written notice

Key milestones from draft to SOW handoff

A sequential milestone view helps coordinate reviews and signals when the agreement converts into the full SOW.

01

Draft Issued

Sender circulates initial Pre SOG draft to stakeholders for comment.

02

Internal Approvals

Legal, finance, and PM teams sign off on commercial and compliance terms.

03

Counterparty Review

Counterparty provides redlines and any required attachments or exhibits.

04

Execution & Archive

Collect signatures, timestamp execution, and store final file with metadata.

Common mistakes when preparing a Pre SOG Agreement

Using informal or trade names instead of registered legal entity names, which can create payment and enforceability issues.
Leaving acceptance criteria vague; without measurable deliverables disputes often arise when converting to a full SOW.
Failing to document an authorized signer’s corporate power, causing counterparties to question authority and delay execution.
Omitting confidentiality or IP clauses when sharing proprietary material, increasing the risk of misused or unprotected information.

Top risks and potential consequences of an incorrect Pre SOG Agreement

Unenforceable Terms: Vague obligations may be void or hard to enforce

Payment Disputes: Ambiguous consideration triggers late payments

Regulatory Exposure: Missing disclosures may violate industry rules

Tax Withholding: Incorrect payee info can trigger backup withholding

Delay Costs: Work without clear scope increases overruns

Data Breach Risk: Insufficient confidentiality increases liability

Representative examples of Pre SOG usage in practice

Real customers have used short-form pre-agreements to accelerate onboarding, preserve rights, and start initial tasks while the full SOW is finalized.

Optica Ventures LLC

Brian Fitzgibbons found streamlined templates reduced confusion in early conversations.

The shorter agreement clarified responsibilities quickly.
By using a concise pre-agreement they accelerated client onboarding and reduced back-and-forth, enabling early deliverables while final commercial terms were negotiated.

Martin Properties

Tim Martin used a pre-SOG to start inspections and basic site work.

Early signature enabled practical work to begin.
The pre-agreement documented acceptance criteria and payment triggers so the team could commence time-sensitive tasks without waiting for a full SOW.

Frequently asked questions about Pre SOG Agreements

Answers to common legal, signature, and retention questions for Pre SOG Agreements used in U.S. transactions.

Need help? Contact support

Is a Pre SOG Agreement legally binding?
Yes, if it meets contract elements and e-signature validity tests: intent, consent, attribution, and record retention. Federal ESIGN (15 U.S.C. ch. 96) and state UETA rules generally treat properly executed electronic signatures as binding.
Can I use an electronic signature?
Electronic signatures are valid under ESIGN and UETA for most Pre SOG Agreements. For consumer-facing records, a consumer disclosure may be required under 15 U.S.C. §7001(c). Use an audit trail with timestamp and signer attribution.
When is notarization required?
Most Pre SOG Agreements do not require notarization. If the agreement controls transfer of real property or creates a power of attorney, state law may require notarization and witnesses; verify with state rules.
How do I correct an executed Pre SOG Agreement?
Document amendments in writing and obtain signatures from the same authorized representatives. Unilateral edits are invalid; use an amendment or replacement agreement to preserve enforceability.
How long should I keep the executed file?
Retain the executed Pre SOG Agreement for at least the active term plus applicable federal or industry retention periods (e.g., IRS 3 years, HIPAA 6 years). Consult counsel for longer holds.
What if the signer's name doesn't match bank or tax records?
Name mismatches can delay payment and trigger backup withholding for tax purposes. Correct the signature block to match legal entity names and collect supporting documentation when needed.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now