Download signNow app
4.7 / 5 rating on

Grantor, In Compliance With Section 13 Of The Lien Law, Covenants That The Grantor Will Form

Use a GRANTOR, In Compliance With Section 13 Of The Lien Law, Covenants That The Grantor Will template to make your document workflow more streamlined.

What this grantor covenant does

This grantor covenant records a property owner’s commitment under Section 13 of the Lien Law. In practical terms, the grantor signs a written promise that can be retained with the related property and lien records. The form should identify the grantor, describe the relevant property or project, state the covenant language accurately, and capture the required signature. SignNow can upload the document, detect fillable fields, route it to the grantor, and store the completed copy with an audit trail. State filing, notarization, and witnessing requirements must be checked before execution.

Legal standing and practical value

A properly executed grantor covenant creates a retrievable record of the grantor’s stated commitment, while its evidentiary value depends on accurate content, signer intent, attribution, and required formalities. ESIGN and UETA support covered electronic transactions, but state lien, property, recording, notarization, and document-exclusion rules still control where applicable.

Why teams look for DocuSign alternatives

Business types using grantor covenants

The form is most useful where property obligations require clear grantor commitments, signatures, and retrievable execution records.

  • Small construction contractors can use the covenant to document grantor commitments, collect signatures, and preserve an executed copy for project records.
  • Real estate law firms can prepare property-related covenant packages, route them to grantors, and maintain an auditable signing history for client files.
  • Commercial property enterprises can standardize recurring grantor forms, assign signing responsibilities, and connect completed records to controlled document repositories.

These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.

Features that support this covenant

SignNow provides a document workflow for preparing, routing, signing, and retaining this grantor covenant while preserving execution evidence.

Field preparation

Upload the covenant and review detected fields before assigning the grantor’s signature, date, and property-related information.

Signer routing

Route the exact covenant to the grantor with defined signing responsibilities and a controlled recipient address.

Audit evidence

Capture timestamps, identity information, and document history that help explain how the covenant was executed.

Record storage

Keep the signed covenant and completion record together for later property, lien, or contract review.

Signer authentication

Use SMS authentication when the transaction requires stronger evidence that the intended grantor accessed the request.

System connections

Connect completed covenant records with supported systems such as Box, Google Drive, NetSuite, or Procore.

How to complete the covenant

Use this sequence to prepare the exact covenant, route it to the grantor, and preserve the completed execution record.

  • Upload covenant:

    Upload the current grantor covenant to signNow.
  • Check fields:

    Review detected fields and add missing fields.
  • Assign signer:

    Assign the grantor and set signing order.
  • Send request:

    Send the covenant for electronic signature.
  • Store evidence:

    Review the signed copy and audit trail.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

Recommended grantor covenant setup

Use a controlled signing workflow that preserves the covenant, signer identity, and execution history with the property file.

SettingRecommendation
Authentication methodEmail verification with SMS OTP
Signature typeTyped or drawn electronic signature
Audit trailCapture timestamps, IP address, and actions
Document retentionRetain through the applicable lien period
EncryptionTLS 1.2/1.3 and AES-256 encryption

How the covenant audit trail works

The audit trail documents execution evidence separately from the form’s substantive property and grantor information.

01

Authenticate signer:

The audit trail records the grantor’s authentication event and assigned signer identity.
02

Capture timestamp:

Each signing action receives a recorded date and time.
03

Record document history:

The completed covenant receives document history and integrity evidence.
04

Seal completion:

The final record preserves the executed document and completion certificate.
05

Review events:

The sender can review signing events associated with the covenant.
06

Export evidence:

Authorized users can retrieve or export the audit trail.

Security controls for signed covenants

Transport encryption:

TLS 1.2/1.3 protects data in transit

Stored encryption:

AES-256 protects stored document data

Control assurance:

SOC 2 Type II certification supports control review

Security certification:

ISO 27001 certification supports information security

