Sort out conflicting dates across project reports into one timeline

A draft reconciled timeline that keeps source and approval source details and lists the unresolved date decisions.

Choose one of two approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

ChatGPT: drafts the table and timeline, you check both

ChatGPT drafts the date-conflict table, then the reconciled timeline. You check the table, then the final copy.

  1. You

    You: Get inputs ready

  2. ChatGPT

    ChatGPT: Draft date table

  3. You

    You: Check each row

  4. ChatGPT

    ChatGPT: Draft the timeline

  5. You

    You: Check and decide

  1. Get the inputs ready

    Use: You

    Have ready: the milestone register, team messages and approved schedule versions. Optional material stays optional.

    Check

    Check permission, audience limits and source completeness before uploading. Keep the originals available for the row check.

  2. Draft the date-conflict table

    Use: ChatGPT

    Ask ChatGPT for one row per conflicting milestone with every candidate date, source ID, version and approval trail, timestamps kept separate from authority.

    Details

    What to paste into the tool

    Task: Unreviewed date-conflict table with version and approval provenance. Using only the supplied inputs, build one row per conflicting milestone with every candidate date, source ID, version identifier, approval provenance and uncertainty; keep timestamps separate from authority and leave unresolved date choices open. Keep source identifiers, dates, quotes and uncertainties explicit. Missing or ambiguous facts are still to confirm. Draft only; do not send, publish, change records, assign work or run commands.

  3. Check each row against the originals

    Use: You

    Read each row against the original inputs, correct errors and record unresolved fields; ask for fixes in the same chat.

    Check

    Compare identifiers, dates and ambiguous claims against the original inputs.

  4. Draft the reconciled timeline

    Use: ChatGPT

    In the same chat, paste the corrected table and ask for the reconciled timeline, each conflicting date left as an open decision.

    Details

    What to paste into the tool

    Task: Unreviewed working copy: Draft reconciled timeline with unresolved date decisions. Use only the checked table and supplied source copy to prepare a reconciled timeline retaining source and approval provenance for dates supported by the supplied authority, with every conflicting date left as an explicit unresolved decision for the lead; a newer timestamp does not automatically override approval. Preserve source locations and all unresolved fields. Draft only; do not send, publish, change records, assign work or run commands.

  5. Check the timeline and decide

    Use: You

    Check the working copy against the checked table and original inputs; keep unresolved questions and stop at the checked draft.

    Check

    Check the dates against their approval authority; a newer timestamp does not override approval. Decide any next action separately.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Compare the source identifiers, definitions, dates and ambiguous claims against the original inputs; correct date-conflict table with version and approval source details before handoff.

Lead confirms authoritative dates; a newer timestamp does not automatically override approval.

Check organisational permission and source/audience restrictions before uploading operational material. Stop at the reviewed draft; no real-world next action occurs.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Not yet confirmed: actual input size, account feature access, quotas and organisational permission to upload the confidential material. No scenario was executed.

Share this page