A CIP steering group’s project Q&A with Copilot help keeps getting lost in disconnected chats. What should they prefer?
Select an answer to reveal the explanation.
Short Explanation
CIP questions and answers dying in chat threads? Prefer a Copilot Page as the living workspace. You need a durable home for answers, not disconnected chats that disappear when new steering members join.
Full Explanation
CIP steering groups accumulate project questions and answers that must remain available as membership rotates. The preferred approach is using a Copilot Page as a living workspace instead of disconnected chats for project questions and answers, because Pages keep Copilot-assisted answers and human clarifications in a durable, revisitable place for capital project governance. Municipal CIP oversight depends on continuity: new steering members should not re-ask settled scope, funding, or schedule questions lost in chat history.
Relying only on ephemeral chats that cannot be revisited by new steering members fails onboarding and institutional memory. Deleting questions and answers as soon as they are written destroys the very knowledge the group needs for later votes and public briefings. Storing contractor tax IDs inside the informal questions and answers notes fails data minimization and creates an unnecessary sensitive-data store in a collaboration scratchpad.
Exam caveat: a living Page is a working knowledge base, not automatically the official CIP budget document or contract file; formal figures still live in finance systems of record. Operational check: migrate recurring questions and answers to the Page, grant access to current steering members, keep tax IDs and similar identifiers out of notes, and periodically verify that Page answers still match current project baselines.