✍️ Article

Project Review Checklist: Find Missing Owners, Dates and Unfinished Tasks

An open task list is not necessarily a failed project. Some items await a reply, some need a responsible person and some are observations that should never have a task deadline assigned to them. A good review preserves those distinctions instead of turning every blank field into an alarm.

GentleTools’ free interactive studios include a Project review radar. It reads the records in the current local browser project and groups items that deserve a second look. It does not send messages or verify a supplier, clinician or authority.

Five checks to make during a project review

Review question What a finding actually means Appropriate next action
Is an entry marked complete? Its stored status is not in the completed set Confirm progress and update the status only if justified
Who owns this item? The owner field is empty Identify the right person; do not guess
Is its date recorded? The date is blank or invalid Check the source and enter the correct date if known
Are comparisons complete? A planned or actual numeric field is missing Find the measurement, quote or receipt; leave unknowns blank
Has a recorded deadline passed? A deadline-type date is earlier than today and the record is open Confirm whether the commitment changed before taking action

The last distinction is essential. The date on a medical observation, care handoff or maintenance record is usually when something was recorded—not a deadline. The radar only uses passed-deadline language for studios whose date field is explicitly designated for deadlines.

Start with unfinished states, not with a blame list

An entry labelled ‘Awaiting reply’ might be progressing exactly as intended. To make it actionable, write whose response you are waiting for and the next agreed review step. If the record describes a claim, agreement or appointment, confirm the original source before communicating it to another person.

Use Client Onboarding Handoff Board or Freelance Revision Approval Desk for work where a written reply changes what happens next. Use Home Repair Request Follow-Up for issues where the chronology of requests and responses matters.

Treat missing numeric data differently from zero

A budget row with a planned cost of 100 and an actual cost of zero does not mean the same thing as a row with no actual value entered. Zero is a claim; blank is unknown.

Suppose you planned to spend 100 on transport. If the trip has not occurred and no receipt exists, the actual amount should stay blank. If the trip occurred and you can confirm no money was spent, zero may be appropriate. The budget comparison guide explains how this prevents misleading totals.

The review radar flags missing comparison values rather than silently substituting zeros.

Review a project in two passes

Pass A: inspect the structure. Are there duplicate task names, responsibilities that need assigning, missing comparison values or unclear dates? The radar can focus the corresponding records, so you can review them without changing the underlying list.

Pass B: verify the facts. Open the real source: a signed agreement, a supplier email, an account statement or a note made at the time. Decide whether a status change is warranted. If someone only promised to respond, do not mark the response received.

For high-stakes health, financial or legal topics, treat the studio as an organizer of user-entered information. It cannot determine clinical significance, eligibility, safety or legal obligations.

Keep the review short enough to repeat

A practical rhythm is to open one project, inspect the most relevant review group, verify two or three facts and save or export a revised snapshot. The goal is not to ‘clear all warnings’ at any cost. Some missing values are legitimately unknown.

If you need to share progress, a short handoff brief may be easier to review than a full set of records. Before sharing, check whether notes contain names or other private details.

Takeaway: a useful review system creates clarity without making decisions on the user’s behalf. Empty fields invite a question, not an invented answer.