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
Common Pitfalls
- 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).
- Missing Biometric Verification — GPS alone proves location, not identity, always pair GPS with biometric verification to confirm the approver is actually the authorized person.
- 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.
- 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.
- 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 configurationvoice-command-integration — GPS-embedded confirmationpre-task-assessment-readiness — Assess readiness before configuring GPS approvaloffline-procurement — GPS approval queuing for offline scenarios
Related Agents
Mobile Workflow Designer (DomainForge) — GPS approval workflow design and UXMobile Testing Specialist (DomainForge) — GPS accuracy and biometric testing
Example Usage
Scenario: Configure GPS approval for emergency steel rebar procurement at construction site
- Location Verification: Project Site ABC, GPS: -26.123, 28.456, geofence radius: 150m (site + laydown area)
- Authority Required: Procurement Manager + Project Manager must approve on-site
- Biometric Authentication: Fingerprint for mobile, Face ID for tablet, PIN fallback
- GPS-Embedded Signature: Proc Manager approves at 14:32 UTC, GPS: -26.1228 (accuracy 8m), fingerprint hash: SHA-256[abc123], order: WO-2026-0589
- 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.
1---2name: gps-approval-configuration3description: Configure GPS-based approval routing with location verification, geofencing, biometric authentication, GPS-embedded signatures, and audit trail for procurement approvals4---56# GPS-Enabled Approval Configuration78## Overview910Configure 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.1112**Announce at start:** "I'm using the gps-approval-configuration skill to configure location-based approval routing."1314## When to Use This Skill1516**Trigger Conditions:**17- Configuring approval workflow that requires location-verified approvals18- Setting up geofenced approval zones for project sites19- Approving high-value orders that require enhanced location verification20- Emergency procurement requiring rapid GPS-verified approval21- Field-based approvals where location context is critical2223**Prerequisites:**24- GPS-enabled device (mobile phone, tablet) with location services active25- Project site locations defined with GPS coordinates26- Geofencing boundaries configured for approval authority zones27- Biometric authentication enabled (fingerprint, face ID)28- Approval authority matrix with location-based routing configured2930## Step-by-Step Procedure3132### Step 1: Location Verification Setup3334Configure GPS coordinate requirements for approval authority:3536| Location Type | GPS Requirement | Authority Level |37|--------------|----------------|-----------------|38| Office (Procurement Department) | Head Office GPS coordinates ±50m | Procurement Officer |39| Project Site (On-Site) | Site GPS coordinates ±100m | Project Manager |40| Remote (Off-Site) | Any GPS location + additional verification | Director/Finance Manager |4142### Step 2: Geofencing Configuration4344Define geofence boundaries for approval authority zones:4546| Project | Site Name | GPS Coordinates | Geofence Radius | Authorized Approvers Within Geofence |47|---------|-----------|-----------------|-----------------|-----------------------------------|48| Project ABC | Main Site | Lat: -26.123, Lon: 28.456 | 200m radius | PM, Site Engineer, Procurement Officer |49| Project ABC | Laydown Area | Lat: -26.125, Lon: 28.458 | 100m radius | Site Engineer only |50| Project DEF | Office Site | Lat: -33.925, Lon: 18.424 | 150m radius | PM, Director, Finance |5152### Step 3: Biometric Authentication Configuration5354Configure biometric verification for GPS-embedded approvals:5556| Authentication Method | Requirement | Fallback |57|----------------------|-------------|----------|58| Fingerprint | Primary method for mobile approvals | PIN code (2FA) |59| Face ID | Accepted for tablet approvals | Pattern lock (2FA) |60| Voice Recognition | Available for voice-embedded approvals | PIN code (2FA) |6162### Step 4: GPS-Embedded Signature Protocol6364Configure GPS-embedded digital signatures:6566| Field | Value |67|-------|-------|68| Approver Name | [Name from user profile] |69| Approval Action | Approved / Rejected |70| GPS Coordinates | [Lat/Lon at time of approval] |71| GPS Accuracy | [Accuracy in meters] |72| Timestamp | [Date + time in UTC] |73| Device ID | [Device identifier] |74| Biometric Hash | [Hash of biometric verification] |75| Approval Order Value | [Order number] |7677### Step 5: Audit Trail Generation7879Configure audit trail with GPS tracking data:8081| Audit Data Point | Description |82|-----------------|-------------|83| Approval Request Sent | Time, to whom, via what channel |84| Approver Location History | GPS trail from request to approval (for journey tracking) |85| Approval Decision Made | Time, location, GPS coordinates, accuracy |86| Biometric Verification | Method used, result, timestamp |87| Order Executed | Time, action taken, by whom |8889### Step 6: Multi-Level Approval with Location Context9091Configure routing with location-based authority:9293| Order Value | Location Requirement | Authority Required | GPS Verification |94|-------------|---------------------|-------------------|-----------------|95| <$25,000 | Office or Project Site | Procurement Officer | Required |96| $25,000 – $100,000 | Project Site required | Project Manager | Required |97| >$100,000 | Project Site + Office | Finance Manager + Director | Required at both locations |98| Emergency Procurement | Project Site only | Procurement Manager + PM | Required |99100### Step 7: Emergency Approval Override101102Configure emergency approval override with GPS verification and post-approval documentation:103104| Condition | Override Action | GPS Requirement |105|-----------|-----------------|-----------------|106| Network outage at site | Emergency local approval queue | GPS coordinates recorded, synced when connection restored |107| Approver not on-site | Remote approval with 2FA | GPS coordinates + photo of site + additional PIN |108109## Success Criteria110111- [ ] Location verification configured with GPS coordinate requirements per authority level112- [ ] Geofencing boundaries defined for all project sites with correct radii113- [ ] Biometric authentication enabled for all GPS-embedded approvals114- [ ] GPS-embedded signature protocol configured with all required fields115- [ ] Audit trail generation configured with complete GPS tracking data116- [ ] Multi-level approval routing configured with location-based authority checks117- [ ] Emergency override conditions defined with GPS verification and documentation118119## Common Pitfalls1201211. **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).1222. **Missing Biometric Verification** — GPS alone proves location, not identity, always pair GPS with biometric verification to confirm the approver is actually the authorized person.1233. **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.1244. **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.1255. **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.126127## Cross-References128129### Related Skills130- `approval-routing` — GPS approval integrates with approval routing configuration131- `voice-command-integration` — GPS-embedded confirmation132- `pre-task-assessment-readiness` — Assess readiness before configuring GPS approval133- `offline-procurement` — GPS approval queuing for offline scenarios134135### Related Agents136- `Mobile Workflow Designer` (DomainForge) — GPS approval workflow design and UX137- `Mobile Testing Specialist` (DomainForge) — GPS accuracy and biometric testing138139## Example Usage140141**Scenario:** Configure GPS approval for emergency steel rebar procurement at construction site1421431. **Location Verification:** Project Site ABC, GPS: -26.123, 28.456, geofence radius: 150m (site + laydown area)1442. **Authority Required:** Procurement Manager + Project Manager must approve on-site1453. **Biometric Authentication:** Fingerprint for mobile, Face ID for tablet, PIN fallback1464. **GPS-Embedded Signature:** Proc Manager approves at 14:32 UTC, GPS: -26.1228 (accuracy 8m), fingerprint hash: SHA-256[abc123], order: WO-2026-05891475. **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.
Construct-AI-primary