Find the questions the intranet plan has not answered.

Use the eight areas below to review one proposed portal scope. Keep the decision or example behind each score; a total cannot resolve an unknown access rule or a missing content owner.

Score evidence, not confidence

0 — Unknown: an answer or owner has not been identified. 1 — Assumed: there is a plausible answer that has not been checked. 2 — Written: the requirement, source and responsible owner are recorded. 3 — Checked: representative users or system owners verified it with an example.

For a fictional equipment request, a written form and an assigned facilities owner might earn 2 for workflow. It reaches 3 only after the intended staff member can submit, the receiving team can act and a rejected request has a useful next step. That is different from merely agreeing that requests are important.

1. Audience and tasks

Identify staff groups, locations, devices, languages and access needs. Check recurring questions and actions with representative users.

Evidence level for audience and tasks0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

2. Content ownership

Name the current source, publisher, reviewer, relevant dates, archive rule and correction route for policies, forms, guidance and announcements.

Evidence level for content ownership0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

3. Findability

Define navigation, everyday search terms and useful filters. Check a missing result and what happens to stale or superseded answers.

Evidence level for findability0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

4. Identity and permissions

Record approved sign-in and role sources, contractors, joiners and departures. Check direct links, search, attachments and exports.

Evidence level for identity and permissions0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

5. Internal workflows

Name who receives requests, approves them and owns the final record. Include a rejected or stalled request and its next action.

Evidence level for internal workflows0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

6. Connected systems

List identity, HR, learning, document and ticketing tools. Record what moves, in which direction, how often and who handles failures.

Evidence level for connected systems0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

7. Operating ownership

Name content, technical, access and support owners. Agree correction, release, backup/export and neglected-content responsibilities.

Evidence level for operating ownership0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

8. Launch checks

Prepare find-and-complete tasks, keyboard/phone checks, denied-access examples, connection failures and support handover evidence.

Evidence level for launch checks0 — Unknown1 — Assumed2 — Written3 — CheckedDecision, evidence reference and next owner

Generate planning summaryReset worksheet

All eight areas start as unknown. Nothing is sent or saved.

Summary to select and copy into your own notes

Choose the next investigation

The summary lists unresolved areas as well as the total out of 24. A low score tells you where to investigate; a high score is not approval, security evidence or a certification. Keep the actual example and the person who checked it in your approved project records. If a score changes, record why.

Start with the area that could invalidate the intended first task. An unknown rule about restricted staff records may matter more than several well-documented announcement features. Agree a next owner and review date rather than averaging that uncertainty away.

Use the result in a bounded scope

Choose a staff question and follow it to a current answer or a completed request. Review useful existing tools before selecting another platform. The scope should explain which content moves, who maintains it and how staff get help when a result is missing.

This worksheet runs only in the page. It does not upload, store or submit answers; reloading clears them. Keep private staff information, policy text and credentials out of the notes. Without JavaScript, use the eight areas and scale in your own document.

Explore employee portal development, review account-lifecycle decisions or describe the unresolved portal task.