{"id":1422,"date":"2014-08-20T09:13:00","date_gmt":"2014-08-20T15:13:00","guid":{"rendered":"http:\/\/www.mooreds.com\/wordpress\/?p=1422"},"modified":"2015-10-26T07:53:06","modified_gmt":"2015-10-26T13:53:06","slug":"the-limits-of-google-forms","status":"publish","type":"post","link":"https:\/\/www.mooreds.com\/wordpress\/archives\/1422","title":{"rendered":"The limits of Google forms"},"content":{"rendered":"
\"paperwork
Photo by Harald Groven<\/a> \"\"<\/a><\/small><\/figcaption><\/figure>\n

I spent a fair amount of time in the spring working on Google forms<\/a>. If you have Google apps for your domain and are doing any kind of data entry at all, you should use Google forms. With this, you can create a web and mobile friendly data entry form easily, with validation, for free.<\/p>\n

And by you, I mean ‘you, the non technical user’–a big win.\u00a0 I’m a big big fan of anything that removes developers from the loop because they are too often the bottleneck.\u00a0 Of course, as you’ll see below, Google forms is not entirely the land of milk and honey.<\/p>\n

Any data entered typically goes into a Google spreadsheet for easy batch processing. You can limit use of the form to your Google apps domain, too.<\/p>\n

Here are some ways that I’ve seen Google forms used to eliminate manual re-keying of data:<\/p>\n