Dashboard

Team delivery, deferrals and audit health.

Under team: —

Offline local
Meaningful Build Week extension

From deferred work to accountable action

Open a synthetic high-risk deferral, generate a live GPT-5.6 operational brief, review it, preserve the decision in the audit chain, and keep the core workflow available offline.

Human approval requiredNo automatic emailNo automatic closureAPI key stays server-side
Use only synthetic or non-confidential records with the AI feature.

Priority work

Open work sorted by urgency, due date and blockers.

Document deferral health

Track deferred shipping, regulatory or internal documents until regularized.

Due this week

Tasks and deferrals due within seven days.

Recent audit

Latest field-level changes by users.

Team workload

Open items by owner.

Cluster / Department dashboard

Cluster Heads see only their approved cluster teams. Dept Head can see every team dashboard and access every team workspace.

Scope
Login as Cluster Head or Dept Head to view consolidated dashboards.

Accessible team workspaces

Open a team from the approved scope. Import teams are grouped under Import cluster; Export teams under Export cluster; MIS/Risk/Core Ops are controlled smaller clusters.

Team
Cluster
Open tasks
Done
Overdue
Deferrals
Action

Team control center

Each workspace has its own editable member list, team lead, task ownership and backup responsibility.

Editable team members

Rename members, set lead, add task beside a person, or remove names no longer used by this workspace.

Workspace readiness check

Built-in operating check for ownership, backup cover, deadline visibility, audit discipline and capacity control.

—

Kanban board

Drag cards across columns. Moving a card creates an audit record under your name.

Task management

Tap any task row to edit completely. Add daily task / BAU with owner, backup member, progress, due date and full audit trail.

TaskStatusPriorityOwnerBackup RPDueProgressUpdated

Project management

Create projects with multiple members, one SPOC / lead, milestone dates, progress, status and full audit trail. Tap any project row to edit it.

Project control: each project can have multiple project members and one SPOC / lead. All create, edit, closure and delete actions are retained in Master Audit DB.
ProjectStatusSPOC / LeadMembersTimelineProgressUpdated

GPT-5.6 Operational Briefs

AI assistance is tied to a selected task, project or deferral. It recommends; a human reviews and decides.

Checking endpoint
1. Minimise dataOnly structured record fields are submitted.
2. Require confirmationThe user must confirm the record is safe to send.
3. Preserve human authorityAI cannot close records, change risk or send email.
4. Audit the outcomeGeneration and reviewer decisions are retained.
Offline behaviour: task, project, deferral and audit functions continue locally. Live GPT-5.6 generation waits until connectivity returns.

Review status

Generated briefs and the human decision recorded for each one.

Brief register

Live model, prompt version, reviewer decision and source record.

Spreadsheet capacity register

High-volume row and column workspace for tasks and document deferrals. Inline changes are audited by user, time and update note.

0 records0 columnsRoom
Page 1
Capacity design: this register renders by page so the interface can handle many records without freezing. For truly unlimited commercial records across many users, connect the sync backend/database; local browser storage still depends on the user device and browser quota.
—
Checking capacity

Capacity is calculated from browser storage estimate when available.

Maximum capacity

Current team workspace

Browser maximum
—
Used storage
—
Remaining
—
Current team size
—
IndexedDB rooms
—
Total records
—
Checking available space and recommendations.

Capacity action guide

What reduces capacity and what cleanup increases capacity.

ActionCapacity impactRecommendation

Safe cleanup tools

Export backup first. These actions reduce local data size inside the active team workspace.

Important: normal task deletion keeps audit evidence and a deleted-record bin. For capacity recovery, use archive/trim tools after exporting a JSON backup.

Security vault

This workspace uses user-name accountability, field-level audit, encrypted backup option and a tamper-evident audit hash chain. The private offline build also refuses to run from normal online hosting.

Build modeProtocol

Security benchmark

Practical offline security score based on identity, audit, encryption, chain verification and backup discipline.

—
—

Run verification to refresh the score.

Encrypted backup

Export a password-protected AES-GCM backup. This protects data when the file is shared, stored or moved between devices.

Important: encryption is only as strong as the password. If the password is lost, the encrypted backup cannot be recovered.

Hash-chained tamper-evident audit chain

Each audit entry is sealed with the previous entry hash. If anyone edits old records, verification will show a broken chain.

Chain status—
Sealed entries—
Issues—
No sealed hash yet
Run verification after importing backup or receiving synced records.

Team access control

Each team has an owner, optional team password, profile login, and storage-location control.

Access control
Profile and storage status will appear here.

Password change centre

Change the key passwords used in this file without changing existing workflow logic. Every successful or blocked change is audited where a user/team context is available.

Controlled

Change my login PIN

