Can this form be signed electronically?

Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are legally valid for consent and contact-sharing forms, provided intent, consent, attribution, and record retention requirements are met.

What if an attendee withdraws consent?

Process a timely revocation; stop sharing the attendee's contact information and update distribution lists. Maintain a record of the revocation and any actions taken to demonstrate compliance.

How do I export attendee data to our CRM?

Export as CSV or JSON with standardized field names. Confirm mapping for name, email, company, and consent fields before import to prevent duplicate creation and preserve opt-in status.

Do I need special handling for health-related information?

Yes. If you collect protected health information (PHI), treat the record as a HIPAA document, execute a BAA with the service provider, and retain records per 45 CFR §164.530(j). Avoid collecting PHI unless necessary.

How long should signed forms be kept?

Retain completed records at least as long as your business needs and applicable law requires; typical minimums include 3 years for tax and business records (IRC §6501(a)) and 6 years for HIPAA-covered information.

What if the attendee data is incorrect after submission?

Allow attendees to request corrections and document changes. Maintain original and corrected records for audit purposes and note the reason for the revision in the record.

Electronic Signature
Templates
Miscellaneous
Networking Meet & Greet

Networking Meet & Greet

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

NETWORKING MEET & GREET AGREEMENT

Organizer Name: Host Name: Event Title: Event Location:

RECITALS

WHEREAS, Organizer: is engaged in organizing business and professional networking events; and

WHEREAS, Host: agrees to provide venue access, on-site coordination, or related hosting services as set forth in this Agreement; and

WHEREAS, the parties desire to set forth their respective obligations, payment terms, confidentiality obligations and the scope of the Meet & Greet to be provided on or about at the location specified above.

SCOPE OF WORK

The Host shall provide the services described below in connection with the Networking Meet & Greet. The Organizer shall provide coordination, marketing and guest management services as set forth below.

Detailed Scope (describe duties, staffing, equipment, setup and breakdown):

PAYMENT TERMS

Organizer shall pay Host the total sum of $ for the services described. Payment schedule:

Payment Schedule (include deposit and final payment milestones):

Late payment shall incur a fee of on any unpaid balance thirty (30) days after the due date, together with interest to the maximum extent permitted by law.

TERM AND TERMINATION

This Agreement commences on and terminates on unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for convenience upon written notice to the other party at least days prior to the effective termination date. Either party may terminate immediately for cause where the other party materially breaches a material obligation and fails to cure such breach within fifteen (15) days after receipt of written notice specifying the breach.

CONFIDENTIALITY

Each party may receive Confidential Information from the other party in connection with this Agreement. “Confidential Information” means non-public business, financial, guest and marketing information, event attendee lists, contact details and other proprietary materials marked or identified as confidential or that reasonably should be understood to be confidential. Each party shall: (a) hold Confidential Information in strict confidence; (b) not use Confidential Information except to perform its obligations under this Agreement; and (c) not disclose Confidential Information to any third party except to its employees, contractors or advisors who have a need to know and who are bound by confidentiality obligations at least as protective as these. Confidentiality obligations shall survive termination or expiration of this Agreement for a period of two (2) years.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to its conflicts of law principles. Venue for any dispute arising out of or relating to this Agreement shall lie exclusively in the state or federal courts located within that state.

ENTIRE AGREEMENT

This Agreement, including any exhibits or schedules expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, negotiations and communications, whether oral or written. Any amendment or modification to this Agreement must be in writing and signed by an authorized representative of each party.

ADDITIONAL PROVISIONS

Independent Contractor. Each party is an independent contractor and nothing in this Agreement shall create an employment, partnership or joint venture relationship. Each party is responsible for all taxes, withholdings and other statutory obligations arising from its performance.

Special Terms or Addenda (if any):

Organizer:

By:

Date:

Host:

By:

Date:

What the Networking Meet & Greet document is

A Networking Meet & Greet is a structured attendee record and permission form used to capture contact details, professional affiliation, connection preferences, and consent to share information among participants. It combines an event registration sheet with a brief opt-in for contact exchange, meeting notes, and follow-up tasks to ensure consistent post-event outreach and proper data handling within a professional setting.

Why use a formal Networking Meet & Greet form

Using a standardized form reduces follow-up friction, documents consent for contact sharing, and creates a reliable record for event organizers and attendees. It supports consistent outreach, mitigates privacy risk, and preserves a clear audit trail of who agreed to share their information.

Who typically completes the Networking Meet & Greet

Organizers, hosts, and attendees fill this form at in-person or virtual networking events to capture baseline contact and consent information before sharing contact lists.

The form is useful across small meetups and larger conferences; completion reduces ambiguity about who may be contacted after the event.

Essential sections to include in the form

A complete Networking Meet & Greet document groups attendee identity, consent, context, and administrative metadata so organizers can manage permissions and follow-ups consistently.

Attendee Identity

Full legal name, preferred name, and primary email address for unambiguous contact and record matching.

Organization

Company or affiliation, job title, and industry tags to help segment follow-up and introductions by relevance.

Contact Permission

Explicit consent checkbox and scope statement describing whether the attendee agrees to have their contact shared with other participants.

Connection Interests

Fields for topics of interest, requested introductions, or stated goals to prioritize post-event outreach.

Follow-Up Actions

