# Your incident declaration form is (probably) too long: The power of concise reporting

DevFeed: [Your incident declaration form is (probably) too long: The power of concise reporting](<https://devfeed.tech/articles/your-incident-declaration-form-is-probably-too-long-the-power-of-concise-reporting-12035.md>)

Original publisher: [Read original article](<https://incident.io/blog/the-power-of-concise-reporting>)

Author: Matilda Hultgren

Published: 2023-11-27T13:43:56Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Forms](<https://devfeed.tech/topics/forms.md>)

Tags: [forms](<https://devfeed.tech/tags/forms.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [report](<https://devfeed.tech/tags/report.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article argues that overly long incident declaration forms delay reporting and can lead to incomplete, inaccurate, or underreported incidents. It highlights that forms with three to six fields can support declaration in under a minute, while forms with more than ten fields nearly double declaration time, and recommends streamlining forms through conditional fields and customization.

## Source excerpt

Do you have a lot of required fields on your incident declaration form? You may be creating lots of extra work for your responders.