Shared Holiday Homes logo
Mike Rodriguez·
Person writing structured notes in a notebook during a group meeting

Shared Holiday Home Decision Log Template

A shared holiday home decision log is one current record of what the co-owners decided, how the decision was approved, when it takes effect, what it replaces, and when it must be reviewed. It is not a transcript of every opinion. It preserves the final operating position after a meeting, message thread, written consent, or other valid decision process.

Use the template below for booking rules, routine spending, guest policies, maintenance choices, document changes, and other practical decisions. Keep tasks, invoices, access codes, personal disputes, and professional advice in their proper places. The log should point to those records only when authorised people need the connection.

Copy This Decision Log Template

Create one row or record for each final decision. Give it a stable ID so a later policy, task, document, or meeting note can refer to it without copying the whole history.

FieldWhat to recordExample
Decision IDA permanent, unique reference that is never reusedBOOK-2026-04
Area and questionThe operating area and the exact question the group resolvedBookings: when does an unused peak-week allocation return to the group?
DecisionThe final rule or choice in complete, neutral languageAn allocated peak week becomes available to all households at 18:00 property time, 60 days before arrival, unless already confirmed.
ScopeWho, what, and which dates or situations the decision coversAll four owner households; peak weeks listed in the current booking policy
Approval recordThe required route, result, participants, and date without reproducing private debateApproved 4–0 through the written process in section 6 of the operating rules on 1 August 2026
Effective dateWhen the decision begins, including any transition rule1 September 2026; existing confirmed bookings stay unchanged
SupersedesThe earlier decision ID or document section this one replacesBOOK-2025-02
Source and evidenceWhere the approved minutes, policy, quote, inspection, or professional response is heldAnnual review record, item 3; booking policy v4
Follow-upNamed tasks, owners, due dates, and linked records needed to apply the decisionMorgan updates the written policy and shared calendar note by 8 August
Review triggerA date or event that requires the group to check whether the decision still worksAfter the 2027 peak season, or after two disputed releases

If a field is not applicable, say so. A blank can look like forgotten work; “not applicable—no earlier decision” makes the record deliberate.

Decide What Belongs in the Log

The log becomes useful when its boundary is predictable. Put final operating decisions in it. Put conversation, action, evidence, and controlled documents elsewhere.

A discussion is not a decision

A message such as “Most of us seem happy with a 60-day release” records sentiment, not approval. It does not show whether the required people responded, whether the group used the correct route, or whether existing bookings are protected.

Capture the discussion in meeting notes or the agreed communication channel. Add a decision-log entry only after the group has reached an outcome through its valid process. If the result is “no decision yet,” create an evidence or consultation task rather than inventing agreement.

The holiday home communication playbook helps separate urgent alerts, general discussion, booking coordination, and durable records. A clean boundary stops a long chat history from becoming the unofficial rulebook.

A task is not a decision

“Ask two roofers for quotes” is a task. “Approve contractor A up to the agreed limit after the comparison and authority check” is a decision. The decision log states the authorised choice; the task records who will carry it out, by when, and what completion means.

This distinction matters when a person leaves a task incomplete. The group can reassign the action without reopening a valid decision. Conversely, completing a task does not grant permission to make a choice that still needs group approval.

A document is not a decision

The signed agreement, trust record, insurance policy, contractor quote, invoice, booking policy, or professional letter belongs in its controlled document location. The log records the decision and points authorised readers to the source.

Do not paste entire sensitive files into a broad operational log. A short reference such as “current policy schedule, property folder, approved 1 August” is usually more useful than another uncontrolled copy.

An observation is not a decision

“Water mark seen above the rear window” is an observation. It should enter the vacation home maintenance log with a date, location, status, and next action. A later entry in the decision log might record approval for a qualified inspection or a repair option.

Do not turn an unverified observation into a diagnosis. The log should show what the group authorised, not pretend that co-owners have professional certainty they do not have.

Use a Six-Step Decision Workflow

A reliable log begins before anyone types the final row. Use the same small workflow whether the decision happens in an annual meeting or between reviews.

1. Frame one answerable question