Change delete password

Change owner modification password

Team password control

Team password is changed from the Team access control section above. Keep all security passwords confidential and do not disclose them in shared documents or public messages.

Control rule: keep password changes limited to authorized users. Delete and owner-password changes are separately audited and do not erase previous audit evidence.

Tamper-evident control seal

Permission rules, delete-password control, master audit retention and encrypted backup discipline are summarized as a control-policy hash. This helps detect changed rules after file updates.

Pending
Delete control: task, project, deferral, document, member removal, deleted-bin cleanup and reset actions are protected and recorded in Master Audit DB when executed or blocked.

Permission Matrix

Role-permission matrix for every user type. This screen explains exactly what each role can do without changing existing operating logic.

Current role
Login to see your current role and approved scope.

Tamper-evident control seal

Role rules, delete controls, row audit and master audit are represented as a tamper-evident control policy hash.

Pending
Security note: this offline HTML app can encrypt backups and hash-seal audit evidence. True hack-proof protection still requires organisation folder permissions, HTTPS/backend login, and server-side database access control.

Improvement roadmap

Potential next steps for a server-backed, multi-user version.

Deferral management

Tap any deferral row to edit completely. Track missing/deferred documents, follow-up commitment, approver, regularization date and full audit history.

Document / ReferenceClient / ProjectStatusOwnerOriginal dueDeferred untilRiskLast update

Calendar

Task due dates and document deferral deadlines.

Docs & notes

Meeting notes, SOPs, decisions or project wiki pages.

Editor

Save creates an audit entry with your name.

Audit trail

Every user update is recorded by field, date, time and update note. This view is read from the master audit database.

Same-field change history

Select any task or deferral in edit view to see all users’ changes for that exact item.

Open an item to view its field history.

Master audit trail database

Separate append-only audit evidence for this team. Task, deferral, member, join, delete and cleanup events remain here even if the original row is deleted or the working audit list is trimmed.

Control rule: this master audit database is locked from app delete and cleanup buttons. Export JSON/encrypted backups regularly. A browser file cannot stop a technical user from editing source code, but normal users cannot remove master audit records through this interface.

User Guide & Operating Manual

Practical instructions for using this team project workspace safely, consistently and with strong audit control.

Purpose: this app is designed for controlled team task management, document deferral follow-up, maker/checker-style accountability, capacity monitoring and evidence retention. Use one selected team at a time and make every update under your own secure profile.

1. First-time signup

  1. Open the file from the approved shared location or controlled server.
  2. Signup email is mandatory and must be a valid organisational email; otherwise it will show invalid email.
  3. Select your team name from the dropdown. Use Add new team to create a customized workspace name. No predefined team names are forced.
  4. Enter your exact individual name, select gender for signup, add mobile number when required, choose an existing or custom role name, and create a four-digit PIN.
  5. Your signup team becomes your default team and your name is added to that team automatically.
  6. Do not share your PIN. All future updates will carry your profile name in the audit trail.

2. Existing user login and guest demo

  1. Select your default team.
  2. Login by either your full name and four-digit PIN, or your registered valid email address and four-digit PIN. You do not need to enter both name and email.
  3. Use Start judge demo — no signup to open the synthetic high-risk deferral and GPT-5.6 review workflow. Guest activity is temporary, isolated from real team data, and clears when you exit, refresh or switch profile.
  4. Name and email login are case-insensitive; users can type upper case, lower case, or mixed case and still log in with the correct PIN.
  5. Gender is required only during signup. Existing-user login asks only for name or email plus PIN.
  6. Signup email is mandatory and supports Outlook follow-up and reminder drafts. Mobile number is optional unless Dept Head has switched on the mandatory mobile rule.
  7. After login, the top header and every tab show the active team name so you can confirm the working team before updating records.

3. Joining another team

  1. If a normal team member selects another team, the app asks whether to send a join request.
  2. The other team workspace will not open until the respective team lead or owner approves the request.
  3. Team lead or owner sees a compact Access requests button in Team Directory only when pending requests exist.
  4. Join request, approval, rejection and member addition are recorded in the master audit trail.

4. Cluster Head / Dept Head access

  1. During signup, choose Cluster Head and select the cluster type, or choose Dept Head for department-wide access.
  2. Import teams are grouped under Import cluster when the team name starts with Import. Export teams are grouped under Export cluster when the team name starts with Export.
  3. MIS, Risk and Core Ops are controlled smaller clusters. Other team names default to Core Ops unless they contain MIS or Risk.
  4. Cluster Heads can open only their cluster teams, access those workspaces and assign tasks/deferrals to any member of those cluster teams.
  5. Dept Head can open every team workspace, check the full consolidated dashboard and assign work to any department member across all teams.
  6. Use the Cluster Dashboard tab for overall dashboard, profile coverage insight and visible-team CSV export.
  7. Dept Head can switch the signup mobile-number rule between optional and mandatory from Settings.

