Auto vs manual scheduling

Every task in Microsoft Project is either auto scheduled or manually scheduled, and the difference decides whether the program does any scheduling at all. An auto-scheduled task moves when its predecessors move. A manually scheduled task stays where someone typed it, whatever the logic says. Since Project 2010 new files start in manual mode, which is friendly for sketching and dangerous for a master schedule. An owner who reports dates from a file full of manual tasks is reporting what someone typed, not what the logic supports. This lesson explains both modes, how to switch, and where manual mode still earns a place.

Learning outcomes

• Explain what Project calculates for an auto-scheduled task and what it leaves alone for a manual one.
• Change the mode of existing tasks and the default for new tasks in Project desktop.
• Use Respect Links and the Task Inspector to find and fix manual tasks that conflict with logic.
• Set an owner rule for when manual tasks are allowed in a master schedule.

The lesson

Two modes, one field

The mode is stored in the Task Mode field, which appears by default beside Task Name in the Gantt Chart [1]. It has two values. An Auto Scheduled task is scheduled by Project from dependencies, constraints, calendars and other factors. A Manually Scheduled task takes the start date, finish date and duration you give it, and Microsoft is clear that Project never changes those dates, although it may warn you about problems [1]. Project also treats a manual task as a placeholder when at least two of start, finish and duration are missing [1].

Figure 1 sets the two side by side. The short version: auto mode is a scheduling engine; manual mode is a drawing tool with a calendar behind it.

Switching mode

For tasks that already exist, select them and choose Manually Schedule or Auto Schedule on the Task tab, in the Tasks group, or pick the value from the Task Mode cell itself [1]. You can select a whole WBS branch, or every row, and switch them in one step.

For tasks you have not created yet, change the project's default. Microsoft documents this through the Task Mode command on the Task tab, choosing Auto Schedule for new tasks [1]. The same setting appears as New Tasks on the status bar at the bottom of the window, and under File > Options > Schedule in the "Scheduling options for this project" section [4]. It applies only to tasks added afterwards [4], so set it in the first minutes of a new file, right after the start date and calendar from Lesson 3 and Lesson 4. Microsoft notes that files created in earlier versions of Project open with tasks auto scheduled [1].

How to spot a manual task

The Task Mode column shows a pin icon for a manual task [4], and the Gantt bar uses a different style from auto-scheduled bars. Manual tasks can also hold text instead of a duration or date, such as "TBD" or "after permit", which auto tasks cannot. In a long file the fastest check is the AutoFilter on the Task Mode column header: filter to Manually Scheduled and count the rows.

Repairing a manual task

Two tools help. Respect Links, on the Task tab, moves the selected tasks so that their dates are determined by their dependencies; Microsoft's documentation says it works on both manual and auto tasks [3]. Use it to snap a manual task back into line without changing its mode. The Task Inspector (Task tab, Tasks group, Inspect Task) opens a pane listing what drives the selected task: predecessors with their lags, constraints, calendars, actual start and leveling delay, and for a manual task it offers the option to auto schedule it [2]. Press F9 if the pane looks out of date [2].

Respect Links is a one-time move. The task stays manual, so the next time logic changes it will drift again. For anything that carries real logic, switching to Auto Schedule is the permanent fix.

Where manual mode helps

Microsoft suggests a mixed approach: manual tasks while a plan is still a proposal, then switching well-defined phases to auto as they firm up [1]. That fits an owner's master at the very start of a project, before the contractor's baseline exists. A placeholder like "Office mezzanine and interiors: dates from contractor baseline" is more honest as a manual task with text than as an auto task with an invented duration. The discipline is to give each placeholder an owner and a date by which it becomes auto scheduled.

Summary tasks can be manual too. A manually scheduled summary keeps the dates you typed instead of rolling up its subtasks, and Project marks the difference when the subtasks run past it. That can be a useful top-down target in early planning, but in a working master it means the summary bar is no longer a summary.

Northgate worked example

The owner's master for Northgate Distribution Centre (fictional), NDC_OwnerMaster_2027-01-11.mpp, was started in January 2027 for Northgate Logistics Inc. (fictional). Before Halvorsen Builders Ltd. (fictional) submitted its baseline, the owner's scheduler built the WBS from Lesson 5 and entered the contract milestones from the Northgate fact sheet. The file was created in a current version of Project, so the default was manual, and nobody changed it. About half the tasks were entered before the scheduler noticed.

A what-if: the permit slips two weeks

To see what that costs, take a hypothetical (not a Northgate fact-sheet event): the City of Vaughan's permit, M2, moves from Fri Feb 26 to Fri Mar 12, 2027. The first site task, Site preparation and excavation, is 10 working days and follows M2 finish-to-start. Figure 2 shows both modes. As an auto task it moves to Mon Mar 15 and, skipping Good Friday on Mar 26, finishes Mon Mar 29. As a manual task it stays at Mon Mar 1 to Fri Mar 12, two weeks before the permit it depends on. Project draws a warning, but every report, filter and Timeline still shows the old dates.

