How to inventory the fields of a web form
A form-field inventory helps document what a form asks for and how its sections fit together. It is useful for preparing an intake checklist or mapping a future data entry workflow.
Start with the right material.
- What you provide
- one active ordinary HTML form inspected with approved page code.
- The intended result
- Export field labels, types and required flags; exclude entered values and password contents.
How the workflow works.
Record readable field labels, types, required indicators and available options. Keep the form's section context so repeated labels such as name or address remain understandable.
What to check in the result.
Compare the inventory with the current visible form state. Conditional fields that have not appeared and hidden backend requirements are outside the observed selection and should not be inferred.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Field label, Input type, Required. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.