April 3rd, 2026

Attik Update - Inspector Google sign-in & safer logins, smoother file uploads, agreements & reports polish & field app updates


Summary

  • Sign-in and accounts: Inspectors can use Google sign-in on the Mobile App, and the system more consistently blocks sign-in for inactive users or accounts without an active company membership—on the web tools, backend, and the inspector mobile app.

  • Files and uploads: Report and workorder uploads now follow a more reliable upload path with support for larger files (up to about 25 megabytes where applied), which reduces failed uploads and aligns limits across tools.

  • Agreements and contacts: You can archive agreements, see clearer handling of signed agreement snapshots, and benefit from fixes to contact tags and merge fields used in agreements and emails.

  • Money and accounting: Card payments through Guardian now ask for billing postal code when required for verification, and QuickBooks-related screens better reflect who is treated as the payer on invoices plus job status sync options.

  • Radon, scheduling, and the workorder: Radon tooling improves equipment transfer flows (including clearer labeling), ties radon-related calendar events to equipment, and adds shortcuts from radon data to the related workorder. Scheduling respects inspector-requested assignments better when jobs move, quote scheduling logic is refined, and editing charges can automatically suggest event end times based on duration.

  • Client reports and the portal: Client-facing report viewing got layout and readability improvements—including defect captions, summary sections, and media counts—with several targeted fixes; the online quote experience was tightened so client-side auth only applies where it should.

  • Attik Mobile: The field app shows sub-item descriptions and whether agreements are signed on the schedule, improves how required dates and times read on inspections, lets you add photos from the device into attachments, shows equipment details on events, supports selecting and copying text more easily, uses over-the-air update infrastructure for future app updates, and uses clearer error titles on login and verification screens.

New Features

Sign in with Google for inspectors (Mobile App)

  • What changed: Inspectors can sign in with Google on the mobile app, aligned with updated authentication on the web and server.

  • Before: Sign-in relied on the previous email and one-time-code flow only.

  • Now: Google is available as a sign-in option where your organization uses it.

  • Why it matters: Faster, familiar sign-in in the field with fewer typing errors.


Over-the-air update support for the mobile app (Mobile App)

  • What changed: The mobile app is set up to receive over-the-air updates.

  • Before: Most changes required a full app store release to reach devices.

  • Now: Certain updates can be delivered to the app without waiting for a store release.

  • Why it matters: Bug fixes and small improvements can reach inspectors sooner when used.


Agreement signed status on the schedule (Mobile App)

  • What changed: The mobile schedule surfaces whether an agreement is signed.

  • Before: That context was harder to see while routing the day.

  • Now: Signed status is visible on the schedule card flow.

  • Why it matters: Inspectors and leads can see paperwork status at a glance before the job.


Agreement archive and signed agreement snapshot

  • What changed: Agreements can be archived on the workorder, and the experience around signed agreement snapshots and related UI was improved.

  • Before: Limited or no archive workflow and rougher handling of signed views.

  • Now: Clearer lifecycle for agreements and how signed copies appear in the product.

  • Why it matters: Easier housekeeping and a clearer record of what clients signed.


Radon: equipment transfer experience and workorder links

  • What changed: Radon calibration and transfer flows were reworked; labels now emphasize equipment transfers, validation and state handling improved, and workorder links and actions appear in the right places from radon event data.

  • Before: Older transfer model and weaker navigation back to the job.

  • Now: A clearer transfer workflow and quicker jumps to the related workorder.

  • Why it matters: Less confusion when moving equipment between inspectors or events and faster access to the job record.


Radon equipment tied to calendar events

  • What changed: Calendar and event handling integrates radon equipment events so scheduling reflects equipment-aware context.

  • Before: Events did not fully reflect radon equipment behavior.

  • Now: Radon equipment is represented more consistently on the calendar side.

  • Why it matters: Office staff can align equipment and appointments with fewer mistakes.


QuickBooks: role-based payer on invoices and job status sync

  • What changed: Invoice contact selection respects role-based rules, and the interface reflects QuickBooks job status sync more clearly, with related backend fixes for display names and automations.

  • Before: Payer contact behavior and sync controls were less aligned with how roles work in Attik.

  • Now: Invoicing and sync setup better match your staff structure and QuickBooks expectations.

