What shipped.

Time off became a financial event, the weekly rhythm became configurable, and the Time-Off Center got a visual overhaul:

• Paid and unpaid time off. Every absence now carries a paid/unpaid designation. When time off is paid, the person’s locked rate is used to compute the cost — and that cost flows through to Analytics, Finance, the financial report, the Team page’s cost column and the Workload view’s paid-vs-unpaid split. Unpaid time off shows as time away without financial impact.
• Configurable week start. The first day of your work week (Sunday or Monday) is now a workspace setting that drives the calendar grid, the frozen-plan capture, the weekly digest, delivery reports and workload calculations. Changing it takes effect at the next week boundary — the running week finishes under the shape it was promised in.
• Time-Off screen rebuilt. The Time-Off management screen received a visual overhaul — a cleaner three-column layout for requests, calendar and balances, with improved filtering and a more readable list.
• The new logo. The PMOlikePRO brand mark was refreshed across the application and the website.

The biggest visual change since launch: the product now opens to a dashboard that shows what matters to your role, and the analytics pages were rebuilt as focused boards.

• Home dashboard. A personalized landing page with widgets tailored to your role — an admin sees the workspace vitals, money position, team workload, delivery scorecard and overdue-and-at-risk lists; a member sees their own day, tasks, hours and milestones. Every widget opens its Quick View on click and has a drill-out arrow to the full page. Widgets sit on a uniform grid so everything lines up, and each one has its own Settings for time ranges, view modes and filters.
• Customizable. Choose which widgets you see, drag them into the order you prefer, and size them by width and length — all persisted per person. An “Add widgets” gallery groups the available widgets by theme with a plain-language description of what each one shows. A Reset button returns to the role’s default starter layout.
• Four Analytics boards. The old Overview and Progress pages have been retired into four focused boards: Delivery compares logged hours against the weekly plan, person by person; Workload shows who is scheduled where and flags overloads; Money shows income, expenses and the financial position over time; Hours is the time ledger, filterable by person, project and date range.
• Money chart. The Home money widget is a real chart — income and expenses as paired bars over your chosen time range (presets or a custom slider), with a running “net so far” line that shows the cumulative position. Figures update live as transactions are recorded elsewhere in the system.
• Task status comparisons. The task-status widget compares open tasks along four axes — by status (with per-state toggles), by priority, by task type, or by client-vs-internal work — each shown as comparison bars or a donut, switchable in Settings.
• Team heat map. A look-ahead heat grid shows who is booked and how heavily, from the next 7 days up to 60. Longer windows label columns by date and compress to fit the widget without scrolling.
• Hours trend and forecast. Your own logged-hours trend over a configurable window, and a team forecast that projects the next two weeks at the recent pace with an honest confidence band.

A release focused entirely on making the product more dependable under real-world conditions:

• Atomic team operations. Removing a team member now completes fully or not at all — no partial state if something interrupts. The last administrator of a workspace cannot be removed, preventing accidental lockout.
• Capacity enforcement. A personal capacity warning appears when a day is planned beyond someone’s available hours, and a hard ceiling of 24 hours per day is enforced on every write path — no more accidental double-shifts.
• Time off respected everywhere. Approved time off now automatically reduces capacity in the scheduling engine, the delivery freeze, and the weekly scorecard — so the system never plans, promises, or scores against hours a person was never going to work.
• Silent behaviors replaced. Drag-to-unscheduled now asks before clearing a person’s schedule. Shared tasks that are shifted no longer silently affect other assignees — the system tells you who is impacted. Undo operations correctly attribute changes. Schedule moves respect locked tasks.
• Improved reading reliability. Long activity histories and time-log records are now read completely, without silent truncation — important for larger workspaces running delivery reports across many weeks.

The calendar and the visibility model both received their largest update since the product launched:

• Calendar visual rework. Each area of the calendar was redesigned individually: member cells show a per-day workload indicator, utilization reads at a glance with a compact gauge, task cards adapt their density to the view (comfortable on the daily, compact on the weekly), day headers show free hours instead of used-of-capacity, milestones sit on their own lane under the date headers, and the monthly view gained richer heat cells with status indicators. The daily view’s redundant hours strip was removed, and the monthly day panel now docks beside the grid instead of pushing it down.
• Shift schedules from every view. The bulk-shift feature is no longer limited to the weekly view — it can be opened from the daily view’s member headers, the monthly toolbar, and individual day-panel rows.
• Member visibility. Each role now sees exactly the work it should: members see their own tasks and those on shared projects; managers and admins see everything. Documents gained per-file sharing controls and a Workspace Library visible to all roles. Task privacy defaults to titles-only for tasks outside a member’s projects, with a per-project override for full visibility. When a member encounters a task they don’t have access to, they can request access — the relevant managers are notified with a one-click grant.

