Projects & Engagements

Provisionr uses a structured model for external engagements — whether we’re serving customers, working with vendors, or partnering with other organizations. Each engagement type has its own naming pattern, group structure, and lifecycle.

The Engagement Models

Model	Who	Pattern	Purpose
Customer	Organizations we serve	Umbrella + Project Triplet	Full engagement lifecycle
Vendor	Organizations that serve us	Vendor group	Vendor management
Partner	Organizations we collaborate with	Partner group (+ optional function)	Alliance/channel work

Customer Model: Umbrella + Triplet

Every customer engagement has two layers:

Umbrella Groups

Umbrella groups are customer-wide — they persist across all projects for that customer.

prv-{owner}-cus-{cusslug}-{facet}@{domain}

Facet	Purpose	On ACLs?
`prosrv`	Delivery leadership & program ops	Optional COLLAB Viewer
`sales`	Account/AM communications	Never
`mktg`	PR/case-study sync	Never
`cpoc`	Customer points of contact	Optional COLLAB Viewer
`announce`	Managers-post broadcast	Never
`all`	Large-program discussion (optional)	Never
`archive`	Records managers for archive phases	Archive only

Project Triplet

Each project within a customer gets three groups:

prv-{owner}-prj-{cusslug}-{prjslug}-{role}@{domain}

Group	Role	Access
`...-dri`	Decision owners	Editors across channels
`...-delivery`	Working team	Editors on TEAM; Commenter in COLLAB
`...-client`	Customer team	Commenter/Editor in COLLAB only

The Three-Drive Model

Every customer gets three shared drives, each at a different sensitivity level:

Drive	Color	Audience	Content
COLLAB (Green)	External-safe	Customer-visible	Agendas, minutes, status, final PDFs
TEAM (Pink)	Internal working	Our team only	Drafts, AI notes, internal minutes
STRICT (Red)	Internal restricted	Need-to-know	Raw recordings, transcripts, evidence

Drive Naming

EXT_{ORG}_Customers-{CusPascal}_COLLAB_Active_{Sensitivity}
INT_{ORG}_Customers-{CusPascal}_TEAM_Active_{Sensitivity}
INT_{ORG}_Customers-{CusPascal}_STRICT_Active_{Sensitivity}

Customer Tokens

Customer identifiers are frozen at registration — they never change.

Token	Purpose	Example
`{cusslug}`	Short canonical key (3-6 chars)	`slope`
`{cusnameslug}`	Readable kebab	`slope-clinical`
`{prjslug}`	Project identifier (3-12 chars)	`mod`, `assess-q1`

Folder Structure

Every project folder uses phase-ordered subfolders:

00_preengagement/  01_kickoff/     02_discovery/   03_delivery/
04_validation/     05_training/    06_handover/    07_closeout/
99_archive/

Each phase contains standardized subfolders (00_inbox/, 01_admin/, 02_agendas/, etc.).

File Naming

Inside drives, files follow this pattern:

{topic}[_{entity}]_{yyyy-mm-dd}_{status}_{v###}.{ext}

Where status is draft, review, or final. Example:

risk_register_slope_2026-02-14_review_v003.md

Pages in This Section

Customers — Full customer engagement model with lifecycle
Vendors & Partners — Vendor and partner engagement patterns