Use Claude Projects so you stop re-explaining the same context every Monday

Example result.

Before I draft, two gaps:
1. Training before or after the import fix: no owner or decision date.
2. The import fix needs supplier approval. Has it been given?

1. Split the context into standing and current material

Projects reward repetition and punish enthusiasm. Choose one task you really repeat, such as a weekly operations update, and write down what never changes:

• the audience and purpose;
• the headings and tone;
• the definitions behind the figures;
• your rules about missing facts and undecided items.

This week’s results, dates and decisions stay out of the project. They go in each week’s chat.

Pick one job per project. A project called “Work” becomes a drawer, and a drawer that holds everything helps with nothing.

Why this works: the audience and format stay the same every Monday; the facts don’t. Giving each a separate place stops an old example from turning into this week’s status.

What you should see: a short list of standing rules, with no figures from any particular week in it.

2. Create a private project and save the brief

Open Projects in the sidebar (or claude.ai/projects) and select + New Project. Give it a name you’ll recognise. On Team or Enterprise, choose Keep it private. Claude can’t see the name and description, so put the brief in Set project instructions and select Save instructions.

Help draft the weekly operations update for [audience].
Use these headings: What changed, Decisions needed, Watch list.
Write plain UK English. Keep the whole update under [length].

Use this conversation's notes for current results and status. Use
project files for definitions and format only, unless I name one as
the current source for a fact. Do not reuse figures or decisions from
an example update.

Do not add dates, owners, figures or commitments. Mark missing items
"to confirm". Keep proposals as proposals. When I give you notes,
tell me first what is missing, before you draft.

[audience] is who reads it, such as “the leadership group”; [length] is your usual limit, such as “200 words”.

Why this works: the source rule tells Claude which material expires at the end of the week. The last line turns the first reply into a gap check, which is cheaper than finding the gaps in a finished draft.

What you should see: the instructions saved on the project page.

3. Add only the references the task needs

In the project’s knowledge area, add a short definitions note and one example update you were happy with. Give each a clear title saying what it is for, such as “Format example only – old figures”.

Leave out last week’s update unless you want last week echoed back. Don’t upload a whole folder in the hope that more context must be better: a small set is easier to check and keep current.

Why this works: the example shows the shape; the definitions explain the numbers. Neither should supply a result.

What you should see: two clearly labelled files, and a note to yourself of which one is authoritative for each definition.

4. Run one week’s update

Start a new chat inside the project and paste this week’s notes:

Prepare the operations update for [period]. Current notes:
[this week's notes]

Use the project's definitions and format, but do not import old
figures or status. For each important figure, name its source and
period.

[period] is the reporting week; [this week’s notes] are the facts as you have them.

Why this works: naming the source and period for each figure makes an imported number easy to spot.

What you should see: a short list of gaps first, then a draft under your three headings.

Check the result

• The period is right, and every figure comes from this week’s notes.
• Definitions match the definitions file.
• Proposals are still proposals, and missing owners or dates say “to confirm”.
• No trend is claimed unless you supplied a real previous-week source.

The usual failure: a number or a comparison from the example update leaks into this week. “Down from eight last week” looks helpful, but eight came from a file labelled as a format example, which may not even use the same definition. Search the draft for the example’s figures and for “up”, “down” and “last week”.

The figure [value] came from the example update, not the current
notes. Remove it. Use [current value and source], or write "to
confirm" if this week's value is missing. Check the other figures for
the same problem and list any corrections.

[value] is the imported figure; [current value and source] is the right one from this week’s notes.

Fictional example. An operations manager at Fenmoor Distribution keeps this in her project and chat:

Definitions file:
"Late orders" means orders dispatched after the promised date.
The weekly update must state the reporting period.

Format example (old figures):
Week ending 25 September: 8 late orders.

This week's notes:
Week ending 2 October: 5 late orders.
Import fix proposed for 9 October, subject to supplier approval.
Training before or after the fix? No owner or date set.

Claude’s first reply was the gap check in the example result above: no owner or date for the training decision, and no confirmation of supplier approval. Two things she knew and hadn’t written down.

The draft then said: “Late orders fell from eight to five in the week ending 2 October.” After the repair prompt, it read:

• What changed: five orders were dispatched after the promised date in the week ending 2 October.
• Decisions needed: whether training happens before or after the import fix. Owner and decision date: to confirm.
• Watch list: the import fix is proposed for 9 October and still needs supplier approval.

What mattered:

1. The gap check came first. Fixing two missing facts before drafting took a minute; finding them in a polished update takes longer.
2. Eight was format, not evidence. The example file supplied the shape and nothing else, so the trend was removed.
3. “Proposed” survived. The rule against turning proposals into plans kept the 9 October fix on the watch list rather than under “What changed”.

The next week, the notes report seven late orders and the fix still awaiting approval. The weekly prompt is the same; only the notes change. If you want a trend, paste last week’s final update as a named source and say the definition hasn’t changed.

Task kit for this job: Download (ZIP) · Reusable instructions

Go deeper

Sources

• What are projects?
• How can I create and manage projects?
• Use Claude’s chat search and memory to build on previous context