Markdown edition

# Create and check a daily news brief in Claude Cowork Projects

> Save a personalized Cowork Project profile, check a current source-linked brief, then schedule one daily task with complete instructions and verify its first result.

By BIGCHANGE.AI Editorial

Published: 2026-10-25T01:45:41.574Z
Updated: 2026-10-25T01:45:41.574Z
Canonical: https://bigchange.ai/blog/claude-cowork-projects-checked-daily-news-brief-guide

![Conceptual charcoal illustration of an unmarked periodical opened on a supported reading ledge beside a rack of other publications, with an analog clock on the wall.](https://bigchange.ai/api/media/file/cowork-daily-news-source-reading-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE. No actual Claude account, news source, saved schedule, completed brief or verified result is depicted.

A daily news brief is useful only if its topics, source limits and dates survive the move from a Project conversation to a scheduled task. Claude Cowork can save Project instructions and run recurring tasks, but each scheduled run has its own session. This guide builds a brief from sources you can open, copies the complete profile into one daily task, and checks its first completed result. It follows Claude's help pages as checked on 25 October 2026; BIG CHANGE did not run a Claude account or generate a news brief.

## The big change

- **What changed:** Cowork Projects hold instructions and references, while Scheduled can run a saved task on a daily cadence. [Claude documents both features](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork).
- **Why it matters:** A reusable profile can guide the first brief, and a complete copy of it can guide later runs. You still need to inspect real citations and the saved task.
- **What to watch:** A scheduled entry does not prove that it used the intended context, found current reporting or delivered a checked result.

## Before you start

Use a paid Claude plan with Cowork Projects and Scheduled available. The [Projects instructions](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) call for the latest Claude Desktop for the setup path below. Controls may look different in the unified Claude experience, and Team or Enterprise access may depend on an administrator. Check that web search or a permitted connector can reach current sources. On the older interface, enable **+ > Web search**; in the unified interface there is no search toggle. Ask for a recent source and look for an actual search indicator, direct citation and accessible page. Writing “search the web” in a prompt does not establish that a search occurred. [Claude's search guide](https://support.claude.com/en/articles/10684626-enable-and-use-web-search) describes the controls and limits.

Decide your real topics and exclusions, approved public source URLs or named connectors you are allowed to use, and the exact route to those sources. Choose a maximum item count **N**, freshness window, daily local time and named time zone, and output sections and order. Make the brief a draft for human review. If a source requires private account access, check the connector's permission and scope before using it. Public links are the simpler route for a remotely run news task. Project account details can be saved to your Claude account, but local files remain on your computer; a task needing local files or apps runs locally and needs Claude Desktop open and connected. Account memory is a separate choice from file and connector access.

## Set up and test the Project

1. In Claude Desktop, open **Projects > + > Start from scratch**. Name the Project and finish the creation flow shown on your screen. Return to Projects and reopen the **saved** Project before adding its profile. If the path is absent, check your Desktop version, plan and organization settings.
2. In the Project instructions, save the complete profile: all chosen topics and exclusions; every allowed source URL or named connector; the access route for each; **N**; freshness window; chosen daily local time and named time zone; and exact output format. Add these rules: include a direct source link, original publication date, supported factual sentence and uncertainty note for every item; keep an event date distinct from its publication date and from a page's retrieval or update date; deduplicate the same event; write “No verified item” for a topic with no supported result; state source access failures; and leave the brief as a human-review draft. Reopen the saved instructions and check each field against your choices.
3. Add only references you approved. An allowed URL in Project context is a reference, not proof that today's page was read. Inspect **Memory > Use account memory** if the Project's context should stay separate from other chats; turn it off for that purpose. Then check file and connector permissions separately. If you choose local references, confirm the folder is connected and Desktop is open and connected for any local task; do not assume a remote scheduled run can read a local folder.
4. Ask for one brief covering your chosen window. Confirm the run actually reached current sources through the selected route. Open each citation yourself and compare the original publisher page, original publication date, reported event date, supported sentence and topic. A page update or retrieval date cannot stand in for the original publication date. Mark broken links, inaccessible pages and ambiguous dates unverified. Group duplicate reports of one event. Save the checked draft only when its items pass; if search or source access failed, fix that access before scheduling.

For general advice on keeping two ongoing work contexts separate, see our [Cowork Projects setup guide](https://bigchange.ai/blog/organize-two-tasks-claude-cowork-projects-guide). The news brief here also requires current-source and scheduled-run checks.

## Prepare the daily task before confirming it

5. Copy every field from the **saved** Project profile into a standalone scheduled prompt. Replace every bracketed instruction below with your real choice. Use the same exact source allowlist and access route that passed the first check. If you use a connector, name the authorized connector and the accessible source scope. If one is unavailable, the task must report the failure and leave affected items unverified.

```prompt
Create a current news brief for human review for [Project name].

Topics: [complete real topic list].
Exclude: [complete real exclusion list].
Permitted sources: [complete approved public source URL/domain list and/or exact named permitted connectors with their permitted scope].
Access route: [web search for approved public sources and/or the exact authorized connector route for each source]. Use only sources you can actually access during this run. If access fails, say which route failed and leave its items unverified.
Maximum: [N] distinct verified items total.
Freshness: original source publication within [chosen window] ending at this run, evaluated in [named time zone]. The scheduled daily local time is [chosen local time] in [named time zone].
Format: [chosen section names, order and output form]. Include a section for every topic, even if empty.

For each item, give its topic, a direct link to the original source page, the original publication date as shown by that source, the reported event date when available, one factual sentence supported by the linked page, and any uncertainty. Keep the original publication date distinct from event date, retrieval date and page update date. Do not claim a date you cannot establish. Deduplicate reports of the same event and make the retained source clear. For an empty topic, write “No verified item.” For inaccessible sources, missing dates, broken links or uncertain facts, state the limitation instead of filling the gap from memory. Do not invent news, links, quotes or updates.

This is a draft for human review. Do not send, publish, purchase or take action on any item. Do not call the draft verified; the reader will open and check the original pages.
```

6. Compare that prompt with the saved Project instructions **field by field**: topics, exclusions, permitted sources, access routes, **N**, window, local time and time zone, format, source/date rules, empty-topic wording, failure handling and review boundary. This copy is necessary because [Claude says each scheduled task runs as its own session](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork); its scheduling manual does not establish automatic inheritance of all Project context. A folder choice or account memory is no substitute for the saved instructions.
7. If your message box still shows **Chat** and **Cowork**, open **Scheduled > New task > Create with Claude** in Cowork. If those choices are absent, use the [new Claude experience's documented conversation route](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) from an existing conversation. In either route, give Claude the complete prompt above and request one run **daily** at the saved local time in the named time zone. Answer any questions. Before clicking **Schedule**, inspect the proposed task name, full instructions and cadence, and verify the intended local time, named time zone and next run in the actual UI. Review approval mode if that control is offered, while keeping the prompt's human-review boundary and source permissions in force. Compare the proposed instructions to your saved profile again. If the next run cannot be verified unambiguously in your local time zone, stop and resolve that before enabling it. Do not infer a timezone control or Project selector from the manual form, which does not document either. Click **Schedule** once only after every field matches. Reopen the task under Scheduled and read back its saved instructions, cadence and next run, plus approval settings if shown. If confirmation is uncertain, inspect the existing task list before trying anything else; do not create a duplicate.

## Check the first completed run

8. At the first actual scheduled completion, open the run from **Scheduled**. Compare its topics, exclusions, source limits, count, window and format with both the Project profile and the task's saved prompt. Open **every** original source link. Check that each factual sentence is supported, the original publication date falls in your window, and event dates are distinguished from publication and page-update dates. Check duplicate events and empty-topic messages. An item without accessible evidence remains unverified.
9. If no run appears, inspect the same task's next run, approval mode and source permissions. If its brief drops rules, repeats stale items or lacks direct evidence, pause or edit **that same task**, recheck its saved instructions and inspect its next completed run. Keep human review before forwarding or acting on any brief. A saved schedule is not evidence of a completed brief or delivery.

The result to keep is a saved Project profile, one human-checked first brief, one matching daily task, and a human-checked first completed scheduled output. Search, fetch and recurring runs consume your account allowance; connected services may carry their own charges. Check the limits and charges on your plan and connectors. This procedure needs no separate API account, and BIG CHANGE measured no cost, saved time or success rate.

## Sources & further reading

- [Organize your tasks with projects in Claude Cowork](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) — creation path, context, memory, account/local file boundary and availability.
- [Schedule recurring tasks in Claude Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) — creation conversation, separate sessions, remote/local runs, task management and readback.
- [Enable and use web search](https://support.claude.com/en/articles/10684626-enable-and-use-web-search) — interface variants, live citations, usage and access limits.

## Sources

- [Organize your tasks with projects in Claude Cowork](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) — Projects path, account/local context, memory and availability; reopened October 25, 2026.
- [Schedule recurring tasks in Claude Cowork](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) — Create with Claude, separate scheduled sessions, remote/local behavior, review and management; reopened October 25, 2026.
- [Enable and use web search](https://support.claude.com/en/articles/10684626-enable-and-use-web-search) — Legacy/unified controls, live citations and search limits; reopened October 25, 2026.