For the resource manager

See true capacity against real demand. Commit with confidence.

People, skills, allocations, leave and scenarios in one model, so overcommitment shows on the heatmap before it shows on the delivery date.

In one sentence

AlignX shows the resource manager true capacity against real demand, with skills, availability, leave and conflicts visible before work is committed.

Written forResource ManagerWorkforce Planning DirectorDelivery Director

The solution

What the resource manager sees first.

Capacity heatmap

Firm load per person per month against their ceiling.

Under, healthy, full or over, with a forecast marker where firm plus tentative crosses the line. Read-only, computed from the bookings.

See the resource product

Resource workbench

Every allocation on a timeline, per person, with its state.

Proposed, confirmed, on hold, firm or tentative. Quick-add from the row, and the peak shows against the ceiling.

See the resource product

Skills and proficiency

Proficiency by skill, level one to four, on the person.

Integration architecture, threat modelling, Azure landing zones. Demand names the skill it needs, so the match is skills-aware.

See the resource product

Rebalance scenarios

A scenario compared against the live plan, person by person.

Fourteen resources change. Over-booked months go from fifteen to none. Promote it and the live bookings follow; leave it and nothing moves.

See the portfolio product

Leave and availability

Who is away, when, and for how long, next to the bookings.

Annual, parental, long service, study. The heatmap already knows, so the December plan is not a surprise.

See the resource product

Day to day

What changes.

Without AlignXWith AlignX
The capacity argumentCapacity is guessed, so commitments are made the organisation cannot staff.
The capacity argumentThe heatmap shows the over months before the gate.
The double bookingFound when two portfolios both expect the same architect.
The double bookingFirm load per person across every portfolio, on one row.
The skills gapWe have capacity but not the right capacity, discovered at kickoff.
The skills gapDemand names the skill; the match is skills-aware.
The reprioritisationRebalancing by email over a week.
The reprioritisationA scenario compared against live, promoted when agreed.
The leave clashDecember plan built without the leave register.
The leave clashLeave sits in the same picture as the bookings.
The pipeline questionDemand for unapproved work is invisible.
The pipeline questionDemand can be raised at pipeline stage and shows as forecast.

The AlignX technology

Nothing new to govern.

  • Runs inside Microsoft 365In your tenant, on your Dataverse. Nothing leaves it.
  • Entra ID governs who sees whatThe roles you already run decide access. No second directory.
  • Australian data residencyYour Dataverse environment sits in an Australian region. Purview and retention policies apply as they do everywhere else.

How AlignX sits inside Microsoft 365

Questions

What resource managers ask us.

What resource, PPM and workforce tools does AlignX replace or integrate with?

AlignX replaces the resource module of your PPM (Planview, Clarity, ServiceNow SPM) and your standalone capacity spreadsheets. It integrates with your HR/HCM (Workday, SuccessFactors), Jira for actual effort, and finance for cost rates. One resource model, drawing from the systems that already own the data.

Do I still need Jira and my HR system if we have AlignX?

Yes. AlignX is not there to replace where work happens or where employee data lives. It integrates. Teams keep working in Jira, HR keeps managing people in Workday, and AlignX holds the connected demand-capacity-skills model that no single system holds today. This is what makes consolidation work.

How does AlignX handle capacity when half my team is on shared services and unfunded work?

The model separates funded, unfunded, shared and dedicated capacity with visible ceilings for each. You see who is committed to what, and how much runway is left before over-commitment. Shared service teams appear against every consuming portfolio without double counting.

Can I model skills, not just headcount?

Yes. Every resource carries a skills profile, and demand records specify required skills, not just FTE. Matching is skills-aware, so you spot the \"we have capacity but not the right capacity\" gap before it becomes a hiring rush or a delivery slip.

How do I forecast demand before projects are actually approved?

Demand can be raised at pipeline stage, before funding. You see what is coming down the tunnel and can flag capacity conflicts to the portfolio board before commitments harden.

Will AlignX show me what other portfolios are about to hit my team?

Yes. Enterprise-wide visibility means demand from every portfolio, transformation programme and BAU stream aggregates against your team. No more surprises when three programmes all need your architects in Q3.

How do we handle contractors, secondments and dotted-line resources?

Every resource type has its own record with contract dates, cost rates and reporting lines. Secondments and dotted-line commitments are first-class, not workarounds. When a contract ends, downstream demand it was covering flags automatically for rebalancing.

See where you stand.

Ten minutes, twenty-one questions, an instant maturity score.