You don't have to choose. Import your training records and credentials from a spreadsheet in bulk, and everything lands in CORA as real, dated evidence from the moment it's imported, not as a pile of data waiting to be made useful.
One register, not two
A face-to-face manual handling session your team ran last year and a First Aid ticket a worker earned from an external provider are the same kind of row in CORA, separated only by category. That's true whether the record was typed in by hand, read off an uploaded certificate, or brought in from your spreadsheet. Your in-person training history and your external credentials sit in one credential register, not two systems that have to be cross-checked against each other.
What the file needs to look like
A header row naming your columns, and six columns CORA looks for by name rather than by position, so your file doesn't have to match anyone else's layout: the worker's email, the credential or training name, the category, the issuer, the date completed, and the expiry date. Extra columns are ignored rather than rejected, so you can export straight from wherever your records live now and upload it as it is.
Dates work in DD/MM/YYYY or YYYY-MM-DD. Bring up to 2,000 rows in one file, plenty for a full workforce's history in a single upload for almost every provider we build this for.
You see the plan before anything is written
Upload the file and CORA shows you the plan first: how many rows are ready to import, which ones matched an existing worker by email, which didn't match anyone, and which have a date or a formatting problem worth a look. Nothing is written to your register at that point. You're looking at a preview, not a result.
Confirm it, and only the ready rows are written, in one action. Close the tab instead, and nothing has changed. A provider who uploads the wrong file and thinks better of it has left no trace.
Every row matches a real person, on purpose
Each row is matched to a worker already in your account by their email address. A row that doesn't match anyone is named back to you, by row number, so you can see exactly which ones need a look. Adding a new person to your account is a decision you make deliberately, because it uses a paid seat, never a side effect of a spreadsheet upload.
Importing the same file twice changes nothing
A worker who already has a First Aid certificate on record, with the same name and the same completion date, doesn't pick up a duplicate row if that same line turns up in a file you import again. A genuine renewal carries a new completion date, so it lands as a new row and your history stays intact rather than being overwritten. Re-running an import you're not sure went through the first time costs nothing.
Where it lands, immediately
Everything imported feeds what's due, the register itself, and every export, from the moment it's confirmed. A screening clearance imported this morning is already inside CORA's expiry chasing tonight. Day one looks like year four, not like an empty system.
What CORA does with what you bring in
CORA holds what you import exactly as it's given, a record of what your workforce completed and when, not a fresh assessment of whether any of it was any good. Every claim on this page is written the same way every claim on this site is written, about what's actually in the file, checkable in a demo.
See the standard we hold every claim on the site to.
Your existing training provider keeps working
Nothing about bringing your history across asks you to change who delivers your team's training. Your CRM keeps running the participant side of your service. CORA runs the workforce side, and this is what makes your workforce evidence complete from the morning you switch on, not six months later once everything's been retyped by hand. Where you want new training delivered inside CORA too, the library carries 90+ NDIS-specific courses ready to assign alongside whatever you've just imported. See what's in the library.
Common questions
Do I lose my training history if I switch to CORA?
Your training history comes with you. Credentials and in-person training records import in bulk from a spreadsheet, landing in CORA with their real dates intact, so your history feeds the register from day one.
Does importing create new worker profiles automatically?
Every row is matched to an existing worker by email. A row that doesn't match anyone is reported back by row number for you to check, rather than turned into a new person automatically.
Can I import the same file twice without creating duplicates?
Yes. A row matching a worker's existing record, by name and completion date, is treated as already recorded, so importing the same file again changes nothing. A genuine renewal, with a new completion date, lands as a new row.