Signature framework:

ESIGN and UETA compliance supports electronic signatures

Execution evidence:

Audit trails preserve timestamps and document history

Connect covenant records to business systems

SignNow integrations can move completed grantor covenants into the systems that manage property, construction, legal, and document records.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Platform requirements for signing

The grantor covenant can be prepared in a desktop browser and reviewed through signNow mobile apps on iOS or Android. Use an up-to-date version of Chrome, Firefox, Safari, or Edge with an internet connection and TLS-enabled access.

  • Browsers Chrome, Firefox, Safari, and Edge
  • Desktop systems Windows and macOS desktop access
  • Mobile apps iOS and Android signNow apps

Organizations handling property and lien records should use managed Windows, macOS, iOS, or Android devices, controlled user provisioning, and role-based access. Teams connecting signNow to document repositories or project systems should verify API, SSO, certificate, and retention requirements before deployment.

Best practices for grantor covenants

Accuracy, signer identity, and execution evidence matter because this covenant may be reviewed alongside lien or property records.

Confirm state execution requirements

Confirm the governing state rule before sending the covenant. Check whether the grantor’s signature requires notarization, witnesses, recording, or a specific acknowledgment, because Section 13 procedures and property-record requirements can vary by jurisdiction and transaction type.

Match property information carefully

Use the exact property and project information appearing in the related lien materials. Compare names, legal descriptions, parcel identifiers, and project references before routing the covenant, then have the grantor review every field before signing.

Control the signing sequence

Route the document in a defined signer order and require the grantor to complete every assigned field. Use SMS authentication when identity risk warrants it, and keep the final signed PDF and completion certificate together.

Archive execution evidence securely

Export the audit trail with the executed covenant and store both records under the applicable retention policy. Restrict access to authorized legal, construction, or property-record personnel and preserve an unaltered archival copy.

Processing stages for the covenant

Processing depends on document accuracy, signer availability, and any state-required notarization, witnessing, recording, or review.

01

Prepare the document

Upload the current covenant and verify grantor and property fields before routing.
02

Deliver to signer

Send the covenant to the grantor by email or controlled signing link.
03

Complete signer review

The grantor reviews assigned fields and completes the required signature.
04

Archive completed record

Store the signed covenant with its audit trail and property records.

Pitfalls when preparing the covenant

  • Entering an incomplete legal property description can make the covenant difficult to match to the correct project or lien record.
  • Sending the grantor an outdated covenant template can create inconsistent language and require a replacement execution.
  • Failing to confirm required witnesses or notarization may leave the signed covenant insufficient for the applicable state procedure.
  • Sharing the completed document through uncontrolled channels can expose grantor identity and property information.

Grantor covenant troubleshooting

These answers address field accuracy, signer access, electronic-signature evidence, plan selection, and state execution requirements for this covenant.

Upload the covenant as a PDF or supported document file, then review signNow’s detected fields manually. Confirm that the grantor’s name, property description, covenant language, and signature placement match the source document before sending it.

Open the recipient settings and verify the grantor’s email address, signing order, and assigned fields. If the grantor cannot access the request, resend it or provide a controlled signing link after confirming the recipient’s identity.

Business includes legally binding eSignatures, templates, audit trails, and mobile apps at $8 per user per month with annual billing. Business Premium adds bulk send and kiosk mode at $15 per user per month annually.

SignNow records signing activity, timestamps, and document history in an audit trail. Preserve the completed covenant and exported audit evidence together, then apply the retention period required for the related property or lien records.

ESIGN and UETA generally recognize electronic signatures for covered transactions when intent, consent, attribution, and record retention requirements are satisfied. They do not override state-specific notarization, witnessing, recording, or document exclusions.

If the covenant requires notarization, use a signNow workflow only if the selected notarization method and jurisdiction satisfy the applicable state rule. Confirm requirements with the relevant state authority before treating the electronic record as complete.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.