Decision Record Library & Templates

Capture why decisions were made so your team — and the teams that follow — can learn, adapt, and avoid repeating avoidable mistakes.

Why decision records matter

Decisions shape outcomes long after the conversation ends. A simple, consistent decision record preserves the rationale, evidence, alternatives considered, the chosen option, who owns it, and when it should be reviewed. That context prevents repeated debates, saves time for new team members, and helps organizations learn from trade‑offs rather than rediscovering them.

Who benefits

Small teams and service businesses, project managers, facility leads, product managers, clinicians changing protocols, shop foremen adjusting process steps, and nonprofit program leads can all use concise records to reduce friction, handoff losses, and reinvention. For example:

• A roofing contractor documents why a particular membrane was selected for a climate risk;
• A hospital quality team records evidence and trade‑offs for a revised discharge checklist;
• A production supervisor logs the decision to change a machine setpoint and the monitoring plan that follows.

What you'll find and do here

This resource provides a lightweight, fillable decision‑record template plus guidance on when and how to use it. After reviewing the template you will be able to:

• Capture the decision summary, scope, alternatives considered, and key evidence in plain language;
• Assign clear ownership, define follow‑up actions, and schedule a review date;
• Store and tag records in a searchable repository so future teams can find relevant context quickly;
• Adapt the template to local practices or include it in your team's domain or toolkit so it evolves with your organization.

Practical guidance — use these rules of thumb

Keep records short and focused: a few paragraphs for rationale and a simple table for owners, dates, and follow‑ups. Capture evidence links or attachments rather than pasting long data. Use a consistent title and tags (project, system, date) to make records discoverable. Schedule a single review date to reassess decisions that depend on new information.

Platform opportunities

If you adopt these templates in your Hunger Engine or shared domain, consider making the template an interactive form so teams can save structured records, store responses as JSON for later reporting, and include decision records in collections or toolkits that travel with site or enterprise copies. These affordances help convert one‑off notes into durable organizational memory without adding bureaucracy.