The platform

Three offerings. One set of checked procedures.

Owners check the manual and keep it current. People are guided through it. Authors write it from the application. All three work from the same procedures, each checked against the live application before anyone relies on it, with the evidence behind every step.

For the manual’s owner

Cicerone | Owner Check the manual and keep it current

Know which lines of your manual are wrong before anyone follows them, and keep them right through every release. Owner takes the two things you already have, the application and the manual that describes it, and tells you whether they still agree.

Pick the application by clicking its window, then add the manual in whatever form it is in. Cicerone splits the manual into procedures, works through each one against the live application, and records every disagreement against the line of the manual that produced it. A step it cannot check safely, such as signing in or anything that would change data, is reported as not checked, never as a defect and never as a pass. In applications that need a login, checking happens inside a session your own person has signed in to; Cicerone never holds the password.

Instructions you own

Paste plain-English instructions and get back a portable navigation script that you own: a plain file, readable by people, that names each target by what a person sees rather than by hidden technical selectors. When the software moves, Owner proposes the correction and you approve it before anything is published. Because the script is yours, you are not tied to a vendor’s tour builder.

The evidence view

For every step: what Cicerone saw on the screen, which control it chose, why, and how sure it was, and why it refused when it refused. When a report calls a step broken, your security, IT or process reviewer can check Cicerone’s work rather than take its word.

Publish what passes

When a procedure passes, you publish it to your people with one decision. If it later stops matching, publication is withdrawn until it is checked again. The audit is the way to start.

For the people who follow it

Cicerone | User Guide your people

Your people get the right step at the moment they need it, inside the application they are already using, instead of a document in another window or a tour someone wrote months ago.

A new joiner opens the application. A small card names the next control and shows where it is: the exact step you checked and published. They click; the card moves on. When Cicerone is not certain which control a step means, it highlights the two or three most likely and asks the person to choose, rather than guessing. If the screen no longer matches, the card says so and offers a way back. It never clicks or types for them, never holds their password, and stops serving a procedure the moment it is withdrawn.

For the technical author

Cicerone | Author Write the manual from the app

Get a user manual for an application that has none, starting with nothing but the application itself. Bring an old manual up to date the same way.

A technical author works through the application in a test environment while Cicerone records each control by the name a person sees, the order of the steps and what each one does, and writes the user manual from that: named controls, ordered steps, and a last-checked date on every procedure. It writes in words first, naming each control as a person sees it, so the manual does not depend on screenshots that go stale. Each procedure is backed by the same navigation script that Owner checks and User guides, so the manual starts life already checked, and after each software release the procedures are checked again and the differences are shown.

The evidence view

Every step of the manual carries its evidence: what Cicerone saw, which control it recorded, why, and how sure it was. A reviewer can check the manual’s work before it is published, rather than take it on trust.

Two environments

Not covered: Citrix or remote desktop, CAD, and drawing or diagram canvases. They show a picture of the software with no named controls, so there is nothing reliable to point at.

Talk to us about the platform

Have a written manual and want to know where it stands? Book the audit. Looking at guided procedures for your people, a manual written from your application, or a Windows desktop application? Tell us which, and we will talk it through.

Request access (Tally, no name needed)

Answers are kept at the named provider or in our inbox, never in a system we build. Role is useful; name and company are not asked for.