Rain Gear & Umbrella Integrity Audit — Seasonal Condition Check

1. Audit Overview & Scope

This form helps you record the condition of rain gear and umbrellas so that wet-weather equipment can be maintained, repaired, or replaced in good time. Please answer each question based on what you actually observe. Where you are unsure, select the closest option and add a note rather than guessing.

 

Audit reference or record number

Audit date

Site, facility, or area covered by this audit

Auditor name

Auditor role, team, or department

Group or person responsible for the gear being audited

Primary reason for carrying out this audit

 

Please briefly describe what triggered this investigation:

 

Please describe the reason for this audit:

Was any gear inspected while it was wet or raining at the time?

 

Please describe the conditions and any steps taken to handle or dry the items afterwards:

2. Weather & Environmental Context

Weather and surroundings can affect how fabric behaves during inspection. Recording these details makes it easier to compare results between audits.

 

Predominant weather during the inspection

Approximate air temperature during inspection (°C)

Recent rainfall pattern in the area

Environmental exposure factors present in the storage or use area

 

Where does the grit or residue mainly appear?

 

Please name the substance or area involved, if known:

 

Please describe the humidity or ventilation situation:

3. Rain Gear Inventory & Usage Profile

Understanding what gear exists, how often it is used, and how old it is helps put the condition findings into perspective.

 

Total number of rain gear items included in this audit

Types of rain gear included in this audit

 

How many breathable rain shells are included?

 

Please note the boot height and sole condition:

 

How many compact folding umbrellas are included?

 

Please describe the gear covers or dry bags:

Has any of this gear been used in heavy rain during the past 30 days?

 

Please summarise the use, how long it was worn, and anything the user noticed:

Typical frequency of use for this gear set

Approximate average age of the gear set (years)

Is there a written inventory or label system identifying each item?

 

Where is the inventory kept or how are items labelled?

 

Please note any difficulties identifying individual items during this audit:

4. Water Repellency Assessment

Water repellency is judged by how the outer fabric reacts to moisture. As a simple reference: a surface where droplets form and roll off is holding up well; a surface that darkens or soaks quickly is losing its repellent finish; visible dampness along stitched seams may indicate leaking seams. This is an observational check only and does not replace specialist testing.

 

Overall water repellency of the gear set

 

Where was the soaking or darkening most noticeable?

 

Please describe where the leaks appear and how quickly moisture came through:

Did you carry out a simple water bead check by placing droplets on the outer fabric?

 

How did the droplets behave on the surface?

 

Which item showed pass-through, and how long did it take?

 

What prevented the bead check from being carried out?

Symptoms of moisture-related wear observed on any item

 

On which item were the marks found?

 

Please describe the smell and how noticeable it is:

Please describe the most serious repellency issue observed, including which item it affects:

How would you rate the overall repellency of the gear set at present?

5. Rain Gear Condition Register

List each item below and record what you observed. In the condition column, use the reference marks shown in the examples: a green mark for a surface where water beads and rolls off, a yellow mark for fabric that soaks or darkens quickly, and a red mark for leaking seams. For umbrella items, record the rib or spoke check; for non-umbrella items, you may write 'Not applicable'. Add or remove rows as needed to cover every item in your set.

 

Rain Gear & Umbrella Condition Register

Rain Gear Description

Water Repellency Condition

Umbrella Spoke/Rib Check

DWR Waterproofing Spray Applied Date

A
B
C
D
1
Breathable Rain Shell
🟢 Water Beads & Rolls Off
Not applicable
3/12/2027
2
Compact Folding Umbrella
🟡 Fabric Soaks/Darkens Quickly
Bent Spoke
9/28/2026
3
Tall Mud Boots
🔴 Leaking Seams
Not applicable
1/15/2027
4
Wide-Canopy Umbrella
🟢 Water Beads & Rolls Off
All Ribs Straight
4/2/2027
5
Packable Rain Jacket
🟡 Fabric Soaks/Darkens Quickly
Not applicable
 
6
 
 
 
 
7
 
 
 
 
8
 
 
 
 
9
 
 
 
 
10
 
 
 
 

