# Gps Approval Configuration

> Configure GPS-based approval routing with location verification, geofencing, biometric authentication, GPS-embedded signatures, and audit trail for procurement approvals

- Skill: `construct-ai-primary/gps-approval-configuration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/gps-approval-configuration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/gps-approval-configuration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/construct-ai-primary/gps-approval-configuration

---


# GPS-Enabled Approval Configuration

## Overview

Configure location-based approval routing using GPS verification, geofencing for approval authority determination, biometric authentication, GPS-embedded signatures, and comprehensive audit trail with GPS tracking data. Ensures approvers can only approve orders when physically present at the correct location.

**Announce at start:** "I'm using the gps-approval-configuration skill to configure location-based approval routing."

## When to Use This Skill

**Trigger Conditions:**
- Configuring approval workflow that requires location-verified approvals
- Setting up geofenced approval zones for project sites
- Approving high-value orders that require enhanced location verification
- Emergency procurement requiring rapid GPS-verified approval
- Field-based approvals where location context is critical

**Prerequisites:**
- GPS-enabled device (mobile phone, tablet) with location services active
- Project site locations defined with GPS coordinates
- Geofencing boundaries configured for approval authority zones
- Biometric authentication enabled (fingerprint, face ID)
- Approval authority matrix with location-based routing configured

## Step-by-Step Procedure

### Step 1: Location Verification Setup

Configure GPS coordinate requirements for approval authority:

| Location Type | GPS Requirement | Authority Level |
|--------------|----------------|-----------------|
| Office (Procurement Department) | Head Office GPS coordinates ±50m | Procurement Officer |
| Project Site (On-Site) | Site GPS coordinates ±100m | Project Manager |
| Remote (Off-Site) | Any GPS location + additional verification | Director/Finance Manager |

### Step 2: Geofencing Configuration

Define geofence boundaries for approval authority zones:

| Project | Site Name | GPS Coordinates | Geofence Radius | Authorized Approvers Within Geofence |
|---------|-----------|-----------------|-----------------|-----------------------------------|
| Project ABC | Main Site | Lat: -26.123, Lon: 28.456 | 200m radius | PM, Site Engineer, Procurement Officer |
| Project ABC | Laydown Area | Lat: -26.125, Lon: 28.458 | 100m radius | Site Engineer only |
| Project DEF | Office Site | Lat: -33.925, Lon: 18.424 | 150m radius | PM, Director, Finance |

### Step 3: Biometric Authentication Configuration

Configure biometric verification for GPS-embedded approvals:

| Authentication Method | Requirement | Fallback |
|----------------------|-------------|----------|
| Fingerprint | Primary method for mobile approvals | PIN code (2FA) |
| Face ID | Accepted for tablet approvals | Pattern lock (2FA) |
| Voice Recognition | Available for voice-embedded approvals | PIN code (2FA) |

### Step 4: GPS-Embedded Signature Protocol

Configure GPS-embedded digital signatures:

| Field | Value |
|-------|-------|
| Approver Name | [Name from user profile] |
| Approval Action | Approved / Rejected |
| GPS Coordinates | [Lat/Lon at time of approval] |
| GPS Accuracy | [Accuracy in meters] |
| Timestamp | [Date + time in UTC] |
| Device ID | [Device identifier] |
| Biometric Hash | [Hash of biometric verification] |
| Approval Order Value | [Order number] |

### Step 5: Audit Trail Generation

Configure audit trail with GPS tracking data:

| Audit Data Point | Description |
|-----------------|-------------|
| Approval Request Sent | Time, to whom, via what channel |
| Approver Location History | GPS trail from request to approval (for journey tracking) |
| Approval Decision Made | Time, location, GPS coordinates, accuracy |
| Biometric Verification | Method used, result, timestamp |
| Order Executed | Time, action taken, by whom |

### Step 6: Multi-Level Approval with Location Context

Configure routing with location-based authority:

| Order Value | Location Requirement | Authority Required | GPS Verification |
|-------------|---------------------|-------------------|-----------------|
| <$25,000 | Office or Project Site | Procurement Officer | Required |
| $25,000 – $100,000 | Project Site required | Project Manager | Required |
| >$100,000 | Project Site + Office | Finance Manager + Director | Required at both locations |
| Emergency Procurement | Project Site only | Procurement Manager + PM | Required |

### Step 7: Emergency Approval Override

Configure emergency approval override with GPS verification and post-approval documentation:

| Condition | Override Action | GPS Requirement |
|-----------|-----------------|-----------------|
| Network outage at site | Emergency local approval queue | GPS coordinates recorded, synced when connection restored |
| Approver not on-site | Remote approval with 2FA | GPS coordinates + photo of site + additional PIN |

## Success Criteria

- [ ] Location verification configured with GPS coordinate requirements per authority level
- [ ] Geofencing boundaries defined for all project sites with correct radii
- [ ] Biometric authentication enabled for all GPS-embedded approvals
- [ ] GPS-embedded signature protocol configured with all required fields
- [ ] Audit trail generation configured with complete GPS tracking data
- [ ] Multi-level approval routing configured with location-based authority checks
- [ ] Emergency override conditions defined with GPS verification and documentation

## Common Pitfalls

1. **Geofence Too Large** — If geofence radius is too large (e.g., 5km), unauthorized approvers outside the actual site can approve. Keep geofences tight to actual site boundaries (100-200m).
2. **Missing Biometric Verification** — GPS alone proves location, not identity, always pair GPS with biometric verification to confirm the approver is actually the authorized person.
3. **Privacy Violations** — GPS tracking of approver location history must comply with privacy laws and company policies. Inform approvers that their location is tracked during approval workflows.
4. **No Fallback for Edge Cases** — Approvals where the device has no GPS signal must have a fallback procedure (PIN + photo) — never block emergency approvals due to GPS failure.
5. **Audit Trail Incomplete** — If GPS coordinates or approval timestamp are missing, the audit trail will not meet compliance requirements. Validate all GPS fields are captured before signature is recorded.

## Cross-References

### Related Skills
- `approval-routing` — GPS approval integrates with approval routing configuration
- `voice-command-integration` — GPS-embedded confirmation
- `pre-task-assessment-readiness` — Assess readiness before configuring GPS approval
- `offline-procurement` — GPS approval queuing for offline scenarios

### Related Agents
- `Mobile Workflow Designer` (DomainForge) — GPS approval workflow design and UX
- `Mobile Testing Specialist` (DomainForge) — GPS accuracy and biometric testing

## Example Usage

**Scenario:** Configure GPS approval for emergency steel rebar procurement at construction site

1. **Location Verification:** Project Site ABC, GPS: -26.123, 28.456, geofence radius: 150m (site + laydown area)
2. **Authority Required:** Procurement Manager + Project Manager must approve on-site
3. **Biometric Authentication:** Fingerprint for mobile, Face ID for tablet, PIN fallback
4. **GPS-Embedded Signature:** Proc Manager approves at 14:32 UTC, GPS: -26.1228 (accuracy 8m), fingerprint hash: SHA-256[abc123], order: WO-2026-0589
5. **Audit Trail:** GPS location, fingerprint hash, device ID, order ID, action, timestamp. Approval recorded for compliance. Emergency documented, order created. Post-approval notification sent to Finance and Director.