Deployment support: automated outreach for 228 families

A two-person Family Readiness office was manually transferring deployment information into a tracker while also trying to send timely information to deploying members and their spouses. I redesigned the workflow using Microsoft Forms, Power Automate, and SharePoint so one submission could update the tracker and trigger the needed communications automatically.

The problem

Before a group deployed, members checked out through the Family Readiness office. Two staff members entered each member's deployment information into a tracker by hand, then separately sent the member and spouse the resources and office contacts they would need during the deployment.

Baseline

  • 2 staff in the office

  • About 35 fields of deployment information per member, entered into the tracker by hand

  • Member and spouse communications sent separately from tracker entry

Where it broke

The handoff after intake. The information existed the moment a member provided it, but people re-entered it into the tracker and then had to send the follow-up information on their own.

The change

The tempting fix was a bigger one: a new app or a family portal. None of that touched the real problem. The useful question was smaller: why are two people retyping information the system already has?

I redesigned the workflow using Microsoft Forms, Power Automate, and SharePoint so one submission handles both the tracker entry and the outreach to the member and spouse.

Result

The redesigned workflow supported 228 families. Deploying members completed an approximately 35-field form, Power Automate populated the SharePoint tracker, and the member and spouse immediately received the appropriate information and attachments. The change removed repetitive tracker entry and made timely outreach possible without adding workload to the two-person office.

The office conservatively estimated the redesign saved approximately 50 staff hours. That estimate was not based on a formal time study, so I treat the 228-family scope and removal of manual work as the primary documented results.

What I learned

Keep what works. Fix what doesn't. Automation did not take Family Readiness out of supporting families. It took repetitive work off two people so they could spend that time on the families who needed them.

Method

Fix the handoff. Map the process from start to done, find the step where work leaves one system and gets redone by hand, and connect it before you replace anything. In EASIER terms: Spot where it breaks, then Improve the way. See all six process guides.

Related free tool

The Who Owns What Map puts every player in a process on one page, so the handoffs show. It is part of the free EASIER toolkit. No email required.

This story also appears in my book, There Has to Be an Easier Way.

Back to all case studies

Previous
Previous

Security authorizations: expired packages cut by more than half

Next
Next

Pharmacy staging: nine seconds a trip, about 220 trips a day