Additional notes about any item listed in the register above:

6. Umbrella Frame & Rib Integrity

Umbrella failures often start with a single bent rib or a stressed joint. Opening and closing each umbrella slowly while watching the canopy shape is usually enough to spot problems before they become unusable.

 

Number of umbrellas inspected

Overall umbrella frame condition

 

Which rib or spoke is bent, and how many are affected?

 

Please describe the frame damage and whether the umbrella can still be opened safely:

Do all ribs sit evenly when the canopy is fully opened?

 

Please describe how the canopy shape is uneven and where the gap or bulge appears:

Does the canopy open and close smoothly without sticking?

 

What happens when you try to open or close it?

Any of the following umbrella faults observed

 

Which umbrella and which rib are affected?

 

How many joints show cracking, and how visible is the damage?

 

Please describe the handle damage:

Number of umbrellas with frame or rib damage

Is any umbrella considered unsuitable for use in strong wind?

 

What should happen to that umbrella?

Please describe the most serious umbrella issue found and the item it affects:

7. Waterproofing Treatment History

Keeping a simple record of when a water-repellent spray or reproofing treatment was applied makes it easier to judge when another application might be useful. Follow the instructions on whichever product you use, as application and drying steps vary.

 

Has a water-repellent spray been applied to any fabric item in this gear set?

 

Date of the most recent application

 

Please note whether a treatment is planned, and any reasons it has not been done:

Product type or label description of the treatment used

How is the application date recorded?

Approximate time elapsed since the last application

Was the item cleaned before the spray was applied?

 

Please explain how the item was prepared, if at all:

Areas or items that received treatment

Notes on the application method, drying time, or any change in performance noticed afterwards:

Suggested date for the next treatment review

8. Storage, Drying & Care Practices

How gear is dried and stored between uses often affects its condition as much as the weather itself. Please answer based on normal practice rather than an ideal routine.

 

How and where the gear is normally stored

 

Please describe the damp or poorly ventilated space and any steps taken to reduce moisture:

 

What kind of outdoor cover is used?

Is gear fully dried before it is put away?

 

Please describe how damp items are handled and how often this happens:

Are items kept away from direct heat sources such as radiators or heaters?

 

How far away from the heat source are they normally kept?

 

Please describe the heat exposure and any effects noticed on the fabric or coating:

How often is the gear cleaned?

Care practices currently followed

Any care or storage improvements you would recommend:

9. Field Performance During Recent Rain

Real-world use is the clearest test of whether gear is doing its job. Please share what users experienced during recent wet weather.

 

Has any item failed to keep the wearer dry during actual use?

 

What type of failure occurred?

 

Approximately what wind strength was it exposed to, if known?

 

Where did the water enter the boots?

Please describe the most recent rainy occasion when this gear was used, including duration and intensity of the rain:

Please rate the following aspects based on recent use

Poor

Below expectations

Acceptable

Good

Excellent

Kept the wearer dry

Comfortable while moving around

Easy to put on and take off

Dried within a reasonable time afterwards

Held up well in wind

Still presentable in appearance

How did users generally feel about the gear during wet weather?

Overall readiness of this gear set for the coming rainy period

10. Risks, Priorities & Corrective Actions

This section turns your observations into a short action list. Priorities are for planning purposes only and can be adjusted to suit your own circumstances.

 

Possible consequences if the identified issues are left unaddressed

 

Which equipment or items could be affected?

 

Which planned activities could be disrupted?

Highest priority item needing attention

Please rank the following actions in order of urgency, from most urgent to least urgent

Reapply water-repellent spray to outer fabrics

Repair or replace damaged umbrellas

Repair leaking seams or closures

Improve drying and storage routine

Purchase replacement rain gear

Schedule a follow-up inspection

Estimated budget needed for repairs or replacements

Target date for completing the agreed corrective actions

Corrective actions agreed, with the person responsible and expected timeline:

Is a follow-up inspection recommended?

 

Suggested follow-up inspection date

11. Supporting Evidence & Attachments

Photographs and records make it easier for others to understand the findings and to compare conditions at the next audit.

 

Please upload photos of the gear condition, including any damage or wet patches