Write the question narrowly enough that the group can tell when it is resolved. “What should we do about bookings?” is too broad. “When does an unused peak allocation return to the group?” can produce a precise rule.

Separate dependent questions. The release deadline, allocation method, guest access, cancellation consequences, and maintenance blocks are different choices. The 12-decision booking-rules guide shows why one calendar policy may need several linked entries.

2. Confirm the decision route

Before counting views, check which valid document or existing rule determines notice, participation, consent, voting, trustee authority, conflict handling, or professional input. Do not invent a universal majority, unanimous threshold, or chair's casting vote.

If the route is unclear, pause the operating decision and assign someone to obtain the relevant document or qualified local advice. The decision log is evidence of what the group recorded; it does not create authority that the group did not have.

3. Bring the minimum evidence

Collect only what the decision needs: a current policy section, calendar pattern, maintenance record, quote comparison, cost category, document version, or written professional response. Label estimates and incomplete evidence honestly.

For a cost-allocation question, use the shared vacation home expense guide or free cost split calculator to compare methods. The tool can make trade-offs visible; the group still decides which method fits its agreement and circumstances.

4. Record the exact outcome

Write one neutral sentence that another co-owner could apply without reconstructing the discussion. Include the scope, effective date, and transition rule beside it. Avoid phrases such as “be sensible,” “as usual,” “when necessary,” or “everyone agreed” unless the record makes those words testable.

Read the wording back before closing the decision. Ask each participant whether the log reflects the result, not whether it perfectly expresses every argument they made.

5. Connect implementation without duplicating it

Name the follow-up tasks, responsible owners, due dates, and source documents. Keep their detailed progress in the task or document system. The decision record should remain stable while the implementation status changes.

For example, a maintenance decision may produce separate tasks to obtain access, schedule a professional, record the invoice, verify completion, and set the next review date. The log links those actions without becoming a second maintenance tracker.

6. Publish, protect, and review

Circulate the draft through the group's agreed correction process. Once final, restrict edits, preserve the effective date, and make the current entry easy to find. Do not silently rewrite history. A later change should create a new decision that clearly supersedes the old one.

Add both calendar dates and event-based triggers. A booking rule might be reviewed after the next peak season. A contractor choice might be reviewed if the scope or quote changes. A guest rule might be reopened after a documented exception rather than on every preference change.

Manage Current, Superseded, and Withdrawn Decisions

Never delete an old decision merely because the group changed its mind. Mark its status and point forward to the replacement. This preserves the operating sequence without suggesting the old rule still applies.

Use four simple states:

  • Current: approved, in effect, and not replaced.
  • Future: approved but waiting for its effective date.
  • Superseded: replaced by a named later decision.
  • Withdrawn: cancelled before taking effect, with the approved withdrawal record identified.

“Expired” can be useful when a decision was deliberately time-limited. Do not use it as a substitute for checking whether the relevant governing document actually allows the rule to lapse.

When correcting a typo, preserve an edit note. When changing meaning, create a new decision ID. This prevents a link in an old task or meeting record from quietly pointing to different instructions later.

Worked Examples for a Four-Household Group

These examples are fictional. They show the level of detail that makes a record usable without prescribing a voting rule, spending limit, safety choice, or legal result.

ID and questionRecorded decisionImplementationReview
BOOK-2026-04: unused peak weekRelease at 18:00 property time, 60 days before arrival; confirmed bookings are unchanged.Update booking policy v4 and add a shared-calendar reminder.After the 2027 peak season or two disputed releases.
MAINT-2026-07: exterior inspectionApprove a qualified inspection within the documented limit; no repair scope is approved yet.Riley arranges access; findings and quote references go in the maintenance log.When the inspection report arrives.
GUEST-2026-03: welcome-book ownerTaylor owns the approved guest guide; local and emergency details need source verification before release.Create a quarterly review task and record the current file location.Quarterly, plus any provider, access, or local-information change.

Notice what is absent: the inspection diagnosis, access code, contractor banking details, personal objections, and every message from the meeting. The log contains enough to apply and audit the decision while leaving controlled information in the correct place.

