Risks, issues, actions, decisions and every other register, all in one place. Built from the registers project managers already keep in spreadsheets, with the links and 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 come straight in 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 requirements to design decisions, assumptions and constraints, and see the gaps. The traceability workbook can be imported from and exported to Excel.
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 show up 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 show up in Needs attention.
Orbelle brings in projects, phases, tasks and team members from Forecast, and issues, releases and epics from Jira. Records can link to Jira issues, and a new Jira issue can be raised from a record when you ask. Nothing already in either system is changed, 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.
Connect Orbelle to a PostgreSQL database on your network, reached over your VPN. Each person 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.
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 people 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.
