Can this form be signed electronically?

Yes. Electronic signatures are legally enforceable in interstate commerce under the ESIGN Act (15 U.S.C. §7001) and in most states under UETA. Ensure intent, consent, attribution, and retention are documented per ESIGN requirements.

When is notarization required?

Notarization depends on the document purpose and state rules. If the count includes an affidavit or deed, a notary may be required; check state notary statutes or the intended recipient's policy first.

How do I correct a submitted count?

Create an amended submission that clearly identifies the corrected fields, attach original and revised documents, and obtain requisite signatures. Maintain both versions in the record for audit trails.

Who may sign on behalf of a church?

Signatory authority typically follows organizational bylaws. Authorized signers are usually the pastor, board chair, or designated officer; include title and role to establish authority for verification.

How long must records be kept?

Follow applicable retention: financial records three years (IRC §6501(a)), HIPAA-related materials six years (45 CFR §164.530(j)). Consult counsel for variations by state or grant terms.

Is remote notarization acceptable?

Remote online notarization (RON) is permitted in many states but requirements vary. Verify state RON rules and identity-proofing standards before relying on remote notarization for attestations.

Electronic Signature
Templates
Project Management
Project Management New Church Count

Project Management New Church Count

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

PROJECT MANAGEMENT — NEW CHURCH COUNT

Project Identification

Project ID: Client Name:

Project Manager Project Manager Contact Project Location / Scope Area

Scope of Work

The Service Provider shall perform a comprehensive New Church Count within the agreed-upon geographic boundaries. The work includes identification, initial contact, verification of status, and compilation of a record for each new church meeting the criteria set forth below.

Detailed Scope Description Out-of-Scope Items

Deliverables and Acceptance Criteria

Deliverables shall be submitted in the formats and at the milestones described below. Acceptance of each deliverable is subject to the acceptance criteria set forth; failure to meet criteria will trigger remediation as provided in Acceptance and Remedies.

Deliverable 1 — Master Registry Acceptance Criteria Deliverable 2 — Contact Verification Log Acceptance Criteria Deliverable 3 — Executive Summary & Recommendations Acceptance Criteria

Timeline & Milestones

Project Start Date: Project End Date:

Milestone 1 — Data Collection Complete Milestone 2 — Verification Complete Milestone 3 — Final Report Delivery

Budget & Payment

Total Project Fee:

Payment Schedule Payment Terms (invoicing, late fees) Change Order Process & Rates

Responsibilities, Assumptions & Data Handling

Responsibilities are allocated as follows. The Client will provide access to any internal lists, reasonable staff cooperation, and timely approvals. The Service Provider will perform counts, verification, and reporting in accordance with professional standards and the schedule set herein.

Key Assumptions Data Retention, Privacy, and Ownership

Acceptance, Remedies & Termination

Acceptance shall be deemed upon written confirmation by the Client that deliverables meet the stated acceptance criteria. If a deliverable fails acceptance, the Service Provider will remediate at no additional cost for a single revision cycle. Either party may terminate for material breach following ten (10) days' written notice and failure to cure.

Confidentiality

Each party agrees to hold confidential all non-public information received in connection with this engagement and to use such information solely for performance under this Agreement. Confidential information does not include information that is or becomes generally available to the public other than by breach of this Agreement.

Limitation of Liability & Indemnity

Except for willful misconduct or gross negligence, neither party shall be liable to the other for consequential, incidental, or punitive damages. The Client shall indemnify and hold the Service Provider harmless from claims arising from Client-supplied data that is inaccurate or unlawfully shared.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the governing_state specified below, without regard to conflict of law principles.

Governing State

Notices

All notices required hereunder shall be in writing and delivered to the contact information specified below.

Client Contact for Notices Service Provider Contact for Notices

Miscellaneous

This Agreement, together with any attachments or change orders executed in accordance with the Change Order Process, constitutes the entire agreement between the parties with respect to the Project and supersedes prior proposals and communications.

Additional Provisions / Special Terms

Client:

By:

Date:

Service Provider:

By:

Date:

What the Project Management New Church Count Is

The Project Management New Church Count is a standardized tracking template used to record the establishment, status, and initial membership metrics for newly planted churches. It captures project identifiers, location and jurisdiction data, launch dates, leadership contacts, initial attendance counts, and supporting documentation. Designed for denominational offices, church planting teams, and grant administrators, the form organizes verification steps, signature attestations, and attachments so results can be audited, routed for approval, and archived. The template supports electronic completion and secure eSubmission to reduce manual handling and improve consistency across multiple planting projects.

Why a Standardized Count Matters

A consistent Project Management New Church Count reduces data errors, speeds approvals, and creates an auditable record for funding, reporting, and oversight. It clarifies responsibilities and preserves the factual basis for membership and attendance claims.

Who Typically Prepares and Reviews This Count

The Project Management New Church Count is completed by project leads and reviewed by denominational administrators who manage church planting programs.

Church planting coordinators and project managers responsible for gathering launch metrics and documentation.
Denominational or regional administrators who verify counts for reporting, funding, and compliance purposes.
Local pastors or board members who provide attestation and operational contact information for the new church.

