Client Progress Deck
Project Development Progress Presentation
Browse the project through its four delivery stages. Completed work is marked in green, the current active stage is highlighted in yellow, and future stages remain locked until approved and progressed.
Stage 02
Project Setup
Environment preparation, structure definition, and service architecture setup.
What Project Setup Means
Project setup is the stage where the approved system direction is translated into real organizational use. At this point, the platform structure already exists, and the next requirement is for the organization to begin supplying the real setup data that the system architecture needs. This includes staff account details, department structure, internal roles, operational content, and the institutional records required to configure the portal into a production-ready working environment.
What the Schema Requires From Users
The current schema is structured around real office operations, which means this stage depends on the organization providing the setup data needed to activate the platform correctly. Users are expected to provide department information, staff identity records, user roles, communication ownership, and the institutional content needed for public and internal workflows. Without this setup data, the system remains technically complete but organizationally unconfigured.
Required Participation From Stage Members
This stage requires active participation from office members. Staff are encouraged to use the portal signup process, create their accounts, and begin simulating office work through the available interfaces. The purpose is to help the organization understand the new workflow model, test usability, and identify any practical feedback before final approval is granted for progression. This is not only a technical review stage, but also an onboarding and institutional familiarization stage.
Approval Condition for Proceeding
The project should only move beyond setup after the organization has completed account creation, basic workflow simulation, and client-side evaluation of the platform. Once all participating members have reviewed the system and the required setup data has been supplied, the approver may confirm progression into the next stage. This ensures that advancement is based on actual institutional readiness rather than only technical completion.
Setup Data and Operational Readiness
The schema already establishes the structure of the organization across users, departments, permissions, posts, tasks, documents, meetings, support, legal, approvals, membership, licensing, royalties, and administration. What is now required is the real institutional data that gives those structures practical meaning. This stage should therefore be treated as the point where the office begins populating the platform and validating how the system behaves in realistic day-to-day use.
Identity and Access Setup
Create user accounts, define staff identity, assign departments, and confirm internal access roles and permissions.
Operational Content Setup
Provide the documents, announcements, updates, institutional information, and workflow records needed to shape the portal into a real office system.
Readiness Validation
Simulate tasks, meetings, approvals, and communication flow so the approver can confirm readiness for the next stage.
Portal Review Instructions
During this setup stage, members should review both the demo and live portal environments. The demo environment is intended for guided learning and workflow familiarization using dummy credentials. The live environment is intended for real account creation and practical platform testing by the organization.
Demo Review Portal
Simulated application walkthrough
Use the demo portal to review the simulated version of the application. Members should use dummy emails and passwords in order to learn the interface, understand the workflow, and observe how office operations are represented in the new system.
Live Review Portal
Real account creation and platform testing
Use the live portal to create real user accounts and begin testing the system with actual organizational participation. This environment should be used by stage members to validate how the platform works with real users, real departmental structure, and real operational input.
Current Setup Decision
This setup stage should be considered active until users have created their accounts, tested the portal, supplied the necessary setup information, and completed departmental review. Once this has been done and the approver is satisfied that the organization has meaningfully engaged with the platform, the project may proceed to the next stage.
Current stage
Project Setup
Required before proceed
Account creation, setup data submission, workflow simulation, and review feedback.
Next locked stage
Development Progress