You are on the PM Workbench demo. A shared example book that resets every night — change anything you like. Features here may not match the live product.Go to pmworkbench.app →
🟡 DEMO

The portfolio book for professional-services firms

Contracts, baselines, people, forecast and actuals in one place — priced per period, compared every month, with the margin against what you bid. Weekly, twice-monthly or monthly, whichever way your people file time.

  • 5 phases
  • 6 roles
  • 23 steps from request to review
  • No password — a code to your work email

How it works

Phases 1 and 2 happen once. Phase 3 repeats for every new project, phase 4 every time card period, phase 5 every month.

  1. 1

    🚀 Subscribe once

    Request a workspace, receive the invitation, sign in.

    • 1.1Request a workspaceOrg Admin · Landing page · onceFill in the request on the landing page: organisation name, work email domain, the person who will be Org Admin.
    • 1.2Workspace provisionedPortfolio Workbench · Our side · within a business dayWe create the organisation, its fiscal calendar in your unit, the status-report checklist and the first Org Admin login.
    • 1.3First sign-inOrg Admin · Sign-in · once per personThere is no password. Enter your work email and a six-digit code arrives.
  2. 2

    🏢 Set up the organisation once

    Calendar, seats, the first logins, holidays. The Org Admin's job.

    • 2.1Confirm calendar & settingsOrg Admin · Organisation · onceCheck the fiscal year start, the time card unit and the timezone; "today" in the book is read in that zone.
    • 2.2Invite managers & grant scopeOrg Admin · Organisation · once, then as people joinCreate the management logins: Director, Senior Managers, Project Managers. Each takes a seat.
    • 2.3Holidays & checklistOrg Admin · Organisation · Resources · once a yearEnter company holidays per country. Mandatory holidays reduce each person's capacity on their country's calendar.
    • 2.4Managers sign inDirector / Senior Manager · Sign-in · once per personEach manager signs in with the emailed code and sets up their authenticator.
  3. 3

    🛠️ Build the book per project

    Projects, baselines, people, assignments — and who may work on them.

    • 3.1Create projectsProject Manager · Project Setup · per projectA form, or the Project Setup template: download, fill in, upload.
    • 3.2Add people & assign themProject Manager · Resources · Project Setup · per projectA person exists once in the library and is assigned many times.
    • 3.3Commit & amend baselinesProject Manager · Baseline · per change orderThe delivery baseline is the initial contract plus every change order; each amendment is a signed delta.
    • 3.4Request PA & Resource loginsProject Manager · Project Setup · per team memberFrom Project Setup → Access on this project: request a Project Administrator or Resource login for a person on the team.
    • 3.5Approve the request?Org Admin · Organisation · as requests arriveThe Org Admin approves each request on the Organisation tab; the seat is taken then.
    • 3.6Team signs inResource · Sign-in · once per personProject Administrators and Resources sign in with the emailed code; no authenticator, because they see no money.
  4. 4

    ⏱️ Run it every week / period

    Forecast, actuals, time off, status, risks, action items.

    • 4.1Enter the forecastProject Manager · Forecast · every periodA grid of people × periods in your unit, from the project's start to twelve months ahead; anything further sits in Remaining until the window reaches it.
    • 4.2Import forecast & actualsProject Administrator · Operations · every periodDownload the template — pre-filled with what the book holds — fill in the yellow cells, upload.
    • 4.3Request time offResource · Resources · as neededVacation, sick, personal — dated, in days; it becomes hours against capacity once approved.
    • 4.4Approve time off?Project Manager · Resources · as requests arriveA manager approves or denies. Only approved time off reduces capacity in the forecast grid.
    • 4.5File the weekly statusProject Manager · Status Reports · every FridayOne report per project per week, ending Friday: answer the checklist, each answer asserts a colour, the worst wins.
    • 4.6Log risks, issues, milestonesProject Manager · Risks & Issues · Schedule · as they ariseOne register across every project you can see, scored severity × probability, highest first.
    • 4.7Action items & Monday packetProject Administrator · Action Items · every MondayA running list per person; on Monday roll the unfinished ones forward.
  5. 5

    📊 Review every month

    Dashboard, forecast vs actual, margins, receivables.

    • 5.1Read the DashboardDirector / Senior Manager · Dashboard · every weekPortfolio at a glance: delivery, status, risks, receivables, action items — each tile is the headline of a tab.
    • 5.2Forecast vs ActualDirector / Senior Manager · Forecast vs Actual · every monthHours and revenue, forecast beside actual, per period, by project and by person; green above forecast, red below.
    • 5.3Record paymentsProject Manager · Receivables · as cash arrivesInvoice amounts are the book's own: hours × bill rate, or the monthly fee once the month is complete.

Who does what

Six roles, one hat each. A role decides which fields a person sees; grants decide which projects.

WPortfolio Workbench

The service — what happens on our side, automatically or by us.

  • Provisions the workspace and sends the invitation
  • Signs people in with a code to their work email
  • Keeps every change to actuals in a history
  • Logs every import and can put it back

Not: See one tenant's data from another — every row is isolated by organisation

OOrg Admin

Holds the organisation's keys: logins, seats, grants and settings. Wears one hat.

  • Approve login requests and manage seats
  • Grant a Director org-wide sight
  • Set the fiscal calendar, time card unit, timezone
  • Keep the company holiday calendar
  • Keep the status-report checklist

Not: See projects, people, forecast or money; Enter any project data

DDirector / Senior Manager

Sees the whole book (with an org-wide grant) or their reporting tree, money included.

  • Read every tab for the projects in scope
  • Create projects and people
  • Approve time off
  • Enter forecast on projects they manage
  • Review Dashboard, Forecast vs Actual, Receivables

Not: Administer logins or settings (that is the Org Admin)

PProject Manager

Owns the projects they manage: the contract, the team, the forecast, the status.

  • Create projects and commit baselines
  • Add people and assign them with rates
  • Enter forecast and import forecast & actuals
  • File status reports, risks, milestones, action items
  • Record payments received
  • Request Project Administrator and Resource logins

Not: See projects outside their own (unless granted)

PProject Administrator

Delegated by a PM to run the project's day-to-day without seeing rates.

  • Enter forecast and import forecast & actuals
  • Assign people (hours and dates, not rates)
  • Keep action items and the Monday packet
  • File status reports and log risks

Not: See rates, revenue, cost or margin — they show as "—"

RResource

A person who delivers the work. Sees their own forecast; does not type it.

  • See their own forecast across projects
  • Request time off
  • Log an issue on a project they are on
  • See and update their own action items

Not: See money, other people's rows, or the project budget; Enter forecast — the PM or Project Administrator does

Request a workspace

Five questions — the same ones provisioning asks. We set the workspace up within a business day and the invitation goes to the person named here.

No password, no card. Self-service sign-up with plans is coming; today we provision on request.