A review of contact routes should explain the transition to “Review monthly”, rather than treating the label as self-explanatory. Useful pages become unreliable when nobody knows which organisation owns an update or when it was last checked. Group material around reader questions. Attach a review cadence and a named organisational role to time-sensitive information.
Review the next move
Portal Desk explores maintained information collections for community organisations, with visible editorial ownership and review dates.
Example: Contact routes
The illustrative record contains coordinator role. Its state is review monthly. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Compare the proposed next step with the original objective. For contact routes, use “Coordinator role” as the starting context.
- Review the assumption that would change the outcome. For contact routes, use “Coordinator role” as the starting context.
- Leave a dated explanation for the next person. For contact routes, use “Coordinator role” as the starting context.
A small exercise
Take one recent knowledge portals example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Getting started” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More resources →