Create a project decision log template

Author: AILesson7 min setupTested with:ChatGPTReviewed: 2026-08-28

Quick answer

Design a durable record that distinguishes decisions from proposals, discussion, and actions. Provide: Project and governance, Current recording problems, Sample decision material. Expected result: A usable decision-log schema, workflow, and example entries with traceable authority.

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

Project and governanceCurrent recording problemsSample decision material

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Design a lightweight project decision log and test it against the supplied sample.

Project, roles, authority, tools, and obligations:
[project]

Current problems and handoff needs:
[problems]

Sample notes, options, evidence, dissent, and actions:
[sample]

Define which events qualify as a decision. Keep proposals, recommendations, approvals, superseded decisions, assumptions, risks, and action items distinct. Create the smallest schema that still records: stable ID, concise decision statement, status, decision date, effective date, decision owner and authority, context/problem, options considered, selected option, rationale, evidence/source links, assumptions, dissent, consequences/trade-offs, affected scope, follow-up actions, review trigger/date, supersedes/superseded-by, recorder, and last update. Explain required versus optional fields and allowed status values.

Specify capture, review, correction, supersession, linking, access, and retention workflow. Never infer approval from silence or attendance. Preserve uncertainty and restricted information by reference rather than copying it. Convert the sample into entries, but label anything not actually decided as Proposed or Unknown and use Unassigned for missing people. Finish with completeness and contradiction checks plus two retrieval examples a future teammate could perform.

Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Project and governance: Orchid help-center project uses Notion and Jira. Support director owns content scope; engineering lead owns technical architecture; security lead approves access to customer data. Project manager records decisions. Product, legal, and regional leads are consulted. Keep a two-year history; restricted security evidence stays in Jira Security.
Current recording problems: Choices are buried in meeting notes, attendees later disagree whether an option was approved, and Jira actions do not link back to reasons. The team needs to find decisions by affected release, owner, and review date. Reversals currently overwrite old pages.
Sample decision material: Meeting 27 Aug 2026. Support director Ana: 'We will launch English public articles on 30 Sep and evaluate Spanish demand after two weeks of preference research.' Regional lead objects that Spanish access is delayed. Ana asks Jo to draft the study by 2 Sep. Engineering lead says locale paths already work. Someone suggests order-specific help; security lead was absent and no decision was made. Source: Notion meeting-2026-08-27.

Example output

Minimum schema: ID, statement, status, decided/effective dates, decision owner + authority, context, options, selected option, rationale/evidence links, assumptions, dissent, consequences/affected scope, actions, review trigger/date, supersession links, recorder, updated date. Required fields are ID, statement, status, owner/authority, source, affected scope, and updated date; a Decided entry also requires decision date, selected option, rationale, and effective condition. Status values: Proposed, Decided, Effective, Superseded, Reversed, Withdrawn, Unknown.

DL-2026-014 — Decided — On 27 Aug, Ana, acting as content-scope owner, selected an English public-article launch for 30 Sep and a two-week preference study before a Spanish-scope decision. Source: Notion meeting-2026-08-27. Rationale evidence: locale paths exist; demand evidence is not included in these notes, so mark Unknown. Dissent: regional lead says delayed Spanish access causes harm; preserve verbatim location, not inferred resolution. Consequence: Spanish is not in the 30 Sep baseline. Action A-77: Jo drafts study by 2 Sep; acceptance/assignee confirmation Unknown. Review trigger: completed two-week research; review date Unknown.

DL-2026-015 — Proposed — add order-specific help. Decision owner: security lead for data access; requester and exact data Unknown. No approval occurred because the authority was absent. Link future security discovery; do not create implementation action yet.

Workflow: recorder drafts within one working day; owner confirms statement/status; corrections append an amendment; later direction creates a new ID linked by supersedes. Jira actions link DL IDs. Monthly review finds stale triggers. Retrieval checks: “show Effective decisions affecting 30 Sep release” and “show Decided items owned by Ana with review dates missing.” Completeness warning: DL-014 lacks research evidence and review date; no contradiction between the two entries.

Why this works

1
A stable decision record reduces repeated debate and makes changed direction explainable
2
Explicit authority and status prevent a discussed option from silently becoming policy

Check the result

Can a reader tell what was decided, by whom, under what authority, and when it applies
Are proposals, actions, assumptions, and superseded decisions represented separately
Does the workflow allow correction without erasing the historical record

Use it with confidence

Frequently asked questions

Practical answers about when to use this recipe, what to provide, and where human review still matters

What should I prepare before using “Create a project decision log template”?

For “Create a project decision log template,” prepare Project and governance, Current recording problems, and Sample decision material. 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 “Create a project decision log template” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A usable decision-log schema, workflow, and example entries with traceable authority—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 “Create a project decision log template”?

The published test record for “Create a project decision log template” 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.

More ways to explore