# Planning & Weekly Updates

## Review The Plan And Schedule

1. Open the company and select **Plan**.
2. Review the generated tasks, recurring work, and quiet hours.

![Company Plan showing the active schedule, recurring work, quiet hours, and operating controls](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/landing/v6/2026-08-11-r1/ui/active-plan-1280.webp)

3. Select **Tasks**, then open a task to inspect its definition and run history.

![Company Tasks showing recurring work with schedules, connected apps, run status, and spend](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/landing/v5/2026-08-11-r1/tasks-recurring-1280.webp)

![Opened company task showing its integrations, skills, schedule, status, and completed run](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/docs/product/2026-08-13-r6/company-task-run-detail-1280.webp)

4. Return after the weekly refresh to review added, continued, and dropped work.

Your company starts with a full week of work planned for it, and that plan **refreshes itself every week** so the company keeps making forward progress instead of going quiet after the first few days. This guide explains how the first plan is created, how the weekly refresh works, and where you can see exactly when the next refresh will happen.

> **Note:** The automatic weekly refresh is part of a feature rollout, so it may not be switched on for every company yet. Everything below describes how planning behaves when the weekly refresh is active.

---

## The First Week's Plan

When you finish onboarding a new company, Neotask immediately writes its **first week of work** as a real schedule of tasks, not a vague to-do list. The plan is built specifically for a brand-new, pre-launch company, so every task can be done right away with the built-in tools, without you having to connect anything first.

A few things are true about that first plan by design:

- It is **one week of forward work**, not a permanent loop. Most tasks happen once; at most a couple repeat (like a single weekly blog post).
- The very first task is to **write and publish your company's first blog post**, and it is set to run right away rather than waiting for a scheduled day.
- The rest of the tasks are spread across **Monday through Friday**, each with a specific day and time, so the week is paced rather than stacked on one day.
- The week is **sequenced to compound**, research first, then drafting, then producing, then preparing to launch, so each day builds on the one before it.

---

## "Your Website Already Exists", The Planner Doesn't Rebuild What's Done

A common failure for an autonomous company is to keep re-doing the same setup work. Neotask's planner avoids this by being **grounded in what your company has already shipped** before it writes a single task.

Every generated company already has a live website that includes:

| Already exists | What it means for planning |
|---|---|
| A **landing page** (hero + content sections) | The planner extends it, never rebuilds it |
| A **working email-capture waitlist** | A real, functioning signup form that is already collecting people, the planner grows it, it does not re-create it |
| A **blog** | The publishing channel, the planner adds posts, it does not "build a blog" |

On top of that, a fixed set of starter deliverables runs automatically (your first blog post, an initial website SEO/copy pass, starter brand assets, a first content batch, a prospect list, and a first briefing). The planner is explicitly told **not to repeat any of these**.

So instead of re-creating finished work, the planner authors genuinely **new, additive** work: a new page or section the site doesn't have yet (an FAQ, a docs page, a case-studies page), defining the offer and pricing, drafting foundational documents, deepening content, growing the existing waitlist, and preparing the launch.

---

## How The Weekly Refresh Works

The most important part of the system is that **the plan does not run out**. Once a week, Neotask reviews the company and writes a **fresh, revised week of real scheduled tasks** to replace the old one.

This weekly review is not a note-taking exercise. It produces actual tasks that update your **task list**, your **schedule view**, and your **plan**, the same way the original plan did, with each task armed to run on its day and time.

After the review, open **Tasks** to see which work was added, continued, changed, or dropped. That record explains how the current week differs from the prior plan.

![Week replanned with added, continued, and dropped work](https://neotask-marketing-assets-417007889150.s3.us-east-1.amazonaws.com/landing/v5/2026-08-11-r1/hero-week-replanned-1280.webp)

### What The Weekly Review Looks At

Before writing next week, the review grounds itself in your company's **real current state**, it never invents a week from scratch:

| It reads | Why |
|---|---|
| **What actually ran** this past week | To see which tasks succeeded, which failed, and what produced results |
| The company's **memory** | To know what has been learned and recorded |
| The **live site** as it exists now | To know what has already shipped and what is already collecting signups |

From that, it **doubles down on what worked, fixes or replaces what failed, and only adds net-new forward work**. It will not re-create anything already built, not the live site, not the working waitlist, not the blog, and not the starter tasks that already ran.

### What You Get Out Of It

The result is a revised week that:

- replaces last week's plan as the company's **current plan**,
- lands tasks on the **weekly calendar with specific days and times**, and
- is **armed automatically** so the tasks run on schedule without you having to re-approve them.

If the review can't produce a coherent week for some reason, it does **nothing** rather than leaving you with a broken or empty plan, and it records that it couldn't, so the situation is visible instead of silent.

---

## When The Refresh Happens

The weekly refresh runs **once a week, on Sunday evening, in your company's own timezone**, roughly between 5:00 PM and 7:00 PM local time. (The exact minute is spread slightly across that window so that many companies don't all refresh at the same instant; it stays consistent for your company.)

Because it runs Sunday evening, your company starts each new week with a **freshly planned, up-to-date arc of work** already on the calendar.

The refresh runs in the background and does not interrupt anything the company is currently doing.

---

## How A Plan Becomes Scheduled Work

It helps to know the difference between the two stages of planning, because the weekly refresh repeats the same flow the first plan went through:

1. **The plan is written.** A week of tasks is authored, each with a category, a goal, and, for everything except the immediate first blog, a specific weekday and clock time.
2. **The tasks are armed.** Each scheduled task is placed on the company's calendar so it actually fires on its day and time, automatically, without needing a fresh approval each week.

The first plan does this at onboarding. The **weekly refresh does exactly the same thing every Sunday evening**, it writes the revised week and arms it, which is why the new plan simply takes over and the company keeps running without a gap.

---

## Seeing The Next Planning Time

You don't have to guess when the next refresh will happen. Open the company and go to the **Plan** tab. Below the weekly schedule, you'll see a small disclosure that reads something like:

> **Every Sunday at 5:30 PM**, Weekly review & plan next week
> Reviews this week's memory, completed work, and progress, then plans next week's build arc. Runs automatically.

That time is read from the **real, live schedule**, so it reflects exactly when your company's next plan will be written, in your company's timezone. If no weekly refresh is currently scheduled, the disclosure simply doesn't appear.

---

## Where Planning Shows Up

| Surface | What you see |
|---|---|
| **Plan** tab | The current plan, the weekly schedule grid (days × times), the "runs first" blog card, and the next-planning-time disclosure |
| **Tasks** tab | The same tasks, one at a time, with runtime status and per-task settings |
| **Schedule view** | Each task placed on its specific day and time across the week |

When the weekly refresh runs, all of these update together, the new tasks appear on the schedule, in the task list, and in the plan view at once.

---

## What This Means For You

- You don't have to re-plan your company every week, it re-plans itself.
- The plan stays **current**, reacting to what actually happened rather than running a stale script.
- The company keeps **moving forward**: building on wins, repairing misses, and adding new work each week.
- You can always check the **Plan** tab to see what's coming and exactly when the next plan will be written.

You remain in control. The plan is yours to refine at any time, connect missing tools, edit tasks, pause or resume work, and the weekly refresh builds forward from wherever the company actually is.

---

## Related

- [Onboarding & Plan Setup](auto-companies-onboarding)
- [Company Modes](company-modes)
- [Company Dashboard](auto-companies-dashboard)