Installation & activation
Choose your Windows, Mac or Linux entry, check IT requirements, and activate online or with a .lic file for supported packages.
Open installation & activationDocumentation
Download the approved stable release without registering. Follow the exact package’s requirements and installation guide. Purchasing is not currently open.
Choose your Windows, Mac or Linux entry, check IT requirements, and activate online or with a .lic file for supported packages.
Open installation & activationA local project-control workspace useful to one PM alongside existing company systems.
Open what it isWeekly triage, meetings to actions, gate readiness, review handoff, and closure.
Open workflowsProject work stays on your computer. An online account holds identity and licence records only.
Open security & privacyExisting tools, storage, company IT, licence ownership, and continuity.
Open questions & answersNotes for approved public stable releases.
Open release notesYour update, at a glance
Keep the old application and a verified backup until you have checked the new version. Follow any instructions supplied with your update.
Follow the highlighted controls below. Screenshots show fictional example data; your project names and version will differ. Select any image to enlarge it.
Step 1 of 5
Wait for Saved, then open File → Import / Merge Workspace….
Open File → Import / Merge Workspace… to reach the Import / Export screen.
Step 2 of 5
Close the Workbench browser tab. Then press Ctrl+C in its runtime console and wait for it to stop.
Closing the browser alone does not stop the application.
The console is the window that opened when you started the Workbench. Wait for it to exit.
Step 3 of 5
In Account → Downloads, open View & Download for your software.
Choose your platform and click Download selected. Extract the complete package into a new folder on a fixed local drive.
Keep the old application folder intact. Do not extract over it.
Step 4 of 5
Use the new package’s supplied launcher and follow its instructions to open your existing workspace.
When the new version reopens the same workspace, no import is needed.
Unexpectedly empty? Stop and check the workspace location before making changes.
Step 5 of 5
Ready to continue. Keep the previous application and backups for recovery.
Stop and confirm the data location with support. Do not edit both copies.
In the new empty destination, open the backup tools, click Import Workspace Backup and choose the full backup you saved in step 1. Review the import preview before confirming.
Import replaces that destination’s workspace; it does not merge two databases. Then complete the checks in step 5.
Use older software only when support confirms it can read the current data. Restoring an older backup can discard newer work. If an update reports incompatible data, stop and request migration guidance.
Each Workbench workspace is a local SQLite database on the user’s computer, including managed attachments. The Windows pilot stores it under %LOCALAPPDATA%\PM Control Workbench\user_db; a supplied universal package uses user_db inside its extracted folder. The website account does not store project content. Employer and client information remains governed by its owner or controlling organisation.
Follow the installation & activation guide for platform-specific launch commands and approved Python options.
The public download page offers approved Windows, macOS and Linux packages. Start your OS package from the supplied launcher. Keep the package on a fixed local drive. Synchronised folders such as OneDrive are not a supported live location.
Saved means the change has been committed in the local workspace database. A second browser tab cannot take over an already open writable workspace.
Use verified snapshots and Backup Explorer restore. Windows pilot snapshots are under user_db\backups\authoritative in the OS-local data root. The optional backup mirror copies snapshots to an approved protected folder; it does not move or sync active storage. OneDrive or network recovery-copy destinations require IT and pilot-support validation. Copying a live database file while the Workbench is running is not a restore method.
Use explicit reports and export packages through approved sharing paths when information needs to leave the Workbench. There is no cloud sync and no multi-user editing of the same workspace.
Follow online activation, or use a signed .lic response when the work computer cannot reach the licence service.
Identity alone does not grant use. A signed licence is bound to a device. Copying the portable folder does not copy activation. A new one-time licence is verified locally without recurring online checks. Initial and replacement-device issuance require the licence service.
After the full 30-day trial, normal editing pauses. Existing work remains readable, searchable, exportable, backed up and recoverable. There is no automatic payment or conversion.
Pay €149 once for permanent use of the eligible purchased release. The licence stays valid offline when the server is unavailable or retired. Corrective builds may be made eligible; future commercial releases are not automatically included and may require a new purchase.
Removing the Windows application folder removes the software; it does not remove the Windows pilot’s OS-local workspace, backup mirrors, or exports. Follow your organisation’s approved retention and deletion procedure for project data separately. A supplied universal package has different bundle-local storage; follow its release-specific instructions.
Use the documentation and send structured bug reports or installation/licensing questions to support@pmcontrolworkbench.com. Written help is best effort; there is no SLA, live-call, consulting, training, custom-development or feature-delivery entitlement. Suggestions create no obligation to implement, prioritise, schedule or report status.