Shared Holiday Home Provider Authority Register Template

A shared holiday home provider authority register should show who may ask, receive information, approve internally, and instruct each provider—and which current source supports that authority. It should separate the group's own roles from whatever the provider, contract, governing document, ownership arrangement, trustee source, or applicable law actually recognises.

Use one row per provider relationship. Record permitted actions narrowly, link to controlled evidence, name a review trigger, and write unverified—do not act when the source is unclear. The register does not grant authority, amend a contract, appoint an agent, interpret a trust or ownership document, or replace advice for the property and jurisdiction.

Keep Four Different Questions Separate

Confusion starts when a useful internal role is treated as proof that a person can bind the account. A payer, portal user, organiser, key holder, named owner, trustee, and provider-recognised contact may have different powers.

The roles and responsibilities chart owns internal accountability. The contact directory owns current people and routes. The service account register owns provider and account metadata. This authority register owns the narrow bridge between an action and the source that permits it.

Copy This Provider Authority Register

Copy these fields into the group's approved system. Give each row a stable ID such as AUTH-001. Use references to controlled records instead of attaching identity documents, signatures, credentials, payment details, or entire contracts to a broadly shared table.

Authority row ID:
Property and service:
Provider and safe account reference:
Named account or contracting party, copied from the current source:
Internal coordinator and backup:
Internal approval source and decision reference:
Provider-recognised person, role or route:
Permitted action: ask / receive / report / approve internally / instruct / change / cancel / dispute
Action boundary or provider restriction:
Authority evidence type and controlled location:
Evidence issue, effective or confirmation date:
Provider verification route and date last checked:
Identity or verification process reference only, never the evidence itself:
Who may view this row:
Who may use the provider route:
Current status: verified / limited / verification assigned / change pending / suspended / superseded
Review trigger:
Next review owner and due date:
Open exception or qualified-advice reference:
Superseded row and replacement reference:
Last verified by and verification date:

Avoid a single field labelled authorised person. It hides whether the person may only receive outage updates, may discuss billing but not change payment, or may issue a cancellation instruction. Record each relevant action separately.

Build the Register in Seven Steps

1. Inventory provider relationships from current sources

Start with current statements, contracts, provider notices, official account records, association documents, approved maintenance records, and the group's governing sources. List only providers and services that actually apply to the home.

Create separate rows when two services have different named parties, permitted actions, evidence, review triggers, or provider routes—even if the brand is the same. Electricity, water, connectivity, waste, alarm monitoring, cleaning, garden work, building management, association services, insurance contacts, and recurring trades may all follow different authority processes.

Do not infer authority from who normally sends emails, holds a key, lives closest, pays first, or knows the provider. Those facts may identify a useful coordinator; they do not settle what the provider or governing source recognises.

2. Copy the named party exactly

Record the named account or contracting party as it appears in the current source. It may be one owner, several owners, a trustee, an entity, an association, or another valid party. If the source and the group's understanding disagree, preserve both as an exception and assign verification. Do not silently rewrite the source.

Link the row to the controlled document and note its issue or confirmation date. A provider homepage, an old email, a payment description, or a previous organiser's recollection may help locate the right route, but it may not establish current authority.

If the authority depends on ownership, a trust, an entity, a court or estate process, a power, or another formal instrument, stop at the reference. The group should use the current instrument and qualified advice appropriate to the facts and jurisdiction rather than recording its own interpretation as a conclusion.

3. Define actions narrowly

Replace broad labels with verbs. For each person or route, ask whether current evidence permits them to:

• request general information;
• receive statements or service notices;
• report a fault or emergency observation;
• discuss a billing query;
• approve a change inside the co-owner group;
• instruct the provider to change, renew or cancel a service;
• add or remove a contact or user;
• change a payment method or billing address;
• dispute a charge or accept a proposed outcome; or
• collect, return or replace provider equipment.

An entry should say may report a fault through the official service line rather than full authority. If the provider will confirm information only after its own checks, record the official process instead of trying to predict the result.

4. Pair internal approval with provider recognition

Most meaningful changes need two separate checks. First, did the group approve the action under its applicable decision rules? Second, does the person sending the instruction have the authority and evidence required by the provider and governing sources?

Record both references. Internal approval without a valid provider route can leave a decision unimplemented. Provider access without internal approval can let one person make a change the group never authorised. The register should reveal either gap before someone acts.

Use the decision log template for the group's choice and keep the provider's acknowledgement or rejection with the service record. A register status such as change pending should never be treated as proof that the requested change took effect.

5. Protect evidence and verification data

The register should contain only enough detail to find and verify the right source. Do not store passwords, recovery codes, security answers, full payment credentials, signatures, identity-document images, private adviser correspondence, or unnecessary personal data in the row.

Write a controlled reference such as restricted authority file / AUTH-001, then limit access according to the actual need and applicable privacy, security, provider and legal requirements. If a provider requests identity or authority evidence, use its verified official route and retain only what the relevant source requires.

