Task changes is where you write down a job and keep its plan up to date. Use it to plan new work, move a planned date, mark work finished or return to a job that needs attention again. Work plan then shows the latest details you have saved.
Each horizontal line, called a row, records one decision about a job. A job keeps the same Task number throughout its history. Each decision has a different Entry number, so you can distinguish the original plan from a later change or completion. You choose these numbers or short labels yourself.
For a new job, start on the next empty row and choose Create under Decision. To update an existing job, use another empty row, enter the same Task number and choose a new Entry number. Keep the earlier row: it explains what you had planned before.
Fill in the complete plan on the new row, including the description, due date and other details that have stayed the same. Work plan reads that latest row as the current plan, so leaving an unchanged detail blank would not tell it to carry the earlier value forward.
Leave the earlier included rows in place and keep these rows in the order you entered them. The last included row that passes its checks supplies the current plan. Sorting this entry page or moving its rows could therefore change which plan is used; use Work plan or Work history to read the work instead.
If you use Google Calendar, send the saved task changes from Start Here → Update Google Calendar. This starts the update with one click. The Google Calendar guide explains the result and how to connect it for the first time.
Include entry is how you confirm that this update should become part of the task’s plan and history. Fill in the row first, read Entry check and review your wording; then tick the box when the entry is Ready. For a later change, add another update rather than unticking an earlier decision, so you can still understand how the plan developed.
Give each decision its own unused number or short label and keep it unchanged. Creating a job, moving its due date and marking it complete are three decisions, so each needs a different Entry number. The Task number stays the same for all three, which keeps them together as one job.
Choose one unused number or short label for the job itself. Reuse it whenever you update that job, even if its date, description or responsible person changes. Using a different Task number would make the update appear to be another job.
Choose the stock number when the work concerns a particular item or lot, such as an inspection of one recorded group. This helps the person doing the work identify the right stock. Leave it blank for a general job that does not belong to one stock record; you do not need to invent stock just to plan work.
Due on is the day you currently intend the work to happen. It can be a future date, because this is a plan. When a job is delayed, enter its new date on a new Reschedule update so that Work plan changes and the previous due date remains in Work history.
Add a Due time when a particular time of day matters for the job. If the work only needs to be done on the chosen day, leave this blank. This keeps the plan clear without making you choose an arbitrary time for every task.
Write what someone needs to do and identify the thing or place involved. Imagine another person reading the task tomorrow without the conversation that led to it: they should be able to understand the job from this description and its Detail. If you are updating a task, include its current full description again, even when the wording is unchanged.
Decision explains what this update means. Use Create when first planning the job, Reschedule when changing its plan, Complete when the work has been done, Cancel when it is no longer needed, and Reopen when it needs attention again.
Every update needs the complete current task details. To reduce retyping, you can copy columns B:L from the previous update into the next empty row, give the copy a new Entry number and change the relevant details before including it. Keep the Task number because it is still the same job. Recording a task decision does not itself move stock, change a quantity or release a hold.
Decided on is the date you made the decision recorded by this row. It must be a date that has already happened. You might decide today to inspect something next Monday: today belongs in Decided on, and Monday belongs in Due on. Keeping both dates makes the planning history easier to understand.
Enter the person or team expected to do the work when an assignment would help. Other people reading the workbook can then see who is taking responsibility. This field does not send a notification, so make any necessary arrangements with that person separately.
If a saved note or stock entry helps explain the job, put its number here so you or a colleague can find it. After an inspection, for example, the note number leads to the findings. Save that note or stock entry on its own page first; writing its number here does not create it.
Detail is space to explain what someone needs to know beyond the short job description. You might explain why the date changed, which area to inspect or what prompted a job to be reopened. Useful context helps a colleague carry out the work and helps you understand the decision later.
Entry check reads the row and tells you whether its current checks pass. Ready means you can review it for inclusion; it is still your responsibility to confirm that the task and dates describe what you intended. If the message identifies a missing or unsuitable value, correct it and read the message again before ticking Include entry.