Skip to content

Commit

Permalink
DRI for offsites (#21479)
Browse files Browse the repository at this point in the history
  • Loading branch information
Sampfluger88 authored Aug 21, 2024
1 parent e972d38 commit 4dd524d
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions handbook/company/communications.md
Original file line number Diff line number Diff line change
Expand Up @@ -718,10 +718,10 @@ Before spending any money on an offsite, inviting people, booking travel, or oth
- a lean budget (including links and street address of lodging and event spaces, estimated airfare, and spending for other food or accomodations)
- a detailed agenda of how time will be spent
- **Bring to e-group:** Ask your manager to bring your plan for the offsite to the next weekly e-group meeting for feedback, edits, and CEO approval.
- **Iteration:** The E-group will discuss live, make edits, and may ask you to provide additional information or changes and return the following week for another pass.
- **Iteration:** The E-group will discuss live, make edits, and establish a DRI for the offsite.

After the plan for the offsite is approved at the e-group meeting (including participants, detailed agenda, and final budget):
- The Head of Business Operations will confirm dates with all approved participants, then book all [lodging](#lodging) and coordinate any additional event space. (Participants [book their own flights](https://fleetdm.com/handbook/company/communications#flights).)
After the plan for the offsite is approved at the e-group meeting (including recommended participants, goals, and budget):
- The DRI will confirm dates with all approved participants, then book all [lodging](#lodging) and coordinate any additional event space. (Participants [book their own flights](https://fleetdm.com/handbook/company/communications#flights).)
- _**Note:** If the plan needs to change again, after it is approved, [ask Apprentice to the CEO for help](https://fleetdm.com/handbook/digital-experience#contact-us)._


Expand Down

0 comments on commit 4dd524d

Please sign in to comment.