FREE COURSE · BEGINNER
Tally

Build and test a three-question feedback form

A working practice form with required questions, a thank-you message and one checked test response.

About 25 minutes4 practical stepsFree to read
A website displayed on a laptop at a bright wooden desk.

Before you start

A Tally Free account and a browser. The exercise uses fictional feedback and no email, file upload, payment field or external integration.

Stay on the free route

Free forms retain Tally branding and are subject to its fair-use terms. Skip custom domains, paid branding removal and other upgrade options. Keep this a practice form: do not share it with real respondents until you have reviewed the wording and any data you intend to collect.

Original practice lesson · Official references checked 14 October 2026 · Button names may differ between app versions.

Your progress

0 of 4 steps complete.

Start first step ↓
STEP 1 · ABOUT 5 MIN

Define the smallest useful form

Ask only questions that help the next decision. Three short questions are enough to practise the complete flow.

  1. Create a blank form called “Practice workshop feedback”. Add a description explaining that this is a fictional test and no real personal information should be entered.
  2. Use the three questions below. Do not add name, email, payment or file-upload fields.
  3. Decide which answers are essential: make the first two required and leave the final comment optional.
Practice example
Title: Practice workshop feedback
Description: Fictional test only. Please do not enter names, contact details or private information.

1. How useful was the session?
Options: Very useful / Somewhat useful / Not useful
2. Which topic should we cover next?
Options: Planning / Design / Automation
3. What could make the next session clearer?
Optional short written comment
STEP 2 · ABOUT 8 MIN

Add question blocks and a thank-you page

Use the manual editor to understand how a form is built rather than starting with a large generated template.

  1. Use the + menu or type / to insert a Multiple choice block for each of the first two questions. Add the three options to each. Use a Short answer or Long answer block for the final comment.
  2. Open each question’s settings with its nearby menu. Set the first two to required and keep the comment optional. Preview the wording and check each option is distinct.
  3. Use /thank to add a thank-you page with the message “Thanks — this practice response helps us test the form.” Keep the default free branding.
STEP 3 · ABOUT 6 MIN

Test the empty and completed form

Test both the normal path and a missing-answer case before relying on a form.

  1. Open Preview. Try to submit without answering the first question and check that the required-field validation stops you.
  2. Choose Very useful and Design, leave the optional comment blank, and confirm the form can reach the thank-you page. Preview responses may not be saved to the submissions table.
  3. Check the form at a narrow phone-sized width or open its preview on your phone. Shorten labels if they are hard to scan.
STEP 4 · ABOUT 6 MIN

Check a real test response

A preview checks the interface. One deliberate submission checks that the published form records the answers.

  1. Publish the fictional practice form and open its link yourself. Do not distribute it publicly or send it to customers.
  2. Submit Very useful, Design and the fictional comment “TEST — make the example text larger.” Open the form’s Submissions tab and check all three values appear.
  3. Record the test result in your notes. Keep the form labelled as a test, and review its wording and data needs before adapting it for real use. Publishing the form does not automatically embed it on your website.
TRY IT YOURSELF · ABOUT 5 MIN

The form is live but has never been tested

Your practice form has three questions, a required field and a thank-you message. You have opened the link, but have not sent a test response.

Original fictional scenario · choose an answer, then read the explanation.

Which check gives useful evidence that the response flow works?

See a worked example and review checklist

Blank required answer → validation stops the submission. Valid fictional answers → one recorded response and the intended thank-you state. Compare the stored answers with what you entered.

  • Required-field validation works.
  • The saved practice response matches the entered answers.
  • The success message matches what the form actually did.

Try it with a new example: Write down what should happen after a real response arrives. Treat notifications or integrations as separate features to configure and test.

This checks one practice decision, not your real work. Answers save only in this browser when storage is available.

MAKE THE LESSON YOURS

Keep your practice notes

Record what you made, what you checked and what you want to improve. These notes stay in this browser; they are not sent to us or synced to another device. Clearing browser data removes them.

Optional · up to 2,000 characters.

YOUR NEXT SMALL STEP

Put your practice to work

Repeat the task with a fresh brief. Check the result before using it for a real project.

Choose your next skill →

Part of Plan and test a small workflow.

GO FURTHER WITH THE PROVIDER

Tally: create your first form

Official guide to question blocks, required fields, thank-you pages and publishing. Our sample asks for anonymous practice feedback only.

Open official learning ↗

Sources and lesson notes