Choose a file or drop it here

Please upload any maintenance, cleaning, or treatment records you hold

Choose a file or drop it here
 

Are there additional items that still need to be inspected?

 

Please list the outstanding items and the reason they were not inspected:

Any other comments, observations, or context that may be useful:

12. Declaration & Sign-off

Please review your entries before submitting. This record reflects what was observed at a particular time and place and may not cover every possible condition of the gear.

 

I confirm that the information recorded here reflects what I observed during this audit

I understand that this form is an observational record and not a technical or safety certification

Auditor signature

Auditor full name (as signed)

Date and time of submission

Reviewed or countersigned by (name and role)

Would you like a copy of this audit summary sent to you?

 

Where should the summary be sent?

Analysis for Rain Gear & Umbrella Integrity Audit Form

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.


 

Form Overview & Purpose

This Rain Gear & Umbrella Integrity Audit Form is a well-structured seasonal condition-check tool designed to help users systematically evaluate rain gear and umbrella performance before and during wet-weather periods. The form spans ten clearly defined sections covering audit metadata, environmental context, inventory profiling, water repellency assessment, item-level condition registration, umbrella frame integrity, waterproofing treatment history, storage practices, real-world field performance, risk prioritisation, supporting evidence, and sign-off. This breadth ensures that findings are contextualised rather than isolated, which supports more informed maintenance, repair, or replacement decisions.

 

Strengths & Effective Design Choices

The form demonstrates several strong design decisions. Its sectional structure moves logically from administrative context to physical observation to actionable outcomes, which mirrors a natural inspection workflow. The inclusion of conditional follow-up questions (for example, asking for specific leak locations only when leaking seams are reported, or requesting wind-strength details only when an umbrella inversion is noted) keeps the form efficient for respondents whose gear is in good condition while still capturing depth where problems exist. The use of emoji-based condition markers (green, yellow, red) in the water repellency assessment and condition register provides an intuitive, at-a-glance visual shorthand that reduces ambiguity in reporting. The table-based condition register is particularly effective for item-level tracking, allowing each piece of gear to be described, rated, and logged with a treatment date in a single row.

 

Section-by-Section Insights

Audit Overview & Scope

The opening section establishes essential context. Audit reference or record number provides a unique identifier that supports filing, retrieval, and cross-referencing between audits. Audit date anchors the observation to a specific point in time, which is important because gear condition can change between checks. Site, facility, or area covered by this audit and Auditor name identify the scope and responsible observer, supporting accountability and follow-up. The question Primary reason for carrying out this audit captures the trigger context—whether a scheduled check, post-storm review, new gear intake, or complaint investigation—with smart conditional follow-ups for the 'Reported failure or complaint investigation' and 'Other' options. The question Was any gear inspected while it was wet or raining at the time? is a thoughtful addition, since wet conditions can affect visual assessment of fabric behaviour; its follow-up captures both conditions and post-inspection handling steps.

 

Weather & Environmental Context

This section adds valuable interpretive context. Predominant weather during the inspection and Approximate air temperature during inspection (°C) help future reviewers understand the conditions under which observations were made. Recent rainfall pattern in the area captures broader environmental exposure. The multiple-choice question on Environmental exposure factors present in the storage or use area is well-designed, covering road grit, mud, coastal salt, industrial exposure, sunlight, humidity, and ventilation—with targeted follow-ups for grit residue, chemical exposure, and humidity/ventilation situations. This data helps distinguish between normal wear and accelerated degradation caused by specific environmental stressors.

 

Rain Gear Inventory & Usage Profile

Understanding the gear set's composition and usage history is essential for interpreting condition findings. Total number of rain gear items included in this audit sets the scope. The Types of rain gear included in this audit question is comprehensive, covering shells, jackets, ponchos, trousers, boots, umbrellas, hats, and covers, with useful follow-ups for specific categories (e.g., boot height and sole condition, counts of compact umbrellas). Has any of this gear been used in heavy rain during the past 30 days? links recent exposure to current condition. Typical frequency of use and Approximate average age of the gear set provide wear-rate context. The question about a written inventory or label system is operationally smart—knowing whether items are individually identifiable affects how reliably findings can be tracked over time.

 

