METEOR SIGN · DOCUMENT PREPARATION & TRACKING

Know what to send.
Know who you’re waiting for.

Prepare signing fields on the document, reuse a template for the next request, and separate the documents you need to sign from those waiting on other recipients.

FROM PREPARATION TO FOLLOW-UP

Keep the document and its next action together.

An offer letter, quotation, or supplier form needs the right fields, a clear recipient task, and a way to follow what remains. Explore how Meteor Sign handles those different parts of the request.

01

Prepare the fields before you send

A document needs more than a signature at the bottom.

Place signatures, initials, dates, names, text fields, checkboxes, and attachments against the relevant pages. The editor keeps page thumbnails beside the document so you can review the layout before sending.

02

Reuse the documents you send regularly

Quotations and offer letters often start from the same structure.

Preview a reusable template, then use it as the starting point for the next request. The template view includes a sales quotation with company, customer, scope, and amount placeholders.

03

See which requests still need a response

Sending a document is only the start of the follow-up.

Review sent documents and the Waiting on Others view. Each request shows recipient counts and signing progress, with a Track Signers action for the next level of detail.

04

Keep your own signing tasks in view

Some documents need your action rather than someone else’s.

Separate Needs My Signature, Waiting on Others, and completed documents. A document that needs your signature has a Review & Sign action; a completed item offers the signed PDF.

05

Find a request without opening every file

A growing document list makes individual requests harder to locate.

Search the tracking view by document title, recipient, or email, and narrow the list with a status filter before reviewing the request.

06

Review the activity record

A process owner may need to understand what happened to a request.

The reports view presents event type, envelope reference, actor, and timestamp, alongside an export action. Review the required records, retention, and export format during your walkthrough.

INSIDE THE APPLICATION

Prepare the document recipients will receive.

Review the page layout and choose the fields the request needs. This application view shows the editor with a sample document.

Meteor Sign · Document preparation

Place the fields a document needs.

The document editor shows page thumbnails and a field library for signatures, initials, dates, text, checkboxes, and attachments.

Open full-size view
Meteor Sign document editor with page thumbnails, a sample quotation, and the signature and form-field library
Meteor Sign · Sample document shown

A PRACTICAL STARTING POINT

Walk through one recurring document.

  1. 1. Identify the document

    Choose a quotation, offer letter, or other recurring request. List the fields recipients must complete.

  2. 2. Identify the people

    Decide who prepares the request, who signs, and who follows up. Review the recipient and routing requirements.

  3. 3. Identify the record

    Agree what counts as complete and which signed files, activity records, and exports need to be retained.

Questions to settle before you start.

Can we reuse our regular documents?

The template area provides reusable document previews and a Use this template action. Bring an example of your own document to review its fields and preparation requirements.

How do we see what is still waiting?

The document workspace separates requests that need your signature, those waiting on others, and completed documents. The tracking view also shows recipient counts and signing progress.

Does this establish legal or regulatory compliance?

Legal suitability, recipient verification, record retention, and regulatory requirements must be assessed for your use case. A product screen or an audit label does not establish certification.

Can it connect to our existing system?

Share the system, available API documentation, and the information that needs to move. Any connection needs a separate technical review and agreed scope.

BRING A REPRESENTATIVE DOCUMENT

Review the workflow against your own request.

Start with a non-confidential sample and the people involved. Confirm field types, recipient steps, activity records, and any integration needs.

Request a walkthrough