Site diaries and daily reports are filled out every day in Dashpivot. Conditional logic lets you hide follow-up fields until a user indicates something worth capturing actually happened that day — keeping forms clean on normal days and ensuring the right details are captured when they matter.
The Scenario
Site diaries in Dashpivot are filled out every day on site. Most of the time, the answer to questions like "Were there any delays on site today?" or "Do any variations need to be recorded, processed, and approved?" is no — and nothing more needs to be captured.
But on the days when something does happen, you need the right follow-up fields to appear immediately in the Dashpivot form — duration of the delay, a description, photos — so the details get captured on the spot. Those fields probably aren't applicable 95% of the time, but when they are important, you definitely want them in the form.
Without conditional logic, you either show those fields all the time (cluttering the Dashpivot form on normal days) or leave them out entirely (risking missed information when something does go wrong).
Conditional logic solves this — and for teams running more complex Dashpivot site diaries with multiple delay types, variation categories, or incident triggers, the same approach can be applied to multiple questions in the same form, each with their own independent logic block.
How It Works
A Yes/No field in the Dashpivot template is set as the trigger. When a user selects "Yes", a set of follow-up fields appears automatically in the form — such as a date and time range for the delay duration, a text field for a description, and a photo field for evidence. When the user selects "No", those fields stay hidden and the Dashpivot form remains clean.
Follow-up fields can be made required in Dashpivot, so if a delay or variation is flagged, the user must fill in the details before the form can progress. Photo fields can be left optional — it's up to you based on your team's needs.
The same logic can be applied to multiple Yes/No fields in the same Dashpivot template — delays and variations can each have their own independent logic block.
How to Set It Up
Setting up conditional logic on a Yes/No field in a Dashpivot site diary template follows the same steps as any other conditional logic setup.
See How to set up conditional logic in Yes/No and List fields on Dashpivot Web for full instructions.
Related Articles