Before you start.
Open with the prerequisites. What does the reader need to have set up, what permissions do they need, and how long will this take? Two or three sentences, no more.
Admin access to your firm's BankBuild workspace. The register can be generated by any admin — usually the firm's RICS responsible principal or a delegate.
The steps.
Lead in with one sentence framing the procedure. Then move straight into the numbered steps below.
What the output looks like.
The generated register contains four sections: tool name and vendor, intended use, reliability assessment summary, and the date of last review. Each section has a stable URL that you can link to directly — useful when a lender's compliance team asks for evidence on a specific tool.
The PDF version is suitable for attachment to monitoring reports. The HTML version is what RICS expects to see at a public URL on your firm's website.
Common issues.
Auto-detection runs on actual usage events from the last 90 days. A tool that was set up but never used won't appear. To add a tool manually, click Add tool → Manual entry on the AI Register page.
If the Generate button is greyed out, one or more reliability assessments are incomplete. The page will list which tools are blocking — work through them in order. Each assessment takes 2–3 minutes.
If the published URL returns a 404 to a lender, the register may be set to internal-only. Toggle it to public from the same page. Changes propagate within 30 seconds.
Next steps.
- Set a review cadence. RICS expects the register to be reviewed at least quarterly — BankBuild will remind you 7 days before the next review is due.
- Add it to your monitoring report template. The public URL can be embedded in the cover page of every monitoring report your firm issues.
- Pair it with the audit trail. The transparency register answers which tools; the audit trail answers which decision used which tool. Both are required.