Coordination Zero OSby Audra Carpenter
Home/Guides/Core Objects Worksheet
Worksheet

Core Objects Worksheet

One page that turns the Core Objects Guide into decisions. Eight objects, one home each, minimum fields, and a retirement list for every duplicate.

Version 1.0 Updated Jul 2026 Pace one working week Pairs with the Core Objects Guide and Tool Sprawl Audit

How to use this

Fillable version
Use the Core Objects Worksheet in Google Sheets.

Make your own copy, then work through the tabs as you make each home, field, connection, and retirement decision.

Make a copy

Work with your completed Tool Sprawl Audit open beside you. The audit told you where things live. This worksheet is where you decide where they should live.

Fill it in the order it appears. Part 1 forces the naming and home decisions. Part 2 defines what each record minimally contains and connects to. Part 3 lists what gets retired. Do not skip to Part 3 because it feels productive. The retirement list only makes sense after the homes are chosen.

The suggested fields and connections are starting points, not requirements. Edit them to match your business. Cutting a suggestion is fine. Adding more than two or three per object usually means you are designing a perfect schema instead of a minimum one. Resist.

Part 1: Name and home

One row per object. Your name for it is whatever you actually call it out loud. The official home is one tool, not two.

ObjectYour name for itWhere it lives todayOfficial home going forward
IdeaWrite hereWrite hereWrite here
ContentWrite hereWrite hereWrite here
CampaignWrite hereWrite hereWrite here
OfferWrite hereWrite hereWrite here
LeadWrite hereWrite hereWrite here
ClientWrite hereWrite hereWrite here
TaskWrite hereWrite hereWrite here
AssetWrite hereWrite hereWrite here

Where the two right-hand columns differ, that row is a migration. Mark it. Every marked row shows up again in Part 3.

Start with your hero object from the audit, the row that had marks everywhere. Its home decision is the hardest and the most valuable, and making it first makes every other row feel easy.

Part 2: Fields and connections

For each object, confirm or edit the minimum fields, then list what it must link to. Cross out what you do not need. Add sparingly.

Object 01

Idea

Fields: the idea itself · source · status

Connects to: the content or offer it becomes

Object 02

Content

Fields: title · format · channel · status · publish date

Connects to: originating idea · campaign · offer it sells · assets it uses

Object 03

Campaign

Fields: goal · date range · status

Connects to: content inside it · offer it promotes · leads it generates

Object 04

Offer

Fields: name · price · what is included · who it is for

Connects to: campaigns that promote it · content that sells it · clients who bought it

Object 05

Lead

Fields: name · contact · source · stage · next action

Connects to: campaign that produced them · offer they are considering · client record they become

Object 06

Client

Fields: contact · active offers · status · key dates

Connects to: origin lead · purchases · active work · content made for them

Object 07

Task

Fields: what · who · when · status

Connects to: the object the work is for

Object 08

Asset

Fields: what it is · file location · usage notes

Connects to: content and offers that use it

Part 3: The retirement list

Every place an object lives outside its official home goes on this list with a verdict.

  • Sync means the tool keeps displaying the object, but edits only happen at the home.
  • Freeze means it stays as a read-only archive and nothing new goes in.
  • Delete means it goes away.
ObjectDuplicate locationVerdictDone
Write hereWrite hereSync, freeze, or delete
Write hereWrite hereSync, freeze, or delete
Write hereWrite hereSync, freeze, or delete
Write hereWrite hereSync, freeze, or delete
Write hereWrite hereSync, freeze, or delete
Write hereWrite hereSync, freeze, or delete

Pull these straight from your audit’s duplication grid. Every mark that is not the official home earns a row here. If a row sits without a verdict for more than a day, the honest verdict is usually freeze. Deciding to decide later is how shadow databases are born.

A worked example

Here is what a finished Part 1 looks like for a solo brand strategist who sells a course and one-to-one consulting. Her stack: HubSpot, Kit, Notion, Google Drive, Google Sheets, and Asana. Yours will differ. The shape should not.

ObjectHer name for itWhere it livedOfficial home going forward
IdeaSparksApple Notes, Notion, voice memosNotion
ContentPostsNotion, Google Drive, KitNotion
CampaignLaunchesKit, Google SheetsNotion
OfferOffersProposals in Drive, her memoryNotion
LeadProspectsHubSpot, Kit, a Sheets exportHubSpot
ClientClientsHubSpot, Drive foldersHubSpot
TaskTo-dosAsana, sticky notesAsana
AssetLibraryDrive, her desktopGoogle Drive

Notice the pattern. She did not buy anything new. Notion became the home for the objects she creates, HubSpot for the objects that are people, Asana for work, and Drive for files. Four homes, eight objects, zero new subscriptions.

And here is a slice of her Part 3, pulled straight from that middle column.

ObjectDuplicate locationVerdictDone
LeadKitSync — Kit displays prospects; edits happen in HubSpot
LeadSheets export from that eventFreeze — imported once, then read-only
ContentGoogle DriveSync — files live in Drive; the record lives in Notion
OfferHer memoryDelete — replaced by a written record
IdeaApple NotesFreeze — new sparks go to Notion; old notes stay put

The offer row is the one to sit with. Her offers were never written down anywhere, which means her memory was the source of truth and every proposal was a fresh reconstruction. Writing the record did not just retire a duplicate. It retired a job.

Completion check

You are done when all four are true.

  • Every object in Part 1 has exactly one official home written down. Not a favorite and a backup. One.
  • Every object in Part 2 has a field list you actually trimmed. If all eight still show every suggestion untouched, you copied instead of decided.
  • Every duplicate from your audit appears in Part 3 with a verdict, and the verdicts are underway.
  • You can answer “where does a lead live?” in one word without checking.

When all four hold, your object model exists. Take it into your first module and build against it.