Copilot Notebooks Tips and Tricks for Ongoing Work

The most useful Copilot Notebooks tips and tricks are to collect references for one clear task, ask one focused question at a time, and check important answers against the original sources. Start with a small, relevant collection instead of adding every document you can find.

A notebook helps you work through material; a project also needs a reliable record of what people accepted. Tools like fenbs keep confirmed decisions, source links, and next steps outside a single notebook, where your other supported assistants can read them.

How do you get a useful result quickly?

Try this sequence with a real question you need to resolve today. For example, a design studio could use a notebook to prepare a client review from an approved brief, a schedule, and recent feedback.

1. Define the job in one sentence: prepare the review agenda, compare feedback, or identify unanswered questions. Name the notebook for that job so its scope stays clear.
2. Open the notebook and add the references needed for that answer. Start with the current brief and the documents that support or challenge it.
3. Set short instructions for the audience and response format. Ask Copilot to separate evidence, suggestions, and information it could not find.
4. Ask a narrow question, such as which client requests conflict with the approved scope. Request the relevant source for each finding.
5. Open the supporting material, correct any mistaken interpretation, and save only the checked findings you need for the next action.

Microsoft describes notebook answers as grounded in your references, meaning they use the material you added to inform the response. Its guide to asking notebook questions↗ (opens in a new tab) explains the basic question-and-answer flow and links to current content support and limits.

Which references should you include?

Include a document because it helps answer the question, rather than because it belongs to the same client. A current scope, a revision request, and a delivery schedule may be enough. An unrelated presentation can introduce assumptions that sound plausible but do not apply.

Use Add references to search, upload, or add a supported link. Microsoft explains the controls for both the Copilot app and OneNote in its reference guide↗ (opens in a new tab). Public web links need to be accessible without signing in; a link to a website does not include all its linked pages.

• Prefer the approved document over an undated copy. Check the source itself for its date and status.
• Label drafts and superseded versions clearly when you need them for comparison.
• Open each essential reference yourself before relying on it. A title in a list is not proof that the needed content is available.
• Review the collection when the project changes. Keep historical evidence only when the question needs that history.

Keep a short explanation of which sources remain authoritative in the project record. In fenbs, Links and listings can retain those references and their status after the notebook has served its immediate purpose.

What should custom instructions say?

Use instructions for habits you want across the notebook, then put the individual assignment in your question. Specify the audience, the preferred structure, and how to handle missing evidence. Avoid competing directions such as asking for both a complete analysis and an extremely short answer.

In the Copilot app, open More options, then Instructions. In OneNote, open the arrow beside the notebook name, then Copilot instructions. Enter your guidelines and save them; Microsoft documents these paths in its custom instructions guide↗ (opens in a new tab).

Write for a design project manager.
Start with the answer, then supporting evidence.
Separate documented facts from proposed actions.
Identify the reference behind each important finding.
If sources disagree or information is missing, say so.
Do not describe a proposed change as an approved decision.

Test the instructions with a question whose answer you already know. If the response misses a qualification, tighten the wording and try again. Instructions guide the response; they do not replace checking it.

How do you ask questions that produce usable answers?

Give Copilot a defined task, a boundary, and an output you can review. Instead of asking for everything about the project, ask which requests need a decision before the review. Then ask a separate follow-up about one disputed request.

• Find conflicts: compare the approved brief with the latest feedback. List disagreements without choosing a winner.
• Prepare a meeting: suggest an agenda based on unresolved questions, with the source behind each question.
• Check a draft: identify statements in this proposal that the references do not support.
• Identify gaps: list the information needed to confirm the schedule that you cannot find in the references.

Ask for an evidence pass before a recommendation pass. You can then challenge the interpretation without rewriting an entire proposal. If you are choosing where to organize this work, Copilot Notebooks versus ChatGPT Projects covers that separate comparison.

How do you check what Copilot gives you?

Treat an answer as a draft until the important claims have been checked. Microsoft warns in its Notebooks FAQ↗ (opens in a new tab) that responses can be inaccurate and that generated artifacts may use only a subset of the attached references.

1. Pick the claims that affect the next action: dates, requirements, quantities, approvals, and exceptions.
2. Open the cited source, or ask for the supporting reference if none is given. Find the passage that actually supports the claim.
3. Read the surrounding context. Check whether the passage describes an option, an old agreement, or a current requirement.
4. Compare conflicting sources and ask the responsible person to resolve the disagreement. Record the answer separately from the generated suggestion.

A second confident answer is not independent evidence. For broader choices between assistants, see Copilot versus ChatGPT; keep this review focused on the notebook and its sources.

What should survive beyond the notebook?

Save the approved conclusion, its supporting link, the person who approved it, and the next step. For the studio, that could be a decision to keep the original scope while asking for a separate estimate on an extra request. Preserve the unresolved question too.

Your AI at work workflow becomes easier to resume when checked findings have a clear home. A notebook session should leave a usable record rather than another summary someone must interpret.

For other workspace questions, see Notebooks versus OneNote, Notebooks versus Google’s notebook app, and Pages versus Notebooks. The guides to Notebooks versus agents and notebook API options cover those separate workflows.

How to do this with fenbs

1. Create a free account, then add the project you are researching. One person can start free, with no credit card.
2. Add the important source URLs to Links and listings, with enough description to distinguish the approved brief from its drafts.
3. Record what a person approved in Decisions and rules. Keep suggestions and unresolved choices separate from confirmed decisions.
4. Save the checked findings and next step in AI context notes and Where we left off. Connect a supported assistant using its setup guide on Integrations and ask it to read that context before continuing.

fenbs does not import Copilot Notebooks or replace their document analysis. If you only need answers from a collection that stays inside Microsoft, a notebook may be enough; fenbs fits when the resulting work needs to continue across supported assistants.