Quickbooks Invoice Settings Section in the Attik Integration Settings
  • Why it matters: Cleaner books and fewer wrong contacts on QuickBooks invoices.


Improvements

Larger, more consistent file size limits for inspection attachments

  • What changed: Attachment size limits were raised and aligned (including about 25 megabytes where specified).

  • Before: Smaller or inconsistent limits caused unexpected rejections.

  • Now: Reasonable headroom for typical photos and PDFs.

  • Why it matters: Less frustration when uploading evidence from the field.


Presigned uploads for reports and workorder files

  • What changed: Uploads increasingly use direct-to-storage presigned URLs with follow-up finalization for a smoother path that avoids common browser and session issues.

  • Before: Uploads were more sensitive to cross-origin and session edge cases.

  • Now: More reliable uploads for reports and workorder file areas.

  • Why it matters: Fewer “upload failed” moments during busy report and documentation work.


Client report reading experience

  • What changed: Layout and styling improvements on report info cards, measured sections and collapsibles, text wrapping, photo modal captions, summary expansion behavior, and media count presentation; report “skin” refinements continue from prior work.

  • Before: Tighter layout, occasional clipping, and harder-to-scan summaries and media.

  • Now: Reports read more cleanly on desktop and small screens.

  • Why it matters: Clients and agents see a more professional, readable report.


Booking and quote detail presentation

  • What changed: Booking detail panels were streamlined for clearer display of key fields.

  • Before: Some details were harder to scan or inconsistently shown.

  • Now: A more consistent, readable layout.

  • Why it matters: Schedulers spend less time hunting for the same facts on every job.


Preserve inspector-requested assignments when rescheduling

  • What changed: When jobs move on the calendar, inspector-requested assignments are kept rather than dropped.

  • Before: Reschedules could clear or ignore those requests.

  • Now: Requested staffing survives the move.

  • Why it matters: Honors commitments made to inspectors and reduces rework.


Event duration and end time when editing charges

  • What changed: Editing charges can automatically derive end times from duration for events.

  • Before: End times had to be managed more manually.

  • Now: Duration-based suggestions reduce manual clock math.

  • Why it matters: Faster, more consistent calendar blocks tied to billed work.


Equipment quantities on new inspections

  • What changed: When inspections are created, equipment quantities use safer defaults and validation so only sensible positive numbers are stored.

  • Before: Missing or invalid quantities could propagate into bad data.

  • Now: Fallbacks and validation keep equipment counts trustworthy.

  • Why it matters: Reporting and scheduling that depend on equipment counts stay accurate.


Report preview and attachment cleanup

  • What changed: Report preview and attachment finalization behavior was cleaned up alongside the new upload approach.

  • Before: Stray or confusing preview and attachment states in some flows.

  • Now: Cleaner handoff from upload to finished attachment or preview.

  • Why it matters: Less confusion before publishing or sending a report.


Agent Assist guidance for general report questions

  • What changed: The knowledge behind report chat was tuned so general questions get gentler, more appropriate guidance.

  • Before: The assistant could feel overly rigid or off-topic for broad questions.

  • Now: More helpful tone and relevance for everyday “how do I…” questions.

  • Why it matters: Inspectors get unstuck without feeling scolded by the helper.


Timezone handling in jobs and agreements

  • What changed: Time zones are handled more consistently across job and agreement experiences.

  • Before: Occasional confusion near zone boundaries.

  • Now: Clearer alignment between displayed times and stored values.

  • Why it matters: Fewer “wrong time” surprises for clients and staff.


Data Exports, quotes, and permissions

  • What changed: Inspectors can access Data exports when their role and permissions allow. Quote-related copy and permission types used in the product were updated.

  • Before: Inspectors were blocked from data exports in the same way as before this change; quote wording and permission labeling may have been unclear or too narrow.

  • Now: Permitted inspectors can use data exports; quotes and permissions read more clearly for everyday use.

  • Why it matters: Trusted field staff can pull exports they are allowed to run; less confusion in quotes and access labels.


