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. Trade Dept Head can see every team dashboard and access every team workspace.
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.
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.
| Task | Status | Priority | Owner | Backup RP | Due | Progress | Updated |
|---|
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 | Status | SPOC / Lead | Members | Timeline | Progress | Updated |
|---|
Spreadsheet capacity register
High-volume row and column workspace for tasks and document deferrals. Inline changes are audited by user, time and update note.
Workspace search
Search the active team workspace only. Each team keeps the same search function with its own records.
Capacity is calculated from browser storage estimate when available.
Maximum capacity
Current team workspace
Capacity action guide
What reduces capacity and what cleanup increases capacity.
| Action | Capacity impact | Recommendation |
|---|
Safe cleanup tools
Export backup first. These actions reduce local data size inside the active team workspace.
Security vault
This deployable workspace uses user-name accountability, field-level audit, encrypted backup options and a tamper-evident audit hash chain. It can run on Cloudflare Pages while retaining offline-first local storage.
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.
Blockchain-style audit chain
Each audit entry is sealed with the previous entry hash. If anyone edits old records, verification will show a broken chain.
Team access control
Each team has an owner, optional team password, profile login, and storage-location control.
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.
Change my login PIN
Change delete password
Change owner modification password
Team password and encrypted file unlock
Team password is changed from the Team access control section above. This Cloudflare edition has no outer HTML unlock password; use profile PINs, team controls, owner authorization and encrypted backups.
Blockchain 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.
Permission Matrix
Role-permission matrix for every user type. This screen explains exactly what each role can do without changing existing operating logic.
Blockchain control seal
Role rules, delete controls, row audit and master audit are represented as a tamper-evident control policy hash.
10/10 improvement roadmap
Items that would move this from strong offline control to enterprise-grade control.
Deferral management
Tap any deferral row to edit completely. Track missing/deferred documents, follow-up commitment, approver, regularization date and full audit history.
| Document / Reference | Client / Project | Status | Owner | Original due | Deferred until | Risk | Last 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.
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.
User Guide & Operating Manual
Practical instructions for using this team project workspace safely, consistently and with strong audit control.
1. Guest Demo
- Select Guest Demo beside Signup and Login, or open
/tools/project-management/demo/. - No signup, PIN or organisation account is required.
- The demo opens a sample Team Lead workspace with tasks, a project and a deferral.
- Demo changes stay only in the current browser tab and are cleared when the tab is closed.
- Server sync, cloud attachments and server reminders are not included in this release.
2. First-Time Signup
- Open the deployed HTTPS site or approved offline copy.
- Select an existing team or create a new team when permitted and below the 20-team limit.
- Enter your full name, a valid email address, gender, optional mobile number and a four-digit PIN.
- Select the correct user type and cluster where applicable.
- Your signup team becomes your default team and all future changes carry your profile identity in audit records.
3. Existing User Login
- Select Existing User Login.
- Choose the relevant user type and team unless logging in as Admin.
- Use either full name plus PIN or registered email plus PIN; name and email matching is case-insensitive.
- Admin is a separate backup-and-governance profile and does not automatically receive operational team visibility.
- Use Change Profile to switch between an approved team role and Admin role.
4. Teams And Join Requests
- Work inside one active team at a time and confirm the team name in the header before updating records.
- A normal member requesting another team is held in pending status until that team’s Team Lead or Owner approves.
- Team Lead and Owner can review pending requests from Team Directory.
- Request, approval, rejection, member addition and access removal are audited.
5. Roles, Clusters And Management Matrix
- Team Member works within approved teams; Team Lead governs the team; Cluster Head governs approved cluster teams; Trade Dept Head has department-wide scope; Admin handles backup and governance controls.
- The local Management Matrix controls view, create, edit, assign, close, delete, team, matrix, automation, restore and notification permissions.
- This browser-local Matrix is an operational control, not server authentication.
- Blocked actions are recorded for control review.
6. Task Management
- Create tasks from Dashboard, Task Management, Management Grid, Spreadsheet Register or Team Directory.
- Complete owner, backup owner, priority, start date, due date/time, progress, estimated hours and work type.
- Use subtasks, dependencies, parent task, milestone, recurrence, approval status, tags, RACI and attachment links as required.
- Use Start/Stop Timer for actual time entries.
- Closing or deleting work follows Matrix permissions, mandatory remarks and password controls where configured.
7. Projects, Portfolios And Goals
- Create projects with lead, members, priority, dates, progress, status and RACI.
- Use Timeline for date comparison and dependency awareness.
- Use Portfolio Health to review delivery risk across projects.
- Use Goals to connect team outcomes with measurable progress.
- Project create, change, closure and deletion remain auditable.
8. Deferral Management
- Record deferred or missing documents with reference, client/project, owner, risk, original due date, deferred-until date, approver and reason.
- On mobile, use Deferrals in the bottom navigation for direct access. The Capacity Meter remains available from the top capacity gauge and the main menu.
- Overdue deferrals remain visible until regularized, waived or closed.
- Use closure remarks and evidence before final closure.
- Every field change and deletion is retained in row audit and Master Audit DB.
9. Management Grid And Spreadsheet
- Use Management Grid to combine tasks, projects and deferrals in one command centre.
- Filter My Work, overdue, blocked, milestones, owner, status and priority.
- Use bulk owner or status changes only within your Matrix authority.
- Use Spreadsheet Register for high-volume row work, custom columns and paginated updates.
- Inline and bulk changes remain audited.
10. Workload, Capacity And Automation
- Set weekly member capacity only when permitted.
- Compare estimated work against available capacity and address over-allocation.
- Create automation rules for status, priority, owner, tags, reminders and follow-up tasks.
- Automation actions run locally and are written to audit history.
- Browser reminders and calendar exports are available; closed-app email delivery is not included in this release.
11. Offline Operation
- The installed PWA and browser copy continue working without internet.
- Changes are stored locally with IndexedDB recovery snapshots and an offline outbox.
- Browser or device cleanup can remove local data; export encrypted JSON or Admin CSV backups regularly.
- Do not treat offline local storage as a substitute for organisational database retention.
12. Online Sync Status
- This consolidated release does not include the former Project Management sync backend.
- All workspace records remain in this browser unless you export a backup.
- Do not point this tool at the main Trade Finance BD ticket API; it is a different service.
- A future reviewed backend must use a separately namespaced API, authenticated server roles and isolated storage before sync controls can be enabled.
13. Members And Attachments
- Team members and roles are managed inside the local workspace.
- Use approved shared-file references rather than uploading files through this release.
- Cloud membership, R2 uploads and server attachment retention are not included.
- Keep confidential files in controlled organisational storage and export local workspace backups regularly.
14. Audit And Evidence
- Use row Audit for item-level history and Audit Trail for working history.
- Master Audit DB retains evidence beyond normal item deletion and cleanup actions.
- Verify the local audit hash chain after import, restore or major review.
- Local audit records are useful evidence but are not protected server records.
- Export audit CSV before review, migration or retention cleanup.
15. Backup And Recovery
- Use encrypted current-team or all-room JSON for confidential portable backup.
- Admin can export and restore the full restorable CSV package.
- Automatic local snapshots are created before important restore actions.
- Review the restore preview before replacing current data.
- Store backup passwords separately; encrypted backup passwords cannot be recovered from the file.
16. Security And Password Controls
- Keep your four-digit PIN private and never update under another person’s profile.
- Owner authorization protects sensitive structural changes; delete password protects destructive actions.
- This version has no outer HTML unlock password.
- Browser-local profiles and passwords are operational controls, not a substitute for server authentication.
- A client-side audit is strong evidence but not legally immutable without protected server retention.
17. PWA Installation And Updates
- Open the HTTPS Cloudflare site and choose Install App when offered.
- The PWA supports desktop and mobile use and keeps core files cached for offline opening.
- When an update banner appears, complete important work, export a backup, then reload.
- If installation is unavailable, verify HTTPS, manifest, service worker scope and browser support.
18. Daily Operating Routine
- Morning: review overdue work, deferrals, workload, approvals and access requests.
- During the day: update progress, time, ownership and evidence under your own profile.
- Before close: review exceptions, confirm reminders and export important reports.
- Weekly: review Matrix access, capacity, automation, audit verification and backup health.
Daily operating checklist
Recommended routine for team leads and team members.
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 Trade 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.
- Public demo: keep the static demo route public only when approved and never enter confidential information in demo mode.
- Desktop/private copies can be used for individual local work; export encrypted JSON or Admin CSV backups to approved controlled storage.
- This release has no Project Management server database or server authentication. Do not use its local profiles as a substitute for organisational access control.
Workspace settings
Configure local team members and workspace details.
Data controls
Local backup design with team-wise restore, all-room export and Admin CSV restore.
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 restore teams, tasks, projects, deferrals, members and audit records.
Admin backup status will appear here after login.
Email is mandatory and must be a valid email address. Gender is required during signup only. Mobile number is optional unless Trade Dept Head makes it mandatory.
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 can rename a team label for maintenance without opening team task/project/deferral data.
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.
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.
No Project Management Functions, D1 schema, Access integration, notification worker or R2 upload service is included in this release. Those capabilities require a separate reviewed backend and isolated storage before any online control is enabled.