Two foundational changes to how the product protects your work:

• Frozen weekly plans. At the start of each week, the scheduled plan is captured automatically. That snapshot becomes the promise — the number delivery is measured against. If someone tries to move promised hours out of the running week, the system warns first and names exactly who would lose what. The weekly digest email compares logged hours against the frozen plan, person by person, so delivery accountability is built into the rhythm rather than assembled after the fact.
• Guardrails on every destructive action. Deleting a project, removing a team member, archiving a client, merging payees — every action that cannot easily be undone now asks for confirmation before proceeding. The most consequential ones (deleting a workspace, removing the last administrator) require typing the name to confirm. Settings lists that previously deleted items silently now show exactly how many records are linked before asking. Nothing in the product changes data irreversibly without your explicit go-ahead.
• Configurable week start. Your workspace’s first day of the week (Sunday or Monday) now drives everything: the calendar grid, the frozen-plan capture, the weekly digest, delivery reports and workload calculations all anchor on the day you choose in Settings.

Two areas that previously required careful manual work now handle much more on their own:

• Intelligent placement. When you drop work onto the calendar, the system checks whether it fits the person’s remaining capacity. If it does, it’s placed. If it doesn’t, a per-day planner opens with the overflow pre-filled so you can decide where it goes — no more silent overallocation. A “first available” button auto-fills from the next open slot.
• Bulk schedule shifts. Move a person’s entire schedule forward or back by any number of days in one action. A dry-run preview shows exactly what will move, what will collide with existing work, and what is locked in place — before anything changes.
• The Time-Off Center. A dedicated three-column management screen for absences: requests on the left, a team calendar in the center, and balances on the right. Time off supports six default categories (vacation, sick, public holiday, personal, parental, unpaid) plus your own custom types, with part-day support and a manager-approval flow. Approved time off automatically reduces the person’s available capacity on the calendar — no more scheduling onto someone who isn’t there.
• Team events. Organization-wide or department-wide time off (public holidays, company days) can be set up as rules that apply automatically to everyone, specific departments, or named people — managed once, reflected everywhere.

A consistency sweep across the whole product, closed out with speed and reliability work:

• One grammar everywhere. Group By, filters and sorting now behave identically across Projects, Tasks, Clients, Contacts, Team, Time tracking — and the analytics pages, which had grown their own dialects. Same controls, same count-chip filters, same ordering rules; each view remembers its own grouping choice.
• The Gantt, rebuilt. Grouping a Gantt now renders independent sections — each group with its own chart and its own timeline — plus a persisted zoom and an Active/Archived scope, matching everything the list view can do.
• Honest loading. Numbers no longer flash misleading values while data streams in: counts hold back until they are real, and lists show proper pending states instead of momentary zeros or placeholder names.
• A faster first paint. Opening a large workspace paints meaningfully sooner — on a thousand-task workspace the initial load runs roughly a third faster, with the gain growing on slower connections.
• Reliability fixes. @mention notifications now reliably reach the people mentioned; the account page’s history-window meter now counts from your workspace’s creation date (never from the age of any individual record); numbers app-wide display with at most two decimals; and spacing was audited across every module so nothing sits crammed or cut off.

None of this changed what the product does — it changed how dependably and quickly it does it, which is the kind of release we intend to keep shipping.

The promise on our trust page — how you leave — is now a button. Workspace administrators can run a complete off-boarding export: one archive containing the workspace’s full structured data and every uploaded file, foldered by the project, task, client, contact or person it was attached to, trash included and marked.

It is deliberately a ceremony, not a casual download:

• Admin-only, deliberately loud — opening the export window notifies every administrator, and each run is logged. An export is a significant act; everyone with responsibility sees it happen.
• Verified twice — the workspace name typed out, then a fresh two-factor code, before anything is signed for download.
• A window, not a faucet — the export window stays open seven days with unlimited re-runs (a failed download of a large archive costs nothing to retry), renewable yearly — and our support can reset the timer whenever a legitimate need arises.
• Streams to disk — the archive is assembled in your browser and streamed straight to a file, so even multi-gigabyte workspaces export without drama.

Together with PDF and Excel reporting, this closes the loop: your data was always yours; now the whole of it leaves in one motion. Details live in the FAQ and the Terms.

When we shipped documents, we said file storage would be the only other paid extra that will ever exist. It is now live, and it works the way the first one does — capacity, never features:

