Co.PropertyTeam wikiCo.Property20 October 2026
Press slash to search. Arrow keys select a result.
Internal knowledge
Browse the wiki

Company OS

Five operating areas

Checked

Managing, Selling, Planning, Delivering, and Learning are operational concepts for seeing the same company picture. They are not an invented staff chart.

Download page Markdown
Interactive mapSelect a node to read its explanation. Use Work on this beside the section to prepare a change.
The Company OS: five connected responsibilities diagramManaging guides Selling, Planning, and Delivering. Delivering produces observations for Learning, and Learning informs Managing. Every area uses records, tasks, and knowledge.Managing — The Company OS: five connected responsibilitiesManagingSelling — Property lifecycle: from enquiry to reviewSellingPlanning — Finance records: support the review before the conclusionPlanningDelivering — Turnover readiness: evidence before a ready decisionDeliveringLearning — SOP learning: turn observations into a better next stepLearning
The five responsibilities share a feedback loop rather than a reporting line.Solid · information flow
Read the diagram as text

Managing guides Selling, Planning, and Delivering. Delivering produces observations for Learning, and Learning informs Managing. Every area uses records, tasks, and knowledge.

  • Managing → The Company OS: five connected responsibilities
  • Selling → Property lifecycle: from enquiry to review
  • Planning → Finance records: support the review before the conclusion
  • Delivering → Turnover readiness: evidence before a ready decision
  • Learning → SOP learning: turn observations into a better next step
What it does

Make the responsibilities, records, tasks, and knowledge handovers understandable without needing to know internal implementation details.

Responsibility

Managing makes priorities, decisions, and review rhythm visible.

Next step

State which area owns the next decision, not just which screen displays it.

The areas are a shared map, not a staff chart

Checked

Managing holds objectives, key results, decisions, meetings, and company rhythm.

Read the details

Managing holds objectives, key results, decisions, meetings, and company rhythm. Selling covers owner relationships, leads, service catalogue work, and property intake. Planning handles finance, commitments, subscriptions, revenue planning, and projects.

Delivering covers reservations, turnover, cleaning, maintenance, charges, and settlements. Learning turns SOPs, incidents, reports, and company knowledge into a better next way of working. The names help a teammate ask the right question; they do not prove a particular person or team exists for each label.

Current
Checked — these are documented operating responsibilities, not asserted job titles or reporting lines.
Proposed next state
Assign a named owner in the relevant current task or decision record, then show the handover explicitly.
Expected outcome
Work can be routed by responsibility without inventing organisational facts.
Checks to include when changing this section
  • Check each area has a plain-language question and a linked diagram node.
  • Review the page for wording that could be mistaken for an employment or reporting claim.

Records, tasks, and knowledge answer different questions

Checked

A record describes something that exists or occurred, such as a property, owner relationship, reservation, or subscription.

Read the details

A record describes something that exists or occurred, such as a property, owner relationship, reservation, or subscription. Its identity and source matter. A task is an accountable next action with a responsible person, due time, and outcome another person can verify.

Knowledge is a reusable explanation: an SOP, incident lesson, report interpretation, or decision note. Keeping these separate prevents a record from being treated as an instruction, or an instruction from being treated as evidence that work happened.

Current
Checked — the distinctions match the operating model in the handoff.
Proposed next state
Add links between these objects at the handover: source record → task → accepted outcome → learning.
Expected outcome
A team member can tell whether they need to inspect a fact, perform an action, or follow a procedure.
Checks to include when changing this section
  • Check the example distinguishes a reservation record from a turnover task and SOP.
  • Check the context export includes only this section’s prose when this section is selected.

A handover is useful when it preserves both context and accountability

Checked

A handover should identify the source record, what is known, the next decision or action, who owns it, when it matters, and what evidence closes it.

Read the details

A handover should identify the source record, what is known, the next decision or action, who owns it, when it matters, and what evidence closes it. “Please look at this” is not enough because it loses the decision boundary.

For example, Selling can hand a qualified owner enquiry to Planning with property identity and agreed next step. Planning can make a commitment visible to Delivering. Learning can turn a repeated exception into a reviewed SOP improvement.

Current
Checked — this is a practical interpretation of the documented areas and shared records.
Proposed next state
Use a clear exception owner when a handover cannot be completed with the available evidence.
Expected outcome
The next person receives a specific, supported action instead of a vague transfer of responsibility.
Checks to include when changing this section
  • Check handover examples name a source, action, and expected evidence.
  • Check related links lead to lifecycle and learning pages rather than an unscoped technical guide.

Apply with care

A concrete safe example

Example, responsibilities & checklist

From record to next action

A reservation is a record: it says something about a stay. “Confirm the cleaning evidence before the next arrival” is a task: it has a responsible person, due time, and verifiable outcome. The approved turnover procedure is knowledge: it explains how to do that task.

Responsibilities

  • Managing makes priorities, decisions, and review rhythm visible.
  • Selling understands owner needs and property fit.
  • Planning prepares commitments, finance, subscriptions, and projects.
  • Delivering runs stays, turnover, maintenance, charges, and settlements.
  • Learning maintains SOPs, incident understanding, reports, and shared knowledge.

Checklist

  1. State which area owns the next decision, not just which screen displays it.
  2. Give every task a responsible person, due point, and verifiable outcome.
  3. Preserve a record’s identity and source rather than relying on a familiar display name.
  4. Link a learning item back to the incident, report, or repeated exception that prompted it.
Expected outcome

A reader can classify work by responsibility, identify the information it needs, and make a clear handover.

Traceability without sensitive material

Source pointers and exports

This page expands the approved handoff into plain-language guidance. It does not include runtime logs, credentials, databases, private evidence, internal QA artifacts, or developer planning history.

Documentation references
  • Handoff / pages/organisation.html
  • Handoff / START-HERE.html
Page MarkdownPage context JSON