There is NO DELETING of unused reports in the queue
next → next up
d
dcoates
I have been a subscriber of your software service (ISN) for many years. I was excited to be able to try the ISN report writer for the 1st time in an upcoming inspection. So, I pulled up many test reports to look at and try to learn the system. In the process, I have many templates active in older reports. I was trying to delete the many templates and discovered there was NO WAY TO DELETE a report. This is a failure in many ways. As inspectors’ things can change on a dime and we have to adjust on the spot. The fact that I cannot remove a template from an inspection is a very difficult position to be in. I am pleased that you think that home inspectors are mistake free, especially with the 45 pages of information that we add to every report. However, mistakes do happen, even to home inspectors. Why was this key function left out of this report writer? This may reflect negatively on your ability to retain clients. I hope that you install a delete button very soon. I cannot be only one who does not want to fight through old reports that will never leave the queue.
Janaya Fix - Product Management
updated the status to
next → next up
Janaya Fix - Product Management
dcoates - My Name is Janaya and I am the Head of Product for our Report Writer product. Thank you for being a longtime ISN subscriber and for sharing this candid feedback. I’m sorry this experience has been so frustrating, especially when you were taking the time to learn the Report Writer before using it on an upcoming inspection.
You’re absolutely right that inspectors need the flexibility to correct mistakes and adapt quickly. Test reports that are no longer needed shouldn’t leave you fighting through a cluttered queue, and I understand why being unable to remove a template or delete a report feels like a significant gap.
I can ask my team to delete the reports for you if that will help. I will also queue up this work for them to create the ability to delete. There are some reasons why we did not initially add this functionality, but I think it is worth reconsidering.