Project Automation: new projects that set themselves up

Every new project used to start with the same half-day of admin. Someone recreates the standard action items, assigns each one to the right person by name, and re-adds the same checklists they added on the last job. It is repetitive, it burns the first day, and it is easy to miss a step or assign the wrong person, so no two projects start quite the same way. Horizon now does that setup for you, the moment a project is created. Setup that runs itself You define once what should happen when a project is created. From then on, every new project in your workspace gets its action items built automatically, before anyone touches day one. Work that used to live in someone's head, or in a checklist nobody could find, becomes something the platform guarantees. Assign by role, not by name Point an action at a project role (Contracts Manager, Project Manager, Site Manager) and Horizon assigns it to whoever holds that role on the new project. People change, secondments happen, someone goes on leave. The automation follows the role, not the name, so there is no template to update every time the org chart moves. Checklists from the first minute Each automated action can carry its own checklist template, so your standard steps (review the head contract, flag key dates) are there from the start rather than added later, or not at all. You stay in control A new Automation page (Admin then Automation) lets a workspace admin view, create and edit these automations. No developer, no support ticket. Creating the project-created automation even seeds an editable example bundle, so you are tuning a working setup rather than staring at a blank page. Run any automation on demand You do not have to wait for a new project. Hit Run on any automation and Horizon asks which project to run it against, then creates the actions right away. Use it to apply a standard setup to a project that already exists, or to test a bundle before you switch it on for real. A full run history Every run is recorded: what ran, on which project, and whether each step succeeded. You and our support team can always see exactly what happened, instead of guessing. Resilient when something is missing If one step cannot complete, say a role is not assigned yet on that project, the rest still run, and the history flags precisely which step needs attention. Nothing fails silently. Export and import across workspaces Build a set of automations you are happy with, then export them to a file and import them into another workspace. Because automations assign by role rather than by specific person, they carry across cleanly, so you can share one setup across the business instead of rebuilding it each time. View the step-by-step guide: export and import project automation triggers Where this goes next This is the first trigger of many. We are building toward more triggers beyond project creation (a tender awarded, a milestone reached), more step types beyond action items (RFIs, notifications, document setup), and scheduling, so automations can run on a calendar, not just on an event. Tell us which repetitive setup steps cost your team the most time. That is what we build next.