Evaluation 1 of 5
NGO fleet allocation across bases
A fleet register becomes useful when a coordinator can identify the vehicle, project and available driver for a specific journey.
- Prepare
- Prepare three fictional vehicles at two bases, one assigned trip and one vehicle awaiting service. Use the same distance unit throughout the example.
- Check
- In Waypoint, review vehicle and project records, schedule a driver and check a conflicting assignment before confirming the trip.
- Read the result
- Compare the actual allocation and exception shown in the demo. A recorded vehicle location is a report, not a continuous GPS feed.
Evaluation 2 of 5
Fuel, mileage and maintenance records
Fuel spending and distance need their own records; a low fuel bill alone cannot establish that a vehicle is efficient.
- Prepare
- Bring a sample fuel receipt, opening and closing odometer readings, a service event and their currency. Remove personal or confidential details.
- Check
- Record the fuel and mileage in the demo, complete a trip and review the service state. Compare totals only within the same currency and distance unit.
- Read the result
- Missing odometer readings and mixed currencies need review before drawing a cost conclusion. Ask to see the exact export your finance team needs.
Evaluation 3 of 5
Programme records and donor reporting
A donor update needs a defined reporting period and a traceable connection between activities, programme records and supporting evidence.
- Prepare
- Choose one fictional project, a funding record, a purchase request and a beneficiary summary. Agree which fields should appear in the donor report.
- Check
- Follow the records through Waypoint's programme workspace. Check the date range, project filter, approval state and information exposed in the report.
- Read the result
- A purchase request is not proof of payment, and an activity count is not an impact result. Keep sensitive beneficiary details out of shared summaries.
Evaluation 4 of 5
Offline field reports and delivery status
A report saved on a field device is useful only when the team can also establish whether it reached the organisation workspace.
- Prepare
- Prepare a fictional field form and agree who will receive it. Open the field kit while connected before testing the offline workflow.
- Check
- Capture a report without connectivity, restore the connection and check its delivery state. Compare the saved content with the received record.
- Read the result
- Keep queued, delivered and reviewed states separate. A delayed report needs the team's agreed escalation route; the software is not an emergency response service.
Evaluation 5 of 5
Country intelligence and voluntary check-ins
Field planning works best when the source date, geographic relevance and team report are visible together.
- Prepare
- Select a country alert, a planned journey and a fictional staff check-in. Note both the source publication time and the person's reporting time.
- Check
- Open the original source and compare its coverage with the journey. Check who can view the location and what happens when a report is overdue.
- Read the result
- Waypoint uses voluntary check-ins. The last reported location does not prove a person's current position, and an alert does not establish that a route is safe.