The Nintex DocGen assessment report, page by page

The report is built to be read top to bottom by a busy owner, then worked section by section by the admin:

• The answer — the estate’s overall standing in one line, with the counts behind it.
• The report card — every area graded; “not assessed” said out loud, never assumed healthy.
• What is at risk for the business — findings grouped by effect, worst first: what may not generate, what users may pick wrongly, what may send empty.
• The decisions — the questions only your organization can answer, with the usual answer marked.
• The plan and its gates, quick wins, and the worklist by action — split honestly between you, fixes applied after your approval, and the DocGen admin.
• What still needs a human, how the estate is built, and upgrade risk — plus a Findings CSV for your tracker.

Two readers, one document. The owner reads the answer, the report card and the business-risk section, and makes the handful of decisions only the organization can make. The DocGen admin works the worklist, applies the structural fixes, and re-scans until the open rules go silent. And when the admin changes — the moment most estates lose their history — the latest report plus the decision register is the handover: what was found, what was decided, what was verified, and what is still waiting for a human. The assessment itself is run by Kemisoft, a listed Nintex partner.

About the figures on this page: counts and percentages describe Horus Eye’s own test orgs, which hold seeded example data. They are examples of what an assessment reports — never typical results and never a benchmark for your org.