Start Without Rebuilding Years of Chat

Do not begin by reconstructing every historic conversation. That creates disputed history and delays a useful current record.

Start with five categories that affect the next 90 days:

  1. current booking and peak-date rules;
  2. routine spending and approval boundaries;
  3. open maintenance choices;
  4. guest, access, and property-information rules; and
  5. current document owners and review dates.

For each category, identify the approved current source. If the group cannot find one, label the question unresolved and schedule a valid decision. Do not backfill a confident-looking answer from memory.

The shared holiday home annual review agenda can help the group find cross-area gaps. Use the log to preserve the decisions that emerge from that meeting and from smaller decisions during the year.

Protect Privacy and Formal Authority

Keep the operational log useful to its intended readers without turning it into a store of unnecessary personal or sensitive data.

Avoid recording:

  • passwords, access codes, alarm details, or spare-key locations;
  • card, bank, identity, medical, or tax data;
  • private accusations or a transcript of a family dispute;
  • unverified safety, legal, insurance, structural, or financial conclusions;
  • professional advice beyond a short reference to the controlled source; and
  • details about guests or workers that the group does not need for the operating decision.

An informal log does not amend title, a trust, a contract, a court order, an insurance policy, a loan, an employment arrangement, or local accommodation rules. Where those records control, use the required formal process and appropriately qualified local advice. The decision log can reference the resulting approved document; it cannot replace it.

FAQ

What should a shared holiday home decision log include?

Include a stable ID, the exact question, final decision, scope, approval record, effective date, superseded decision, source reference, follow-up tasks, and review trigger. Record enough context to apply the result without reproducing the whole debate.

Is a decision log the same as meeting minutes?

No. Minutes record what happened in one meeting, including attendance, agenda items, and discussion at the level the group requires. A decision log collects final operating decisions made across many meetings and written processes, then shows which decision is current.

Is a decision log legally binding?

The log itself does not create authority merely because someone wrote an entry. The effect of a decision depends on the ownership, trust, contract, entity, court, insurance, lending, and local-law context plus the valid approval process. Obtain qualified advice when that effect matters.

Should rejected options go in the log?

Usually not in detail. Record the final outcome and the source record where authorised readers can find the necessary rationale. If a rejected option creates a future constraint—for example, a quote expires or an inspection is still required—capture that fact neutrally without copying private debate.

How often should the log be reviewed?

Review it when a stated date or event occurs and as part of the group's periodic operating review. Also check it after ownership, trustee, insurance, provider, property-condition, or governing-document changes that may affect an entry. Do not assume an old operational decision remains valid after its authority or facts change.

Who maintains the decision log?

Give one person responsibility for publishing the agreed wording and protecting version history, with a backup. That role does not grant extra voting power or permission to alter decisions. The group should use its existing process to approve corrections and changes.

Is this for commercial fractional ownership or timeshares?

No. This template is for a private family, friend, sibling, trustee, or small co-owner group already sharing or jointly owning a particular holiday home. Provider-managed fractional products and timeshares have their own contracts, management powers, use rights, and record systems.

Turn Decisions Into Visible Follow-Through

Start with the current rules that affect the next 90 days. Record the exact outcome, connect it to one source and the necessary tasks, then give it a review trigger. A short log people trust is better than a complete-looking archive built from guesswork.

The free shared holiday home rules generator can help an existing private group frame booking, guest, cost, care, communication, and decision questions. It creates a discussion draft, not a legal agreement. When the group has approved its operating choices, Shared Holiday Homes can keep the related house documents, property information, and follow-up tasks together. Start a free trial when the group is ready to replace scattered administration with one shared workspace.

Ready for one place the whole group can trust?

Shared Holiday Homes gives families, friends and co-owners one calendar, shared tasks, and a home for house documents — so the next trip starts with less admin.

About Us

We help families, friends and co-owners organise a holiday home without the admin — one calendar, clear jobs, and every document where everyone can find it.

Quick Links

Contact

Email: support@sharedholidayhomes.com

© 2026 Shared Holiday Homes. All rights reserved.