
Plan your Cyber Essentials renewal before the current certificate expires. The Cabinet Office’s procurement guidance says suppliers must recertify every 12 months to maintain a valid certificate; failing to do so leaves them uncertified.[4] Start by checking the expiry date, the customer’s requirements and who will coordinate the work. Do not treat last year’s certificate as this year’s completed application.
Build the renewal around what has changed since the previous assessment. Ask your IT provider and certification body what they need, then work backwards from the date you need the outcome. Keep preparation, assessment and any customer deadline separate. A submitted application is not the same thing as a confirmed result.
Start with the certificate and the contract
Find the current certificate and record the organisation name, scope, certification level and expiry date in one place. Compare those details with the customer’s actual requirement. Ask the person managing that relationship to check the contract wording rather than assuming a certificate uploaded last year still satisfies the next review.
If a customer needs continuous certification, ask what evidence it expects during renewal and who should receive the replacement certificate. Raise a possible gap early. Do not assume there is a grace period or describe the business as currently certified once its certificate has expired. Ask the certification body to resolve any uncertainty about dates.
Give the renewal a named owner
Choose somebody inside the business to coordinate the renewal, even if your IT provider handles the technical preparation. Give that person access to the previous application, the assessor’s contact details and the records needed to answer questions. Avoid leaving the whole process in the inbox of somebody who has moved roles.
Agree who will check technical answers, approve purchases and authorise the final submission. Put cover in place for holidays and absences. Ask each contributor for a realistic readiness date based on the outstanding work, rather than picking a submission date first and hoping everyone can meet it. Keep unresolved questions in a shared action record.
Review changes instead of copying old answers
Use the previous answers as a starting point for investigation, not as a completed renewal. Ask what has changed: new starters, another office, replacement devices, different cloud services or a new IT supplier. Have the technical team compare the current working setup with the scope you intend to submit.
For each change, record who checked it and what evidence supports the answer. If staff now work differently, explain that to the certification body before making assumptions about scope. Keep passwords, recovery codes and customer information out of the planning record. Link to the appropriate internal evidence instead of copying sensitive material into a spreadsheet.
Check that the controls still work
A certificate does not replace ongoing maintenance. The Cabinet Office warns that Cyber Essentials provides assurance at the time of testing, and that organisations which stop patching or maintaining secure configuration can become non-compliant well before the year ends.[4] Ask for a current review rather than a promise that everything passed last time.
Request a written account of unresolved updates, unsupported software and access-control concerns. Have your IT team identify what needs changing, who owns it and whether business applications need testing afterwards. Agree maintenance windows before booking disruptive work. Keep a distinction between a proposed fix, an installed change and a change somebody has checked successfully.
Allow time for questions and remedial work
Ask the certification body which current assessment materials and process apply to your renewal. Confirm what happens if an answer needs clarification, a technical issue remains open or an appointment changes. Get any quoted fees and follow-up arrangements in writing. Do not infer a guaranteed turnaround from your experience of the previous assessment.
Where Cyber Essentials Plus is required, discuss the audit arrangements separately and use our preparation guide for the practical checks. Tell the assessor about unavailable devices or planned replacements early. If the schedule becomes tight, agree the next action with the assessor and customer rather than submitting answers you cannot support just to meet an internal diary entry.
Leave the next owner a usable record
After renewal, save the confirmed outcome, submitted answers and agreed scope where the business can find them. Update the person responsible for customer assurance and replace old certificate copies where appropriate. Record the next expiry date and arrange an earlier internal review. Make those records accessible to a colleague rather than dependent on one person’s memory.
If you need help checking the technical preparation, bring the current certificate, known changes and outstanding questions to BMT. Our Cyber Essentials support page explains how preparation support differs from independent assessment. Agree the work and its owner first, then confirm the renewal arrangements with your certification body.
Sources
[4] Cabinet Office: PPN 014, Cyber Essentials scheme (see Q7 on renewal)
