A renovation company receives a LINE message asking, “What would this size roughly cost?” A staff member asks for the floor area, property type, and requested work one message at a time. Another staff member asks in a different order, so two similar inquiries receive different first estimates.
A training provider uses a paper questionnaire at exhibitions to recommend one of three courses. Staff total the answers afterward and email the result. If one answer is missing, they must contact the visitor again, and the recommendation slips to the next day.
Moving that intake online may reduce uncertainty before a consultation. But copying questions onto a screen does not create a useful diagnosis or estimate.
Decide the promise after answering before adding questions
“More questions may improve accuracy, but what if the form becomes so long that people leave?”
When a business considers a web diagnosis or estimate simulation, question count and screen design are tempting starting points.
The respondent is trying to learn something simpler: which situation fits, what the rough range is, and what to do next.
Do not start with the questions.
Start with what appears after the answers and what decision that result supports.
If there are three outcomes, ask only what separates those three outcomes.
If staff must review the request before discussing an amount, do not promise an instant estimate.
Use a short guided intake and state when a person will reply.
The short answer
Use this order to choose a first format without creating an oversized questionnaire.
- Start with a short web diagnosis when answers can lead to three or four useful guidance outcomes
- Start with a rough estimate simulation when quantities and choices determine a range and exceptions are explainable
- Start with a guided intake and personal reply when staff experience or conversation changes the answer
- If the promised result is unclear, place six to ten recent requests in one comparison table
For each request, record the customer problem, questions staff asked, guidance given, exceptions, and next action.
Before designing screens, check whether the same input should reliably produce the same guidance.
When showing a rough range, put inclusions, exclusions, and conditions requiring formal review beside that range.
Separate information needed for the result from information needed for a reply.
If a result can be shown anonymously, ask only people who want personal help for contact details afterward.30-second check: should you test a diagnosis, estimate, or guided intake first?
Answer four questions to choose a provisional starting point: a short diagnosis, a rough estimate simulation, a guided intake, or question-and-result planning.
This is not a final decision.
Use it to choose the next real request to test and what to discuss with a service provider or development company.
30-second check
Should you test a diagnosis, rough estimate, or guided intake first?
0/4
Answer the 4 questions first
Use the promised result, decision rule, next action, and contact-information timing to choose a first format.
When unsure, choose the answer closest to your most recent real call, message, or email exchange.
Write the result in three lines before writing questions
Draft every result using three lines.
- What is the current situation?
- What should the person check next?
- How should they describe it when asking for help?
For example, a booking-method diagnosis could show this result.
- Current situation: an existing booking service may work if the person only needs to check one staff member and one room
- Next check: decide whether staff approval is required before a booking becomes final
- How to ask: discuss a flow where staff approve the first booking and returning customers choose an open time directly
Any question that cannot change or clarify that result is a candidate for removal.
Company size, job title, or a full address should not appear before the result if they do not affect it.
Compare manual guidance, existing forms, diagnosis services, and a focused custom flow
This table is not a ranking.
It compares starting points by result logic, calculation needs, and work after submission.
Fast-changing prices are intentionally omitted.
| Representative starting point | Best fit | Main benefit | Downside or check | Plan and connection conditions | First test |
|---|---|---|---|---|---|
Paper questionnaire or short guide page plus a staff reply | Request volume is still low, and staff conversation or exception handling changes the answer | Test whether people understand the questions and value the guidance before introducing a new system | Answers and replies easily become separated. Use consistent fields so staff do not ask and answer differently | Start with existing calls, LINE, or email. Define who can see personal information and how long records remain | Compare six to ten recent requests and see whether they form about three repeatable outcomes |
| Google Forms section routing | A few answers should skip irrelevant questions, while staff still review and reply | Test conditional paths in an existing form and learn which questions people do not need to see | Answer-based section routing is limited to multiple-choice and dropdown questions. Complex scoring or personalized results need more work | Check Google account conditions, organization settings, collaborators, and access to any connected working sheet | Limit the outcomes to two or three and test one answer that skips an unnecessary section |
| Typeform outcomes and scoring | Each answer should connect to an outcome, or points should place the respondent into a result range | Test answer-to-outcome matching, score ranges, branching, and calculations without first building a custom flow | Test ties, missing answers, and combinations that overproduce one result. Logic support also depends on the question type | Official help currently lists logic, scores, variables, and custom endings on the Free plan. Confirm response allowances and paid features in the current account | Replay about ten real requests and check both the expected outcome and whether its wording supports a useful next action |
Focused custom diagnosis or estimate flow | The business needs unique calculations, exceptions, saved results, or connections to existing customer or product information | Explain results in the business's language and tailor boundaries, exclusions, and the consultation handoff | Calculation rules and guidance require ongoing updates. Define how incorrect ranges are corrected and who answers questions | Discuss site placement, information transfer, content ownership, retention, and consent for measurement or follow-up | Test one request type with three outcomes or one calculation, then let staff review the formal handoff |
Why official guidance supports fewer, purposeful questions
The W3C forms tutorial says to request only what is required for the process, because irrelevant or excessive information makes abandonment more likely (reference).
It also recommends splitting long forms into a sequence of smaller logical stages and communicating progress.
The GOV.UK Design System says a service should know why it asks every question and request only information it really needs (reference).
It also recommends offering “I do not know” or “I am not sure” when those are valid answers.
Making a form shorter does not mean deleting fields at random. Remove questions that have no reason to change the result.Google Forms can send respondents to different sections based on answers, but the routing control is available only for multiple-choice and dropdown questions (reference).
Before choosing a tool, write which answer skips which question and leads to which result.
Separate a diagnosis from a rough estimate simulation
A web diagnosis chooses a guidance category or next action from the answers.
A rough estimate simulation calculates an amount, duration, or quantity range from defined conditions.
They look similar but require different checks.
| Decision point | Web diagnosis | Rough estimate simulation |
|---|---|---|
| Result unit | Type, suitable approach, or next guide | Amount range, duration range, or rough quantity |
| What changes the result | Priority, current method, or required support | Quantity, unit, additions, minimums, and maximums |
| Required qualification | It is an entry point for comparison or consultation, not a final decision | Inclusions, exclusions, effective date, and conditions requiring formal review |
| Test focus | The expected outcome appears and its explanation makes sense | Boundary values, exceptions, rounding, and missing input do not produce misleading ranges |
Typeform's official help also distinguishes an Outcome quiz, which links answers to endings, from a Score quiz, which assigns points and maps score ranges to endings (reference).
Choose the approach your staff can explain, not the one that merely sounds more advanced.
Separate result, guidance, and consultation questions
Classify each possible question by purpose.
Questions that change the result
The answer changes the diagnosis outcome or rough estimate.
Examples include number of users, desired timing, and whether this is recurring or one-time work.
Questions that change guidance after the result
The result stays the same, but the next guide or warning changes.
Examples include whether the service is used in store and online or whether staff approval is needed.
Questions first needed for personal consultation
Staff need them to reply, but they do not affect the diagnosis.
Examples include name, email, full address, and a detailed open request.
Ask whether the third group can wait until after the result.Write a decision-supporting result, not just a result name
“Type A” or “80% recommended” does not tell someone what to do.
Keep each result short, but include these elements.
- Describe the current situation in everyday language the respondent recognizes
- Show about two important answers that led to the result
- Give one fact the respondent can check next
- State when personal consultation is needed
- State what the diagnosis or estimate cannot decide
If you display a score, explain what that score represents.
Precise-looking decimals and percentages are inappropriate when no one can explain their meaning.
Define inclusions and exclusions before the estimate formula
People naturally focus on the number a simulation shows.
Place the assumptions beside the result.
- Define the unit for every quantity
- State what work or products the base range includes
- State conditions that add work or cost
- State conditions outside the simulation
- Explain tax, delivery, travel, and discount treatment
- State which input requires formal staff review
As a practical test, check values immediately below and above each minimum and maximum, as well as blank, zero, and unusually large values.
W3C guidance recommends forgiving reasonable input formats and allowing people to review and correct what they entered (reference).
Do not block someone because a phone number uses a different separator or a harmless numeric format.
Do not turn “I do not know” into a dead end
Respondents may not know every condition.
Forcing “not decided” or “needs an on-site check” into another answer weakens the result.
Give that response a useful route.
- Explain what information would allow the diagnosis or estimate to continue
- Explain what the person can check, such as a photo, measurement, or contract
- Provide a consultation route that works without that information
- Avoid an automatic result when staff review is required
Do not force “none of these” into an unrelated outcome.
If it appears repeatedly, revisit the scope before adding another result.
Reconsider whether contact details are needed before the result
Requesting a name, company, phone number, and email before the first question asks undecided visitors to identify themselves before receiving value.
Separate three stages.
- Answers required to produce the diagnosis or estimate
- Information used to save or resend the result
- Contact details required for a personal reply
If stage one can produce the result, contact details can wait.
Japan's Personal Information Protection Commission guidance covers notification or publication of purpose when directly collecting personal information and appropriate safeguards for personal data (reference).
Applicable requirements vary by information and use.
At minimum, be able to explain why each item is collected, who sees it, where it goes, and when it is removed.
Five signs to discuss a focused custom flow
After testing an existing form or diagnosis service, consider a focused custom discussion when several of these conditions overlap.
- A rough estimate combines unique quantities, limits, additions, and exceptions
- Each result changes the guidance, documents, consultation fields, or responsible team
- Respondents need to save progress and continue later
- Answers need to connect to existing product, member, booking, or customer information
- Staff need to update result wording or calculation rules and review change history
One condition may still fit an existing service setting.
Prototype the connected area where manual work continues.
Limit the first scope to one request type and three outcomes
A renovation company should not begin with residential houses, apartments, and stores at once.
It could start with one request type, such as apartment interior consultation.
A sufficient first scope looks like this.
- Cover one request type
- Use three or four outcomes
- Ask one thing in each question
- Include a not-decided option
- Connect every result to one next action
- Ask only people who want help for contact details
- Let staff review the result
Japan's Digital Agency guidebook describes improving services from actual user voices and behavior, across planning, design, delivery, and operation (reference).
Do not add questions from internal assumptions alone. Check whether real respondents understand the wording and result.
Pause before asking about health, income, or family information
Some diagnosis topics make health, income, family, or contract information look useful.
First confirm that it truly changes the result.
If it is necessary, define why it is asked, what happens without it, who can see it, and how long it remains.
When using an external form or diagnosis service, also check these points.
- Identify the countries or regions where answers are handled
- Confirm what collaborators and contractors can see
- Define when answers connect to other customer information
- Name the person responsible for removing unneeded responses
- Provide a route for correcting incorrect results or guidance
A diagnosis is not exempt from ordinary information handling.
Confirm professional requirements for the specific information and operation.
Six preparations before consultation
1. Compare six to ten recent requests
Anonymize examples from calls, LINE, email, and paper.
Put the questions asked, guidance given, exception, and next action on one row.
2. Group them into about three outcomes
Combine requests that received similar guidance.
Do not force an outlier into the closest result.
3. Mark the questions that changed the guidance
Ask staff why a different answer was given.
Move questions that did not affect the outcome later in the journey.
4. Write estimate boundaries and exclusions
Document minimums, maximums, additions, exceptions, and formal-review conditions.
“This is only an estimate” is not enough explanation.
5. Choose one action after each result
Direct the respondent to read guidance, book, request a formal consultation, or prepare a document.
6. Let a real requester read the words
Ask the person to explain the question, difference between choices, reason for the result, and next action in their own words.
Revise where their explanation differs.
Web diagnosis and estimate planning checklist
Select each item as you confirm it.
You can still ask for help while some items remain open.
Copyable consultation note
Use this note when discussing whether to test a web diagnosis, a rough estimate simulation, or a guided intake.
Write “confirm during consultation” for anything still unknown.
Copy a web diagnosis and estimate planning note
Use this note before choosing diagnosis, estimate, or guided intake. Write “confirm during consultation” for unknown items.
What we want to discuss about a web diagnosis or rough estimate simulation: Business or service in scope: Example: apartment interior renovation consultation Question requesters currently ask: Example: roughly what this floor area and work would cost Current intake method: Example: receive LINE messages, calls, and emails, then ask follow-up questions one at a time One recent request: Example: confirmed floor area, property type, requested work, and timing, then gave a rough range Result we want to show: Example: one of three suitable consultation routes or a qualified amount range Action after the result: Example: review scope conditions and request a formal consultation Questions that change the result: Example: floor area, property type, and requested work Questions that only change guidance after the result: Example: whether the person stays during work and whether timing is decided Information first needed for personal consultation: Example: name, email, full address, drawing, and site photos Route for an “I do not know” answer: Example: explain what document to check and offer a consultation without it Estimate inclusions and exclusions: Example: base work is included; extra repair, tax, and furniture moving require separate review Estimate boundaries, exceptions, and out-of-scope cases: Example: above a defined area, on-site review required, or outside the service area When contact details are requested: Example: show the result anonymously and ask only people who request formal help What the first prototype should test: Example: ten real requests reach the expected three outcomes and support a next action What we want to decide: Example: start with an existing form, diagnosis service, or focused custom view Examples we can share: Example: anonymized LINE request, paper questionnaire, previous rough range, and guidance email
Your next step
Choose one recent request today and create four columns.
- What the requester first asked
- What staff asked next
- What guidance or range staff finally gave
- What the requester did afterward
Add another request using the same columns.
Three repeating guidance groups are possible diagnosis outcomes.
A repeatable range from quantities and choices is a possible estimate simulation.
A result that changes after staff review is a guided-intake candidate.
Further reading
- World Wide Web Consortium, Web Accessibility Initiative, Forms Tutorial, first published September 2014, updated March 27, 2026, accessed August 5, 2026
- World Wide Web Consortium, Web Accessibility Initiative, Validating Input, updated July 27, 2019, accessed August 5, 2026
- Government Digital Service, GOV.UK Design System, Question pages, publication and update dates not stated on the page, accessed August 5, 2026
- Google, Google Docs Editors Help, Show questions based on answers, publication and update dates not stated on the page, accessed August 5, 2026
- Typeform, Help Center, Quiz and scoring: what's the difference between Outcome quiz and Score quiz?, publication and update dates not stated on the page, accessed August 5, 2026
- Typeform, Help Center, Free plan, publication and update dates not stated on the page, accessed August 5, 2026. Reconfirm current plan limits before use
- Personal Information Protection Commission, Japan, Guidelines on the Act on the Protection of Personal Information, General Rules, published November 2016, partially revised June 2026, accessed August 5, 2026
- Digital Agency, Government of Japan, Guidebook for Introducing a User-Centered Perspective in Administrative Services, page updated October 17, 2025, PDF revised April 1, 2025, accessed August 5, 2026