Accounts
Coverage · terms · reports · team · documents
Azumo · Operations Command Center
Welcome back
New Searches
Source report
Billing —
Last refresh: —
Billing Reports
Open source
Source
Bench by Month per Resource
Source
Embedded EazyBI Bench by Month
Source details
Operating Views
Assignees · PMs · Clients
—
PMO QA Center
Actions + QA
Operations quality queue
PMO QA Center
Needs review
—
Passed checks
Alert details
Filter and scan active rows by source, owner, status, and due date.
Procedures & report links
Jira vs Harvest discrepancies
People logging Harvest hours against a client they are not assigned to in Jira.
Run the Harvest Hours report to populate this check.
Harvest assignments
Harvest API · assignments
Active Harvest users
Click the card to show or hide this list.
| User | Type | Team access | PM on |
|---|
Project Status
Live from Jira PSA reports
Loading project reports from Jira…
Account Coverage
Jira PSA Account Coverage
| Client | Status | PM Assigned | CSM Assigned | TL Assigned | Accounts Coverage | Link |
|---|
Due Dates
Next due dates
Upcoming Due Dates —
Upcoming from Jira due dates
| Assignee | Client | Position | Due Date | Assignment |
|---|
Pending Assignments
—
Pending —
| Key | Assignee | Client | Role | Start |
|---|
Bench
—
Bench Report —
Active/New Hires only| Name | Position | Available | Status | Next Assignment | Technology | Due |
|---|
Internal Projects
Internal allocation
Internal Projects
Source
Source details
Harvest Hours Control
Billing hours review
Harvest API
Trends
—
Logged Harvest Hours
—
Harvest API · weekly snapshot
→
Loading weekly sheets…
Forecast — Assignment Due Dates
Jira In Progress due dates
In Progress assignment due dates grouped by month. Each Jira assignment key counts once; overdue rows remain visible until updated.
—
| Due Date | Month | Client | Assignee | Position | Assignment |
|---|
Process Portal
Admin only
Process Definition FrameworkGoal & methodology
The main objective of the Azumo Process Definition Framework is to centralize and standardize the documentation of all key processes within Azumo — from project management and software development to customer service and HR management.
Its mission is to provide a single source of truth accessible to all employees, promoting transparency, efficiency, and consistency in the execution of tasks — a guide for training new employees and for the continuous improvement of processes.
How we get there
01 · Definition & documentation
Formalize steps, owners, inputs, outputs, metrics. Store it somewhere accessible — this module.
02 · Implementation & monitoring
Communicate, train, support with the right tooling (Jira, Harvest), monitor performance.
03 · Evaluation & improvement
Analyze the data, adjust the process, automate repetitive tasks, ask for feedback.
04 · Continuous cycle
Not an end state — every process gets re-evaluated and feeds back into step 01.
💡 Process maturity is not achieved overnight. It requires a long-term commitment to continuous improvement and the active participation of the whole team.
How to document a process
Name
The outcome, as a verb phrase: Assign a person to a project.
Owner & co-responsible role
Owner: accountable end to end. Co-responsible: shares accountability, backs up the owner and notifies PMO of any change. Always roles, never names.
Objective
Why the process exists and its expected result. No steps here.
Scope
Starts when · Ends when · Includes · Does not include.
Trigger
The start event: SOW signed, Epic moves to Hired, Every Friday EOD.
Roles & responsibilities
[Role] — [verb] [object] [when]. Each role is a lane; a system that acts on its own (e.g. Jira) gets its own lane.
Steps
Action verb + object + where: Create the Epic in Azumo Assignments. One action per step. Description (optional): When · Input · Do · Output. Actions only — the “why” goes in Objective.
Decisions
A yes/no question: Does the Epic already exist? Set where both Yes and No go.
⚡ Automated · 🔗 Link · 📄 Doc
Mark ⚡ when a system does the step (don't write “automatically”). Use 🔗 for the tool or file used in the step. Use 📄 when the step produces or needs a document.
Validations
Checks that prove the process worked, ideally measurable: Epic is in “Started”, Hours match the timesheet.
Resources
[Tool] – [what it is]: Jira – Azumo Assignments board.
Related processes
Link hand-offs (previous / next) instead of repeating another process's steps.
Before publishing
For each block ask: does it tell someone what to do, or what to know? Actions go in Steps; facts in Roles, Validations and Resources; reasons in Objective.
Documented processes
This week
Help & Changelog
v3.3
Releases
Before v3.0
Sep 2026
Data integrity — TAG/Aldridge Group deduplicated, PMO QA counts unified with Accounts Coverage, Due Dates now shows ticket column
Sep 2026
Harvest Hours — weekly expected hours and threshold % now remembered across sessions; Forecast assignee filter is now free-text search
Aug 2026
Harvest Weekly — Mon/Sun billing delta columns; Bench/Internal export in spreadsheet template format
Aug 2026
Role-scoped views — Harvest Hours Control, Pending Assignments and Due Dates now filter by role (PM/CSM/TL/Assignee), matching Forecast
Aug 2026
Bench count fix — Bench (FTE) metric now counts people consistently between the Overview card and the detailed bench list
Aug 2026
Nav & dark mode fixes — module dropdowns no longer stack on top of each other; fixed low-contrast KPI icons in dark mode
Aug 2026
Activity log — detects assignment changes, PM changes, and Harvest bench in/out over 14 days
Jul 2026
QA Center — billing × bench anomaly detection (flags people billing ≥80% in Jira who also have bench hours in Harvest)
Jul 2026
Info icons — Utilization Rate (Assignment) and Utilization Rate (Billing) KPI cards now show formula tooltip on hover
Section guide
Overview — KPI snapshot: headcount, utilization, bench, active clients
Operating Views — assignee/PM/client breakdown with filters
PMO QA — anomaly detection: bench conflicts, missing coverage, access mismatches
Accounts Coverage — Jira PSA coverage: who has PM/CSM/TL assigned
Due Dates — assignments expiring within 60 days
Forecast — assignments expiring by month (future)
Bench — people with available capacity
Harvest Hours — weekly logged hours vs. expected; copy to spreadsheet
Logged Harvest Hours — weekly capacity & utilization sheets and Summary (replaces the Excel); Harvest vs. Jira billing cross-check
Project Status — last reported status per project (Current / Former); file a new status report from the row or from Accounts → New report
Pending Assignments — open assignment requests; create one with Assignments → New assignment
Process Portal — Azumo processes: steps, roles, diagrams and weekly cadence (administrators only)
Billing — eaZyBI billing report embed
Trends — historical KPI snapshots
How to
Review a week — Accounts → Logged Harvest Hours. Pick the week from the tabs at the bottom of the sheet; green dot = Open, grey = Closed, blue = imported from Excel.
Close a week (PMO) — once Harvest is complete, click Close week. Numbers and the Jira billing % are frozen; Reopen unfreezes it if something changes.
Check a number — hover the cell for its formula and inputs, or turn on ƒx Formulas to see every column's formula and its source.
Take the data out — ↓ Copy sheet pastes straight into Google Sheets or Excel; ↓ CSV downloads a file.
File a project status report — Accounts → Reports, click + Report on the project (or Accounts → New report). It creates the Project Status ticket in Jira PSA.
Request a new assignment — Assignments → New assignment. It creates the ticket in Jira AA.
Change the theme — moon / sun buttons in the top bar.
Support & access
Access issues — contact PMO. Only
@azumo.co accounts are authorized.Data refresh — board data syncs automatically. The "Last updated" timestamp in the footer shows the most recent sync.
Missing client / wrong coverage — update the source in Jira PSA. The board reflects Jira data within one refresh cycle.
Something looks off with the new design? — add
?lf=0 to the URL to go back to the classic look on this browser (?lf=1 turns the new one back on), and let us know.Feedback / bugs — open a ticket in the PMO project or message Federica González directly.
PMO Board is maintained by the Azumo PMO team. Source: Jira PSA · Harvest · Notion.