Try the Waypoint field-team demo
Explore source dates, a travel review and voluntary check-in records using demonstration data.
A practical buying guide
Waypoint presents sourced country intelligence alongside travel assessments, voluntary staff check-ins, vehicle reports and incident records. Start with the source date and your organisation's check-in and escalation procedures.
Bring this brief to your demonstration
Evaluate Waypoint with one fictional journey, one field report and one person responsible for reviewing it. A useful trial shows both the information received and what the coordinator still needs to establish.
| Requirement | Demo exercise | Evidence to keep |
|---|---|---|
| Intelligence source and coverage | Open the source behind a country or incident item and compare its published date and location with the proposed journey. | Keep the original source reference and the unanswered coverage question. A country-level item does not establish conditions along a specific route. |
| Voluntary check-in | Inspect a supplied report, its time and its reported location. Explain to the reviewing coordinator what is known and what is not current. | Record the last-report time and reviewer. Treat the location as a report, not proof of continuous tracking or the person's present position. |
| Weak-connectivity handover | Ask to demonstrate the supported offline field-report workflow, reconnect and compare the locally saved report with the received record. | Distinguish observation, saving and delivery times. Confirm which workflows support offline use and what remains unavailable without a connection. |
| Missing and unread reports | Prepare one missing report and one received but unread report, then ask the coordinator to explain the next action for each. | Name the responsible role and the organisation's contact procedure. Confirm any automated alert separately; a missing report does not establish an emergency. |
| Regional team handover | Review the same fictional report from the field team's and head office's time zones, including a date boundary and the required working languages. | For teams in Africa, MENA or South America reporting to a USA or UK office, record the actual language, time-zone and connectivity checks completed. |
| Service and hardware boundaries | List any requirement for satellite communications, SMS fallback, continuous location tracking or a staffed response service separately. | Confirm these requirements and providers in writing. Do not infer them from the presence of a map, an intelligence feed or a voluntary check-in. |
Choose a pilot only when the team understands source freshness, report delivery, privacy responsibilities and who follows up. Waypoint supports operational review; it does not guarantee safety or replace the organisation's travel approval and response arrangements.
A field coordinator needs to review travel information while understanding when the team last reported.
Worked planning example · fictional data
Illustrative coordination review: your organisation expects ten reports by its agreed time. Seven have arrived and one of those has not yet been reviewed.
The follow-up queue contains three missing reports plus one unread report: four different tasks.
Use last-report times and your organisation's agreed contact procedure. A missing report is not proof of danger, and a received location is not a live position.
A check-in is a supplied report, not continuous tracking. Intelligence and assessments cannot guarantee safety or replace official advice and organisational judgement.
Check the time of the last voluntary report, the location supplied and the person responsible for following up. Test a late report against your team's contact procedure using demonstration records. Waypoint check-ins describe information supplied by staff; they do not establish continuous location tracking or that a person remains at the reported place.
Link to this answerOpen the original source and compare its publication time, location and coverage with the proposed journey. Keep a recent incident separate from a general country assessment, and record gaps that need a human decision. Waypoint supports sourced intelligence and travel review; your organisation still needs its own approval, communication and escalation process.
Link to this answerSaved describes a record retained on the field device; delivered means it reached the destination workspace. In a connectivity test, compare the queued report with the received version after reconnecting. Record the delivery time separately from the observation time. Agree who follows up on an undelivered report before relying on the workflow.
Link to this answerShow the reporting time with an explicit time zone and compare it with the team’s agreed reporting window. Avoid treating the manager’s local clock as the field team’s clock. Test a report sent around midnight or a date boundary, then confirm how Waypoint presents the time in the operational view and export.
Link to this answerKeep the source, publication date and geographic scope beside the proposed journey. Record who reviewed the information and which questions remain unresolved. An alert may justify further investigation without establishing the conditions of a particular route. The organisation’s authorised manager makes the travel decision using its own current procedures.
Link to this answerUse the languages the actual team reads: for example Arabic in a MENA pilot, French or Afrikaans where relevant in Africa, and Spanish or Portuguese in South America. Review a complete field-report handover, including names, dates and numeric fields. An available interface translation should be checked against the team’s vocabulary and training needs.
Link to this answerSet reporting expectations, the contact owner and the response to a late report. Test the agreed procedure with fictional staff before an operational pilot.
Link to this answerRead the observation time and treat the location as a past supplied report. It does not establish where the person is now.
Link to this answerOpen the original source and look for a specific reported place and time. Record the remaining uncertainty before relating it to a local journey.
Link to this answerReview publication dates, geographic relevance and the original reporting behind each item. Keep conflicting or missing information visible to the authorised travel reviewer.
Link to this answerTest the supported field-form behaviour, then verify delivery after reconnecting. Agree the team's communication fallback independently of the software demonstration.
Link to this answerIt establishes that a report was supplied at a particular time. The team still needs its own communication, follow-up and travel-approval procedures.
Link to this answerCompare their reported times and purposes without assuming continuous tracking. Confirm the organisation's actual workflow for supplied staff and vehicle observations.
Link to this answerRetain the source link, date, reported location and relevant context. Let the authorised person review that evidence rather than relying on a headline alone.
Link to this answerChoose a planned location with limited coverage and ask the team to identify what remains unknown. Agree the additional sources and human review needed.
Link to this answerThe manager should find the last supplied report and follow the agreed late-report procedure. Evaluate that decision process separately from any promise of safety.
Link to this answerExplore source dates, a travel review and voluntary check-in records using demonstration data.
View the official Waypoint introduction and compare it with your team's actual reporting requirements.
Compare supported source families, timestamps and map precision before preparing a travel review.
Prepare your country, language and handover requirements with a relevant regional checklist. Each section is also available in Arabic.
Waypoint brings NGO projects, donor funding, purchase approvals, people, beneficiaries, documents and fleet planning together with sourced country intelligence and voluntary field-team check-ins.
Explore VCMP WaypointVCMP Command connects security contracts, assigned obligations, officer shifts, patrol observations, incident deadlines and reviewed delivery evidence in one organisation workspace.
Explore VCMP CommandHelp us improve VCMP
We use optional analytics cookies to understand which pages people visit and how they discover VCMP. We do not use these analytics cookies unless you accept them.
Read our privacy policy