Scheduled Automation: your operating rhythm runs itself

Two weeks ago we shipped Project Automation, and every new project started setting itself up. We also said scheduling was next. It's here. Running a project well is not only the setup on day one. It is the rhythm. Every day, week, and month there is a set of things a good Project Manager does without fail: chase RFIs and variations, review the action list, send the Friday client update, submit the monthly progress claim. Miss them and things quietly slip. Until now, that rhythm lived in people's heads and calendars. It depended on remembering, and it varied from project to project and person to person. Automated Actions could already build a project's action items the moment the project was created, but they only fired on an event. There was no way to say "do this every Friday" or "do this on the 25th of every month". Now there is. Run on a daily, weekly, or monthly schedule Set an automation to run every day, on the weekdays you choose (every Friday, say), or on chosen dates each month (the 25th, for the progress claim), with sensible handling of month-end dates like the 31st. A schedule is now a trigger in its own right, alongside "when a project is created". Every active project, covered automatically A scheduled automation runs itself across every active project in your workspace. You do not run it project by project, and new projects are picked up automatically. Set the cadence once and it holds across the whole business. Assigned to the right role, with due dates that make sense Point an action at a role (Project Manager, Contracts Manager) and Horizon assigns it to whoever holds that role on each project at the moment it runs. Due dates move with the schedule, so recurring work can land as "due today" or "due in three days" and always carries a sensible deadline. For must-do items, an automation can flag when the responsible role is not assigned on a project, instead of quietly creating an unassigned action. Nothing important goes unowned. A ready-made PM Operating Rhythm Setting up a schedule seeds an editable example built from a real Project Manager operating rhythm: the daily, weekly, and monthly actions a PM should never miss, from maintaining the construction program to submitting the monthly claim. Keep it, trim it, or reshape it into your own standard. Dependable by design Scheduling is built to be trusted with your cadence. The same day's actions are never created twice, even if the system retries. If a single step or a single project cannot complete, the rest still run, and the run history shows exactly what needed attention. Nothing fails silently. Everything you know still applies This is the same Automated Actions you may already use, managed from the same Admin, then Automation page. Same bundles, same assign-by-role, same checklists, same run history, and the same export and import, so you can build a cadence once and reuse it across workspaces. How to try it Head to Admin, then Automation, then New trigger, and choose Daily, Weekly, or Monthly. Horizon seeds the editable PM Operating Rhythm example. Adjust the actions, roles, checklists, and due dates to match how your team works, then switch it on. From the next run, the actions appear on your active projects automatically, assigned to the right people. Where this goes next A Contract Administrator operating rhythm is next, with Site Manager and other roles to follow, so each role's cadence can run itself. Per-workspace time zones and richer scheduling options are on the way, along with more automated step types beyond action items. Tell us which recurring actions cost your team the most time. That is what we build next.