Risks, issues, actions, decisions and every other register in one place, linked to each other, with the automated reporting a spreadsheet can’t provide.
The portfolio overview shows every project on one screen. Needs attention lists the extreme and high risks, major issues, overdue actions and registers that are due for review.
Existing registers can be imported from Excel or CSV.
Risks, assumptions, issues and dependencies, plus internal risks, actions, decisions, a change register and a punch list for each project. Import your current registers from Excel or CSV, with a preview before anything is added.
Link an issue to the risk that caused it, or a decision to the actions it created. Links work both ways, and a risk can be raised from any record.
Ratings come from your organisation’s risk matrix. Select any chart bar, figure or heat map cell to open the risks behind it. The health rating explains each reason behind it and what would clear it.
Trace each requirement to the design that satisfies it and the verification that proves it, and see the gaps. The matrix exports as a formal, controlled document in Excel and Word, and the workbook can be imported back.
A fixed review format: headline figures, a phase review with its dates taken from the schedule, the four AAR questions, the issue log, changes and lessons learned, linked back to the project’s records.
Agendas, attendees and minutes, with the actions and decisions raised in each meeting. Meetings with minutes still due appear in Needs attention.
A timeline of each project’s phases and milestones against the baseline, with dependencies, actions and other dated records alongside. Slipping milestones appear in Needs attention.
Orbelle brings in projects, phases, tasks and team members from Forecast; the projects you choose from Broadcom Clarity, with their schedule, risks, issues, change requests and team; and issues, releases and epics from Jira, which records can link to. All three are read-only: Orbelle never changes anything in them, and keys and tokens are never saved.
Lessons from every project in one place, each linked to the project and record that produced it, so the next team can find them.
Record what each organisation is trying to achieve, with a measure, a target, the policies it serves and the funding behind it. Link a project once, and its records, Jira issues and approved change costs count towards it. A timeline shows the milestones, the deadline and whether the trend reaches the target.
The project register report, After Action Reviews, the registers workbook and an executive outcomes report, each built from the registers in one step. Client packs leave out internal risks.
Every active project with its health, open risks, issues and overdue actions, grouped by stage, and one Needs attention list across them all. Filter the whole view by client or customer contact.
Connect Orbelle to a PostgreSQL database on your network, reached over your VPN. Each user signs in with their own database account, and every change is recorded with who made it.
Keep the register in SharePoint lists, using your Microsoft work account to sign in. Every register field is its own column, so the data can be read and filtered in SharePoint.
Where your organisation runs Orbelle Server, the desktop app connects through it instead. Users sign in with their organisation or Orbelle account, and don’t need a database account of their own.
If the database can’t be reached, work carries on and is saved locally. Changes are sent as soon as the connection is back, and if two users edit the same record, their edits are combined field by field.
The connection shows at the top of every page. The footer shows the licence, the version and when the database last synced.
When you’re off the VPN, the status indicator turns amber and the register keeps working locally. It reconnects and syncs automatically.
