This form helps a household work through an internet outage in a calm, organised way. Fill in what you can observe right now. Nothing here is a professional diagnosis or a guarantee of a fix; it is simply a shared record so everyone knows what has already been tried.
Household or network nickname
Person filling in this form
Date of this troubleshooting session
Time the problem was first noticed
Best estimate of when the connection last worked normally
What kind of home internet connection do you believe you have?
Fibre to the home
Cable or coaxial
Phone line (DSL or similar)
Mobile or cellular router
Fixed wireless or antenna based
Satellite
Not sure
Other
How many people in the household are affected right now?
Is anyone currently working, studying, or in an online meeting from home?
Before touching any equipment, work out how far the problem reaches. A single device behaving oddly is a different situation from every device in the house being offline.
Are all devices in the home currently unable to reach the internet?
Does mobile data on a phone work while the home internet is down?
Do nearby neighbours or nearby households also appear to be offline?
Yes, several neighbours confirm they are offline
One neighbour is also offline
No, neighbours seem to be online
I have not been able to ask anyone
Not applicable, no neighbours nearby
What symptoms does the connection show at its worst?
Complete loss of connection
Very slow loading
Pages load partly or images fail
Frequent disconnections
Device says connected but nothing loads
Unusual error messages in the browser
Video calls freeze or drop
Other
Complete one row per device. For Router Light Configuration use one of: All Green, Blinking Amber, Solid Red, All Off. For Resulting Fix Status use one of: Back Online, Still Down. Tick the reboot checkbox only after the device has been fully powered off and on again. This table is a shared observation log, not a technical diagnosis.
Affected Devices, Router Lights, Reboots and Results
Affected Device | Router Light Configuration | Physical Reboot Completed? | Resulting Fix Status | |
|---|---|---|---|---|
Smart TV | All Green | Back Online | ||
Phone | Blinking Amber | Still Down | ||
Work Laptop | Solid Red | Still Down | ||
Tablet | All Off | Still Down | ||
Game Console | All Green | Back Online | ||
Any device that does not fit the table above, or any pattern you noticed while filling it in:
Look at the main internet box (often called a router, modem, gateway or hub). Do not unscrew anything or open the casing. Simply note what the indicator lights are doing and take a photo if you can.
Overall, what is the light configuration on the main box right now?
All Green
Blinking Amber
Solid Red
All Off
Mixed colours I cannot describe
No lights at all on any box
Which individual indicator lights can you see on the box?
Power
Internet or WAN
DSL or line
Wi-Fi or wireless
Ethernet or LAN ports
Mobile or signal bars
Alarm, warning or status
None are visible
Optional photo of the front panel lights (please avoid photographing any labels showing security code or account numbers)
Has the main box been fully powered off, waited on, and powered back on during this session?
How many times has the main box been restarted since the problem began?
Does the box feel unusually warm, or is anything buzzing, clicking or smelling odd?
Many home outages come down to something simple and physical: a loose cable, a switched-off socket, or equipment hidden behind furniture with no airflow.
Which physical checks have been carried out today?
Power cables pushed fully into the sockets
Wall socket switched on and tested with another device
Network or phone cables clicked firmly into place
Damaged, kinked or chewed cables looked for
Any splitter, adapter or extension inspected
Equipment moved out of a closed cupboard
Antenna or outdoor dish checked from ground level only
None of these yet
Has anything changed in the home recently that could be related?
Where is the main internet box located?
Open shelf or desk with airflow
Inside a cabinet or cupboard
Behind a television or furniture
On the floor in a hallway
Garage, basement, loft or utility area
Outdoors under cover
Other
How warm does the equipment feel to the touch, from 1 (cold) to 5 (very hot)?
These checks separate two different problems: not being able to join the home network at all, versus joining the network but having no internet through it.
Can your device still see the home Wi-Fi network name in its list?
Wi-Fi network name you are trying to use
Which of these have you already tried on a device?
Turning Wi-Fi off and on again on the device
Forgetting the network and rejoining it
Restarting the device itself
Trying a different device on the same network
Trying a cable connection instead of Wi-Fi
Turning off any VPN or private relay
Checking whether the device clock and date are correct
None of these yet
Signal strength where you are testing, from 1 (very weak) to 5 (excellent)
Is there a separate Wi-Fi extender, mesh unit or powerline adapter in use?
If mobile data is available, these checks help work out whether the problem is inside the home or further along the line. Use only official status pages or messages you can verify yourself.
Have you checked your provider's service status page or app using mobile data?
Any outage reference, notice number or announcement code you have seen
Have you seen any message from your provider by text, email or letter about service in your area?
How confident are you that the problem is outside your home?
Very confident it is an outside problem
Somewhat confident
Unsure either way
Somewhat confident it is inside the home
Very confident it is inside the home
Occasionally a service stops because of something on the account rather than the equipment. These questions are only for your own reference and to prepare for a conversation with your provider.
Account or customer number (optional)
Are you aware of any unpaid balance, expired payment method or recent billing change?
Has any equipment been added, swapped or returned recently?
Roughly how old is the main internet box?
Less than a year
About 1 to 3 years
About 3 to 5 years
More than 5 years
I do not know
Has an automatic software or firmware update run on the equipment recently?
I have avoided writing security code, full payment card numbers or similar sensitive details anywhere on this form
Recording what the household has been doing to cope helps later when deciding how urgently the problem needs to be escalated.
Which workarounds are being used right now?
Mobile data on phones
Mobile hotspot shared with other devices
A neighbour's or relative's connection
Public or community Wi-Fi
Downloading material earlier for offline use
Rescheduling calls or classes
Using a wired connection instead of Wi-Fi
No workaround available
Workaround Log
Workaround Used | Started At | Minutes Planned | Did It Restore Access? | Effective Minutes | |
|---|---|---|---|---|---|
Mobile hotspot for homework | 9:15 AM | 60 | 60 | ||
Public library Wi-Fi visit | 11:00 AM | 120 | 120 | ||
Wired cable to the router | 1:40 PM | 30 | 0 | ||
0 | |||||
0 | |||||
0 | |||||
0 | |||||
0 | |||||
0 | |||||
0 |
How disruptive has this outage been for the household so far?
Not disruptive at all
Slightly disruptive
Moderately disruptive
Very disruptive
Severely disruptive
Describe the main impact in practical terms (missed classes, delayed work, missed appointments, entertainment, staying in touch):
Does anyone in the household rely on the internet for something health, safety or accessibility related?
This section prepares you for a support conversation and keeps a record of what was agreed. Notes here are for your own reference.
Has support been contacted about this outage yet?
Ticket, case or reference number from support
Date and time support was contacted
What outcome did support give?
A known outage is being worked on
A technician visit was arranged
Equipment replacement was arranged
Settings were changed remotely
Advice was given to try more steps at home
The issue was closed without action
No answer or no resolution yet
Summary of what support said, in your own words:
Would another household member like to add anything to this record?
Wrap up by recording where things stand right now and what should happen next. Update this form again if the situation changes.
Current overall status of the home internet
Fully back online on all devices
Back online but slower than usual
Online on some devices only
Intermittent, dropping in and out
Still completely down
Waiting for a technician or replacement
Please rate how each area performed during this troubleshooting session
Strongly disagree | Disagree | Neutral | Agree | Strongly agree | |
|---|---|---|---|---|---|
How clear were the instructions in this form? | |||||
How organised did the household feel while working through the steps? | |||||
How confident are you that the cause has been identified? | |||||
How satisfied are you with the outcome so far? | |||||
How likely are you to use this form again? |
What should happen next?
Keep monitoring for the next hour
Repeat the reboot steps later today
Wait for the provider's estimated fix time
Attend a technician visit
Test a different cable or adapter
Ask a neighbour again about their service
Consider a backup connection for important tasks
Nothing further for now
When should this form be reviewed or updated next?
Final notes, reminders or questions to ask the provider next time:
The observations recorded here reflect what the household could see and try at the time, and no step described here should be treated as a professional or guaranteed fix
Signature of the person completing this form
Analysis for Why Is the Internet Down? Family Troubleshooting Checklist and Log
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This is a thoughtfully designed household troubleshooting form aimed at guiding a family through an internet outage in a calm, structured manner. The form's title, "Why Is the Internet Down? Family Troubleshooting Checklist and Log", clearly sets expectations: this is a shared observation and logging tool, not a professional diagnostic instrument. The introductory paragraph in the first section reinforces this framing by stating explicitly that nothing recorded constitutes a professional diagnosis or guaranteed fix. This tone-setting is a notable strength, as it manages user expectations and reduces the risk of over-reliance on the form's guidance.
The form is organized into ten logical sections that follow a natural troubleshooting progression: from initial household context, through scope-of-problem assessment, device-level logging, router and modem checks, physical and environmental inspection, Wi-Fi and local network diagnostics, external service status checks, account and billing considerations, workaround tracking, and finally support contact and follow-up planning. This linear flow mirrors how a methodical person might naturally investigate a problem, making the form intuitive to follow even under stress.
This opening section gathers contextual information that frames the entire troubleshooting session. The question "Household or network nickname" provides a simple identifier for the record, which is useful if a household maintains multiple troubleshooting logs over time. The question "Person filling in this form" establishes accountability and helps clarify who performed which observations, particularly important in a multi-person household where different members may contribute at different times.
The questions "Date of this troubleshooting session", "Time the problem was first noticed", and "Best estimate of when the connection last worked normally" collectively build a timeline. This temporal data is operationally valuable because it helps establish the duration and onset of the problem, which can inform whether the issue is sudden (potentially an outage or equipment failure) or gradual (possibly related to environmental changes or equipment degradation).
The multiple-choice question "What kind of home internet connection do you believe you have?" is well-designed with a "Not sure" option and conditional follow-ups. The follow-up for "Not sure" asks the user to describe visible equipment, which is a practical approach to helping non-technical users provide useful information. The follow-up for "Other" allows free-text description. This branching logic reduces friction for users who lack technical knowledge while still capturing actionable detail.
The question "How many people in the household are affected right now?" captures the scale of impact, while "Is anyone currently working, studying, or in an online meeting from home?" introduces an urgency dimension. The conditional follow-up on the "yes" branch asks for specifics about urgent needs (e.g., exam at 2 pm), which is practical for prioritizing troubleshooting efforts. The "no" branch provides reassuring text that lowers urgency, which is a thoughtful user experience touch.
This section is well-positioned before any equipment is touched, as the introductory paragraph advises. The question "Are all devices in the home currently unable to reach the internet?" is a critical scoping question. Its conditional logic is extensive: a "yes" answer prompts the user to list tested devices, while a "no" answer leads to a single-choice question about the specific pattern observed. This branching is one of the form's strongest design features, as it tailors the troubleshooting path to the actual situation.
The follow-up options under "Which description best matches what you are seeing?" cover six distinct scenarios (single device, wireless-only, wired-only, single room, slow speed, intermittent drops), each with its own targeted follow-up. For example, selecting "Only wireless devices are offline" triggers a question about whether a wired device still works, with a paragraph noting this pattern may point to the wireless component. This kind of context-sensitive guidance is genuinely helpful for non-technical users.
The question "Does mobile data on a phone work while the home internet is down?" serves a dual purpose: it helps distinguish between a home network issue and a broader service problem, and the follow-up text encourages using mobile data to check provider status pages and keep the form updated. This is a practical, forward-thinking design choice.
The question "Do nearby neighbours or nearby households also appear to be offline?" helps distinguish between a localized equipment problem and a wider service outage. The follow-up options and branching (including a reminder prompt when the user hasn't been able to ask) show careful consideration of real-world constraints.
The multiple-choice question "What symptoms does the connection show at its worst?" captures symptom patterns across multiple dimensions (complete loss, slow loading, partial loading, disconnections, false-connected states, error messages, video call issues). The follow-ups for error messages and "Other" allow precise detail capture.
The table "Affected Devices, Router Lights, Reboots and Results" is a central data collection element. It uses four columns: "Affected Device", "Router Light Configuration", "Physical Reboot Completed?", and "Resulting Fix Status". The introductory paragraph provides clear instructions on the expected values for each column and cautions that the table is a shared observation log rather than a technical diagnosis. The sample rows (Smart TV, Phone, Work Laptop, Tablet, Game Console) serve as helpful examples of how to fill in the table.
The open-ended question "Any device that does not fit the table above, or any pattern you noticed while filling it in" provides a catch-all for observations that don't fit the structured format. This is a good complement to the table, ensuring no relevant detail is lost.
This section focuses on the main internet equipment. The introductory paragraph includes a safety caution (do not open the casing) and suggests photographing the lights. The question "Overall, what is the light configuration on the main box right now?" uses a single-choice format with six options, including "Mixed colours I cannot describe" and "No lights at all on any box." The conditional follow-ups are particularly well-designed: for example, selecting "All Off" triggers a question about whether the wall socket is on, with a practical instruction to turn it on and wait. Selecting "Solid Red" asks whether a red light has appeared before and whether it cleared on its own.
The multiple-choice question "Which individual indicator lights can you see on the box?" helps identify which specific lights are relevant to the situation. The image upload question "Optional photo of the front panel lights" includes a thoughtful privacy caution about avoiding labels with security code or account numbers.
The question "Has the main box been fully powered off, waited on, and powered back on during this session?" is a core troubleshooting step. Its follow-up logic is practical: if "yes," it asks how long the box was off (with a note that very short power-offs may not be sufficient), and if "no," it provides clear instructions for performing the step. The question "How many times has the main box been restarted since the problem began?" captures repetition data that can be useful for identifying persistent issues.
The question "Does the box feel unusually warm, or is anything buzzing, clicking or smelling odd?" includes an important safety-oriented follow-up that advises switching off equipment and contacting a qualified technician if there are concerns about heat, smoke, or electrical safety. This is responsible guidance within the form's scope.
This section addresses the physical layer of troubleshooting. The multiple-choice question "Which physical checks have been carried out today?" covers eight common checks (power cables, wall sockets, network cables, damaged cables, splitters, equipment location, antennas, and "None of these yet"). The conditional follow-ups are appropriate: for example, finding damaged cables prompts a description request with a caution not to repair mains wiring, and checking antennas includes a safety note about ground-level observation only.
The question "Has anything changed in the home recently that could be related?" with its follow-up "What changed?" covers eight categories of recent changes (new devices, equipment moves, new cables, renovations, weather, power cuts, firmware updates, and "Nothing obvious"). This is a well-targeted question that can surface common causes of connectivity issues.
The question "Where is the main internet box located?" with follow-ups for cabinet and behind-furniture placements suggests temporary relocation as a test. The question "How warm does the equipment feel to the touch, from 1 (cold) to 5 (very hot)?" uses a simple rating scale to capture thermal information without requiring technical knowledge.
This section distinguishes between being unable to join the local network and being connected but having no internet access. The question "Can your device still see the home Wi-Fi network name in its list?" is a fundamental diagnostic step with extensive branching. If the device can see the network, follow-ups explore whether it connects and what happens when opening a website. If it cannot see the network, follow-ups check for distance/coverage issues and recent network name changes.
The question "Wi-Fi network name you are trying to use" captures the specific SSID being tested. The multiple-choice question "Which of these have you already tried on a device?" covers seven common device-level troubleshooting steps, with targeted follow-ups for key options (e.g., forgetting and rejoining the network, trying a cable connection, checking date/time settings).
The question "Signal strength where you are testing, from 1 (very weak) to 5 (excellent)" provides a simple subjective measure. The question about separate Wi-Fi extenders or mesh units includes a practical note about restarting those units after the main box is back on.
This section helps determine whether the problem is internal or external. The question "Have you checked your provider's service status page or app using mobile data?" with its detailed follow-up options (known outage, planned maintenance, no known issues, page won't load, login problems, other) captures a range of outcomes. The follow-up for login problems wisely notes that account issues may be relevant and directs users to the account section.
The question "Any outage reference, notice number or announcement code you have seen" captures reference information that can be useful for follow-up. The question about provider messages (text, email, letter) and the confidence rating "How confident are you that the problem is outside your home?" help assess the user's own judgment about the situation.
This section addresses account-level factors that might affect service. The question "Account or customer number (optional)" is appropriately marked as optional, which is good practice given the sensitivity of account information. The question "Are you aware of any unpaid balance, expired payment method or recent billing change?" includes a caution against writing full payment details on the form.
The question "Has any equipment been added, swapped or returned recently?" with its detailed branching covers new equipment delivery, returns, SIM changes, and address moves. The follow-up for new equipment asks whether it has been activated, which is a practical check. The question about equipment age and firmware updates rounds out the equipment history.
The checkbox "I have avoided writing security code, full payment card numbers or similar sensitive details anywhere on this form" is a thoughtful privacy reminder that reinforces good data hygiene practices.
This section captures how the household is coping with the outage. The multiple-choice question "Which workarounds are being used right now?" covers eight options with targeted follow-ups (mobile data allowance, permission to use a neighbour's connection, cable connection results).
The "Workaround Log" table is a practical tracking tool with columns for workaround description, start time, planned minutes, whether it restored access, and effective minutes. The formula in the last column (IF(column4=1,column3,0)) automatically calculates effective minutes based on whether the workaround was successful, which is a useful built-in calculation.
The disruption rating "How disruptive has this outage been for the household so far?" and the impact description question help contextualize the urgency. The question about health, safety, or accessibility dependencies includes a responsible note directing users to appropriate emergency services for urgent matters.
This section prepares users for support interactions and records outcomes. The question "Has support been contacted about this outage yet?" branches into contact method details (with a wait-time question for phone calls) or preparation guidance if support hasn't been contacted yet. The preparation follow-up asks users to list details they want to mention, which is genuinely helpful for organizing a support conversation.
The questions about ticket numbers, contact date/time, and support outcomes capture the full support interaction. The outcome question "What outcome did support give?" has seven options with detailed follow-ups (technician visit details, equipment replacement details, remote settings changes, recommended steps, closure reasons). The question "Would another household member like to add anything to this record?" supports collaborative documentation.
The closing section provides a structured wrap-up. The question "Current overall status of the home internet" uses six options with targeted follow-ups (speed comparison, affected devices, drop frequency, visit dates). The matrix rating question "Please rate how each area performed during this troubleshooting session" captures five dimensions of user experience feedback, which is valuable for form improvement.
The follow-up planning question "What should happen next?" covers eight options, and the review date question ensures the form is revisited. The final checkbox "The observations recorded here reflect what the household could see and try at the time, and no step described here should be treated as a professional or guaranteed fix" reinforces the form's advisory nature. The signature field provides a formal record of completion.
This form collects a rich dataset spanning temporal information (dates, times, durations), categorical observations (light configurations, symptom types, connection types), quantitative measures (number of affected people, restart counts, signal strength ratings, disruption ratings), structured tabular data (device status table, workaround log), and free-text narrative descriptions. The combination of structured and unstructured data provides both analytical depth and contextual richness.
From a data quality perspective, the form's extensive use of conditional logic and specific follow-up questions encourages detailed, relevant responses. The pre-populated example rows in the tables serve as helpful templates. The inclusion of "Not sure" and "None of these yet" options reduces the risk of forced inaccurate responses.
Privacy considerations are addressed throughout the form: the image upload includes a caution about avoiding sensitive labels, the billing section warns against entering payment details, the account number field is marked optional, and the final checkbox reminds users to avoid sensitive information. These are proportionate, practical measures for a household-level form.
The form demonstrates strong UX awareness through several design choices: the calm, non-technical tone throughout; the progressive disclosure enabled by conditional logic (users only see relevant follow-ups); the use of plain language alongside technical terms (e.g., "main internet box (often called a router, modem, gateway or hub)"); the inclusion of safety notes where appropriate; and the reassuring text on "no problem" branches.
One potential friction point is the overall length of the form. With ten sections and extensive conditional branching, a full completion could take considerable time. However, the form's purpose as a shared household log justifies this depth, and the conditional logic means users only encounter relevant questions. The section-by-section structure also allows natural breaks.
The sample data in the tables (device status table and workaround log) is a helpful touch that shows users exactly what kind of information is expected. The matrix rating at the end provides a built-in feedback mechanism, which is a thoughtful inclusion for continuous improvement.
This form is an exceptionally well-structured and thoughtfully designed household troubleshooting tool. Its greatest strengths lie in its logical progression from context-setting through systematic diagnosis to outcome recording; its extensive use of conditional logic that tailors the experience to the user's actual situation; its clear, calm, non-technical language that makes the form accessible to all household members; its consistent safety and privacy awareness; and its comprehensive coverage of both technical observations and household impact. The form successfully balances depth of data collection with usability, and its explicit framing as a shared observation log rather than a professional diagnostic tool sets appropriate expectations. Areas where the form could be further refined include potentially offering a "quick start" or abbreviated path for users who want to record only the essentials, and considering whether some sections could be made optional or collapsible to reduce perceived length. Overall, this is a practical, user-friendly, and responsibly designed form that serves its stated purpose effectively.
Mandatory Question Analysis for Why Is the Internet Down? Family Troubleshooting Checklist and Log
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Household or network nickname
Recommendation: Requiring this field ensures that each troubleshooting log can be clearly associated with a specific household or network. In a shared family environment where multiple logs might be created over time (e.g., one per outage), this identifier prevents confusion and supports organized record-keeping. The practical necessity of this field depends on whether the form creator expects multiple logs to be maintained; if only a single log is used at a time, this could potentially be made optional without significant loss of clarity.
Person filling in this form
Recommendation: Requiring this field establishes clear attribution for the observations and actions recorded. In a multi-person household, different members may contribute to the troubleshooting process at different times, and knowing who completed each entry supports accountability and helps clarify whose observations are being recorded. This is particularly useful when reviewing the log later or when contacting support, as it helps establish who performed which steps. The form creator should consider whether a simple first name is sufficient or whether more detailed identification is needed for their specific use case.
Are all devices in the home currently unable to reach the internet?
Recommendation: Requiring this question supports the form's core troubleshooting logic. This is a critical scoping question that determines which follow-up path the user will take. Without an answer to this question, the conditional branching that follows cannot function correctly, and the troubleshooting guidance would be incomplete. Making this mandatory ensures that every session begins with a clear assessment of the problem's scope, which is operationally important for directing subsequent troubleshooting steps effectively. The necessity of this requirement is well-supported by the form's structure, as this question directly drives the branching logic in the following section.
Overall, what is the light configuration on the main box right now?
Recommendation: Requiring this question ensures that a key visual observation about the main equipment is captured for every troubleshooting session. The router or modem light configuration is one of the most accessible diagnostic indicators for non-technical users, and recording it provides a concrete data point that can be referenced later or shared with support. The conditional follow-ups that branch from this question (e.g., checking the power socket if lights are off, describing blinking patterns) rely on this answer being provided. Making this mandatory supports the form's systematic approach to equipment assessment.
Has the main box been fully powered off, waited on, and powered back on during this session?
Recommendation: Requiring this question ensures that one of the most commonly recommended troubleshooting steps is explicitly addressed in every session. Whether the answer is yes or no, the form provides appropriate follow-up guidance (timing details for a completed reboot, or instructions for performing one). Recording this information prevents redundant troubleshooting attempts and helps establish what has already been tried. The form creator should note that the practical importance of this field depends on whether the form is used as a real-time troubleshooting guide or as a retrospective log. Capturing this step supports clear documentation, in both cases.
Can your device still see the home Wi-Fi network name in its list?
Recommendation: Requiring this question supports the form's diagnostic framework for distinguishing between local network issues and internet connectivity problems. The answer to this question determines which follow-up path is taken, exploring either the connected-but-no-internet scenario or the cannot-see-network scenario. Without this information, the Wi-Fi troubleshooting section would lack a clear starting point. Making this mandatory ensures that every session includes this fundamental connectivity check, which is operationally useful for narrowing down the likely area of the problem.
Has support been contacted about this outage yet?
Recommendation: Requiring this question helps establish the current escalation status of the issue. The answer determines whether the form records details of a completed support interaction or helps the user prepare for one. This information is operationally useful for tracking whether the household has taken the step of seeking external assistance and for avoiding duplicate support contacts. The form creator should consider whether this question's mandatory status aligns with their intended use; if the form is primarily used before support is contacted, this question might be better placed as optional or positioned differently.
Current overall status of the home internet
Recommendation: Requiring this question ensures that every troubleshooting session concludes with a clear statement of the current situation. This serves as a natural summary point and provides a reference for any follow-up or review of the log. The conditional follow-ups (speed comparison, affected devices, drop frequency, visit dates) provide additional detail based on the selected status. Making this mandatory supports the form's goal of maintaining an up-to-date shared record that the whole household can reference. The necessity of this requirement is well-supported by the form's structure as a living document that is meant to be updated as the situation changes.
The form currently designates eight questions as mandatory across its ten sections. This is a reasonable proportion for a form of this length and complexity, and the mandatory fields are distributed across the beginning, middle, and end of the form rather than being clustered together. This distribution helps maintain a sense of progress and ensures that key data points are captured at each stage of the troubleshooting process.
Balancing data collection depth against completion rates: The form's extensive conditional logic already helps manage user effort by showing only relevant follow-ups. The mandatory fields are generally straightforward to answer (yes/no questions, simple text fields, or single-choice selections), which minimizes the effort required to complete them. However, given the form's overall length, the form creator should monitor whether users tend to abandon the form before reaching the final sections. If completion rates are a concern, consider whether some mandatory fields in the middle sections (such as the router light configuration or Wi-Fi network visibility questions) could be made optional, since the conditional logic would still provide useful guidance even if these questions are skipped.
Conditional logic and mandatory fields: The form's conditional branching is well-integrated with its mandatory fields. For example, the mandatory question about whether all devices are offline drives extensive follow-up logic, making its required status operationally justified. The form creator should ensure that mandatory fields that trigger conditional logic are always answered before the user can proceed, as skipping them would result in incomplete troubleshooting guidance.
Best practices for mandatory field selection: The current selection of mandatory fields focuses on identification (household nickname, person filling in), scope assessment (all devices offline), equipment status (router lights, reboot status), network visibility (Wi-Fi network name), escalation status (support contacted), and final outcome (current status). This covers the essential checkpoints of a troubleshooting session. Consider whether the date and time fields near the beginning of the form should also be mandatory, as temporal information is operationally valuable for tracking the progression of an outage. Conversely, the signature field at the end is not marked mandatory, which may be appropriate depending on whether formal sign-off is expected.
Placement and number of mandatory fields: With eight mandatory fields across a form that contains well over a hundred total questions and elements, the mandatory-to-total ratio is low, which is generally favorable for user completion. The mandatory fields are positioned at logical checkpoints rather than being front-loaded, which supports a natural flow. The form creator may wish to review whether the mandatory fields in the later sections (support contacted, current status) are consistently reached by users, as these are positioned after several lengthy sections. If users commonly stop before these points, consider whether the form could be restructured to surface the final status question earlier, or whether a brief summary or checkpoint could be inserted mid-form to encourage continued completion.
Additional observations: The form includes two checkboxes (the sensitive data avoidance reminder and the observations disclaimer) and a signature field, none of which are marked mandatory. Whether these should be required depends on the form creator's governance needs. If the form is intended as a formal household record, requiring the sensitive data checkbox could reinforce privacy awareness. If the form is purely informal, keeping these optional is reasonable. The form creator should periodically review the mandatory field set based on user feedback and completion data to ensure it remains aligned with the form's practical use.