{"id":19150,"date":"2026-05-12T13:23:04","date_gmt":"2026-05-12T13:23:04","guid":{"rendered":"https:\/\/sertifier.com\/blog\/?p=19150"},"modified":"2026-05-12T13:23:08","modified_gmt":"2026-05-12T13:23:08","slug":"certificate-of-training-governance-playbook","status":"publish","type":"post","link":"https:\/\/sertifier.com\/blog\/certificate-of-training-governance-playbook\/","title":{"rendered":"Certificate of Training: Standards, Wording, and a Governance Playbook for Credible Issuance"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A <strong>certificate of training<\/strong> is only as credible as the evidence behind it and the controls around how it\u2019s issued. For compliance, safety, and workforce training teams, the challenge isn\u2019t producing a PDF\u2014it\u2019s issuing training credentials consistently across departments, proving what was taught and assessed, and enabling fast verification when an auditor or employer asks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key takeaways<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Define what the certificate proves<\/strong>: attendance, completion, or verified competency\u2014each needs different evidence.<\/li>\n\n\n\n<li><strong>Standardize fields and wording<\/strong> so certificates hold up across teams, vendors, and audits.<\/li>\n\n\n\n<li><strong>Govern issuance like a controlled document<\/strong>: roles, approvals, naming, and version control.<\/li>\n\n\n\n<li><strong>Make verification easy<\/strong> with a recipient-first workflow and employer-friendly checks.<\/li>\n\n\n\n<li><strong>Manage lifecycle<\/strong>: expirations, renewals, and revocations should be designed upfront.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">What a certificate of training is (and how it differs from completion-only proof)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>certificate of training<\/strong> is a credential that attests a person received instruction on a defined topic, within a defined scope, under a defined issuer. The key is <em>traceability<\/em>: the certificate should link back to what was taught, when, by whom, and under what requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>certificate of completion<\/strong> typically proves that someone finished a course or module sequence. It may not prove the learner demonstrated competency, met a minimum score, or performed a skill to standard.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A practical way to avoid misunderstandings is to label the credential based on what it actually proves:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Attendance<\/strong>: the person was present for training.<\/li>\n\n\n\n<li><strong>Completion<\/strong>: the person completed required activities (modules, time, assignments).<\/li>\n\n\n\n<li><strong>Competency<\/strong>: the person demonstrated capability against stated criteria (assessment, observation, performance).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Comparison table: training certificate vs completion proof<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Attribute<\/th><th>Certificate of training<\/th><th>Certificate of completion<\/th><\/tr><\/thead><tbody><tr><td>Primary claim<\/td><td>Training delivered on a defined scope<\/td><td>Course finished<\/td><\/tr><tr><td>Best for<\/td><td>Compliance documentation, safety programs, workforce qualification pathways<\/td><td>Professional development, onboarding milestones, internal learning paths<\/td><\/tr><tr><td>Evidence expectation<\/td><td>Training outline + attendance\/completion + (optional) assessment records<\/td><td>Completion status and date<\/td><\/tr><tr><td>Audit readiness<\/td><td>Higher when scope, version, issuer, and record links are included<\/td><td>Depends on supporting records outside the certificate<\/td><\/tr><tr><td>Verification need<\/td><td>Often requires external verification and lifecycle controls<\/td><td>Often used as informational proof; verification varies<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">What to include: required fields, training scope, and audit-friendly details<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For consistent issuance, treat your certificate as a standardized data record, not just a document. Your goal is to make the credential understandable to someone outside your team without extra emails.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Required fields (baseline)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Recipient legal name<\/strong> (and optional unique learner identifier if your program uses one)<\/li>\n\n\n\n<li><strong>Credential name<\/strong> (use a controlled naming standard)<\/li>\n\n\n\n<li><strong>Issuer name<\/strong> (entity responsible for the claim)<\/li>\n\n\n\n<li><strong>Issue date<\/strong><\/li>\n\n\n\n<li><strong>Training date range<\/strong> (if different from issue date)<\/li>\n\n\n\n<li><strong>Delivery modality<\/strong> (in-person, virtual, blended, self-paced)<\/li>\n\n\n\n<li><strong>Instructor or training provider<\/strong> (if relevant to credibility)<\/li>\n\n\n\n<li><strong>Certificate ID<\/strong> (unique, non-guessable where possible)<\/li>\n\n\n\n<li><strong>Verification method<\/strong> (a link or process to verify authenticity)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Training scope details that reduce audit back-and-forth<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Learning objectives<\/strong> in 3\u20137 bullets<\/li>\n\n\n\n<li><strong>Topics covered<\/strong> (outline-level, not a full textbook)<\/li>\n\n\n\n<li><strong>Duration<\/strong> (stated clearly; avoid ambiguous \u201chours\u201d if it varies by learner)<\/li>\n\n\n\n<li><strong>Applicable policy, SOP, or program reference<\/strong> (internal reference name\/number)<\/li>\n\n\n\n<li><strong>Course version<\/strong> (ties the certificate to the correct content revision)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Wording patterns that hold up<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use plain language that matches the evidence you can produce.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Attendance wording<\/strong>: \u201cThis certifies that [Name] attended training on [Topic], delivered by [Issuer\/Provider], on [Date(s)].\u201d<\/li>\n\n\n\n<li><strong>Completion wording<\/strong>: \u201cThis certifies that [Name] completed [Course] requirements on [Date].\u201d<\/li>\n\n\n\n<li><strong>Competency wording<\/strong>: \u201cThis certifies that [Name] demonstrated competency in [Skill\/Standard] as evaluated by [Method] on [Date].\u201d<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Failure mode to avoid: mixing claims. If you say \u201cdemonstrated competency\u201d but only track attendance, you create an avoidable compliance risk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The asset: Certificate governance playbook (roles, approvals, naming, version control)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When multiple departments issue certificates, credibility problems usually come from inconsistent naming, uncontrolled templates, and unclear authority. A lightweight governance playbook prevents drift.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Roles and responsibilities (RACI-style)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Program owner (Accountable)<\/strong>: defines what the certificate claims and what evidence is required.<\/li>\n\n\n\n<li><strong>Training admin (Responsible)<\/strong>: issues credentials, manages rosters, handles corrections.<\/li>\n\n\n\n<li><strong>Compliance\/Safety (Consulted)<\/strong>: validates required fields and retention requirements; reviews claim language.<\/li>\n\n\n\n<li><strong>HR\/L&amp;D (Consulted)<\/strong>: aligns to internal frameworks and learning pathways.<\/li>\n\n\n\n<li><strong>IT\/Security (Consulted\/Approver)<\/strong>: reviews data handling, access control, integrations, and vendor security.<\/li>\n\n\n\n<li><strong>Legal\/Privacy (Consulted)<\/strong>: reviews consent language, privacy notices, and cross-border considerations (if applicable).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Approvals: what must be signed off<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Credential definition<\/strong>: name, description, and what the holder is being certified for.<\/li>\n\n\n\n<li><strong>Evidence rule<\/strong>: attendance-only vs completion vs competency, with required artifacts.<\/li>\n\n\n\n<li><strong>Template and wording<\/strong>: standardized language approved once, reused often.<\/li>\n\n\n\n<li><strong>Lifecycle policy<\/strong>: does it expire, require renewal, or allow revocation?<\/li>\n\n\n\n<li><strong>Verification approach<\/strong>: how a third party checks authenticity.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) Naming standards (reduce duplicates and confusion)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use a predictable structure<\/strong>: \u201c[Program\/Domain] \u2013 [Topic] \u2013 [Level or Claim Type]\u201d<\/li>\n\n\n\n<li><strong>Separate topic from claim<\/strong>: for example, \u201cForklift Safety \u2013 Completion\u201d vs \u201cForklift Safety \u2013 Competency.\u201d<\/li>\n\n\n\n<li><strong>Define controlled vocabulary<\/strong>: \u201cAttendance,\u201d \u201cCompletion,\u201d and \u201cCompetency\u201d mean specific things in your organization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Version control rules (tie the credential to what was taught)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Version the curriculum<\/strong>, not just the certificate template.<\/li>\n\n\n\n<li><strong>Record the version on the credential<\/strong> so you can answer \u201cWhich SOP revision was trained?\u201d<\/li>\n\n\n\n<li><strong>Define change thresholds<\/strong>: minor edits may not require a new credential version; major scope changes should.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Evidence and assessment: how to document competency vs attendance<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The fastest way to make your certificates more credible is to align the claim with the evidence you can retrieve quickly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Evidence ladder (choose the lowest level that meets your needs)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Level 1: Attendance record<\/strong> (roster, sign-in, virtual attendance log)<\/li>\n\n\n\n<li><strong>Level 2: Completion record<\/strong> (module completion, required activities, acknowledgement)<\/li>\n\n\n\n<li><strong>Level 3: Knowledge check<\/strong> (quiz\/exam attempt record, pass criteria, date)<\/li>\n\n\n\n<li><strong>Level 4: Performance assessment<\/strong> (skills observation checklist, evaluator identity, criteria, result)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Common failure modes (and how to prevent them)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ambiguous pass criteria<\/strong>: define what \u201cpassing\u201d means and store it with the record.<\/li>\n\n\n\n<li><strong>Orphaned evidence<\/strong>: avoid keeping the only proof in an inbox or a spreadsheet with unclear ownership.<\/li>\n\n\n\n<li><strong>Evaluator ambiguity<\/strong>: for competency claims, record who assessed and under what rubric.<\/li>\n\n\n\n<li><strong>Template drift<\/strong>: different teams editing certificate language until it no longer matches the evidence.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Verification workflow: recipient experience and employer checks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Verification is where a certificate shifts from \u201cnice to have\u201d to \u201ctrusted.\u201d A good workflow supports two audiences: the recipient sharing their credential and the verifier confirming it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Recipient experience (shareable, portable proof)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>One link<\/strong> the holder can share with HR, an employer, or an auditor.<\/li>\n\n\n\n<li><strong>Clear credential details<\/strong>: what it is, who issued it, and what it covers.<\/li>\n\n\n\n<li><strong>Optional badge pathway<\/strong>: if your audience uses digital credentials, you can issue a digital badge aligned to the same claim for easy sharing.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you use Open Badges, align to the published specification so the credential is portable across systems. See the <a href=\"https:\/\/www.imsglobal.org\/spec\/ob\/v3p0\" target=\"_blank\" rel=\"noopener\">Open Badges specification<\/a> for terminology and data model expectations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Employer\/auditor checks (fast authenticity confirmation)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Confirm issuer<\/strong>: the verifying page should clearly show the issuing organization.<\/li>\n\n\n\n<li><strong>Confirm status<\/strong>: valid, expired, or revoked should be unambiguous.<\/li>\n\n\n\n<li><strong>Confirm scope<\/strong>: the verifier should see the training\/competency claim and dates without requesting extra files.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Managing revocations, expirations, and renewals for training credentials<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Training credentials often have lifecycle requirements. If you don\u2019t design these upfront, teams will handle them ad hoc, which creates inconsistent records.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Set lifecycle rules per credential type<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No expiration<\/strong>: use when the content doesn\u2019t become outdated and the risk is low.<\/li>\n\n\n\n<li><strong>Expiration<\/strong>: use when knowledge or procedures change, or when policy requires periodic refreshers.<\/li>\n\n\n\n<li><strong>Renewal<\/strong>: define what counts as renewal (refresher course, reassessment, supervisor sign-off).<\/li>\n\n\n\n<li><strong>Revocation<\/strong>: define revocation reasons (issued in error, misconduct related to credential claim, invalid assessment) and the approvals required.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Operational controls you\u2019ll need<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Reason codes<\/strong> for revocation and re-issuance (so reporting is consistent).<\/li>\n\n\n\n<li><strong>Audit trail<\/strong> of who changed status and when.<\/li>\n\n\n\n<li><strong>Recipient notification workflow<\/strong> for expiration reminders and status changes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to scale: templates, automation, and credential management<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Scaling issuance across departments requires standardization plus controlled flexibility. The goal is to issue credentials quickly without letting every team invent its own rules.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Template system (standard where it matters)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>One master template per credential family<\/strong> (safety, compliance, onboarding), parameterized by topic.<\/li>\n\n\n\n<li><strong>Locked wording blocks<\/strong> for the claim language and required fields.<\/li>\n\n\n\n<li><strong>Configurable blocks<\/strong> for delivery modality, instructor, or program references.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Automation options (reduce manual errors)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Roster-based issuing<\/strong> to reduce typos and mismatched dates.<\/li>\n\n\n\n<li><strong>Rules-based awarding<\/strong> (issue upon completion criteria) when your learning systems can provide completion status.<\/li>\n\n\n\n<li><strong>Central status management<\/strong> for expirations, renewals, and revocations.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Security and procurement considerations<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Access controls<\/strong>: limit who can issue, edit templates, and change credential status.<\/li>\n\n\n\n<li><strong>Data minimization<\/strong>: store only what you need on the credential; keep sensitive data in systems of record.<\/li>\n\n\n\n<li><strong>Verification integrity<\/strong>: prefer verifiable links\/pages over attachments forwarded by email.<\/li>\n\n\n\n<li><strong>Integration fit<\/strong>: confirm how credential records align with your HR, LMS, or compliance tooling.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Internal resources (to support your certificate system)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/sertifier.com\/\" target=\"_blank\" rel=\"noopener\">Sertifier digital credentialing platform overview<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/sertifier.com\/blog\/\" target=\"_blank\" rel=\"noopener\">Sertifier resources on digital credentials and verification<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation steps (for compliance, safety, and workforce training teams)<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Inventory your certificates<\/strong>: list every certificate of, certificate of completion, and training record currently issued across departments.<\/li>\n\n\n\n<li><strong>Classify each credential claim<\/strong>: attendance vs completion vs competency; remove mixed\/ambiguous language.<\/li>\n\n\n\n<li><strong>Define required fields<\/strong> and a standard wording library approved by compliance\/safety.<\/li>\n\n\n\n<li><strong>Set governance<\/strong>: assign an accountable program owner, define who can issue, and establish template\/version control.<\/li>\n\n\n\n<li><strong>Design verification<\/strong>: decide what verifiers see, how status is displayed, and how recipients share credentials.<\/li>\n\n\n\n<li><strong>Implement lifecycle rules<\/strong>: expiration, renewal criteria, revocation approvals, and notification workflows.<\/li>\n\n\n\n<li><strong>Pilot and scale<\/strong>: start with one high-risk program, validate audit readiness, then expand to other departments.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Decision checklist<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Claim clarity<\/strong>: Can we state exactly what the certificate proves in one sentence?<\/li>\n\n\n\n<li><strong>Evidence retrievability<\/strong>: Can we produce supporting records without chasing emails or spreadsheets?<\/li>\n\n\n\n<li><strong>Consistency<\/strong>: Are naming, required fields, and wording standardized across departments?<\/li>\n\n\n\n<li><strong>Verification<\/strong>: Can an employer\/auditor verify authenticity and status quickly?<\/li>\n\n\n\n<li><strong>Lifecycle<\/strong>: Do we have clear rules and an audit trail for expirations, renewals, and revocations?<\/li>\n\n\n\n<li><strong>Access control<\/strong>: Do we control who can issue and who can change status?<\/li>\n\n\n\n<li><strong>Portability<\/strong>: If needed, can the credential be shared as a digital credential (e.g., Open Badges) without rework?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">People Also Ask (FAQ)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What is the difference between a certificate of training and a certificate of completion?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A certificate of training attests training was delivered on a defined scope and dates by an issuer. A certificate of completion attests the learner finished required course elements. Neither automatically proves competency unless you explicitly document assessment and criteria.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What should a certificate of training include for audit purposes?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">At minimum: recipient name, credential name, issuer, issue date, training date(s), a unique certificate ID, and a verification method. For stronger audit readiness, include learning objectives, topics covered, course version, and references to relevant policies or SOPs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can a certificate of training prove competency?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It can, but only if the credential claim matches documented assessment evidence (e.g., rubric-based observation, test criteria, evaluator identity, and results). If you only track attendance, keep the claim limited to attendance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do employers verify a training certificate?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The most reliable approach is a verification page or link that confirms issuer identity, credential details, and current status (valid\/expired\/revoked). Avoid relying on forwarded attachments as the primary proof.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should training certificates expire?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Some should, especially when procedures, policies, or safety requirements change. Decide per credential and document the renewal pathway so status changes are consistent and auditable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do we prevent different departments from issuing inconsistent certificates?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use a governance playbook: controlled naming, locked wording, required fields, role-based approvals, and version control tied to curriculum changes. Centralized credential management helps enforce those rules at scale.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion: make your certificate of training verifiable, governed, and scalable<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A credible <strong>certificate of training<\/strong> is a controlled credential: it states a precise claim, references the right scope and version, and can be verified with a clear status. If you standardize your fields and wording, set governance roles, and design lifecycle and verification workflows, you reduce audit friction and improve consistency across departments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re managing training documentation across multiple programs, manual templates and scattered records make it hard to stay consistent, answer verification requests, and control expirations or revocations. A credential management workflow can standardize issuance and make verification straightforward for recipients and employers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/app.sertifier.com\/en\/signup\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Start free trial<\/strong><\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn what a certificate of training should prove, what to include for audits, and how to govern issuance across departments with consistent wording, verification, and lifecycle controls.<\/p>\n","protected":false},"author":3,"featured_media":19149,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"","rank_math_description":"","rank_math_focus_keyword":"Certificate of Training","rank_math_canonical_url":"","footnotes":""},"categories":[1430,939],"tags":[],"class_list":["post-19150","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-certificates","category-digital-credentials"],"_links":{"self":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/19150","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/comments?post=19150"}],"version-history":[{"count":1,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/19150\/revisions"}],"predecessor-version":[{"id":19176,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/posts\/19150\/revisions\/19176"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media\/19149"}],"wp:attachment":[{"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/media?parent=19150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/categories?post=19150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sertifier.com\/blog\/wp-json\/wp\/v2\/tags?post=19150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}