Concourse → Guides
Guides for planning a portal
Practical reading for the person who has been asked to "sort out the intranet". Use them with or without us.
guide 1
Writing labels people understand
Labels should name what people will find or do. "Holiday and leave" beats "HR Hub". "Report a fault" beats "Facilities". Avoid words that describe a container rather than its contents, such as resources, hub, zone or quick links. Keep labels short, test them by asking someone where they would look for a specific item, and change the label, not the person, if they guess wrong.
guide 2
Who owns which content
Every page needs a named owner, not a team name. The owner is responsible for accuracy and for responding to review reminders. Where content is copied from a source of truth elsewhere, such as an HR policy, link to that source instead of duplicating it. Agree what happens when an owner leaves: content should pass to their replacement, not become orphaned.
guide 3
Planning access for external users
Suppliers, members and partners need accounts that can be approved, reviewed and removed without fuss. Decide who approves new external users, how often access is reviewed and what happens when a relationship ends. Avoid shared logins; they make it impossible to remove one person's access or to see who did what.
guide 4
Ten questions to ask any portal supplier
- How will you find out what our users need?
- Who will own content after launch, and how will you prepare them?
- Which platform, and why that one for us?
- What will it cost to run each year, all in?
- How do we leave if we need to?
- How do you check accessibility?
- Who approves user accounts?
- What happens to personal data in old content?
- What support hours do you offer, honestly?
- What will you not do?