Log project deadlines as all-day events
A new project brief writes its deadline onto the production calendar as an all-day event the whole team can see.
New submission on your project intake or order form
Create an all-day event on the due date with the project name and brief in the details
One-directional. A submission triggers the action — nothing is written back into your form.
The bad week is the one where two deliverables landed on the same Friday and nobody noticed until Thursday night. The intake form already asks for a deadline, so this flow writes it onto the production calendar as an all-day event the moment the brief arrives.
Studios and small production teams treat the result as a shared wall planner. Nothing is entered twice, and the month view shows what is already due before anyone agrees to take the next job on.
Setting it up
- 1
Publish the project scope form with Project Deadline required — a brief with no date has nowhere to land on the calendar.
- 2
Create a Zap on New Submission for that form and add Google Calendar's Create Detailed Event action.
- 3
Choose the production calendar the whole studio subscribes to, so a new deadline is visible without anyone forwarding an email.
- 4
Format Project Deadline as a plain date in a Formatter step, then map it to both start and end and tick the all-day option — a value carrying a time will shift the block by a day.
- 5
Write the summary as Company plus Project Name, so the month view reads as a client list rather than a list of job titles.
- 6
Put Project Objectives and Expected Deliverables into the description, so the team sees what is actually due rather than a bare title.
- 7
Map Email Address to attendees only if you want the client to see the date too, and keep budget and internal notes out of the description if you do.
- 8
Submit a test brief with a deadline three weeks out, confirm the block sits on the right day, then turn the Zap on.
What maps where
Using the Project Scope Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Google Calendar |
|---|---|
| Project Deadline | The date of the all-day event on the production calendar |
| Project Name | Second half of the event summary |
| Company | First half of the summary, so deadlines group by client |
| Expected Deliverables | Event description, listing what is actually due that day |
| Project Objectives | Event description, under the deliverables, for context on the brief |
| Email Address | Guest on the event when you want the client to hold the date as well |
Variations worth knowing
Chain a second Create Detailed Event action built from Desired Project Start Date. The calendar then shows both ends of the job, and a brief that starts next week but lands in November stops looking like a quiet month.
Add a Formatter date step that subtracts seven days from Project Deadline, and create a second all-day event on that date titled as a checkpoint. Production gets a nudge with time to react rather than a reminder on the morning itself.
If something isn't arriving
All-day events want a date with no time attached. Run Project Deadline through a Formatter set to YYYY-MM-DD, and set the Zap's timezone to the studio's, so a midnight value is not pushed across the date line.
Every submission creates a new event, and nothing from the calendar flows back. Add a Find Event step that searches for Project Name, then use Update Event where there is a match so the revision moves the existing block instead of adding one.
Frequently asked questions
Can the client see the deadline calendar?
Two ways: invite them with Email Address so they hold the single date, or share the production calendar read-only if they should see the whole schedule. Both are Google Calendar settings; the form has no part in it.
Does the whole brief end up on the calendar?
Only the fields you map. Budget, constraints and success criteria stay in formformform responses, where the team can filter, search and export them, and the event carries just enough to say what is due.
Can I get a reminder before the deadline itself?
Set default notifications on the production calendar, so every event created there alerts the team on your schedule. For a longer runway, build the checkpoint event a week earlier with a Formatter date step.
Related automations
- Add service appointments to the dispatch calendar
A booking arrives and lands on the dispatch calendar with the address as a map pin and the job in the title.
- Block time for the calls customers ask for
Someone asks for a call, and a block appears on the rep's calendar with the customer invited and their question attached.
- Book consultations at the slot the client picked
A prospect picks a date and a time on your request form, and the consultation lands on your calendar with them invited.
- Put candidate interviews on the hiring team's calendar
A shortlisted candidate chooses an interview window and the event appears on the hiring calendar, Meet link included.
- Turn event registrations into calendar invitations
Someone registers for your workshop and Google Calendar sends them the invitation, with their details in the event.
- Book a new patient's first visit from their intake form
A finished intake form books the patient's first visit in Acuity Scheduling and carries their contact details into the appointment.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free