Introduction

This KB describes a production-ready pattern for tracking ISO 9001 and ISO 14001 certificates in Parakeet Risk, including a normalized record schema, 90/60/30 day reminder logic, example renewal SLAs, and export steps. It aligns with Parakeet’s certification workflows and notifications so teams can stay audit‑ready without abandoning spreadsheet-based processes. See Certification Automation and Features.

Data model: certificate record (field dictionary)

Use one record per certificate (per site or multi‑site scope). The fields below are minimal, auditable, and map cleanly to Parakeet forms, lists, and exports.

Field	Description	Example/Format
Issuer	Accredited certification body (CB).	“Acme Certification Services”
Scope Text	Formal scope statement appearing on the certificate.	“Design and manufacture of food-contact packaging.”
Certificate Number	Unique CB identifier; include revision if present.	“QMS-9001-2023-0147 Rev B”
Effective Date	Certificate effective/start date.	ISO date (YYYY‑MM‑DD)
Expiry Date	Certificate end date on the CB record.	ISO date (YYYY‑MM‑DD)
Sites/Materials Covered	Site list and/or material families within scope.	“Plant A; Plant C; PET/HDPE bottles”
Reviewer	Internal owner who validates updates.	“Quality Manager – Plant A”
Approver	Management representative (MR) or compliance lead.	“Director, Quality & Compliance”

Notes:

• Add optional fields as needed (CB contact email, surveillance cadence, uploaded PDF, NC/CAPA link). Keep the core dictionary stable for clean exports.

• Parakeet’s spreadsheet synergy lets you import these fields from existing Excel trackers while adding workflow, audit trail, and reminders. See Features.

Reminder logic (90/60/30 with escalation)

Goal: ensure recertification or extension is completed before Expiry Date and that updated certificates are re‑approved and distributed.

Trigger basis

• For each certificate, compute DaysToExpiry = Expiry Date – Today.

• Run evaluation daily; queue reminders when DaysToExpiry matches thresholds and when required tasks are incomplete.

Notification tiers

• T‑120 (pre‑check): create a planning task to confirm CB schedule, scope changes, and internal audit readiness.

• T‑90: notify Reviewer; open “Recertification Plan” task. Delivery via in‑app + email; optionally mirror to Google Calendar.

• T‑60: escalate to Approver; require CB date confirmation and document set freeze plan.

• T‑30: high‑priority alert to Approver and site leadership; block risky shipments/process changes that would invalidate scope (use Parakeet policy tasks). Optional Slack/Teams alert via Slack integration or Microsoft Teams integration.

• T‑7: final checkpoint that the renewed certificate file is uploaded and approved.

• T+1 (lapse): trigger incident workflow and customer notification checklist as applicable.

Auto‑closures

• When a renewed certificate is uploaded, validated by Reviewer, and approved by Approver, close all open reminder tasks for that record.

Renewal SLA examples (adapt to your CB contract)

Use service levels to define who does what, by when. Attach these SLAs to the Reminder tasks.

• CB booking: Recertification audit date confirmed ≥75 days before Expiry; owner: Reviewer; approver: MR/Approver.

• Document set freeze: Required procedures, risk assessments, and records finalized ≥14 days before CB audit; owner: process owners; approver: MR.

• Nonconformity (NC) response: Submit NC responses and evidence ≤15 business days after CB report; owner: CAPA owners; approver: MR.

• Certificate distribution: Upload renewed certificate ≤3 business days of receipt; Reviewer validates metadata; Approver signs off; automated distribution to customer portals where applicable.

• Scope change control: Any de‑scope/up‑scope approved within 5 business days by MR and operations; downstream risk registers updated in Parakeet.

Workflow configuration in Parakeet

• Record template: Create a Certificate content type with the field dictionary above. Enable file attachments for CB PDFs and surveillance reports. See Certification Automation.

• Calendar sync: Sync Effective/Expiry and key SLA dates to team calendars using Google Calendar integration.

• Chat alerts: Route 60/30/7-day alerts to the appropriate channel with Slack or Microsoft Teams. Include certificate link, site, scope, and pending actions.

• Action boards: Auto‑create remediation cards for NCs and recertification tasks using Trello integration; two‑way sync status back to Parakeet.

• Spreadsheet synergy: Import existing Excel trackers, preserve columns, and layer on approvals, validations, and audit logs. See Features.

Exports and “what the screenshots show”

While this KB doesn’t include images, your export views should display the following so auditors can reconcile certificates quickly:

• List export (CSV/Excel): One row per certificate with all field dictionary columns, plus computed “DaysToExpiry,” “Status” (Active/Planned/Lapsed), and “Next Action Due.”

• Detail export (PDF): Certificate metadata, approval trail (Reviewer/Approver with timestamps), file hash of the uploaded PDF, and a change log (who changed what, when).

• Audit pack export: Bundle current certificate PDF, surveillance reports, NC/CAPA summaries, and scope confirmation into a single archive.

UI callouts to capture in your internal screenshots:

• Certificate list with filter = “Expiry ≤ 60 days.”

• A certificate detail page showing populated Scope Text and Sites/Materials Covered.

• An approval panel with Reviewer approval logged and Approver sign‑off complete.

• A reminder task at T‑30 and the linked Trello card or Slack thread.

Supplier certificate roll‑up (optional)

If you extend ISO tracking to supplier quality/environmental certifications, set supplier as a parent entity and roll up risk status to your third‑party dashboards. Use Parakeet’s integrations and monitoring patterns from Solutions and industry pages like Manufacturing or Packaging to align with existing supplier oversight workflows.

Audit readiness tips

• Evidence integrity: Store the issued PDF and lock metadata after approval; any edits require a new approval.

• Single source of truth: Avoid duplicate trackers by designating Parakeet as authoritative and scheduling a weekly export for downstream teams.

• Change control: Tie scope changes to CAPA and policy workflows; keep an audit trail.

• Business continuity: Link certificate status to incident playbooks so an unexpected lapse initiates communications and containment. See Continuous Compliance.

Quick start checklist

• Create the Certificate record type using the field dictionary.

• Bulk‑import current certificates from Excel.

• Configure reminder rules (T‑120/90/60/30/7/T+1) and owners.

• Connect Google Calendar and Slack/Teams channels.

• Define and publish renewal SLAs; embed them in task templates.

• Test with a staging certificate set to expire in 10–14 days to validate alerts and closures.