Build apps · Your App Cloud
Digitize the paper forms you receive
Put new submissions on an online form, and photograph the paper copies that still arrive. Keep each value suggested from a photo unconfirmed until a person checks it against the image.
Built around a purpose
From a box of sign-up forms to rosters you can rely on.
For anyone who retypes handwritten forms today. That might be a league registrar with a box of sign-up sheets or a front desk with a clipboard of new-client forms. It could also be a property office collecting repair requests from its mail slot. It fits when most people could answer online but some will keep handing you paper.
For illustration: Northgate Youth Soccer, a volunteer-run league in Santa Rosa, California. About 300 players register each spring, most on a two-sided paper form handed out at schools and collected at a sign-up day in the park. The registrar types every form into a spreadsheet. Bring the blank form, the registrar's spreadsheet columns and eight filled copies, including one written in pencil, one with a crossed-out phone number and one with the back left empty.
One registration list for the season. Online and paper sign-ups sit together with their source marked, and each paper registration keeps both photographed sides. Rosters draw only on confirmed registrations, and every paper one has been checked against its photo.
Saved registrations, stored photos of the paper forms, the Vision model's suggestions and the registrar's sign-in are backend capabilities, so this is an app with data; a page that explains how to register would be a one-page site. Model and service usage is metered separately. Build and preview it on any plan; on Free, AI in previews is free up to $1 a month. Putting it live needs Go or Pro. See pricing
Read filled copies before the blank one
Lay the eight copies side by side and mark what families actually did. Look for answers squeezed into the margin and two age-group boxes checked where one was asked for. Watch too for a "See back" note with nothing on the back, and a birth date written as 5/6/17. Those marks show which questions confuse people and which ones nobody answers.
Keep only the fields the league reads
List what the registrar uses from each form and drop the rest, such as the fax number. Split boxes that hold two answers, like "Parent name and phone", into separate fields. Let the age group follow from the birth date instead of the box a parent checked. Describe this record to Studio, not a copy of the page.
Open an online form for new families
Build the online form on that same record, with checks a pen can ignore. Date of birth takes a real date, the phone number takes ten digits, and photo consent becomes a yes or no instead of a lone box a parent could skip. Print the form's web address at the top of the paper version, so next season's flyers point people online.
Photograph paper copies into the same list
Paper still arrives on sign-up day. A volunteer photographs both sides of each form with a phone, and each pair of photos opens a registration with paper as its source and a status of needs review. Ask Studio for a step in which a Vision model suggests a value for each field from the photos. Store those suggestions apart from the values a person confirms.
Confirm each value against the photo
Ask Studio for a review screen that shows the photographed page large enough to zoom into, next to the suggested fields. The registrar reads the handwriting, corrects or confirms each value, and phones the family about any required answer that is missing. Let only confirmed registrations reach a team roster.
Scope the first version
What a first version includes.
Registration record
One per player with the fields the league kept, a source of online or paper, and a status of needs review, waiting on family or confirmed.
Online registration form
Required questions, a proper date field for date of birth, yes or no questions where the paper had a lone checkbox, and a confirmation screen showing a registration number.
Paper intake from a phone
An upload, used in a phone's browser, for the front and back of one paper form. It opens a new registration with paper as its source.
Suggested beside confirmed
The Vision model's suggestion for each field kept next to the value the registrar saved, so you can see which fields get corrected most often.
Review screen
The photographed page beside its fields. Required fields stay unconfirmed until someone has compared them with the handwriting.
Waiting on family
Registrations missing a required answer, such as an emergency contact, with the guardian's phone number and a note of each call made.
Test it in the preview
Before you share it.
- Put the pencil copy and the one with the crossed-out phone number through review. Zoom into both on the review screen, and retake any photo where a digit can't be read there. The saved number should be the one the guardian meant, with the model's suggestion still visible on the record.
- Try to confirm a registration whose emergency contact is empty. The app should refuse and move it to the waiting-on-family list.
- Register one player online and then again on paper, as families sometimes do. Confirming the paper copy should warn you about a match on name and date of birth rather than add a second player. If it doesn't, ask Studio for that check.
- Enter a birth date that falls exactly on the league's age cutoff. The player should land in the age group the league's rules give, not the one next to it.
- Fill in the online form on a phone with the text size turned up, then on a laptop using only the keyboard. Every question should keep its label, and an error should name the answer that is missing.
- Signed out, open a registration link and a photo link; neither should load. If coaches will sign in, try a test coach account. It should show that coach's own roster and emergency contacts, not other teams' players or any form photos.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Vision models
Make sense of images and documents
Database
Keep data and context for apps and agents
File storage
A home for your documents and media
Authentication
Give the right people access
Shape the details
Make it work for your world.
- Every field you keep is one more value to confirm on each paper form. Before a question goes onto the online form, ask who reads the answer and what they do with it. A question kept only because the old form had it slows every review.
- Some people will keep choosing paper: a grandparent registering a child, families at the park on sign-up day, anyone short on phone data. Reprint the paper form with its questions in the online form's order, so a reviewer reads the page and the screen in the same sequence.
- A photo keeps everything on the page, including notes you chose not to store as fields, such as a custody arrangement written in the margin or a child's medication. Keep photos and medical answers behind sign-in with the access you describe for each collection, and agree with the league's board when paper originals get shredded.
- Look at the corrections after the first 50 paper forms. If the registrar rewrites one field on most of them, such as the guardian's email address, stop suggesting it. Have it typed instead, or ask for block capitals on the next printing.
A little more context
Good questions.
Can people fill out a digital version instead?
Yes, and most new submissions should come that way. Build the online form on the same record as the paper intake. Then a registration typed on a phone and one photographed at the park end up in one list, each with its source marked. Print the online form's address on every paper copy you still hand out.
Can a model read handwriting?
A Vision model in the app can suggest values, and some of them will be wrong. Pencil, cursive, crossed-out answers and a 1 that looks like a 7 can all lead to wrong suggestions, and you only learn which fields suffer by testing your own forms. Keep suggestions apart from confirmed values, and have a person compare each one with the photo.
Are the signatures legally binding?
That depends on where you are and what the form is for, so ask whoever relies on the signature, such as the league's insurer or a lawyer. The app can keep the photo of each signed page with its registration. An online form can collect a typed name and an agreement checkbox, which is not ink on paper.
What should we do with the box of old forms?
First decide whether you need them as records at all. If only this season matters, store the box and start fresh. If you need past registrations, such as those of returning families, photograph them into the same list with a source such as "paper, last fall". Review them in batches once this season's forms are done, and keep the paper until its batch is confirmed.
How is this different from building a form from a photo?
The image to form page linked below starts from a photo of a blank copy and covers shaping the online form around it. This guide covers the copies that come back filled in and the review that makes their answers usable. If what arrives is receipts and invoices rather than forms, the document organizer guide below fits better.
Explore Pricing for plans, included capabilities, and usage details.
Start from what you have
Bring the file you already use.
Keep exploring.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building