Water Repellency Assessment

This is a core diagnostic section. The introductory paragraph wisely frames the assessment as observational rather than technical, setting appropriate expectations. Overall water repellency of the gear set uses the three-tier colour system (beading, soaking, leaking seams) with conditional follow-ups that drill into specific affected areas. The simple water bead check question captures whether a hands-on test was performed and how droplets behaved, with a follow-up for pass-through events. The Symptoms of moisture-related wear multiple-choice question covers a practical range of indicators—dull surfaces, flaking coatings, mineral marks, musty odour, lining separation, and colour change—with targeted follow-ups. The open-ended question on the most serious repellency issue and the five-point overall repellency rating provide both narrative and quantitative summaries.

 

Rain Gear Condition Register

The table-based register is one of the form's strongest features. With columns for Rain Gear Description, Water Repellency Condition, Umbrella Spoke/Rib Check, and DWR Waterproofing Spray Applied Date, it consolidates item-level data into a single, scannable format. The pre-populated example rows (e.g., 'Breathable Rain Shell' with a green mark and treatment date, 'Compact Folding Umbrella' with a yellow mark and bent spoke) serve as helpful guidance for respondents. The instruction to write 'Not applicable' for non-umbrella items in the rib check column is a practical touch. The accompanying additional notes field allows for exceptions or nuances that do not fit neatly into the table.

 

Umbrella Frame & Rib Integrity

This section provides dedicated attention to umbrella structural health. Number of umbrellas inspected and Overall umbrella frame condition (with the three-tier straight/bent/broken scale) provide a quick summary. The yes/no questions about even rib seating and smooth opening and closing are practical, hands-on checks with detailed follow-ups. The umbrella faults multiple-choice question covers a thorough range of common failure modes—bent ribs, cracked joints, torn canopy, missing tips, shaft damage, runner faults, handle breakage, and fabric sagging—with specific follow-ups for each. The question about unsuitability in strong wind and its disposition follow-up (set aside, repair, replace, discard) directly supports actionable decision-making.

 

Waterproofing Treatment History

Tracking treatment history is operationally valuable for planning reproofing schedules. Has a water-repellent spray been applied is a clear gateway question with useful follow-ups for both yes (date of last application) and no (planned treatment and reasons). The questions on product type, how the application date is recorded, time elapsed since last application, whether the item was cleaned beforehand, and areas or items treated collectively build a practical maintenance picture. The suggested date for the next treatment review field closes the loop by prompting forward planning.

 

Storage, Drying & Care Practices

Storage and care habits often explain condition findings. The storage method multiple-choice question covers a realistic range of options, with follow-ups for damp spaces and outdoor cover. Is gear fully dried before it is put away? and Are items kept away from direct heat sources? address two common causes of premature degradation. The cleaning frequency and care practices questions capture routine maintenance habits. The closing recommendations field invites the auditor to suggest improvements, which is a constructive addition.

 

Field Performance During Recent Rain

Real-world performance data complements lab-style observation. Has any item failed to keep the wearer dry during actual use? is a critical yes/no question with a detailed failure-type follow-up. The recent rainy occasion description captures contextual use data. The matrix rating question efficiently collects ratings across six performance dimensions (dryness, comfort, ease of use, drying time, wind resistance, appearance) using a five-point scale. The emotion rating and star rating for overall readiness add subjective and summary measures that are easy to interpret at a glance.

 

Risks, Priorities & Corrective Actions

This section effectively converts observations into action. The possible consequences multiple-choice question helps stakeholders understand the stakes of inaction. Highest priority item needing attention forces a clear decision. The ranking question for six corrective actions provides a nuanced urgency ordering. The estimated budget, target date, corrective actions with responsible person, and follow-up inspection recommendation fields together create a practical, trackable action plan.

 

Supporting Evidence & Attachments

The image upload and file upload fields encourage photographic and documentary evidence, which strengthens the audit record and supports future comparison. The question about outstanding items not yet inspected is a good completeness check. The open comments field captures any remaining context.

 

Declaration & Sign-off

