System Validation Checklist

<aside> 🧭

FLOW WORK SYSTEMS GLOBAL NAVIGATION

OPERATE 🎛 CEO Dashboard ☀ Daily Action 🗓 Weekly Review ⚡ Quick Create

<aside> ✅

SYSTEM VALIDATION CHECKLIST

Use this checklist to confirm that the workspace is accurate, easy to use, properly secured, and still connected to the correct master databases.

</aside>

01 · Architecture

[ ] Each type of information has one master database where it is created and updated.
[ ] Dashboards use linked views rather than duplicate trackers.
[ ] Every operating unit has a clear focus, value-delivery path, current obstacle, accountable leadership, and regular executive review schedule.
[ ] Every active Strategic Goal defines a material outcome, owner, success criteria, target date, and linked execution.
[ ] Every KPI Scorecard defines the evidence source, current and target values, accountable owner, trend, and review cadence.
[ ] Every active initiative has a defined result, next milestone, owner, completion or approval requirements, next handoff, known exceptions, review schedule, and at least one Strategic Goal or KPI connection.
[ ] Business dashboards show only records connected to the correct Business relation.
[ ] Each major-project dashboard uses the canonical Project relation to filter its task and supporting-module views. Project View Filter is used only when a specifically identified legacy view has been tested and cannot yet be migrated.
[ ] In the final duplicated client workspace, recreate all ten Quick Create forms against the duplicated canonical data sources, submit one record through each form, and verify every response destination. Reusable page structures are used only when the record requires a structured body.

[ ] Every actionable task has a status, priority, Responsible Person, due date, expected result, and clear conditions for completion.
[ ] Waiting tasks identify a structured Waiting On Person or Waiting On Supplier relation, plus the next follow-up or escalation condition.
[ ] Blocked tasks identify a structured Blocked By Tasks relation when another task is the source, or a precise narrative blocker and escalation rule when no structured source applies.
[ ] Decision-required tasks are connected to a formal Decision Record and visible in Decisions Needed.
[ ] Completed tasks include proof of completion—such as a file, link, approval, delivered result, or recorded outcome—and identify who receives the work next.
[ ] Today, In Progress, Next Actions, Overdue, Waiting, Blocked, Decisions Needed, and Routing & Completion Audit return the expected records.

[ ] Meeting records connect Participants, formal Decision Records, and executable Follow-Up Tasks; action outcomes are not left only in meeting text.