go-live updates & timetable
The BRCGS Directory will soon be upgraded to a next generation replacement.
As we progress throughout development toward go-live this page will provide regular updates, FAQs and key-date information as and when available.
This page was last updated; 31st July 2020
If your query is not covered on this page, or you require further information, please contact firstname.lastname@example.org
Certification Body Directory access (30 July 2020)
Access to the Directory via Trace One Network will soon be closed.
With immediate effect; All Certification Body Directory users should access the current Directory exclusively via the Login link at the top right of this page.
If any Certification Body users require a password reset, please contact email@example.com, stating the account username requiring a password reset.
New passwords will be issued within 48 hours. Users can continue to login via trace one network until the new password is issued.
Updated intermitently as new queries are raised or previous answers updated
Q1: Will there be new audit report templates for the new Directory?
A; Yes; New audit templates containing additional tags for all audit types will be released in advance of go-live. These additional tags will enable the new Directory to make a number of administrative decisions previously manually actioned by the administrator. This will make the audit submission process far quicker and reduce the opportunity for human error
Q2; Will the audit report templates we use today work in the new Directory?
A; To be confirmed. We recognise there will be a period where audit reports completed for the old Directory will be submitted to the new. We aim to mitigate the need to recreate those reports in new templates, however the basis for this has yet to be defined
Q3; Will Insight still be available?
A; Yes. There may be a brief interruption of service as the platform is reconfigured for the new Directory, however this is not expected to be prolonged
Q4; Do we have to recreate all our auditors in the new Directory?
A; No – auditor profiles will be migrated to the new Directory. However there will be a period of time where new profile creation and amendments to existing profiles is suspended to allow data-preparation for the move
Q5; When is API / cross-platform synchronisation available
A; We expect API connectivity to be available soon after go-live. The basis & scope for API projects has yet to be defined
Q6; Will my existing user credentials work in the new Directory?
A; Prior to go-live BRCGS will ask all Certification Bodies to declare which user accounts should be recreated (& if any additional accounts) in the new Directory. New passwords will be required for all users
Q7: If there is a period where the Directory is unavailable during switchover, will this be recognised in KPI assessments?
A; Yes, where submissions cannot be administrated due to Directory down-time only
Q8; How are suppliers being notified of this change?
A; Suppliers will be informed of the switchover via username and logo fulfilment and by email bulletins sent daily to sites with audits due
Q9; Will previously set up audit sharing relationships be recognised in the new Directory?
Q10: Will the public Directory remain?
A; Yes; the publicly accessible Directory listing Certification Bodies and certificated sites will be superseded by a modernised replacement
Switchover milestones and dates
API interest registration (TBC)
Training materials available (TBC)
Training platform available (TBC)
New audit documents released (TBC)
Certification Body action required
Declare sub/remote office address & contact details (format & dates TBC)
Declare user accounts required (format & dates TBC)
(all dates and durations yet to be defined)
Audit submission freeze (TBC)
Auditor profile creation freeze (TBC)
Auditor profile amendment freeze & validation (TBC)
Holding area closure (TBC)
In progress & in revision audits resolved (TBC)
Existing Directory becomes inaccessible (TBC)
New Directory made available for audit submissions and auditor profile amendments (TBC)
API availability (TBC)