Required and Optional Fields¶
When creating a monitoring field, you can decide whether it must be completed before a visit can be submitted.
This is controlled using the Required toggle.
Choosing which fields are required helps ensure important information is always collected while allowing flexibility for optional observations.
Required Fields¶
Enable the Required toggle for information that must always be captured during a visit.
FieldOps will prevent users from submitting the visit until all required fields have been completed.
Typical required fields include:
- Visit Date
- Site Name
- Facility Condition
- Number of Staff
- Inspector Name
Required fields are clearly indicated during visit creation.
Optional Fields¶
Leave the Required toggle disabled for information that may not apply to every visit.
Examples include:
- Additional Comments
- Recommendations
- Follow-up Notes
- Observations
- Supporting Details
Optional fields can be completed when relevant but will not prevent a visit from being submitted.
How Validation Works¶
When a field officer submits a visit, FieldOps automatically checks every required monitoring field.
If one or more required fields have not been completed:
- The visit cannot be submitted.
- The missing fields are highlighted.
- A validation message is displayed to guide the user.
After the required information is provided, the visit can be submitted successfully.
Choosing Required Fields¶
When deciding whether a field should be required, ask yourself:
- Is this information essential for reporting?
- Is it needed for compliance or donor requirements?
- Will every visit always have this information available?
If the answer is yes, make the field required.
If the answer is no, consider making it optional.
Best Practices¶
A well-designed monitoring template balances data quality with usability.
We recommend that you:
- Make only essential fields required.
- Keep required questions to a reasonable number.
- Avoid requiring information that may not always be available in the field.
- Use optional fields for observations, comments and recommendations.
- Review required fields periodically as monitoring requirements evolve.
Overusing required fields can slow down field work and lead to incomplete or inaccurate responses.
Example¶
Consider the following section:
| Field | Required |
|---|---|
| Visit Date | ✔︎ |
| Officer Name | ✔︎ |
| Facility Condition | ✔︎ |
| Number of Staff | ✔︎ |
| Observations | ✖︎ |
| Recommendations | ✖︎ |
| Additional Comments | ✖︎ |
In this example, the essential monitoring information is mandatory, while narrative responses remain optional.
Next Step¶
Continue to Template Snapshots to learn how FieldOps preserves the exact monitoring template used for every visit, ensuring historical data remains accurate even after templates are updated.