Every job goes through the same sequence — brief, draft, internal review, client review, sign off, invoice — and somebody types it out again on every new item. There are two native ways to stop doing that, and one reason they both eventually stop working.
The native answers
Both real, both free, both fine for a while.
Duplication is the one most teams land on. Keep one item set up perfectly and duplicate it for each new job — subitems come with it, and so do their column values.
A board template works when a new job means a new board rather than a new row. Set one board up, save it as a template, and every future board starts complete.
Where they run out
And then nobody knows which one is current.
Duplication works while there is one kind of job. The moment there are three — a small job, a full project, a retainer — there are three master items sitting in a group called Templates (do not delete), and one of them is six months out of date.
Then somebody duplicates the wrong one, or duplicates the right one and forgets to clear the dates from the last job, and the whole thing quietly stops being a system.
The thing that catches everyone
With its own columns, and its own column ids.
The subitems under your items are rows on a hidden board that monday creates the first time anybody adds a subitem. It has its own columns — often just Owner, Status and Date — and they are unrelated to the parent board’s columns even when the names match.
This is why an automation written against the parent’s Status does nothing to a subitem, why a formula referring to one cannot see the other, and why any tool that fills in subitem values has to know which board it is really writing to. It is also why a brand-new board has no subitem columns at all until somebody adds one by hand, once.
What a good template does
Five empty rows called “Draft” save almost nothing.
The typing is not the work. The work is deciding who owns each step, what status it starts in, and when it is due. A template that produces five nameless rows has saved you thirty seconds and left you the twenty minutes.
And the dates have to be counted rather than written. “Internal review three days after we start” is what a process means; “internal review on the fourth of March” is right once. Counting backwards matters as much — client review five days before delivery is exactly as ordinary a thing to mean, and a template that can only count forwards from today gets it wrong.
If you want one built that way
A named set of steps, with the work already assigned.
Blueprints belong to a board and can be offered to others deliberately. Each step can set every column your subitems have — not a fixed three — and its date is counted from the day you apply it, or forwards and backwards from the item’s own start and due dates.
Before anything is created you see exactly what will be: every row, with its owner, status and worked-out date. A structure created by surprise has to be deleted one row at a time.
Try it — build one, then apply itQuestions people ask
Yes, in two ways. Duplicating an item copies its subitems, and an automation can create a subitem when something happens. Neither gives you a named, reusable set you can pick from a list.
Because subitems live on a hidden board of their own with its own columns. The parent’s Status and the subitems’ Status are two different columns with different ids, which is why an automation written against one does nothing to the other.
Yes, including their column values — which makes “keep one perfect item and duplicate it” a genuinely workable answer for a small team. It stops working when there are several kinds of job, because now there are several perfect items and nobody knows which is current.
Relative, always. A template with a fixed date is right the first time and wrong every time after, and correcting five rows by hand is exactly the twenty minutes the template was meant to save.
Keep reading
One board, one status column, and one automation per transition.
Why a status column cannot represent “two of the three have agreed”, the native workaround and what it costs, and when to stop working around it.
What guests actually cost, when a shareable board is the right answer, and how to get a signature from somebody who will never have a login.
Every step with its owner, status and date already filled in. No account, nothing to install.
Not on monday.com? Send an approval from here — no account, no install.