What a charter settles
A charter exists to answer authority questions before they turn into escalations. Most RevOps functions fail on ambiguity rather than capability. The team is asked to own the forecast process but cannot require reps to update close dates. It is asked to fix data quality but has no power to reject a field request. It is asked to align sales and marketing but has no standing to decide when the two disagree. A charter converts each of those from an argument into a written rule.Write it in the first ninety days of the function existing. Writing it later means renegotiating positions people have already staked out.
The four sections worth writing
Scope owned. List the specific processes and systems RevOps controls, such as CRM configuration, pipeline stage definitions, the forecast cadence, territory and quota administration, and the reporting layer. Be concrete enough that a reader can tell whether a given request falls inside it.
Scope not owned. This section prevents more conflict than the first one. State plainly that RevOps does not set the number, does not manage reps, does not own campaign creative, and does not decide pricing. A team without a stated boundary becomes the place work goes when no one else wants it.
Intake. Describe how a request reaches the team, what information it must carry, how it gets prioritized, and what the response time commitment is. Requests arriving through hallway conversations and direct messages are the main reason RevOps backlogs become unmanageable.
Decision rights. Name who decides, by category. Definition changes, system changes, and process exceptions each need a stated owner and a stated escalation path.
Decision rights are the hard part
The other three sections are descriptive. This one transfers authority, so it requires real executive agreement.
Make the categories concrete. Who decides what qualifies as a sales accepted lead. Who can approve an exception to the discount process. Who can change a pipeline stage definition mid-year, given that doing so breaks historical comparability. Who arbitrates when sales wants a deal counted in this quarter and the close-date rules say otherwise.
That last one has teeth. ORM finds that a rep changing the close date is the strongest available signal of deal slippage, which only holds as a signal if the rules around close dates are enforced consistently. A charter is what makes enforcement possible without a fight each time.
Review it on a schedule
Set an annual review, plus a trigger review whenever the go to market motion changes. Adding a second product, moving upmarket, or bringing on a partner channel all change what RevOps has to own. A charter written for a single-motion business will quietly stop matching reality, and the sales forecasting process is usually the first place that mismatch shows up.
Frequently Asked Questions
What goes in a RevOps charter?
Four things: the scope RevOps owns, the scope it explicitly does not own, the intake process for requests, and the decision rights that settle conflicts between functions. Everything else, including tooling plans and roadmaps, belongs in other documents that the charter points to.
How long should a charter be?
One to two pages. A charter that runs longer stops being read, and an unread charter settles no arguments. Detail belongs in the process documents the charter references.
Who approves the charter?
The executive RevOps reports to, plus every function leader whose work the charter constrains. Approval from the reporting manager alone is insufficient, because the charter only works if the leaders bound by it have agreed to it in advance of a dispute.
How is a charter different from a RevOps roadmap?
The charter defines authority and lasts for a year or more. The roadmap defines sequenced work and changes every quarter. Companies that write a roadmap without a charter end up with a list of projects nobody has authorized the team to run.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like revops charter into prescriptive action for your team.
Schedule a Demo