Published Updated

Reception finds visitor-access policy version 3 on the main intranet. A regional team page still offers a PDF of version 2. Both look like normal company guidance, yet they give staff different instructions for checking a visitor's sponsor.
Policy management can work alongside your intranet. Keep the employee portal's familiar navigation, news and team resources. Connect policy discovery to a workflow that identifies the approved release, its audience, acknowledgement requirements and review history. The useful decision is where those controls will live and how every employee-facing route stays connected to them.
An intranet can already have publishing controls. For example, Microsoft documents SharePoint page approval through Power Automate and page version history. Assess your configured process against the policy requirements: ownership, approved content, effective release, audience, responses and scheduled reassessment. If the existing setup meets them, a separate policy application needs a clear additional purpose.
FormKiQ fits when you want those policy activities together in a dedicated business application, connected to the document and governance controls in your AWS environment. The intranet can continue to provide the organisation's broader employee experience. Choose the authority for the policy record explicitly so that two systems do not maintain competing “current” versions.
| Control | Policy application | Intranet connection |
|---|---|---|
| Release decision | Retain the reviewed revision, approval, effective date, owner and release decision. | Present the released title, owner and access route when that release is effective. |
| Employee discovery | Identify the current policy and enforce the reader's access. | Connect navigation, search results and team pages to that approved source. |
| Acknowledgement | Record the identified employee's required response against the exact release. | Provide the configured acknowledgement route and show only authorised status information. |
| Review and replacement | Record reassessment, supersession or retirement, keeping the earlier release and decisions. | Update owned links and indexes, identify stale presentation and direct staff to current guidance. |
Complete approval and confirm the effective date, audience and acknowledgement requirements.
Use the agreed policy reference and authenticated access path on the intranet.
Reconcile changed links, review outcomes and replacements with the policy record.
A configured policy landing link can open the current approved release for an authorised reader. The publication process should keep drafts and future-effective content out of that route. Historical evidence needs the exact earlier revision: an acknowledgement of version 3 must remain attached to version 3 after version 4 is released. The controlled-revisions guide explains the difference between a working file and an approved release.
Check access at the destination as well as visibility in the portal. Microsoft notes that SharePoint audience targeting is different from page security. Showing a policy tile does not grant document access, and hiding it does not establish a restriction. Test employee, reviewer and restricted-document routes using the identities that will actually use them.
Record explicit acknowledgements in the policy workflow. A page view or clicked link does not establish that response. If a change also requires learning or assessment, use the policy and LMS guide to connect those additional records without merging their meanings.
For a policy assistant, the AI policy-answer guide tests current, upcoming and historical questions against their applicable releases. It follows a future-effective policy through source preparation and answer verification.
This fictional connected publication extends the Policy and Procedure Management example. Facilities owns POL-1042; reception and security staff reach it from the main intranet and a regional team page.
Facilities prepares version 3 while version 2 remains current. Security and operations review the proposed procedure. The owner confirms the effective date, audience, required acknowledgement and next review before release.
When version 3 takes effect, the configured publication updates the intranet card's metadata and policy link. Staff open the approved release through the authenticated route. Version 2 stays available as earlier history to permitted users, with its status clearly identified.
A release check finds the regional page's version 2 PDF. The page owner replaces that owned copy with the governed policy link and requests the relevant search update. The publication record keeps the affected page and resolution so the remaining routes can be checked.
A receptionist follows the link and explicitly acknowledges version 3 through the policy application. A reviewer can reach the appropriate review history; an unauthorised reader cannot open restricted material. The owner sees missing responses separately from publication or access failures.
At the scheduled review, Facilities reaffirms the unchanged procedure and sets the next review date, or routes a proposed revision through approval. A later replacement or retirement updates the employee-facing route while preserving the earlier release and response history.
Updating the main card does not recall downloaded PDFs or guarantee that every search index refreshes immediately. Inventory the pages and copies your organisation controls, assign owners and check the published result after changes. Where controlled copies are needed, define their status, update responsibility and review process.
If the policy source is unavailable, use an agreed contingency route and clearly identify any last-verified information. A portal should not label an unverified cached revision as current. Assign failed updates and stale results for reconciliation after recovery. These presentation and recovery rules are part of configuring the connection to the chosen intranet.
For a temporary departure from an internal requirement, the policy-exception guide follows an agreement-registration backlog through approval, review and a decision about the remaining work. It distinguishes the end of permission from verified closure and preserves the earlier terms when renewal is considered.
Begin with the policy workflow and the controls your existing intranet supplies. Where FormKiQ manages the policy lifecycle, connect employee navigation to that approved source and retain the exact release behind each response. Clear ownership of links, updates and review decisions keeps the familiar employee portal connected to current guidance.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.