The sign-off section is appropriately thorough. The confirmation checkbox establishes that the record reflects actual observations. The optional understanding checkbox clarifies the observational (non-certification) nature of the form. Auditor signature and auditor full name provide accountability. The date and time of submission, countersignature, and copy request fields round out the administrative record.

 

Overall Summary

This form is a comprehensive, well-organised audit tool that balances breadth of coverage with practical usability. Its strengths include logical section flow, effective use of conditional follow-ups to reduce unnecessary questions, intuitive visual condition markers, a structured item-level register, and a clear path from observation to action. The form collects a rich mix of structured data (ratings, dates, counts, selections) and qualitative detail (descriptions, notes, observations), which supports both quick trend analysis and in-depth review. Data quality is supported by contextual questions (weather, usage, age, storage) that help interpret condition findings, and by the sign-off section that establishes record provenance. From a user experience perspective, the form is long but well-segmented; respondents who complete it section by section should find the flow manageable. The conditional logic reduces friction where possible. One area for potential refinement is the overall length—respondents with large gear inventories may find the item-level register and multiple sections demanding. However, for a seasonal audit intended to inform maintenance and replacement decisions, the depth of coverage is proportionate and valuable. The form avoids overclaiming and appropriately frames its outputs as observational records rather than technical certifications.

 

Mandatory Question Analysis for Rain Gear & Umbrella Integrity Audit Form

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.

 

Mandatory Question Analysis

Audit reference or record number
Recommendation: Requiring a unique reference or record number supports reliable filing, retrieval, and cross-referencing between audits. Without it, records may be difficult to distinguish or organise, especially when multiple audits are conducted across different sites or periods. Whether a sequential numbering scheme, a date-based code, or another format is used should be determined by the form creator's existing record-keeping conventions.

 

Audit date
Recommendation: Making the audit date mandatory ensures each record is anchored to a specific point in time. Gear condition can change between inspections, so knowing when observations were made is essential for interpreting findings and planning follow-ups. This field supports chronological record-keeping and trend tracking across multiple audit cycles.

 

Site, facility, or area covered by this audit
Recommendation: Requiring the location or scope identifier ensures that findings can be attributed to a specific place or area. This is particularly useful when audits are conducted across multiple sites, storage areas, or event locations. It supports targeted follow-up actions and prevents confusion between records from different environments.

 

Auditor name
Recommendation: Capturing the auditor's name establishes accountability for the observations recorded. It enables follow-up questions to be directed to the right person and supports record integrity. The form creator may wish to clarify whether a full name, display name, or employee/role identifier is preferred, depending on their internal practices.

 

Primary reason for carrying out this audit
Recommendation: Requiring the audit reason helps categorise the record and provides context for the findings. A scheduled seasonal check, post-storm review, new gear intake, pre-event readiness check, or complaint investigation each carry different implications for how results are interpreted and acted upon. This field supports consistent record classification and prioritisation of follow-up work.

 

Total number of rain gear items included in this audit
Recommendation: Making the item count mandatory establishes the scope of the audit at a glance. It helps verify completeness—reviewers can check whether the condition register covers all items—and supports inventory reconciliation. This is especially useful when audits are compared over time to track gear fleet size changes.

 

Overall water repellency of the gear set
Recommendation: This is a core diagnostic field. Requiring an overall repellency rating ensures that every audit record includes a primary condition indicator, which can be quickly reviewed without reading the full report. The three-tier colour scale (beading, soaking, leaking seams) provides a consistent, interpretable summary. The necessity of this field depends on the form creator's intended use, but for a condition audit it serves as a key summary data point.

 

Number of umbrellas inspected
Recommendation: Requiring the umbrella count ensures that the umbrella-specific sections have a defined scope. It helps confirm that all umbrellas in the gear set were considered and supports consistency between this figure and the item-level register. If no umbrellas are included in a particular audit, the respondent can enter zero, which is itself informative.

 

Overall umbrella frame condition
Recommendation: Making the overall frame condition mandatory ensures that every audit with umbrella items includes a structural integrity summary. The three-tier scale (all ribs straight, bent spoke, broken frame) provides a clear, comparable indicator. This supports quick triage—identifying umbrellas needing repair or replacement—without requiring detailed reading of follow-up notes.

 

