Conditional clause
Explicit language stating which obligations are contingent, the precise triggering event, and whether any part remains binding despite the contingency.
Marking an agreement or clause as 'Subject To' signals conditional intent, limits immediate obligations, and helps allocate risk while negotiations continue. In the U.S., electronic execution of conditional agreements is permitted under ESIGN (15 U.S.C. §7001) and UETA when other legal exceptions do not apply.
Organizations use Subject To Agreements when they need a short-form record of agreed points without committing to full performance or final language.
Use the document when you intend to preserve negotiated terms but require specific events or approvals before creating a fully binding contract.
Sellers, property owners, or contract counterparties use the form to record conditional consents, reserve rights, and set performance triggers. The profile usually includes contact details, corporate capacity, and any necessary corporate resolution evidence showing signing authority.
Buyers, acquirers, or lenders use the document to document conditions precedent (financing, approvals). They typically attach evidence of financing, proof of funds, or purchaser authority to avoid later challenges to enforceability.
Explicit language stating which obligations are contingent, the precise triggering event, and whether any part remains binding despite the contingency.
Specific conditions (financing approval, inspection, title clearance, regulatory consent) with measurable standards and responsible parties.
Clear timeframes for satisfactions, extensions, and defaults so parties know when contingencies lapse or convert to binding obligations.
A short section identifying which sections (e.g., confidentiality, exclusivity, expense allocation) remain binding while others are conditional.
Capacity lines for signers, corporate officer titles, and date fields; include witness or notary lines if required by jurisdiction or document type.
Reference exhibits such as term sheets, financing commitments, inspection reports, or approval checklists that define the contingency evidence.
| Field | Configuration |
|---|---|
| Signature order | Set signers in sequential or parallel order per negotiation needs. |
| Conditional fields | Use conditional visibility for contingency evidence attachments. |
| Authentication | Require email plus SMS or KBA for high-assurance signers when needed. |
| Audit trail | Enable full event logging for timestamps and IP capture. |
Decide on signer authentication level, file formats, and retention location before sending the Subject To Agreement.
Ensure the platform supports audit trails, secure storage, and any required compliance frameworks such as HIPAA or 21 CFR Part 11 when applicable.
Enter the specific date by which financing must be committed; ties to lender conditions.
Define the inspection completion date and defect cure period.
Set a target date for title objections to be raised or cured.
Specify the date by which governmental approvals must be received.
State the date after which unspecified contingencies terminate by default.
| 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 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 |