View the data

Item	Before	After the what-if slip
M2 Building permit issued	Fri Feb 26, 2027	Fri Mar 12, 2027
Site preparation (Auto Scheduled, 10d, FS from M2)	Mon Mar 1 to Fri Mar 12, 2027	Mon Mar 15 to Mon Mar 29, 2027 (Good Friday Mar 26 skipped)
Site preparation (Manually Scheduled)	Mon Mar 1 to Fri Mar 12, 2027	Unchanged: Mon Mar 1 to Fri Mar 12, 2027

The clean-up

The scheduler fixes the file in four steps. First, set New Tasks to Auto Scheduled on the status bar, so nothing new is added in manual mode. Second, AutoFilter the Task Mode column to Manually Scheduled. Third, review each manual task: if it has real logic, select it and choose Auto Schedule; if it is a genuine placeholder for contractor work not yet planned, leave it manual, put "placeholder" in the name and give it a note naming who will replace it and by when. Fourth, press F9 and use the Task Inspector on any task whose dates jump, to see which link or constraint now drives it.

Screenshot to come

Figure 3 is the rule the owner's scheduler now applies to every new task.

Screenshot to come

Owner's move

• Specify auto scheduling. The owner's master, and any contractor schedule delivered in Project format, should have every task with logic set to Auto Scheduled.
• Allow manual placeholders only before the baseline. Each one gets "placeholder" in the name, an owner and a convert-by date.
• Count manual tasks in every update. One AutoFilter on Task Mode tells you whether the dates are calculated or typed.
• Do not accept slack or critical path from a file with manual tasks on the path. Those dates do not respond to logic, so neither does the float. Lesson 11 covers what to look for.

Common mistakes

1. Leaving the default. New files start manual, and the first fifty tasks go in that way before anyone notices.
2. Using Respect Links as the fix. It moves the task once. The task is still manual and will drift on the next change.
3. Manual tasks to "hold" a contract date. The date never moves, so a delay upstream never reaches the milestone. Use a deadline instead (Lesson 12).
4. Manual summary tasks in a working master. The summary keeps its typed dates while the subtasks move, and the WBS roll-up stops telling the truth.

Quick quiz

1. For a manually scheduled task, Project:

   1. Recalculates dates from links on F9
   2. Never changes the dates, but may show warnings
   3. Applies the project calendar to the typed dates
   4. Converts it to auto when it gets a predecessor

2. In a new file created in a current version of Project, new tasks are by default:

   1. Auto Scheduled
   2. Manually Scheduled
   3. Placeholders
   4. Inactive

3. Changing the New Tasks setting on the status bar to Auto Scheduled:

   1. Converts every existing task
   2. Affects only tasks added afterwards
   3. Converts only summary tasks
   4. Is the same as Respect Links

4. What does Respect Links do?

   1. Deletes links that conflict with dates
   2. Moves selected tasks so their dates are determined by their dependencies
   3. Locks the task to its constraint
   4. Switches the task to auto mode permanently

5. In the Northgate what-if, the permit moves to Fri Mar 12, 2027. The auto-scheduled 10-day Site preparation finishes:

   1. Fri Mar 12
   2. Fri Mar 26
   3. Mon Mar 29
   4. Tue Mar 30

Show answers and explanations

1. B. Microsoft says Project never changes a manually scheduled task's dates, though it may warn about problems [1].
2. B. New tasks are manually scheduled by default; files from earlier versions open auto scheduled [1].
3. B. The default applies only to tasks created after the change [4]. Existing tasks need Auto Schedule on the Task tab.
4. B. That is Microsoft's description of the Respect Links command [3]. The task's mode does not change.
5. C. Mon Mar 15 plus 10 working days, skipping Good Friday (Mar 26), ends Mon Mar 29.

Key terms

Task Mode

The task field that records whether a task is Manually Scheduled or Auto Scheduled.

Auto Scheduled

Project calculates the task's dates from dependencies, constraints and calendars.

Manually Scheduled

The task keeps the dates and duration entered by the user; Project does not move it.

Placeholder

A manual task missing at least two of start, finish and duration.

Respect Links

A Task tab command that moves selected tasks to the dates their dependencies require, once.

Task Inspector

A pane (Inspect Task) that lists the factors driving the selected task's dates.

References

1. Microsoft. Task Mode (task field). Microsoft Support.
2. Microsoft. View and track scheduling factors. Microsoft Support (Project desktop).
3. Microsoft. Application.TaskRespectLinks method (Project). Microsoft Learn.
4. Taradigm. Manual Scheduling vs Auto Scheduling in Microsoft Project.

Verified on November 6, 2026.

Next lesson in this trackCritical path and total slack