Intranet Homepage Content Plan

Homepage plan Plan a homepage employees can use A practical guide for editors and content owners shaping a useful intranet homepage. Fictional sample context: Northstar Services uses this example to connect homepage slots with employee needs, owners, and review rhythms. Give every slot a job A useful homepage helps an employee find a relevant update, complete a common task, or reach a trusted resource. Each slot below has one primary purpose, a role accountable for its content, and a review rhythm. Northstar's sample mix balances timely information with durable task links. The subject owner checks accuracy; the homepage editor keeps the overall mix clear and current. Worked example: a weekly homepage mix Cadences are illustrative planning choices, not service guarantees. Slot Purpose for employees Owner role Review rhythm Priority update See a timely change and the action or date that matters Internal Communications Editor Check each publishing day; remove or update when no longer current Team news Understand a relevant operational or people update Department Content Owner Review weekly and before the item becomes stale Key task links Reach frequently used tasks without searching across departments Digital Workplace Editor Check links and task relevance monthly Learning pick Find one useful development resource or scheduled learning opportunity Learning Content Owner Review monthly and after a resource changes Turn an announcement into an employee answer Instead of “Operations transformation update,” write: “From Monday, submit equipment requests through the Service Desk. See the request steps and what information to include.” The revised item names the change and gives a clear next action. Continue the plan Move from content slots to ownership, then check the employee journey. Ownership and governance See role responsibilities and a practical review handoff. Employee journeys Check how homepage content supports common moments and tasks. Ownership and governance Make accuracy and coordination explicit A workable example separates editorial coordination from subject-matter accountability. The homepage editor maintains the page's overall mix and checks that items have an owner and review date. The content owner remains responsible for the accuracy and usefulness of their subject matter. When a content owner finds a change, they send the editor revised employee-facing copy, the intended audience, and the next review point. The editor checks fit and placement; the appropriate approver resolves changes that affect broader policy or organizational messaging. Example role matrix Keep one accountable role visible for each item, even when several people contribute. Homepage editor Coordinates the homepage as a whole and makes sure each published slot has a clear purpose. Checks that the item has an owner and review date. Edits for plain language, audience, and a useful next action. Flags overdue or ownerless content for a decision. Content owner and approver The content owner maintains subject accuracy; an approver reviews changes when the publishing workflow calls for it. Confirms facts, audience, and whether the item is still needed. Sends the editor revised copy and a review point. Escalates unresolved subject or approval questions to the responsible role. Run a lightweight review Use the same sequence for routine checks and content changes. Check purpose and accuracy Confirm the intended employee audience, the action or answer, and whether the content is still correct. Confirm ownership and timing Name the responsible role and record the next review point in the team's content tracker. Update, retain, or remove Revise useful content, keep it with a future review point, or remove it when it no longer serves a clear employee need. Governance questions What if the content owner changes? The homepage editor asks the relevant team to name a replacement owner. Keep the item under review until someone accepts responsibility; update the tracker before the next routine review. What if an item no longer has a clear audience? Ask who needs it and what they should do or know. If the answer is unclear, discuss removal or relocation with the subject owner rather than keeping the item on the homepage by default. Who decides when an update needs approval? Use the organization's publishing workflow. In this example, the editor routes changes affecting broader policy or organizational messaging to the appropriate approver; the subject owner still checks factual accuracy. Related planning pages Homepage plan Return to the worked content mix and slot review rhythms. Employee journeys Test whether homepage slots help employees reach a useful next step. Employee journeys Organize content around what employees need Journey-based planning starts with an employee's moment or task, not the department that owns the information. For each moment, identify the answer or action the homepage can help with, then point to a reliable next resource. The example below follows a new starter during the first week. It is a planning scenario, not a claim about Northstar's live onboarding service. Worked example: a new starter's first week Each stage connects an employee need to a content owner and a useful destination. Find essential information The homepage highlights the starter guide and makes the route to practical first-week information easy to spot. People Content Owner Understand a team update A concise team item explains what has changed and who it affects, with a link to the fuller update when needed. Department Content Owner Locate a learning resource A learning pick names the audience and topic and links to the relevant learning resource. Learning Content Owner Review checklist: does each moment work? Use the questions to review content with employees or the relevant owner. Journey moment Homepage support Owner role Usefulness check Find essential information A visible starter-guide link with a clear label People Content Owner Can a new starter identify the right guide without knowing an internal team name? Understand a team update A short update with audience, change, and next action Department Content Owner Can an affected employee tell what changed and whether they need to act? Locate a learning resource A learning item that names its topic and intended audience Learning Content Owner Can the employee tell whether the resource is relevant and where it leads? Return to the planning details Homepage plan Review the example slots, purposes, owners, and rhythms. Ownership and governance See who maintains content and how review decisions are handled.