5. Team Directory

  1. Use Team Directory to maintain team lead, team owner and editable member list.
  2. Member names cannot be duplicated, including spacing or case variations.
  3. Renaming a member is audited and automatically updates related task owner, backup responsible person and deferral owner fields.
  4. Use Add task beside a member for quick allocation.
  5. If a member is approved in another team, Team Lead/Owner can see that other approved team access on the member card for control visibility.

6. Task management

  1. Create tasks from Dashboard, Task Management, Spreadsheet Register or beside a member name.
  2. Always select owner, backup responsible person, priority, due date and progress percentage.
  3. Assignment control: task add, edit and delete remain available with audit trail. Team Members can assign within their own approved team, Team Lead/Owner can assign within the team, Cluster Head can assign within the selected cluster, and Dept Head can assign across all teams.
  4. Start date must not be after due date, and backup responsible person should be different from the owner.
  5. Missed-deadline tasks remain red until completed. Completed tasks show green.
  6. Use the row Audit button to see who changed which field, with date, time, old value, new value and note.
  7. The Assign button is available on task, project and deferral rows; selected assignee/owner/SPOC email is shown from the user profile so follow-up is easier and less error-prone.
  8. Use Follow-up on a task/project/deferral row to open an Outlook/email draft addressed to the selected member. It will not send automatically; review and send manually.
  9. Use Reminder on a task/project/deferral row to generate a reminder email draft to your own registered email. It will not send automatically.
  10. Use Export team tasks CSV from Task List to export the whole team task register.
  11. Delete is available from the task form, requires the delete password, and the deleted task evidence remains in Master Audit DB.

7. Project management

  1. Create projects from the Project Management tab.
  2. Each project supports multiple project members and one SPOC / Lead.
  3. Tap any project row to open complete editable project details.
  4. Project create, edit, closure, delete and SPOC/member changes are recorded in the Master Audit DB.

8. Document deferral tracker

  1. Record deferred or missing documents with reference number, client/project, owner, original due date, deferred-until date, risk level and approver.
  2. Overdue or expired deferral items remain visible for follow-up.
  3. Every deferral update and deletion is written to row audit and master audit.
  4. Use this tab for regular follow-up commitments until the document is regularized, waived or closed.

8. Spreadsheet Register

  1. Use the spreadsheet view for high-volume row and column work.
  2. Add task rows, deferral rows and custom columns as needed.
  3. Use pagination for large records rather than loading every row at once.
  4. Inline updates require user identity and are recorded in audit.

9. Search

  1. Use the top search box for quick search inside the active team.
  2. Use Workspace Search for deeper search across tasks, deferrals, docs, notes and audit records.
  3. Search results are limited to the selected team workspace.

10. Audit Trail and Master Audit DB

  1. Use row-level audit buttons for a specific task, deferral item, spreadsheet row or member name.
  2. Use Audit Trail for normal working history.
  3. Use Master Audit DB for retained evidence. It keeps records even if a task or deferral row is deleted.
  4. Master audit is blocked from normal delete and cleanup buttons inside the app.
  5. Export master audit CSV before major reviews, data migration or clean-up.

11. Security Vault

  1. Use encrypted backup export for confidential records.
  2. Keep the encryption password separately and securely. Lost passwords cannot be recovered from the file.
  3. Use audit hash-chain verification after import, restore or sync.
  4. Use Password change centre to change your own four-digit PIN, delete password and owner modification password where authorized.
  5. Team owner can set or replace a team password where required.
  6. Keep file-level access credentials confidential and avoid writing them in shared documents or public messages.

12. Capacity Meter

  1. The fuel meter shows browser/device storage health for the active workspace.
  2. When remaining capacity falls below 20%, the meter turns red and the app shows action guidance.
  3. Capacity is reduced by tasks, deferrals, notes, comments, custom columns, imports and audit records.
  4. Capacity improves by archiving completed work, closing deferrals, clearing deleted bin, exporting backups and moving long-term data to backend/database storage.

Admin and team-member dual access

  1. Only one person can hold the sole Admin role at a time.
  2. The same person may also sign up separately as a Team Member, Team Lead, Cluster Head or Dept Head under an approved operational team.
  3. When that person logs in as Admin, only Admin Dashboard / backup authority appears and team operational data remains hidden.
  4. When the same person logs in under the operational role, the normal team workspace appears according to approved team access.
  5. Use Switch role / profile to move between Admin login and operational team login; no join popup is shown for roles already approved or already signed up.

