Twenty candidates, each with a different profile, a different deadline and a portfolio in a different state. This workspace puts the caseload on one screen, flags the mechanical gaps in every file, and records who did what and when. The judgement stays with your people.
Try the workspace →Three roles in the demo: adviser, reviewing expert, management.
Fictional data, held on your device. In your own installation: accounts per organisation, rights per role, hosting where you need it and a data processing agreement.
Advisers do not lose time on the advice, they lose it on reconstructing where each candidate got to, chasing the evidence that never arrived, and writing up afterwards what an auditor will want to see. Software cannot judge whether a piece of experience demonstrates a competency. It can absolutely stop you finding out three weeks before a deadline that an area was still empty.
Every candidate with their stage, deadline and coverage, sorted so the urgent ones surface.
Empty areas, unattached evidence, unmeasurable results, borrowed “we”, duplicates between areas.
Every action recorded, never edited, exportable to CSV when someone asks you to prove the process.
A pilot means a handful of real files, your advisers, and a fortnight of us watching what breaks. Pricing, hosting and the review workflow get decided from that, not from a slide.
Talk about a pilot →No. It flags mechanical facts: an empty area, evidence with no issuer, a result with no number, the same activity used twice. Whether an experience genuinely demonstrates a competency is judged by your adviser, your reviewer, and ultimately by the assessors. We do not want that decision and we do not take it.
Quality frameworks ask providers to evidence that support actually happened and that decisions were traceable. The trail records every action, is never edited, and exports to CSV so you can hand it over as it is.
That is open, deliberately. A licence per organisation and a price per candidate both make sense for different sizes of provider, and we would rather settle it with the first pilots than publish a number we would have to walk back.
Accounts and roles that actually enforce anything, separation between organisations, a real database, hosting where your regulator expects it, and a data processing agreement. All of that is the work after a pilot is agreed, not before.
Updated on · Published by ProRédaction