Choose one scope
Name the product, feature, queue, launch or proposed service being assessed.
NARDUXUse ten operating domains to identify what is clear, partial or unknown, then turn the most important gaps into owned next actions.
This is most useful as a cross-functional discussion, not a private confidence exercise completed by one person.
Name the product, feature, queue, launch or proposed service being assessed.
Mark each statement only when a current document, system, test or accountable owner supports it.
Use Clear, Partial or Unknown. “Clear” means adequate for this scope, not perfect forever.
Move hard stops and dependencies into the 30-day worksheet with an owner and evidence target.
This worksheet has no submit action, application storage or analytics, and Nardux does not receive the entries. Your browser may preserve fields temporarily; use Clear checklist and close the tab when finished. Print a working copy if needed, and do not enter sensitive case material.
Check the supporting statements, choose one domain status, and record the evidence or gap owner. The controls do not submit data anywhere.
The checklist is deliberately unscored. Prioritization depends on consequence, dependency and evidence, not the percentage of boxes checked.
Unlawful purpose, unclear data authority, untrained specialist-risk review, unsafe access or no emergency owner should stop or narrow the work.
Policy, authority, access, escalation and reviewer readiness often need to exist before a moderation pilot can test production decisions.
An unknown involving minors, credible harm, privacy, security, legal duties or worker exposure outranks many completed routine controls.
Once safe operation is supportable, use quality, appeals, trends and action records to improve consistency and capacity.
Choose the gaps that unblock safe decisions. A target date without an owner and evidence definition is not a complete action.
For the assessed scope, decide whether to proceed, remediate, narrow, refer, pause or stop, then record why.
This checklist provides general operational planning questions. It is not legal, security, privacy, employment, clinical or other professional advice; it does not identify every applicable obligation or risk; and completing it does not certify readiness. Requirements vary by product, users, jurisdiction, content, data, workforce and actual conduct.
Sources were accessed August 11, 2026. They inform the questions but do not certify Nardux or determine which laws apply to a specific organization.
Industry functions, policy, operations, investigations and quality context.
Governance, product, operational and transparency practices.
Rules, notice, appeals and transparency considerations.
Identity, access, devices, protection, monitoring and recovery foundations.
Accountability, limiting collection, safeguards, openness, access and retention context.
General workplace health and safety responsibilities relevant to operating design.
They are not submitted to or stored by Nardux. Your browser may preserve native form fields temporarily, so use Clear checklist and close the tab when finished.
There is no numerical score. A single hard stop or serious unknown can block a scope even when many routine items are clear. Use evidence, consequence and dependency to prioritize.
No. It can surface questions for the appropriate owner or specialist, but it does not determine legal obligations, certify security or approve high-risk content work.
The accessible HTML worksheet is the maintained version. No separate PDF has been produced and tested yet. You can use your browser’s print function for a working copy.
Share the product scope and the readiness areas that remain unclear without sending user content or sensitive evidence.