Sub-item descriptions on the mobile schedule (Mobile App)

  • What changed: Schedule cards can show descriptions for sub-items where available.

  • Before: Only top-level context was obvious on the card.

  • Now: Line-item detail is visible at a glance.

  • Why it matters: Inspectors see scope detail before arriving on site.


Equipment details on inspection events (Mobile App)

  • What changed: Events can show equipment details in the inspection view.

  • Before: Equipment context was thinner on mobile.

  • Now: Field staff see what equipment applies to the event.

  • Why it matters: Better preparation and fewer “wrong gear” moments.


Add photos from the device to attachments (Mobile App)

  • What changed: Attachments integrate with the device photo picker for adding images.

  • Before: Adding photos was less integrated with native picking.

  • Now: Familiar camera-roll style selection for inspection attachments.

  • Why it matters: Faster documentation from photos already on the phone.


Selectable text in inspection views (Mobile App)

  • What changed: Text in inspection areas supports selection for copy and accessibility-style use.

  • Before: Some blocks were hard to select.

  • Now: Easier to copy addresses, notes, or codes.

  • Why it matters: Less retyping when sharing details into messages or maps.


Bug Fixes

Guardian card payments: billing postal code required

  • What changed: Card payments through Guardian now collect billing ZIP or postal code when needed for address verification.

  • Before: Missing postal data could cause declines or processor errors.

  • Now: The form prompts for what the processor expects.

  • Why it matters: Smoother checkout and fewer mystery payment failures.


Pay at Close: order totals and client details

  • What changed: Logic that updates Pay at Close order totals and resolves client information was refined.

  • Before: Edge cases could produce inconsistent totals or buyer or client context.

  • Now: Totals and client-related data align more reliably with how the job and payer are set up.

  • Why it matters: Fewer surprises on invoices and payment-at-close flows.


Contact tags and merge fields for agreements and messaging

  • What changed: Validation and behavior around contact tags and merge fields were corrected alongside agreement work.

  • Before: Tags or fields could fail or insert incorrectly.

  • Now: More reliable personalization and tagging.

  • Why it matters: Client-facing emails and agreements show the right names and labels.


Web auth: magic links, session, and user status

  • What changed: Web authentication was tightened for user status, magic-link error handling, and session membership behavior.

  • Before: Some magic-link or session edge cases failed or showed inconsistent status.

  • Now: Sign-in flows and active-session behavior are more reliable.

  • Why it matters: People spend less time fighting the login experience.


Company switching, archived reports, payroll filters, and settings navigation

  • What changed: Fixes for switching companies, how archived reports appear, payroll filtering, and which settings navigation options show for a user’s permissions.

  • Before: Wrong company context, missing or wrong lists, or incorrect menu visibility.

  • Now: Expected behavior across those areas.

  • Why it matters: Daily work in multi-company or payroll-heavy offices is less error-prone.


Client portal and quote routes: authentication scope

  • What changed: Client edge authentication is limited to quote-related paths so other experiences are not unintentionally gated.

  • Before: Auth could leak into areas where it did not belong.

  • Now: Quotes stay protected without breaking unrelated pages.

  • Why it matters: Clients see fewer odd login prompts on public-style pages.


Reports: indicated items, sewer scope signature line, and related layout fixes

  • What changed: Corrections to how certain report indicators render and removal of an inappropriate sewer scope signature line where it did not belong, plus related layout fixes.

  • Before: Misleading indicators or extra signature noise.

  • Now: Report sections match the intended template behavior.

  • Why it matters: Clearer deliverables for clients and fewer template arguments.


Mobile: required info date and time display (Mobile App)

  • What changed: Required information date and time values are formatted consistently on inspection.

  • Before: Some values were hard to read or oddly formatted.

  • Now: Human-readable dates and times.

  • Why it matters: Inspectors confirm required details faster on site.


Mobile: login and verification error titles (Mobile App)

  • What changed: Error alerts on login and OTP verification use consistent, clear titles.

  • Before: Titles were inconsistent or vague.

  • Now: Users immediately know which step failed.

  • Why it matters: Faster recovery from typos or expired codes.