Assigned owner, follow-up deadline, and brief notes to convert conversations into tracked next steps.

Event Metadata

Event name, date, location (or virtual link), host contact, and form version for auditability and context.

Required data elements to collect

Full Name: Legal first and last name

Email Address: Primary contact email

Company / Affiliation: Employer or organization name

Job Title: Role or position

Consent Checkbox: Explicit yes/no choice

Notes: Short meeting notes or action items

Step-by-step: completing the Networking Meet & Greet at an event

Follow these steps to ensure you capture consent and complete records consistently for each attendee.

01

Prepare Template: Load the current form version and confirm event metadata.
02

Collect Details: Ask attendees to provide name, email, company, and title.
03

Record Consent: Have attendees check opt-in for contact sharing.
04

Assign Follow-Up: Add owner and deadline for post-event outreach.

How to set up the online Meet & Greet workflow

Configure online fields and routing to match your event process and downstream systems.

Field	Configuration
Signer Roles	Organizer \| Attendee
Authentication	Email link \| SMS code
Conditional Fields	Show follow-up owner only if opt-in selected
Auto-Routing	Export to CRM or send CSV to host

Where completed forms should go

Route signed records to the organizer, archive, and any integrated systems to maintain a single source of truth.

Organizer Inbox: Primary copy for event staff
CRM Import: Map fields for contact creation
Shared Storage: Archive signed PDFs in a secure folder
Participant Copy: Provide attendee a receipt of their submission

Digital delivery and format considerations

Choose a platform that supports secure PDF export, CSV/JSON data export, and the authentication level your event requires.

File Formats: PDF for legal record; CSV or JSON for CRM ingestion
Integrations: Connectors for Salesforce, Microsoft 365, Google Workspace
Security Features: TLS/AES encryption and audit trail retention

Ensure your chosen platform meets any sector-specific compliance needs before collecting or sharing attendee contact data.

Timing and deadlines to manage around the event

Set clear cutoffs for registration, day-of check-in, and follow-up to keep communications timely and compliant.

Registration Cutoff:

Specify a deadline for sign-ups and data collection

Day-of Check-In:

Confirm identity and consent at arrival

Follow-Up Window:

Contact opt-in attendees within 48–72 hours

Data Retention Start:

Clock begins when form is completed

Consent Revocation:

Honor withdrawal requests promptly per policy

Common mistakes when preparing or using the form

Skipping an explicit consent statement and assuming permission to share contacts leads to privacy disputes.
Collecting free-text phone numbers without formatting causes import failures into CRMs and automated dialers.
Failing to version-control the template can leave organizers using outdated consent language inconsistent with policy.
Not exporting signed records to a secure archive increases the risk of data loss and audit gaps.

Key risks and potential legal exposure

CCPA Exposure: Risk of CCPA enforcement

Data Breach: Notification obligations and remediation costs

Contract Confusion: Unclear consent harms downstream obligations

CRM Errors: Incorrect imports create compliance issues

Consent Withdrawal: Must stop sharing upon valid revocation

Recordkeeping Gaps: Missing audit trail may impair defenses

Practical tips for accurate and efficient completion

Apply consistent processes and simple fields to reduce friction and protect attendee privacy while making post-event follow-up manageable.

Keep the form concise

Limit required fields to those strictly necessary for follow-up. Short forms increase completion rates and reduce data entry errors; optional fields can capture richer context without blocking submission.

Use explicit, narrow consent language

Phrase sharing permissions clearly (who will receive data, for what purpose, and how long). This reduces ambiguity, assists legal compliance, and makes revocation procedures straightforward.

Standardize formats

Require MM/DD/YYYY for dates, E.164 or consistent local format for phone numbers, and full company names. Standardization simplifies CRM mapping and reduces manual cleanup.

Archive signed records securely

Store PDFs with audit trails in encrypted storage and retain an exportable dataset for CRM ingestion and compliance review; maintain access logs for accountability.

Comparing common eSignature options for running the form

Vendor features and pricing affect cost, compliance, and scale; the table highlights starting price and common platform capabilities relevant to event forms.

	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 by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions and troubleshooting tips

Answers to common questions about consent, e-signing, data exports, and handling withdrawal of permission for Networking Meet & Greet records.

Need help? Contact support

Can this form be signed electronically?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are legally valid for consent and contact-sharing forms, provided intent, consent, attribution, and record retention requirements are met.
What if an attendee withdraws consent?
Process a timely revocation; stop sharing the attendee's contact information and update distribution lists. Maintain a record of the revocation and any actions taken to demonstrate compliance.
How do I export attendee data to our CRM?
Export as CSV or JSON with standardized field names. Confirm mapping for name, email, company, and consent fields before import to prevent duplicate creation and preserve opt-in status.
Do I need special handling for health-related information?
Yes. If you collect protected health information (PHI), treat the record as a HIPAA document, execute a BAA with the service provider, and retain records per 45 CFR §164.530(j). Avoid collecting PHI unless necessary.
How long should signed forms be kept?
Retain completed records at least as long as your business needs and applicable law requires; typical minimums include 3 years for tax and business records (IRC §6501(a)) and 6 years for HIPAA-covered information.
What if the attendee data is incorrect after submission?
Allow attendees to request corrections and document changes. Maintain original and corrected records for audit purposes and note the reason for the revision in the record.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now