• 10 GB included in every workspace, as before. Most teams will not need more for a long time.
• +50 GB per pack, $5 per organization per month (or $48 per year — the same 20% annual saving as the plan). Stackable up to twenty packs — a full terabyte.
• Self-serve on the Billing page — a stepper shows the exact prorated amount before you confirm; Paddle bills it together with your subscription. Remove packs anytime; the change takes effect at the end of the paid period.
• Lapse is graceful — if a pack ends, a 30-day grace keeps the higher limit. After that the quota returns to what you pay for, and files stay put: only new uploads pause while you are over.

The pricing page now shows both extras side by side — and the whole-bill calculator on the home page includes them, because the entire bill should always be computable from one screen.

Conversations carry evidence now. Every composer in PMOlikePRO — the team chat, each record’s conversation room, and work journals — accepts file attachments through the paperclip, drag-and-drop, or a straight paste from the clipboard.

The part that keeps things tidy: attachments are real documents, not chat debris.

• Filed where they belong — before sending, a target bar lets you file the attachment onto the conversation’s record, the workspace, or any other entity. The file lands in the Documents system with a type, exactly like a direct upload.
• Same rules, same audit — the format allowlist, the 50 MB limit, previews, and the activity trail all apply. A file shared in chat is as governed as one uploaded to a project.
• Privacy holds — messages reference files by identity only; what a reader can open is decided by their permissions at the moment they look, never by the message itself.

Attachments count toward the workspace’s storage like any other file — the pricing page covers what’s included and how packs extend it.

Two quality-of-life releases in one:

The cards. Kanban task and project cards were rebuilt on a fixed layout grid: every card the same height by construction, every block in the same place, so a board scans like a table instead of a collage. Long titles wrap instead of truncating; progress, dates, people and workload gauges each have a reserved slot. Financial figures on cards remain visible only to the roles entitled to them — re-verified as part of the rebuild.

The ordering. Every configurable list in Settings — statuses, priorities, types, and the rest — now reorders by drag. The order you set is the order the whole app uses: dropdowns, groupings, and board lanes. Admins and managers can even reorder board columns by dragging the column headers directly. And dragging a project into a paused lane now asks the scheduling question instead of silently parking the work.

Every record in PMOlikePRO can now carry its paperwork. Files attach to projects, tasks, clients, contacts and team members, and a dedicated Documents window shows the whole workspace’s files in one place — filterable, grouped, with a 30-day trash.

What shipped, in plain terms:

• Upload anywhere — a Documents panel in every entity dialog, plus drag-and-drop and paste. Every upload carries a document type (contract, invoice, brief, and your own custom types), so the pile stays sorted from day one.
• Preview built in — PDFs, images, media and text open in place; everything else downloads. A strict format allowlist and a 50 MB per-file limit keep the storage honest (the Terms spell out the rules).
• Audited end to end — uploads, downloads, renames and deletions land in the activity trail like every other action.
• 10 GB included — every workspace starts with 10 GB of storage. Administrators are warned at 80% and 95%; at 100% uploads pause and nothing is ever deleted.

Storage fills with use, so it is also the second of the only two paid extras that will ever exist — see the pricing page for how packs work.

The product and its shopfront now speak one visual language. The application’s shell — navigation sidebar, login screen, logo and the spacing rhythm around everything — was redesigned into Executive Slate: light canvas, white cards, teal accent, the same system this website is built on. Clicking “Log in” no longer feels like crossing into a different company.

Two things beyond looks:

• A leaner front door. The sign-in page now loads only what a signed-out visitor needs — a fraction of the previous payload — and the full application streams in after authentication. First paint on a fresh visit is noticeably quicker.
• One design system, enforced. The shell’s colors, controls and spacing come from the same token set everywhere, so future screens inherit consistency instead of approximating it.

Entity journals and team chat are now one system: every task, project, client, contact and person has a conversation room, and journal notes live there as messages.

That changed what “activity history” covers, so the Terms of Service (section 11) and the Privacy Policy (section 6) now say it plainly:

• Kept for the life of the workspace — the structural content your team creates: tasks, projects, clients, contacts and files.
• Follows your history window — conversational content (chat messages and journal notes, including pinned ones), together with automated activity records and notifications: 12 months included, up to 48 months with the Extended history add-on.

Nothing is deleted before your window ends, a safety buffer of at least 7 days applies beyond it, and the Extended history add-on keeps longer windows exactly as before. If you want a longer record, the add-on is available on the pricing page.

