Property managers, facilities teams and safety leads all have checks that come round every month. Here each property is one saved entry. Every month GravityOps Recurring Form Submissions submits it again, and the new entry starts a Gravity Flow User Input step assigned to the inspector, who gets an email link to record what they found.
The form
- Property (Single Line Text)
- Inspector email (Email)
- Inspection month (Date)
- Findings (Paragraph Text) and Result (Radio Buttons: Pass, Needs repair), left empty in the parent entry
The Gravity Flow step
- Step type: User Input.
- Assign to the Inspector email field, so each property can have its own inspector without a WordPress account.
- Editable fields: Findings and Result.
- Turn on the assignee email and put
{workflow_entry_link: token=true}in the message. The token lets the inspector open the step from the email.
The Recurring feed
- Repeat every 1, Calendar unit months, Run time Specified local time 09:00.
- Update Date Field(s): Inspection month.
Each run is a full submission, so Gravity Flow starts the workflow on the new entry the same way it does for a form someone fills in. The parent entry stays as the template; this month’s findings live on this month’s entry, and last month’s stay where they were.
Gravity Flow sends the link to its inbox page, so set that page in Gravity Flow’s settings to keep inspectors on your site’s front end. If an inspection is missed, the step simply waits; Gravity Flow’s own reminders and expiration settings handle follow-up.
More examples: recurring work in Gravity Forms. Plugin used: Recurring Form Submissions, with Gravity Flow.