Do not send documents through a link or phone number copied from an unexpected message. Locate the official provider route independently from a current statement, known portal, or provider website, and assign suspicious contact to the appropriate security or fraud process.

6. Route changes and exceptions without overwriting history

Authority changes should move through explicit states. Preserve the previous row, open the proposed change, link its internal approval, follow the provider or governing process, record the provider response, and verify the result before marking the new row active.

For an approved provider switch, use the service provider change handover to coordinate outgoing and incoming accounts, dates, access, equipment, finance and open exceptions. For a departing co-owner, use the co-owner access removal handover to inventory physical and digital routes. Neither workflow should claim that the other has completed an authority change.

7. Verify with a real, low-risk retrieval test

Ask an authorised person who did not build the register to select one provider and answer four questions without exposing secrets:

1. What service and property does this row cover?
2. Who may coordinate and who may approve internally?
3. What current source shows who may perform the next provider action?
4. What event would reopen the authority review?

Use a low-risk information request or source check when the provider allows it. Do not create a live contract, payment, cancellation, access or identity change merely to test the register. Record the date, route, result and follow-up; then keep the row limited or verification assigned if the test did not establish the needed action.

Fictional Example: Cottage Broadband Authority

Four friends share a private cottage. Jamie pays the broadband bill, Priya stores the contract, Morgan receives outage texts, and Lee manages the home's admin calendar. Their old spreadsheet lists all four as authorised, but nobody can identify the source or the actions each person may take.

They create AUTH-004. The current statement names Jamie as the account holder. The group decision log names Lee as the internal coordinator for the renewal review, but that assignment does not authorise Lee to change the service. The provider's current official account record confirms that Jamie may discuss billing and submit an instruction after its required checks; Morgan remains a notification contact only.

The row links to the controlled provider confirmation and the group's renewal decision. It records separate actions for receiving notices, discussing billing, approving internally and instructing the provider. Priya's contract access is a document permission, not provider authority. No password, signature, identity image or payment detail is copied into the register.

When Jamie plans to leave the co-owner group, the row changes to change pending. The friends use the applicable group, provider and qualified routes to review the account. They do not mark Lee as the replacement until the provider confirms the change. This fictional example demonstrates record boundaries, not a legal result or a recommendation for any provider or ownership structure.

Review on Events, Not Just a Calendar

Choose a periodic review frequency that fits the provider and risk, but reopen a row when any of these events occurs:

• an owner, trustee, entity, account holder, coordinator or provider contact changes;
• a service renews, transfers, closes, disputes a charge or enters an interruption;
• the provider changes its portal, verification method, contact route or terms;
• the property is sold, inherited, refinanced, placed into or removed from a structure, or changes use;
• a person dies, loses capacity, withdraws, becomes unavailable or has access removed;
• a governing document, decision rule, court order or professional instruction changes;
• a credential, device, email address, phone number, payment method or identity record is compromised; or
• a provider refuses an instruction or identifies conflicting evidence.

Record the trigger, affected actions, interim limit, review owner, source and verified outcome. Never update last verified simply because somebody reviewed the spreadsheet formatting.

FAQ

Is the bill payer automatically authorised to change the service?

Do not assume so. Payment, internal approval, account naming and provider-recognised authority are separate questions. Use the provider's current official record, the applicable governing sources and qualified advice where needed.

Can the group appoint an authorised person in this register?

The register records an authority created and recognised elsewhere; it does not create one. Follow the valid group, provider, ownership, trustee, contractual and legal processes that apply.

Should the register contain identity documents or signatures?

Not by default. Keep only a controlled reference and the minimum status needed for coordination. Use the provider's verified official route and the applicable privacy, security, retention and legal requirements for any evidence.

What if authority is different for billing, faults and cancellation?

Create separate action rows or a clear permitted-action matrix. A person who may report an outage may not be able to receive account information, dispute a charge, change payment or cancel the service.

What if the provider will not confirm authority?

Mark the action unverified—do not act, preserve the attempted official route and provider response, and assign the correct escalation or qualified review. Do not work around verification by impersonating another person or reusing their access.

Does an online portal prove that its user may bind the account?

No conclusion should come from access alone. Record what the current provider and governing sources permit. Portal access, a saved password or visibility of account data may be an access state rather than authority for every action.

Who should see the register?

Only the audience that needs its approved coordination fields. Create a narrower view where possible, and keep personal data, controlled documents, identity evidence, credentials, payment information and adviser material in their appropriate restricted systems.

Map Authority Without Inventing It

A useful provider authority register gives every service action a current source, a narrow scope, an internal approval, an official provider route, a review trigger and a named next owner. It makes uncertainty visible instead of letting convenience harden into assumed power. The maintenance schedule can help the group draft recurring review tasks, but every interval, assignee and action still needs approval against the real provider and authority sources.

Shared Holiday Homes can keep approved property information, supporting house documents and assigned tasks together for families, friends, siblings, trustees and small private co-owner groups. It does not become the provider, contracting party, legal adviser, trustee, credential manager or authority source. Start a free trial when your group wants one place for the coordination around its real-world providers.