Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Template: electronic handover protocol with check‑in app
Mobile template for an electronic handover protocol. Required fields, photo uploads, GPS timestamps and clear integration tips for your booking system.
Quick answer
This template provides a ready mobile handover protocol for check‑in apps. It includes required fields, photo upload fields, GPS timestamps, digital signatures and integration hints for booking systems like x25pronto. Use it to reliably record condition, participants and timing of handovers.
Purpose and scope
This template documents handovers of packages, spare parts or confidential documents that are safely packed and fit in a passenger car. It is built for mobile check‑in apps on Android and iOS. The goal is clear, verifiable recording of condition and time.
Required fields (must collect)
1) Handover ID (auto or manual) 2) Booking number / reference (link to booking system) 3) Sender (name, company, address) 4) Recipient (name, company, address, authorization) 5) Driver/Courier (name, ID) 6) Handover location (free text + structured address) 7) Date and time (device time + GPS timestamp) 8) Condition (checkboxes: intact, visible damage, packaging opened) 9) Recipient signature (digital signature field) 10) Courier signature
Photo uploads and evidence
Attach at least one photo at handover. For damage, include three photos: overall view, detail of damage, damaged label/marking. Photos should store GPS metadata automatically. Limit file size (e.g. 2–5 MB) and offer optional compression.
GPS timestamp and time records
Record device time, server time and GPS coordinates with a unique timestamp. Warn users on discrepancies. Store coordinates in WGS‑84 and show a simple map preview. Photo metadata combined with GPS improves traceability.
Integration tips for booking systems
Support REST API (POST /handover), webhooks for status changes and CSV/XML export. Fields to link: handover_id ↔ booking_number, status (open/closed), timestamps, signature URL and photo URLs. Use OAuth2 or API keys for auth. Plan for retry and error callbacks.
Data protection and retention
Keep personal data only as long as needed. Encrypt photos and signatures at rest and in transit (TLS). Provide a deletion workflow after retention period. Inform recipients about purpose and retention when requesting signatures.
Frequently asked questions
Which fields are required for legally solid records?
At minimum: handover ID, booking number, sender, recipient, date/time with GPS timestamp, condition, digital signatures and at least one photo. This mix ensures traceability.
How do I connect the template to my booking system?
Expose a REST API endpoint to accept POSTs with handover data and use webhooks for real‑time updates. Agree on field names (e.g. booking_id) and authentication (OAuth2/API key).
What if there is no GPS signal?
Show a warning and allow manual address entry. Save device time and mark entries with missing GPS. If possible, request re‑capture where GPS is available.
How do customers receive the handover records?
Provide automatic PDF export by email, a download link in the customer portal, or direct CRM/booking system ingestion. PDFs should include photos, signatures and timestamps.