diff --git a/events/README.md b/events/README.md
index 89d39d1c..5976d624 100644
--- a/events/README.md
+++ b/events/README.md
@@ -13,5 +13,6 @@ What meetings, and regular events do we have.
 | [Lunch & Learn](/events/lunch-and-learn.md#readme) | A meetup where we talk about things that inspire us. |
 | [Open Standup](/events/open-standup.md#readme) | How do we do whole-team standup at Artsy? |
 | [Show & Tell](/events/show-and-tell.md#readme) | Internal presentations with no preparation |
+| [Writing Office Hours](/events/writing-office-hours.md#readme) | Weekly meeting for support sharing knowledge |
 <!-- end_toc -->
 <!-- prettier-ignore-end -->
diff --git a/events/writing-office-hours.md b/events/writing-office-hours.md
new file mode 100644
index 00000000..3c758f5c
--- /dev/null
+++ b/events/writing-office-hours.md
@@ -0,0 +1,21 @@
+---
+title: Writing Office Hours
+description: Weekly meeting for support sharing knowledge
+---
+
+Writing office hours are a weekly drop-in meeting run by [Ash][] every Monday at 2pm (NYC time) in the café area on
+the 24th floor, or over Slack. The purpose of Writing Office Hours was originally to help Artsy staff with
+_writing_, specifically blog posts. Today, the office hours are for help with sharing knowledge _generally_ and not
+just through writing.
+
+Here are some examples of good uses of Writing Office Hours:
+
+- You'd like to write a blog post but don't know where to start.
+- There is a conference you're thinking of submitting to and want some feedback on your application.
+- There's an important email you have to write.
+- You're presenting a [Lunch & Learn][lnl] to the team and want to go through a dry run first.
+- You will be a guest on a podcast and want to organize some thoughts first.
+- You have _most_ of a blog post written out, but want help getting it over the finish line.
+
+[ash]: https://github.com/ashfurrow
+[lnl]: ./lunch-and-learn.md