Company context audit checklist

1. Choose three recurring tasks

Choose tasks where missing company information causes observable rework. Use examples such as a proposal, a handover or an explanation of a company process. Avoid starting with a broad ambition such as “connect everything”. For each task, describe the details that would make an answer useful.

2. Map the sources behind those answers

Write down exact source locations, not only tool names. Identify the current source and any documents that compete with it. A current handbook, an archived presentation and a draft are three different source roles, even if all contain the same topic.

3. Separate reference knowledge from guidance

Mark useful facts and documents as reference knowledge. Identify only the small set of recurring requirements that need an accountable approval decision. If following a stale version could materially change company work, name the owner who decides the requirement and the people it applies to.

• Reference information the task needs: ____________________________________
• Company requirement that must be explicit: _________________________________
• Person accountable for that requirement: __________________________________
• Audience and exceptions: _________________________________________________
• Event that should trigger a review: _______________________________________

4. Check access and delivery

For each source, confirm that its intended audience is appropriate. Record unanswered access questions instead of assuming that an administrator’s permission applies to everyone. Identify the AI tools in which people need the context, including the actual workspace plan and administrator responsible for setup.

• The source area is selected explicitly, with sensitive or unrelated material excluded.
• The intended audience is named and the access evidence is understood.
• Someone knows how to remove access and verify that future delivery stops.
• The AI-tool setup can be tested by an ordinary employee account.
• A correction has an obvious destination and accountable owner.

5. Run the same task before and after

Use this evaluation prompt: “Complete [task] for [audience]. Use current company sources where available, identify any missing information and link the sources supporting the answer.” Do not paste the expected answer into the request. Record the original output and repeat after the selected context is available.

Have the relevant owner review both answers for current facts, applicable guidance, attribution, usefulness and access. A better-written answer is not enough if it still uses the wrong company rule. Add one changed-source test and one access-denied test before expanding the rollout.

6. Leave with three actions

Choose one source correction, one ownership decision and one small delivery test. Assign a person and a date to each. This turns the audit into a bounded improvement rather than a permanent documentation project.

Continue with a practical next step

• Complete an ownership record
• Evaluate a context platform