Design a project status and overdue task tracker

المؤلف: AILesson7 دقائق للإعدادتم اختباره مع:ChatGPTتمت المراجعة: 2026-08-28

إجابة سريعة

Track ownership, deadlines, dependencies, blockers, and overdue work with explicit status rules. قدّم: Projects and review workflow, Status and deadline rules, Required task information. النتيجة المتوقعة: A maintainable task table, overdue logic, project summary, and review routine.

أضف سياقك

يبقى نصك في هذا المتصفح. لا يرسله AILesson Prompts إلى نموذج أو خادم.

Projects and review workflowStatus and deadline rulesRequired task information

الأمر الخاص بك

تبقى الحقول غير المعبأة ظاهرة كعناصر نائبة، لذا يمكنك نسخ الأمر وتحريرها

Design an Excel project status and overdue task tracker.

Projects, users, update cadence, and review decisions:
[workflow]

Status, completion, overdue, blocked, and priority rules:
[statusRules]

Required task fields, dependencies, milestones, and reporting needs:
[fields]

Define one row's grain, stable keys, controlled lists, required dates, and who owns each update. Keep user-entered status separate from formula-derived health. Return table layouts, validation rules, formulas for overdue and due-soon work, dependency and blocker handling, project-level summaries, conditional formatting, and a review checklist. Explain how to preserve history when dates or status change. Do not infer progress from elapsed time alone or mark a task late after it is completed.

جرّب في المختبر

خاص افتراضيًايتم تجميع الأمر محليًا في متصفحك. تجنب وضع معلومات سرية في أي خدمة ذكاء اصطناعي ما لم تسمح مؤسستك بذلك.

من المدخلات إلى النتيجة

مثال عملي

شاهد كيف يحول السياق الملموس هذه الوصفة إلى نتيجة قابلة للاستخدام

المدخل الفعلي

Projects and review workflow: A six-person operations team manages five concurrent projects. Owners update tasks each Tuesday; the manager reviews overdue work, milestones, and blockers on Wednesday. Projects stay in one workbook.
Status and deadline rules: Statuses are Not started, In progress, Blocked, Done, and Cancelled. Done requires CompletedDate. A task is overdue after DueDate unless Done or Cancelled. Due soon means within 3 calendar days. Priority is High, Medium, or Low. Blocked tasks require a reason and next review date.
Required task information: ProjectID, TaskID, Task, Owner, Priority, StartDate, DueDate, Status, CompletedDate, DependencyTaskID, IsMilestone, BlockerReason, NextReviewDate, LastUpdated, and notes. Need owner and project summaries plus a weekly history.

مثال على المخرجات

Create a Tasks Excel Table with the requested columns and a unique TaskID that never changes when a task moves. Use controlled lists for Owner, Priority, Status, and IsMilestone. Validate that Done requires CompletedDate, Blocked requires BlockerReason and NextReviewDate, and DependencyTaskID exists in Tasks. Keep Status user-entered; add a formula-derived Health column.

Health logic: if Status is Done or Cancelled, return Closed; if DueDate is blank, return Review; if DueDate<TODAY(), return Overdue; if DueDate<=TODAY()+3, return Due soon; if Status is Blocked, return Blocked; otherwise return On track. Put Blocked before date tests instead if the team wants blockers to dominate. Add DaysPastDue only for open overdue work and do not calculate percent complete from calendar time.

Build PivotTables by ProjectID and Owner showing open, overdue, due-soon, blocked, and completed counts; list overdue high-priority tasks rather than hiding them in totals. Add a Milestones view sorted by DueDate. Each Tuesday, append ProjectID, TaskID, Status, DueDate, Health, Owner, and SnapshotDate to a History table so deadline changes remain visible. Wednesday checks: duplicate IDs, missing owners or dates, invalid dependencies, stale LastUpdated, blocked items without review dates, and summary counts reconciled to filtered task rows.

لماذا يعمل هذا

1
Stable task IDs and separate derived health fields make changed deadlines and statuses auditable.
2
Explicit completion and overdue rules prevent false alerts and inconsistent reporting across projects.

تحقق من النتيجة

Does every task have one stable ID, accountable owner, and unambiguous due date rule?
Are completed tasks excluded from overdue and due-soon flags?
Can project summaries be reconciled to the underlying task rows?

استخدمها بثقة

الأسئلة الشائعة

إجابات عملية حول متى تستخدم هذه الوصفة، وما الذي تقدمه، وأين لا تزال المراجعة البشرية مهمة

What should I prepare before using “Design a project status and overdue task tracker”?

For “Design a project status and overdue task tracker,” prepare Projects and review workflow, Status and deadline rules, and Required task information. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Design a project status and overdue task tracker” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A maintainable task table, overdue logic, project summary, and review routine—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Design a project status and overdue task tracker”?

The published test record for “Design a project status and overdue task tracker” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

المزيد من طرق الاستكشاف