Work has a conversation, and it now lives where the work does. This release adds a messaging layer across the whole product:

• A room on every record — projects, tasks, clients, contacts and people each carry their own conversation. Decisions land next to the thing they were about.
• Team chat — one workspace-wide channel for everything that isn’t about a single record.
• Journals joined the stream — work journals are messages now: same composer, same room, same history, still filterable to just journal notes.
• @mentions that notify — mention a person and they get a bell notification; reference a project or task and it renders as a live chip that opens the record.
• Sensible message rules — a 15-minute window to edit or delete your own message (marked as edited), and pinning for the messages a room should keep on top.

Privacy is structural: what a mention chip reveals is decided by the reader’s permissions at the moment they look — a reference to something you cannot see stays locked, whoever sent it.

Chat and journal messages are conversational content, so they follow your workspace’s history window — the Terms say exactly which content lives forever and which follows the window.

We planned three tiers. Then we asked the obvious question: why should any team have to study a comparison table to find out which parts of the product they’re allowed to use?

So there are no tiers. PMOlikePRO has one plan — and it contains the entire product:

• $15 per user per month, or $144 per user per year (save 20%).
• Every feature included — projects, scheduling, time tracking, financials and budgets, reports and exports, enforced MFA, audit exports. All of it, for everyone, from day one.
• Every future feature included. New capabilities ship to every customer. Features are never the upsell.
• The only optional extra that may ever exist is additional storage.

Update: the last point has since changed. Optional extras now cover data extras only — how much your organization stores and for how long: Extended history (live on the pricing page) and Storage (coming with the Documents feature). Features are still never the upsell.

Update: both extras are now live — Extended history and Storage packs, side by side on the pricing page. That list is complete and final; see the storage-packs entry above.

The pricing page has the full picture, and the 14-day self-serve trial arrives with launch. Until then, request a demo — walkthroughs are personal, on scenarios that look like your operation.

PMOlikePRO is moving from private development to production. What that means in practice:

• This website — pricing structure, guides, changelog and support are now public, with more arriving weekly.
• Production hardening — the launch checklist is being worked through: registration with company-email verification, billing, and operational monitoring.
• Demo program — walkthroughs with the founder are open now. Request a demo and see the platform on scenarios that look like your operation.

Pricing tiers are published; per-seat numbers are announced at launch.

A release about trust and speed at the same time — because they turn out to be the same work:

• Role-scoped reads. Member and viewer accounts now receive only the projects, tasks, clients and contacts they are actually assigned to — enforced at the database layer. Privacy improves, and so does performance: each session carries a fraction of the data it used to.
• Archive & data lifecycle. Finished engagements move to an archive tab — out of the daily working set, still fully reportable. Auto-archive can sweep long-finished work on a schedule you control, and reports include archived history on demand.
• Write-gate lockdown. Every write path was re-audited and re-gated by role, with a permanent automated guard added to the development pipeline so regressions can’t slip in silently.
• Windowed loading. The calendar and the time ledger now load by visible period, keeping the interface fast regardless of how much history the organization accumulates.

• One lifecycle rule, applied everywhere. Finishing, cancelling or pausing a project or task keeps every hour already worked and releases every future allocation. History stays truthful; capacity comes back to the team automatically.
• Recurring work, remodeled. A weekly duty is now a single task worked over time — one journal, one time history, one progress record — with its schedule materialized onto the dates it recurs. No more clone armies burying the board.
• Schedule polish. Frozen name columns, cleaner drag behavior, overallocation surfacing and a shared legend across every list — the planning surface got a coat of rigor.

• A real time ledger. Time entries moved into a dedicated, append-only store — browsable by period, rolled up per task, per project and per person, and built to survive scrutiny.
• Server-side financial gating. Rates, budgets and costs are now delivered only to manager and admin sessions. Accounts that shouldn’t see money never receive it — not hidden in the interface, simply never sent.
• Dual margins. Effort (planned vs. worked hours) and money (budget vs. actual cost) are reported side by side, so neither can masquerade as the other.
• Structured reports. Branded PDF and Excel exports with delivery status, time and financials — ready for steering meetings and client reviews.

• Enforceable MFA. TOTP two-factor authentication for every account — and organizations can require it outright, holding un-enrolled accounts at the door until they comply.
• Hardened sign-in. Bot-challenged login and rate-limited authentication endpoints.
• Audit trail. Sign-ins, permission changes and destructive operations are recorded, so “who did that?” has an answer.
• Isolation, verified. Tenant isolation and role boundaries re-audited end to end — with the fixes applied and regression guards added to the pipeline.