13. Backup and restore

  1. Export current team JSON backup before any major change.
  2. Export all rooms JSON backup before browser reset, device change or migration.
  3. Login as Admin and use Admin export full restorable CSV backup before replacing or deleting the old HTML file. Admin is backup-only and cannot view team data.
  4. The app shows a Backup reminder. If no Admin CSV backup has been taken within the recommended period, Admin will see a warning.
  5. After opening the new updated file, login as Admin and use Admin import restorable CSV backup. A restore preview screen will show teams, profiles, tasks, projects, deferrals, members and master audit counts before import.
  6. The restore imports only fields that exist in the updated version and ignores deleted/unknown old fields.
  7. Use encrypted backups for sensitive team data.
  8. Use normal CSV exports for reporting, review meetings and management submission; use Admin CSV only for backup/restore.
  9. Restore/import only from trusted backup files and confirm only after reviewing the preview.

14. Permission Matrix and tamper-evident control seal

  1. Use the Permission Matrix tab to see the role boundaries shown in this browser-local build.
  2. The matrix is informational and does not replace server-side authorization.
  3. Local audit entries record create, edit, reassignment, closure, deletion, and blocked protected actions.
  4. The control-policy hash is a hash-chained tamper-evident seal for the current rule set; it is not a blockchain or proof of immutable storage.
  5. Use encrypted backups for data protection. A server-backed version would still require authentication, authorization, HTTPS, database controls, and independent security testing.

Daily operating checklist

Recommended routine for team leads and team members.

MorningCheck overdue red tasks, deferral due items and pending access requests.
During the dayUpdate task progress with clear note and correct owner/backup RP.
Before closeReview audit exceptions, export important CSV reports and back up if major changes occurred.

Control rules

Use these rules to preserve data quality and audit reliability.

  • Use your own profile only; do not update under another person’s name.
  • Keep four-digit PIN private.
  • Do not delete a task to hide history. Master Audit DB retains the evidence.
  • Keep existing controls when updating the app. Add new rules only unless a change specifically asks to remove or replace a condition.
  • Owner modification password: adminship transfer, admin restore, team rename, team security settings, backup import and team reset are protected by the current file owner authorization password. Use Security Vault to change it when needed.
  • Assign work within your approved team, cluster or department scope; blocked cross-scope attempts are written to the Master Audit DB.
  • If a user forgets the four-digit PIN, Admin can unlock any profile; Cluster Head and Dept Head can unlock the sole Admin; Team Lead/Owner can unlock teammate profiles only.
  • Delete password control: task, project, deferral, document, member removal, deleted-bin clearing and team reset actions require the current delete password. Failed attempts are audited. Use Security Vault to change it when needed.
  • Desktop/private copy can be used for individual/local backup; for live team updates use organisation shared location or controlled server.
  • For true simultaneous multi-user use, deploy the backend sync option with proper authentication and database backup.
Important: browser-based files cannot provide the same physical access control as a server database. For commercial deployment, use HTTPS, user authentication, server-side permissions and scheduled database backups.

Workspace settings

Configure team members and online sync endpoint.

Team ID is controlled by the team selector.
For this package, keep /api/operational-brief. Store OPENAI_API_KEY only as a Cloudflare secret—never inside this HTML.

Data controls

Maximum local backup design with team-wise restore, all-room export, admin CSV restore and online sync controls.

Admin restorable CSV backup

Login as Admin to export the full file data as a restorable CSV. After app update, open the new file, login as Admin and import this CSV to fetch and show the same teams, tasks, projects, deferrals, members and audit records.

Backup reminder

Admin backup status will appear here after login.

Profile data control

Email is mandatory and must be a valid email address. Gender is required during signup only. Mobile number is optional unless Dept Head makes it mandatory.

Mobile number policy will appear here.
Sole Admin profile control

Only one person can hold Admin access. The same person may also keep a separate team-member profile and log in under that team for operational work.

Admin team-name control

Admin can rename a team label for maintenance without opening team task/project/deferral data.

Team ID is retained; only the displayed team name changes. Unknown old CSV fields remain ignored during restore.
Profile PIN unlock / reset

Admin can unlock/reset any profile PIN. Team Lead/Owner can unlock only approved teammates in the current team. The reset is audited in Master Audit DB where a team context is available.

Local backup status

The app keeps a browser backup and a larger IndexedDB room backup where supported. Export JSON or Admin CSV before major clean-up, browser reset or device change.

Commercial multi-user deployment

Deploy the included Node sync server. Put the server URL in “Sync API base URL”. The HTML remains static and can be hosted on Cloudflare Pages, GitHub Pages or any static hosting.

GET /api/workspaces/:room/events
POST /api/workspaces/:room/events