Document the inbound-logging runbook
Writes the standing instruction for how inbound sources get captured going forward — which field to fill, how to tag each channel, what to do with ambiguous enquiries — so logging stays consistent across whoever handles intake.
In / outAttribution conventions document → inbound-logging runbook (field-by-field instructions, tagging rules, ambiguous-case handling)
You might say…
“The conventions exist but they're only in my head and the moment someone else handles intake the data goes off the rails — this writes the runbook so the system survives someone else doing the logging.”
What it does
Writes the short standing instruction for how inbound sources get captured going forward — which field to fill, how to tag each channel, and what to do with ambiguous enquiries — so logging stays consistent across whoever handles intake. Used after conventions are designed, to make them durable. Single human-in-loop drafting judgement.
Trigger: Use after conventions are designed, to make them durable and transferable to anyone handling intake.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation