Is your event Approved? Find out →

Submit a Comms request.

One form · Two paths · Event or Project

Step 1 of 6 · Path
Beta test phase only — projected release date — fall 2026 Beta test phase only — projected release date — fall 2026 Beta test phase only — projected release date — fall 2026
Step · 1 of 6

First — what are you submitting?

Pick one. Every other question on this form depends on this answer.

One request can include several items — a poster, a slide and a social post, for example — as long as they're all for the same event, project or campaign. You'll add them in a moment. Different campaign? Submit a separate request.

Quick test: Is there a date on the calendar this is for? If yes → Event. If the deliverable would still need to exist with no date attached → Project.

Step · 2 of 6

Who are you?

Your name, your email, the ministry you're submitting on behalf of — and the one person who'll review proofs and approve the work.

Don't see your ministry? Pick "Other" — the PM will route correctly.
Point of Contact for this request
Receives proofs, gives feedback, and approves final assets. One person only. Consolidated feedback through a single contact protects the timeline.
Step · 3 of 6 · Event Path

Tell us about the event.

Name, level, and the three dates that matter — Event Date, Launch Date, Due Date.

Levels are entered manually until the ministry-plan system locks (October 1, 2026). The Creative PM will verify during triage.
Three dates, in order: the Due Date is when Communications delivers finished assets to you for review. The Launch Date is when promo goes public (registration opens, signage up, emails go). The Event Date is when the event itself happens. Lead time is measured from Launch Date.
Comms delivers to you by
Promotion goes public
Event itself happens
When registration opens to the public — often the same as Launch Date, but not always.
Step · 3 of 6 · Project Path

Tell us about the project.

What you need made, what kind of deliverable it is, and when you need it.

What do you need made?

Add everything this project or campaign needs. Each item gets its own line for the team.

When do you need the deliverable in hand?
Step · 4 of 6 · Event Path

Assets & channels.

Select everything you need for this event — it all travels together as one request.

Select the assets and channels you need for this event. Items grayed out aren't included at your level. You're not required to select everything available — the Creative PM will scope the actual production based on what you choose.

Assets
Brand & Creative
Video & Platform
Email & Direct
Social & Digital
Print & In-Building
Communication Channels

Mon–Wed are ministry-specific outbound days. Thu–Fri are church-wide communication days. Sends to 500+ recipients require Comms approval.

Ministry email
Mon–Wed
Ministry text
Mon–Wed
Church-wide email
Thu–Fri
Church-wide text
Thu–Fri · gated 500+
Social media
Church or ministry pages
App push
Level 1–2 only
Website listing
idlewild.org
Digital signage
RiseVision · lobby
Print / handouts
Lobby · classrooms
More specific audiences = better engagement, less fatigue.
Step · 5 of 6

The ask, budget, and acknowledgments.

A short synopsis, your budget code, and four acknowledgments that confirm ministry-leader approval and alignment with the playbook.

A few clear paragraphs. Bullet points are fine.
Budget Codes
3-digit department code
5-digit expense code
Optional — only if your request involves printed pieces.
Required Acknowledgments

All four are required to submit. These mirror the agreements in the Idlewild Communications Playbook.

Step · 6 of 6

Review & submit.

Read it back, edit anything, then submit. Submission pushes directly into Monday.com.

✓

Thanks for testing this.

Your test request came through. This form will be fully up and running very soon — thanks for your patience while we finish connecting it.

Need to submit another request? Start over →

← Back to Playbook