Microsoft Forms and Google Forms: Collecting Information Safely

The activities director builds a quick sign-up form for the family cookout, then adds a question about dietary restrictions. A week later someone adds "any allergies or conditions we should know about?" and the form has quietly become a collection point for health information, sitting in a free-form tool nobody in IT has looked at.

Online forms from Microsoft 365 or Google Workspace are genuinely useful. They replace paper sign-in sheets, shift-swap requests and supply orders. The trouble is that they are so easy to create that sensitive data ends up in them before anyone decides whether it should.

Decide first whether a form is the right tool

A good rule for department heads: forms are fine for information about staff logistics, events and supplies. They are a poor fit for anything that identifies a resident together with a diagnosis, medication, behavior, incident or payment detail.

If you are unsure, ask what would happen if the response list were forwarded to the wrong person. If the answer is "mildly awkward," a form is fine. If the answer is "we would have to talk to compliance," use your EHR or another approved system instead.

Know who can see the responses

Every form has an owner, and responses live in that owner's account. That raises questions most people never ask.

If the creator leaves, do the responses go with their account when it is deleted?

Is the form owned by a person or by a shared team location that the organization controls?

Who else was added as a collaborator, and do they still work here?

Does the form write responses into a spreadsheet that has its own, wider sharing?

That last one catches people. The form may be private, but the linked spreadsheet in someone's OneDrive or Drive may have been shared with a whole department "so everyone can see the sign-ups."

Avoid the public link

Both platforms let you choose who can fill out a form. The options generally range from anyone with the link, to only people in your organization, to specific named people.

For anything internal, choose the organization-only option. That means a respondent has to sign in with a work account, which also gives you a record of who submitted what. A link that anyone can open can be forwarded, posted in a group chat or picked up by a spam bot.

Public forms have a legitimate place, such as a tour request or a job inquiry from the community. Those should collect only what you would be comfortable seeing on a postcard: a name, a phone number, a preferred time. Do not ask a public form for dates of birth, Social Security numbers, insurance details or medical questions.

Watch what the form asks and what it stores

Responses sit in the platform until someone removes them. A form built for a one-time event can hold names and phone numbers for years.

Ask for the minimum. Every extra question is something you now have to protect.

Avoid free-text boxes where people will volunteer more than you wanted.

Turn off response emails that copy answers to a personal address.

Set a calendar reminder to export what you need and delete the rest when the event ends.

A short checklist before you share a form

Does the form ask for anything that identifies a resident with health information? If yes, stop and use an approved system.

Is the form owned by a shared or organization-controlled location rather than one person's account?

Is it limited to people in your organization, unless it truly must be public?

Is the linked spreadsheet or results file shared only with the people who need it?

Who will delete the responses, and when?

Write the answers down in two lines and keep them with the form. If a surveyor or an insurer ever asks how your facility collects information electronically, that note is a good start.

Give staff a clear yes and no

Most department heads are not trying to cut corners. They need a fast way to collect an answer, and nobody told them where the line is. A one-page guide with examples of what is fine (potluck sign-ups, uniform sizes, training attendance) and what is not (anything with a resident's condition) prevents most of the problems before they happen.

It also helps to name a person to ask. A quick message to your administrator or privacy officer before building the form is much easier than cleaning up afterward.

How we can help

UnityCare IT helps care organizations set up Microsoft 365 and Google Workspace so forms and shared files default to organization-only access, with ownership kept in places the facility controls. We can review the forms and shared spreadsheets already in use and help you write a short, plain guide for department heads on what belongs in a form and what does not.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support