Local pastors, regional directors, and grant officers commonly act as signers or approvers depending on organizational rules.

Core Components Included in a Professional Count

A complete Project Management New Church Count groups data into six functional sections so reviewers can quickly verify launch readiness and initial metrics.

Project ID

Unique identifier for the church planting project to ensure records match organizational databases and avoid duplication across reports.

Location

Street address, city, state, and ZIP plus jurisdictional notes to support local reporting and any state-specific filing or tax requirements.

Launch Dates

Planned and actual start dates, expressed as MM/DD/YYYY, used to calculate reporting periods and trigger retention or audit timelines.

Membership Counts

Initial attendance and membership metrics with a line-item breakdown (adults, children, regular attendees) for financial and program planning.

Verification

Fields for supporting documents, witness attestations, or notary statements to substantiate counts when required by policy or grant terms.

Signatures

Designated signature blocks for local and denominational signers with space for dates and role descriptions to establish authority.

Required Information at a Glance

Full Legal Name: Official party name

Church Name: Operating or doing-business-as

Address: Street, city, state

Launch Date: MM/DD/YYYY

Verification Type: Notary or witness

Attachments: Supporting PDFs

Step-by-Step: Completing the New Church Count

Follow these sequential steps to complete, verify, and submit the Project Management New Church Count with a clear audit trail.

01

Prepare documents: Gather charter, attendance logs, and identification documents.
02

Enter details: Populate project ID, location, dates, and counts.
03

Attach evidence: Upload photos, minutes, or supporting PDFs.
04

Sign and submit: Obtain required signatures and route to reviewers.

How to Configure the Online Workflow

Configure routing and authentication to match organizational approval requirements before sending the count for signatures.

Field	Configuration
Signing Order	Sequential by role
Authentication Method	Email + SMS code
Retention Setting	Archive 7 years
Notifications	Daily summary emails

Where to File and How Submission Works

Understand routing, review, and archival destinations so completed counts reach the correct organizational records and compliance stores.

Upload: Submit completed form to denominational document repository.
Route: System sends to reviewers based on signing order.
Approve: Designated approver confirms accuracy and signs.
Archive: Store signed copy in secure records for retention.

Digital Delivery and Platform Considerations

Choose file formats and integrations that match your document management and reporting systems before sending the count for signatures.

File Formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: Email, SMS, KBA

Typical Deadlines and Reporting Cadence

Set clear internal deadlines for count submission and corrections to align with funding cycles and annual reporting requirements.

Monthly Internal Reports:

Submit by the 5th business day after month end for rolling dashboards.

Quarterly Summaries:

Aggregate and submit quarterly counts within 15 days of quarter close.

Annual Certification:

Finalize and archive certified counts by December 31 each year.

Correction Window:

Allow a 60-day window for documented corrections after initial submission.

Audit Response:

Provide requested records within 30 days for internal or external audits.

Common Preparation Errors to Avoid

Entering inconsistent definitions for membership categories creates reconciliation errors and undermines comparative reporting across projects.
Using abbreviated or mismatched names between ID and the form causes verification delays and may trigger requests for corrected submissions.
Failing to attach supporting documentation, such as meeting minutes or attendance logs, increases the chance of rejection during funding or compliance review.
Skipping signer role descriptions or unsigned signature blocks results in incomplete records that cannot be accepted for official certification.

Risks and Potential Consequences

Data Inaccuracy: May affect funding eligibility

Late Submission: Delays program disbursements

Privacy Breach: Regulatory exposure possible

Invalid Signature: Document may be unenforceable

Missing Records: Audit findings and remediation

Grant Noncompliance: Funds may be reclaimed

eSignature Vendor Comparison for Submitting Counts

Below is a concise pricing and feature comparison focused on common eSignature needs for completing and submitting Project Management New Church Count 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 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

Frequently Asked Questions and Troubleshooting

Answers to common questions about validity, notarization, corrections, retention, and electronic submission for the Project Management New Church Count.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic signatures are legally enforceable in interstate commerce under the ESIGN Act (15 U.S.C. §7001) and in most states under UETA. Ensure intent, consent, attribution, and retention are documented per ESIGN requirements.
When is notarization required?
Notarization depends on the document purpose and state rules. If the count includes an affidavit or deed, a notary may be required; check state notary statutes or the intended recipient's policy first.
How do I correct a submitted count?
Create an amended submission that clearly identifies the corrected fields, attach original and revised documents, and obtain requisite signatures. Maintain both versions in the record for audit trails.
Who may sign on behalf of a church?
Signatory authority typically follows organizational bylaws. Authorized signers are usually the pastor, board chair, or designated officer; include title and role to establish authority for verification.
How long must records be kept?
Follow applicable retention: financial records three years (IRC §6501(a)), HIPAA-related materials six years (45 CFR §164.530(j)). Consult counsel for variations by state or grant terms.
Is remote notarization acceptable?
Remote online notarization (RON) is permitted in many states but requirements vary. Verify state RON rules and identity-proofing standards before relying on remote notarization for attestations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now