Find the pages that hold Rovo back.

Rovo can only answer as well as your Confluence pages allow. DocLamp reviews every space, marks what makes a page hard to use, and tells your team where to start.

Try it free on the MarketplaceRead the docs

For Confluence Cloud. Free for teams of up to 10 users.

Engineering Handbook

On-call rotation

Owned by the Platform team

Every incident goes to the engineer on call, who must acknowledge it within the SLA.

Business acronyms never spelled outHigh impact

The rotation is currently planned in a spreadsheet. It moves to the new scheduling tool soon.

Unanchored relative datesLow impact

Escalation

TODO who to call when nobody answers.

Empty or unfinished pageHigh impact

Known gaps in this runbook are tracked in OPS-142.

Jira reference as plain text instead of a linkMedium impact

An example page with the issues DocLamp would report. Each one comes with how to fix it.

What you can count on

  • Built on Atlassian ForgeDocLamp runs inside Atlassian Cloud. Your content never leaves it.
  • Restricted pages stay restrictedDocLamp never reads them, and tells you how many it skipped.
  • Same content, same scoreConsistent rules and no AI service, so results don't drift from one day to the next.
  • Your pages stay yoursDocLamp never edits a page. A report is published only when someone asks for one.

Rovo answers from your pages, as they are

“…you will have the best results when your Confluence site is full of detailed, up‑to‑date content.”

Atlassian, Use Rovo to search for answers

DocLamp shows, space by space, where your pages fall short of that and what to fix first.

What DocLamp checks

DocLamp reads your pages the way a careful editor would, with Rovo in mind.

Structure
Pages that are unfinished, or hard to follow for someone who wasn't there when they were written.
Clarity
Wording that only insiders understand slows newcomers down. It misleads Rovo too, which can borrow a meaning from another page.
Freshness
Statements written for a given moment that may no longer be true.
Connections
Pages nobody links to, cut off from the rest of your documentation.
Findability
Spaces organized in a way that makes the right page hard to find.
Jira context
Work your pages talk about, without a link Rovo can follow to Jira.

From install to fixed pages

DocLamp does the reading in the background. Your team steps in only to fix what it finds.

  1. Choose the spaces

    A site admin picks the spaces DocLamp may read. Nothing is read before that choice, and an excluded space is never touched.

  2. Read the scores

    The overview shows the site score, how many pages are well prepared and what holds each space back. Inside a space, page quality and structure are scored separately. The lower one counts, because a single weak spot is enough to mislead Rovo.

  3. Fix what weighs the most

    Pages with several issues come first. Issues are ranked by impact, so starting at the top gains the most points. Each one says how to fix it and lists every page it affects.

  4. Watch the score move

    Every space is reviewed again each day. On the space's home page, the DocLamp macro shows the trend and the issues your team has fixed.

Example of the DocLamp overview.
The Engineering Handbook space three weeks later, with the DocLamp macro on its home page.

The score where your team works

Add the DocLamp macro to a space's home page. Everyone who opens the space sees where it stands, which way it is heading, what the team has already fixed and how its new pages compare with older ones.

  • It updates itself after every analysis.
  • It shows only the space it sits in, and only to people who can see that space.
  • One click opens the full analysis in DocLamp.
  • You add it in a few seconds. DocLamp never edits your pages for you.

When teams turn to DocLamp

Before rolling out Rovo

See which spaces are ready and which need work, so Rovo starts from content your team trusts.

When Rovo's answers disappoint

Check the spaces it draws from for undefined jargon, statements that may have aged and pages cut off from the rest.

To keep documentation in shape

Daily monitoring shows which way each space is heading, and the macro keeps the score in front of the team.

To set documentation guidelines

DocLamp points out the issues that several spaces share. They come from habits, not one-off slips, and call for a guideline everyone follows rather than space-by-space fixes.

Your content stays in Atlassian

DocLamp runs entirely on Atlassian's own platform. We, its publisher, can't read your pages or the results stored for your site.

  • You choose which spaces DocLamp reads. Nothing is read before that choice, and an excluded space is never touched.
  • Restricted pages are never read. The app tells you how many it skipped.
  • People only see results for spaces they already have access to.
  • Your pages are never edited. A report page is created only when someone asks for one.
  • Uninstalling the app erases everything it stored, within 28 days.
  • No AI service and no tracking, in the app or on this site.

