@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix content: <http://purl.org/rss/1.0/modules/content/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<https://lhero.org/portfolio/lh-governance-documents/>
  a sioc:Post ;
  dc:title "Review reminders" ;
  dcterms:identifier 148024 ;
  dc:modified "2026-09-21T16:11:44Z"^^xsd:dateTime ;
  dc:created "2026-09-21T16:11:44Z"^^xsd:dateTime ;
  sioc:link <https://lhero.org/portfolio/lh-governance-documents/review-reminders/> ;
  sioc:has_creator <https://lhero.org/author/1/#account> ;
  sioc:has_container <https://lhero.org/#posts> ;
  content:encoded """<ul class="lh_portfolio-meta"><li><strong>Part of:</strong> <a href="https://lhero.org/portfolio/lh-governance-documents/">LH Governance Documents</a></li></ul>
<p class="wp-block-paragraph">Owners are reminded through BuddyPress notifications. Nothing is sent on a site where BuddyPress notifications are not active, and there is no other channel.</p>



<h2 class="wp-block-heading">When</h2>



<ul class="wp-block-list">
<li>Once when the next review comes within 30 days.</li>
<li>Once when the review becomes overdue.</li>
<li>Again every 30 days while it stays overdue.</li>
</ul>



<p class="wp-block-paragraph">Only documents in force are checked: drafts, pending and scheduled documents are skipped. Each new notification replaces the previous one, so an owner never has more than one per document. The wording is worked out when the notification is shown, so a due notice reads as overdue once the date passes, and several at once are grouped into one notice linking to the Review due list in wp-admin.</p>



<h2 class="wp-block-heading">Who</h2>



<p class="wp-block-paragraph">The document&#8217;s owner user, or everyone holding its owner role on the site when no user is set. Recipients are worked out at each reminder, so a change of owner takes effect on the next one.</p>



<h2 class="wp-block-heading">Clearing</h2>



<p class="wp-block-paragraph">Recording a new adoption or amendment date moves the next review date, which deletes the notification straight away and starts a fresh cycle. Trashing or deleting the document also clears it.</p>



<h2 class="wp-block-heading">Scheduling</h2>



<p class="wp-block-paragraph">The check runs once a day on each site, on Action Scheduler when available and otherwise on WP-Cron, and is unscheduled when the plugin is deactivated. The notification type and its wording are registered by this plugin, so it must be active on whichever site members read their notifications on; network activation covers that.</p>



<h2 class="wp-block-heading">Admin list</h2>



<p class="wp-block-paragraph">The Governance documents list in wp-admin shows type, owner, adopted and next review, sorts by adopted or next review, and has a Review due view counting documents due within 30 days or already overdue.</p>
"""^^rdf:XMLLiteral ;
  sioc:content """Part of: LH Governance Documents
Owners are reminded through BuddyPress notifications. Nothing is sent on a site where BuddyPress notifications are not active, and there is no other channel.



When




Once when the next review comes within 30 days.
Once when the review becomes overdue.
Again every 30 days while it stays overdue.




Only documents in force are checked: drafts, pending and scheduled documents are skipped. Each new notification replaces the previous one, so an owner never has more than one per document. The wording is worked out when the notification is shown, so a due notice reads as overdue once the date passes, and several at once are grouped into one notice linking to the Review due list in wp-admin.



Who



The document&#8217;s owner user, or everyone holding its owner role on the site when no user is set. Recipients are worked out at each reminder, so a change of owner takes effect on the next one.



Clearing



Recording a new adoption or amendment date moves the next review date, which deletes the notification straight away and starts a fresh cycle. Trashing or deleting the document also clears it.



Scheduling



The check runs once a day on each site, on Action Scheduler when available and otherwise on WP-Cron, and is unscheduled when the plugin is deactivated. The notification type and its wording are registered by this plugin, so it must be active on whichever site members read their notifications on; network activation covers that.



Admin list



The Governance documents list in wp-admin shows type, owner, adopted and next review, sorts by adopted or next review, and has a Review due view counting documents due within 30 days or already overdue.
""" ;
  sioc:topic <https://lhero.org/?taxonomy=author&term=cap-1> .

<https://lhero.org/author/1/#account> rdfs:seeAlso <https://lhero.org/author/1/?feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=author&term=cap-1> rdfs:seeAlso <https://lhero.org/?taxonomy=author&term=cap-1&feed=lhrdf&format=turtle> .