How these docs stay fresh

Most help centers go stale. A new button gets added, a label gets renamed, a step gets simplified — and six months later the screenshot still shows the old version. We’ve all been there.

The Assure Pro docs are built to solve that problem. This page explains how, and what you can do if you ever spot a page that doesn’t match what you’re seeing on screen.

The promise

Every page describes the product as it works today. When the Assure Pro team ships a change, the matching help page is updated as part of the same release. You should never see a step here that doesn’t exist in the product, or miss a step that does.

If a page tells you to click New invoice and the button now says Create invoice, that’s a bug — see If something looks off below.

How the updates happen

Each page lists the parts of the product it covers — the screens you see, the buttons you click, the forms you fill out. When the Assure Pro team makes a change to any of those parts, two things happen:

The change is flagged against every page that mentions it.
An updated draft of each flagged page is prepared, reviewed by a human, and published with the next release.

The draft is written by Assure Pro’s docs assistant — the same kind of writing tool many help centers now use behind the scenes — and then a person on our team reads it before it goes live. The result is that pages update with the product, not weeks or months later.

You don’t have to do anything for this to work. The page you’re reading right now was checked the last time the related product code shipped.

What’s actually checked

For each page, the docs assistant checks:

Button and tab names — if a label changed, the page is updated to match
The order of steps — if a step was added, removed, or simplified, the instructions follow
Form fields — if a new field appeared or an old one was retired, the page reflects it
Mentioned limits — file size caps, time-out windows, retry counts — these get re-pulled from the product
Status names — if Awaiting signature becomes Pending signature, the doc tracks the rename

Screenshots are added by hand and updated separately when a screen changes meaningfully. We don’t replace a screenshot just because a pixel moved.

What’s not auto-updated

A few things still need a human touch and don’t get refreshed automatically:

Tips and “what to watch out for” callouts — added by people who know the workflow
Tax-domain context — the explanation of why an 8879 matters or how an extension affects deadlines
Recommendations — when a doc says “most firms leave this on,” that’s a judgment call, not a fact pulled from code

These sections only change when we decide they need to.

If something looks off

If you spot a page that doesn’t match what you see in the product, the fastest fix is to let us know:

Message your team from inside the portal — they can flag it for us
Reach out to Assure Pro support if you’re a firm admin

A doc that doesn’t match the product is a real bug, and we treat it like one. Most are fixed in the next release.

Why we do it this way

A help center is only useful if you trust it. If you’ve ever followed instructions that didn’t match the screen in front of you, you know how quickly that trust evaporates.

By tying every page to the part of the product it covers, and re-checking the page whenever that part of the product changes, we keep the docs in step with what you’ll actually click. It’s a small thing, but it’s the difference between docs that help and docs that frustrate.

What’s next

Browse the main sections — the sidebar is grouped by what you do day to day
Getting started — the orientation tour, if you’re brand new