The practical brief and exercises are ours. Official references support the product guidance; we do not host the providers’ course content.

Checked 14 October 2026. Tool plans can change; consult the provider before choosing an upgrade. These beginner exercises have not been presented as certified or exhaustive product testing.

Progress saves in this browser. No site account needed.

THE OTHER FEW

Find the few things worth knowing.

Explore AI tools, software and technology through official sources, clear trade-offs and practical comparisons, so you can find the few that matter to your task.

Popular searches:

🔥 Fresh Few

Recently added to our catalogue, with a reason to explore each one.

💎 Hidden Gems

Editorial alternatives with a specific reason to consider them.

📊 Popular Categories

More from The Other Few
Personal Few

Build the few tools that work together.

Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.

Stack suggestions are task-fit decisions, not product rankings. Commercial relationships must never change compatibility.
READY

Tell us the outcome.

We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.

Evidence-first: current pricing, feature availability and platform support should be shown only when verified from an appropriate source.
THE OTHER FEW · INTELLIGENCE LAYER

From task to decision.

The shortlist now explains the fit, the trade-offs and what to do next.

PERSONALISED FIT
✦

Task understanding

Translate natural-language goals into task signals before matching products.

GoalUse caseConstraints
◎

Compatibility

Show why a tool fits this search instead of presenting a permanent product score.

PlatformExperiencePriority
↗

Decision path

Move naturally from shortlist to profile, alternatives, compare and saved tools.

ExploreCompareSave
DISCOVERY

Go beyond the shortlist.

Browse editorial collections when you want to explore rather than solve one task.

Fresh FewOnly products with a genuine freshness signal.Explore →
Hidden GemsInteresting products that deserve a closer look.Explore →
Popular CategoriesStart with the job, then narrow to the Few.Browse →
VERIFIED SOURCES · EDITORIAL FIT · NO PAID RANKING
RECOMMENDATION GRAPH

See why the Few connect.

The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.

GRAPH ACTIVE
YOUR TASKgoal + constraintsTASKFITTOOLEVIDENCE intentexperienceplatformpriorityproductalternativesourcefreshness
EXAMPLE DECISION PATH
1 · GoalBuild a website for a small business.
2 · ConstraintsBeginner · web · low-code · ease.
3 · Candidate setReplit · Lovable · Claude — narrowed before presentation.
4 · Trade-offLovable favours simplicity; Replit offers more control; Claude is broader rather than purpose-built for the build.
Compatibility is task-specific. It is not a permanent product rating.

Graph signals

These are the relationships the engine can reason over as the catalogue grows.

Goal / intentConstraintTask fitAlternativeWorkflow overlapEvidenceFreshnessSaved context
Important: the graph does not invent evidence. Unsupported claims remain unsupported until verified.
PERSONAL DECISION LAYER

Make the decision smaller.

Bring your goal, saved tools, workflows and fresh changes together. The Other Few narrows the decision without pretending there is one universal winner.
● Decision context ready
Launch a businessBuild a websiteCreate videosResearch & decide
GoalWaiting
ConstraintsWaiting
Your FewLocal saves
ChangesFreshness ready
Start with the outcome.

We'll turn it into a smaller, clearer decision using the intelligence already built into The Other Few.
Fit is contextual. Editorial judgement, evidence and commercial relationships remain separate.Private on this device.
Intelligence Core
Make the catalogue smarter, not just bigger.
The intelligence layer now treats products, tasks, constraints, alternatives and workflows as connected evidence. Expansion is staged into verification lanes rather than filling the catalogue with unverified entries.
18 core records · verification-first
18Core records
7Categories covered
14Relationship types
0Fabricated records

Connected catalogue

Core products are connected to the tasks and categories they are already structured to serve.

Expansion lanes

These are research lanes, not unpublished product claims. A lane becomes catalogue data only after source verification and taxonomy review.
Editorial rule: catalogue breadth never outranks evidence quality. A product can enter the research queue without entering the public Few.
Intelligence Core

One brain. Every decision.

The catalogue, Finder, Decision Engine, workflows, Your Few and freshness signals now have a shared conceptual layer. The goal is not more results — it is better decisions with fewer tools.
● CORE MODEL READY

Decision graph

The same product can play different roles depending on the user's outcome and constraints.
18core products
7active categories
0saved tools
0watched tools
GoalOutcome
IntentTask
ConstraintsFit limits
ProductsCatalogue
DecisionFew