Header Metadata
Project name, map ID, creator, date, version, and contact information to link the file to contract and delivery records.
A consistent template reduces ambiguity, speeds approvals, and creates an auditable record that documents technical specifications and acceptance terms for map outputs.
Teams and individuals who prepare, review, or accept geospatial deliverables commonly use this template.
Use the template to reduce rework, clarify acceptance criteria, and create a retrievable record for audit or contract compliance.
A project manager signs to confirm scope and delivery milestones. They verify that map padding, coordinate reference systems, and file formats match contractual requirements, and they record acceptance dates for project tracking and invoicing.
A GIS lead signs to attest technical compliance of the map deliverable. They confirm layer visibility, metadata accuracy, padding measurements, and that exported files conform to the agreed projection and scale requirements.
Project name, map ID, creator, date, version, and contact information to link the file to contract and delivery records.
Document the spatial reference system, datum, and projection to ensure recipients interpret geometry correctly.
Numeric padding or buffer values with units, tolerances, and whether padding applies to extent, layers, or export margins.
List included layers, visibility rules, symbology notes, and any layer-level exclusions or anonymization steps.
Explicit tests or checks (extent verification, coordinate accuracy, file integrity) required before sign-off.
Role-based signature blocks, printed names, titles, and date fields to capture approval and attribution.
| Field | Configuration |
|---|---|
| Required Fields | Mark metadata, padding, and signature fields as required. |
| Routing Order | Set signer sequence: creator → GIS lead → client. |
| Authentication | Use email plus optional SMS code for signer verification. |
| Attachments | Allow upload of GIS exports and checksum files. |
Ensure the chosen platform supports common geospatial file types and secure eSignature workflows before sharing templates.
Submit map package within agreed delivery window.
Allow 3–5 business days for GIS lead verification.
Allow up to 7 calendar days for client acceptance.
Plan 2–4 business days for minor corrections.
Client must sign within the agreed acceptance window.
Creator packages map files and completes template fields.
GIS lead runs coordinate and padding checks.
Client reviews visual and technical criteria.
Store signed files and checksums per retention policy.
| 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 vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A venture GIS team used the template for repeated site deliverables to clients
A property manager standardized lease-area maps and buffers using the template