When a date moves, nothing slips through

What this module does

A customer date moves three weeks to the right. The Project Manager has 40 tasks across two workstreams pinned to that delivery: review submittals, schedule the test, pre-stage the casting, brief the operator, fly the inspector, sign off the report. With fixed dates on each task, the Project Manager spends an hour clicking each task's calendar and dragging it, half the dependencies break in the process, and one task gets missed and surfaces three weeks later when the inspector is already in the air. With offsets, the Project Manager moves one date and the 40 tasks re-derive their start and due dates in one move.

Key pages

Tasks organises work in three levels: a space per project, topics (checklists or workstreams) inside it, and the tasks themselves. Tasks do not hold fixed calendar dates; each stores an offset from its topic's start and a duration, so rescheduling a topic to a new start date recalculates every task. A topic built once becomes a blueprint: each task's owner, offset, and duration is a template that can be duplicated into another project or attached to a Business Central document. When the document event fires, a posted goods receipt for instance, the matching template topic copies in and schedules from the date the event was posted.

Project Managers reschedule a whole workstream in one decision instead of forty. The operator opens My Tasks and sees what is due today instead of a chat asking them to do five things they cannot find on the calendar. The admin builds the topic templates once for “new project setup” and “month-end close” and they get reused for every new project that starts. And the follow-up that posting a goods receipt implies (book the inspection, photograph the part, file the certificate) is captured at the source instead of remembered in a notebook nobody reads back.