Latest Updates

What's New You can now hide inspector images and names on all unsigned agreements (both existing and future) with a new global setting under Agreements. Why It Matters This is especially useful for companies offering ancillary services where the primary inspector isn't performing the service. When enabled, no inspector photo or name will appear on unsigned agreements, allowing you to maintain proper credential representation and avoid displaying the wrong inspector for specialized services. Please note that this setting does not impact placeholder text set for your agreements. Details New setting available under Agreements in your dashboard Applies globally to all unsigned agreements (existing and future) When enabled, no inspector photo or name will display on unsigned agreements Particularly helpful for ancillary services performed by certified specialists Timing & Audience This update is available to all users as of today.

What's New This week's release includes fixes for issues affecting final report navigation, signature field display, and placeholder rendering in the Web Editor. What We Fixed Table of Contents navigation on mobile browser — Clicking a section in the TOC side menu would intermittently fail to navigate to the correct section, especially after scrolling up and re-selecting. Signature field displaying when empty — Empty or removed signature fields were still appearing in the report preview. Edit buttons were also getting cut off when a signature section landed at the bottom of a page. Both are resolved. Inspector notes placeholder rendering <p> tags — The {{INSPECTOR_NOTES}} placeholder was outputting raw HTML tags in the Web Editor, Web Viewer, and PDF instead of clean text.

What's New We fixed an issue where updating tags on agent records wasn't always triggering the "record updated" signal in Zapier, which meant some tag changes weren't being picked up by Zapier workflows. What We Fixed Agent record tag changes not triggering Zapier updates — Adding or removing tags on an agent record now correctly fires the "record updated" event, ensuring your Zapier workflows run as expected. Note: A similar issue exists for client record tag updates and is being addressed in an upcoming fix.