Connect one source

The situation

For a month you have pasted the same export into the same workspace every Monday. Four minutes to run the report, download it, open it, copy it. Twice you pasted the previous week's file by mistake, and both times the summary that came back was fluent, specific and wrong about the branch that mattered.

So you connect the folder instead. The export lands there automatically; now the tool can read it directly and the four minutes are gone.

The first answer you get cites a file called weekly_numbers_2024_OLD_donotuse.

The folder had eleven months of superseded exports in it. You knew that. You had simply never had to think about it, because your clipboard had been doing the filtering.

The principle

Pasting gives a tool a snapshot you curated, and connecting a source gives it whatever that source contains today — including everything you had forgotten was in there.

Three things get better immediately. Freshness: there is no export step, so there is no stale file to paste by accident. Scale: you can ask a question across two hundred documents, which you were never going to paste. Continuity: the same source is there next week without you doing anything, which is what makes a workspace worth configuring at all.

One thing gets harder, and it is not small. Your clipboard was a filter you were applying without noticing. A connection removes it. What the tool reads is now defined by the boundary of the container — folder, drive, mailbox, table — and containers accumulate drafts, superseded versions, other people's work, and files whose names no longer describe their contents. Retrieval finds what matches your wording, not what is current or correct, and a confident answer built on a 2024 file looks exactly like a confident answer built on this morning's.

This raises two questions properly: how you check an answer that came from a source you did not read yourself, and what a tool should be allowed to see in the first place. Unit 5 is where both get answered. Here you do the smaller thing: connect one source, and write down its boundary.

Worked example

Shown here in Microsoft 365 Copilot.

The wrong answer, in full, because it is the whole lesson:

Q: Which branches are furthest behind on picked against booked?

A: Northgate and Fairview are furthest behind, at 71% and 74% of booked
volume picked. Kirkstall is closest to plan at 96%.

  [weekly_numbers_2024_OLD_donotuse.xlsx]

Nothing on that page looks wrong. Three branches, three percentages, no hedging, and every figure in it is real — out of a file that stopped being true eleven months ago. The line at the bottom is the only thing separating it from a good answer, and it is the line everybody skims.

The five lines that make a source safe to use. Write them once, keep them beside the workspace:

SOURCE      The Weekly-Numbers folder on the Ops site
IN SCOPE    The current-week export and the 12 most recent prior weeks
OUT         Everything else my account can open, including the 2024
            archive subfolder
TRAP        Old exports use identical column names — always name the week
            you mean in the question, never say "the latest"
REFRESH     The export lands Monday 07:00. Anything asked before that is
            answering from last week.

Then the question changes shape to match:

Using only the export dated this Monday in the Weekly-Numbers folder, list
the three branches with the largest change in "short" against their own
four-week average. Name the file you used. If this Monday's export is not
present, say so and stop.

And the answer comes back naming weekly_numbers_2026-08-03.xlsx, which you can open in one click. "Name the file you used" is the cheapest line in this lesson. It costs nothing, and it is what turned the first wrong answer from a mystery into a two-second diagnosis.

In your tool

Connecting a source is one of the few places where the tools genuinely differ, because the boundary is set partly by your organisation and not by you.

Product surfaces checked 2026-08-04.

Try it

Pick exactly one source. One folder, one sheet, one mailbox label — the one you have pasted from more than twice. Connect it. Then write the five boundary lines above for it.

You are done when the TRAP line names something real: one file, naming convention or duplicate in that source that will mislead the tool. If you cannot name one, you do not know the source well enough to connect it yet. Do not connect a second source in this session.

Common failures

• Connecting everything on day one. Whole drive, all mail, every channel. Answers start arriving from superseded drafts and half-finished documents, and because you cannot tell which answer came from where, you stop trusting the good ones too.
• Reading "connected" as "current". A connection reads the source faithfully. If the source is a folder where last week's file never got replaced, the answer is stale — and now delivered with the extra authority of having been retrieved rather than pasted.
• Treating the connection as a decision about permission. Being able to reach a source is not the same as being allowed to send it somewhere, and neither one tells you whether the answer is right. Those are separate judgements with their own rules, and Unit 5 is where you build them.