Read the security details

Atlassian Cloud

Your Confluence siteOnly the spaces you chose

reads pages

DocLampRuns on Atlassian Forge

keeps results in

Forge hosted storageSame location as your site's data

No outside destination

Anywhere else, including usYour pages and results never get here
We only receive app logs with counts and durations, which a site admin can turn off, and the licensing contacts Atlassian shares with app publishers.

Documentation drifts. DocLamp keeps watch.

Your teams keep writing, editing, moving and archiving pages. Each change can bring an issue back: an acronym nobody spelled out, a statement that will age, a page left without links. DocLamp reviews every space again each day and tells you when one slips.

  1. Day 1

    See where every space stands

    Choose the spaces that matter. On most sites, their scores appear within minutes.

  2. Every day

    Every space is reviewed again

    New pages, recent edits and new spaces are checked too. Your fixes show the next day, and DocLamp counts every issue your team has fixed.

  3. When a score drops

    You see it first

    DocLamp flags the space at the top of its overview, with what got worse, so you can act while it is still small.

  4. After the clean-up

    See what your team writes now

    DocLamp compares the pages created in the last 30 days with older ones, so you know whether your team's writing habits are changing.

  5. Every month

    A history that keeps growing

    Each month adds a point to the curve, and each year one that stays for as long as DocLamp is installed. Your starting score stays too, so you always see how far you have come.

Pricing

Free for teams of up to 10 users. Larger sites pay per user, billed by Atlassian through the Marketplace, and every plan starts with a free trial of at least 30 days.

In the last ten days of the trial, DocLamp offers a summary you can publish for your management: the site score, where it started and the issues fixed. An annual subscription gets one each year, in the month before it renews.

Every plan includes

  • Every check, on every space you choose
  • Daily monitoring, and your score history for as long as you use DocLamp
  • The DocLamp macro and reports you can publish
  • Email support, with replies within 24 hours
Price per user per month, by number of users on your site
Users on your sitePer user, per month
Up to 10Free
11 to 100$1.20
101 to 250$1.00
251 to 1,000$0.75
1,001 to 2,500$0.45
2,501 to 5,000$0.30
More than 5,000$0.15 or less

US dollars, before tax. The Atlassian Marketplace shows the exact price for your site, monthly or yearly, before you buy.

Questions

Something else? We're happy to help.

Email uscontact@doclamp.com

Does DocLamp send our content to an AI?

No. The analysis runs inside Atlassian Cloud, applies fixed rules and calls no AI service. The same content always gets the same score.

How is DocLamp different from archiving apps?

Archiving apps help you retire old pages. DocLamp looks at the pages you keep: how they are written, linked and labeled, so that Rovo and your colleagues can use them.

Can DocLamp see our restricted pages?

No. It reads with its own Atlassian account, which view restrictions exclude. Each space's page says how many pages were skipped, counting only pages you can already see.

Will DocLamp change our pages?

Never. It creates a new page only when someone asks for a report, filed under “DocLamp reports” in the space they choose.

How long does the first analysis take?

It starts as soon as a site admin has chosen the spaces, in the background. On most sites the overview fills up within minutes. Up to 10,000 pages are analyzed per space.

Can we share the results with our management?

Yes. Publish any space's analysis as a Confluence page in one click. In the last ten days of a trial, and in the month before an annual subscription renews, DocLamp also offers a site summary you can publish, with the site score and where it started. It quotes only site-wide totals, no page and no space.

Does it work with Confluence Data Center?

No. DocLamp is for Confluence Cloud only, because it is built on Atlassian Forge, which runs in Atlassian Cloud.

Which languages does the app speak?

English and French. Each person sees the app in their Atlassian profile language. Most checks work in pages written in any language; page wording is read in English, French, German and Spanish.

Can we take our data with us?

Yes. From the overview, open Detailed curve and export every score DocLamp has kept, space by space, as a CSV file: the first analysis, and the daily, monthly and yearly points.

What happens if we uninstall it?

Atlassian keeps the app's storage for 28 days, in case you reinstall, then deletes it. Nothing is kept anywhere else.

Start with the spaces that matter most.

Pick a few spaces, read their scores and fix the pages that weigh the most. Free for teams of up to 10 users.

Try it free on the MarketplaceRead the docs