Has a water-repellent spray been applied to any fabric item in this gear set?
Recommendation: Requiring this treatment-history gateway question ensures that every record captures whether reproofing has been performed. This is important for planning future maintenance cycles and for interpreting repellency findings—a gear set with no recent treatment may show expected wear rather than unexpected failure. The yes/no structure keeps this quick to answer while the follow-ups capture relevant detail.

 

Has any item failed to keep the wearer dry during actual use?
Recommendation: This field captures the most direct measure of gear performance—whether it actually kept users dry. Requiring a response ensures that real-world failure data is not omitted, which is critical for prioritising repairs or replacements. The yes/no format is quick, and the conditional follow-up captures failure specifics only when relevant.

 

Highest priority item needing attention
Recommendation: Requiring a priority selection ensures that every audit concludes with a clear, actionable top-priority item. This prevents findings from remaining purely descriptive and supports efficient resource allocation. The inclusion of a 'No action needed at this time' option ensures the field is answerable even when gear is in good condition.

 

I confirm that the information recorded here reflects what I observed during this audit
Recommendation: This confirmation checkbox establishes that the respondent attests to the accuracy of their observations. Requiring it supports record integrity and signals to the auditor that the submission is a deliberate, reviewed entry. It is a standard practice for observational records, though its specific necessity depends on the form creator's internal governance requirements.

 

Auditor signature
Recommendation: A signature provides a formal attestation of the audit record. Requiring it supports accountability and record authenticity, particularly when audits may be reviewed by others or retained over time. The form creator should ensure their platform supports an appropriate signature capture method (e.g., drawn, typed, or uploaded) that suits their workflow.

 

Auditor full name (as signed)
Recommendation: Requiring the printed full name alongside the signature ensures the record is legible and attributable, even if the signature itself is stylised or difficult to read. This supports reliable identification and follow-up. It complements the signature field and the earlier auditor name field, though the form creator may wish to consider whether capturing the name twice is necessary or whether one instance could be auto-populated.

 

Overall Mandatory Field Strategy Recommendation

The form's mandatory field strategy is generally well-balanced. Mandatory fields are concentrated in three areas: administrative identification (reference number, date, site, auditor name), core condition indicators (item count, repellency rating, umbrella count and frame condition, treatment history, field failure status), and accountability (confirmation, signature, printed name). This distribution ensures that every completed audit includes the minimum data needed for it to be useful, traceable, and actionable.

 

Key observations and recommendations:

 
  • Depth vs. completion rate: With 15 mandatory fields spread across a long form, the required-field burden is moderate. The conditional follow-up logic is effective at reducing unnecessary questions, which helps maintain completion rates. However, form creators should monitor whether respondents abandon the form at any particular section and consider whether any mandatory field could be made optional without significantly reducing data utility.

  • Conditional logic: The form already uses conditional follow-ups effectively (e.g., umbrella-specific questions only when umbrellas are present, treatment date only when spray has been applied). This is a strong practice. Consider whether the umbrella frame condition question could be conditionally required only when the umbrella count is greater than zero, to avoid forcing a response when no umbrellas are in scope.

  • Field placement: Mandatory fields are reasonably distributed from the beginning to the end of the form, which avoids clustering all required questions in one block. The sign-off section appropriately places mandatory attestation fields at the conclusion, after all observations have been recorded.

  • Duplicate name capture: The form captures the auditor's name twice—once in the overview section and once in the sign-off section. While this may serve different purposes (identification vs. attestation), the form creator may wish to evaluate whether both instances need to be mandatory or whether one could reference the other.

  • Proportionality: The mandatory fields are proportionate to the form's purpose as a condition audit. None appear to demand information that is universally or legally required; rather, they support the operational goal of producing a complete, attributable, and actionable audit record. The form creator should periodically review mandatory field selections based on respondent feedback and the practical needs of those who process the audit results.

 

To configure an element, select it on the form.

To add a new question or element, click the Question & Element button in the vertical toolbar on the left.