What can be configured?
Familiar terminology and relevant fields
Use labels and information structures that make sense to the people maintaining records. An industry neutral platform can support different operating contexts without requiring every team to adopt the same sector language.
Assessments suited to the task
Create configurable questions and checklists for control reviews, supplier assessments, operational checks and other assurance activities.
Linked records and accountable work
Relate risks, controls, incidents, documents and actions so that teams can follow an issue through the relevant management process.
How can existing information be brought across?
Implementation support includes preparation and conversion of customer data for import. Review the quality and structure of existing registers before deciding what to migrate, consolidate or archive.
A clear starting scope helps establish the fields, ownership and links required for useful records after launch.
What integration options are available?
iGRCs provides APIs for importing and exporting data, alongside spreadsheet export. These options can support exchanges with other applications and reporting tools.
Each integration needs a defined purpose, agreed data fields, suitable authentication and testing. A discussion of APIs does not imply that a ready-made connector exists for every external product.
Configuration within a standard service
iGRCs is provided as a standard SaaS platform. Configuration should preserve security, performance and future upgradeability. Any development ideas that lead to improvements in functionality are for the benefit of all our customers.
Frequently asked questions
Is configuration the same as bespoke development?
No. Configuration adapts supported options within the platform. Bespoke development changes software code and is excluded from the standard service described here.
Which integrations are already available?
Tell us which application and data flow you have in mind. We will confirm the relevant API options and any existing connection rather than assume compatibility.
Can our existing terminology be retained?
Configurable labels and fields can help reflect your working language. Confirm the particular requirements during a demonstration.
Discuss your information flow
Share your current registers, priority processes and proposed connections so we can explore a practical configuration.