A short thread on tips for using Google Forms.

Firstly, everything I have learned about Google Forms was via @missdcox amazing YouTube tutorials. All the ways we use Google Forms are based on these videos. I would start by watching these: https://t.co/5FnIwEAFlk
We design Google Forms collaboratively across the department. These are created on the department Google Drive. The use of admin questions at the start of a Google Form enables this.
Teachers can access their class responses via the drive. All responses can be downloaded onto a Google Sheet and then filtered according to class/teacher/question.
We primarily use Google Forms for MCQs. At KS3, these are set weekly as the final task for students to complete. Most questions are based off knowledge students will have looked at in that week.
We use questions from previous MCQs so students are revisiting topics. These questions could be ones which students have struggled with or ones which link to knowledge looked at in the week’s lesson. To import questions from prior MCQs, click on the import icon in the sidebar.
The sidebar allows you to do other things such as add extra question, add image, video or section.
We use MCQs to check both knowledge and skills. Here is an example where we check students understanding of thesis statements.
You can give feedback on correct/incorrect answers. Click on answer key answer and then on add answer feedback. You can provide feedback on correct and incorrect answers. This could include links to attachments or a video which would further support students.
We provide discussion statements where students identify their view. Students really enjoy these as a way of engaging with big questions. We encourage students to discuss their responses with friends and family. Their responses could also be discussed in Google Meet.
You can also use Forms to get students writing short answers. We haven’t done this given the increase of workload in checking answers and also MCQs can be more diagnostic. Nonetheless, they provide another way of receiving student responses.

More from Tech

After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile

You May Also Like