Automated MedVision Transportation Digest
Every night, WebRun opens MedVision QuickCap, finds every participant scheduled for day center or a medical appointment tomorrow, builds a ride by ride manifest in Google Sheets with pickup times, addresses, and mobility equipment needs, and posts a Slack digest to the transportation team.
How do I coordinate PACE participant transportation every day?
WebRun checks MedVision QuickCap every night for participants scheduled for day center or a medical appointment the next day, builds a ride by ride transportation manifest in Google Sheets with pickup times and mobility needs, and posts a Slack digest to the transportation team, so dispatch starts the morning with a complete, organized route list instead of a scramble.
- Tomorrow's ride manifest is ready before the transportation team leaves for the day
- Unconfirmed authorizations surface before a van is dispatched, not after
- Pickup, address, and equipment details are pulled straight from MedVision QuickCap, not retyped by hand
Built for PACE transportation coordinators · PACE dispatch staff · PACE day center directors · PACE program administrators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
quickcap.medvision-solutions.comin a real browser with your saved login - no setup, no API keys. -
1
MedVision QuickCap - find tomorrow's transportation needs
medvision-solutions.com
WebRun opens MedVision QuickCap to find tomorrow's transportation needs. - Open MedVision QuickCap and list every participant scheduled for day center or a medical appointment tomorrow
- Capture each participant's pickup address, appointment time, and any mobility equipment or escort need
- Flag any participant whose transportation authorization has not been confirmed
Done when Every participant needing transportation tomorrow has been listed with pickup details.
-
2
Google Sheets - build the ride by ride manifest
google.com
WebRun opens Google Sheets to build the ride by ride manifest. - Open the Transportation Manifest tracker
- Build tomorrow's ride list sorted by pickup time and route area
- Add each participant's address, appointment time, mobility equipment, and escort requirement
- Flag any unconfirmed authorization at the top of the sheet for dispatch to resolve first
Done when Tomorrow's manifest is organized by route with every pickup detail filled in.
-
3
Slack - alert the transportation team
slack.com
WebRun opens Slack to alert the transportation team. - Post the manifest link and a summary count to the transportation Slack channel
- Call out any participant with an unconfirmed authorization or special equipment need
- Leave route planning and driver assignment to the transportation coordinator
Done when The transportation team has tomorrow's manifest and knows what needs attention first.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it assign drivers or plan routes automatically?
No. WebRun builds the manifest with every pickup detail filled in, but assigning drivers and routes stays with your transportation coordinator.
How does it know a participant needs transportation?
It reads MedVision QuickCap's day center attendance and appointment schedule for each participant, so anyone marked for a ride tomorrow lands on the manifest without anyone re-entering the schedule by hand.
What happens if a participant's ride is not yet authorized?
It flags that participant at the top of the manifest and in the Slack digest, so dispatch resolves the authorization before a driver is assigned instead of after the van is already out.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.