How to Structure monday.com Agency Tasks and Subitems

Quick answer: Structure agency work so each deliverable has a clear owner, a definition of done, a due date, and the next approval or dependency. Use subitems for separable pieces of work, not every micro-action. Then choose follow-up questions that point to the right item and record reported progress without automatically granting creative or client approval.

A creative agency can finish the design and still miss the launch. The copy might be awaiting legal review, the product team may not have approved pricing, and the person marked as the campaign “owner” may not control any of those decisions. When a monday.com board uses one item for an entire campaign, a status of “in progress” conceals the precise handoff that needs attention.

Automate your Project Follow-ups!

Project dashboard with workflow gears and AI icons representing monday.com agency tasks and subitems

Start with deliverables, not departments

Agencies often organise boards by design, copy, paid media or accounts. Those functions matter for workload planning, but clients experience outcomes: a landing page, a launch email, an approved creative suite or a campaign report. A project board becomes more reliable when the parent item represents the visible deliverable and subitems represent the steps that must happen to release it.

For example, a “Spring Product Launch” parent item could have subitems for approved brief, copy draft, design execution, client review, compliance review, final export and channel scheduling. The account manager remains responsible for coordination, while each specialist owns the step they can actually complete. This makes status requests specific instead of asking one person whether an entire campaign is ready.

monday.com’s guide to subitems describes their ability to provide an additional layer of detail and maintain separate columns. A board’s exact hierarchy should reflect the team’s workflows, and an AI integration’s ability to update subitem columns must be tested rather than assumed.

Choose the right level for a parent item

A parent should be something a stakeholder can recognise as a deliverable or milestone: “Paid social creative set approved”, “October newsletter scheduled”, or “Webinar registration page ready for QA”. Avoid giant parents named only “Marketing” or “Client X”; they offer no reliable point of completion.

Conversely, do not make every colour correction and five-minute tweak a subitem. Too much granularity makes the board difficult to maintain and creates a long list of unnecessary follow-up calls. Add a subitem when it has its own owner, deadline, evidence, dependency or approval. Where none of those differ, use a checklist within the task instead.

Asana’s creative production research also illustrates the value of central briefs and clear review responsibilities. The principle applies regardless of platform: creative work needs a defined request, assigned decision-makers and a discoverable record of feedback.

Build a usable status and approval structure

An agency board usually needs more than “Not Started”, “Working” and “Done”. Consider separate concepts: production status, review status and launch readiness. A designer may have completed a file while client approval is still pending. A copywriter may be finished while mandatory compliance feedback remains unresolved.

For the production stage, possible proposed values are Brief Needed, Ready to Start, In Production, Ready for Review, Revisions Requested and Work Delivered. For the approval stage, possible values are Awaiting Client Decision, Approved, Changes Required and Not Applicable. Use separate evidence and date fields when the approval has contractual importance. These are suggested board values, not a claim about a default Autoza configuration.

The team’s “definition of done” should specify the file location, asset version, naming convention, required sizes, proofing comments and approver. “Design done” without a shared export folder often means another round of searching and rework. To see how approvals fit into a board, read how to follow up on creative approvals in monday.com.

Map ownership before you automate any follow-up

Consider a social campaign with a design lead, a freelance motion editor, an account manager and a client approver. Ask the design lead about export readiness, the editor about render blockers, the account manager about consolidated feedback, and the approver about the decision deadline. Do not direct the same generic “What is the status?” call to all four.

Create one responsible person per subitem whenever possible; record who can supply a status and who is authorised to approve. A freelancer can confirm that files were uploaded, but should not be asked to decide that a client has accepted them. Where the same person performs and approves an action, make that responsibility explicit and apply the client’s review policy. If freelancers tend to go quiet, see when freelancers miss project reminders.

With Autoza AI for monday.com, the published product functionality includes configured check-in questions, scheduled calls, status/notes/timestamp updates and call summaries. A planning exercise should map each question to an allowed recorded outcome and verify that all relevant item and subitem mappings work in the live installation. Never assume voice transcription alone can safely interpret ambiguous approval language.

Use three different follow-up scripts

Production-owner check-in

Ask: “Which version is ready? What still needs work? What is the current blocker? When can the review-ready file be shared?” This is appropriate for copywriters, designers and developers. Record a promised delivery time separately from a verified upload.

Account-manager check-in

Ask: “Has feedback been consolidated? Which decision is awaiting the client? What is the earliest realistic launch date if approval arrives today?” Record the dependency owner, not merely the account manager’s optimistic prediction.

Client approver follow-up

Approval communication needs special care. An authorised account lead may schedule a call that asks whether the approver has had an opportunity to review the current version and when a formal decision is expected. Do not turn conversational praise such as “looks great” into formal acceptance. Route formal approval through the agreed written channel or signed mechanism.

Example: a landing-page launch board

A hypothetical launch could contain a parent item “Product landing page live”. Its child actions would include copy approved, design approved, development complete, analytics QA passed, consent review completed and deployment authorised. If the developer reports “page is built but analytics still fails”, the status update should identify the unfinished QA dependency rather than mark the entire parent as ready.

A good follow-up captures “analytics owner will retest Thursday by 11 a.m.” and then alerts the project lead if that dependency remains open. The agency still decides whether a launch can proceed. The AI is a status collection layer, not an approval engine.

Avoid three common board mistakes

First, keep duplicative status fields under control: if the parent and all subitems contain incompatible status definitions, nobody knows which one governs. Second, avoid assigning a parent to a person who cannot answer about the subitems. Third, do not automatically advance a client-facing milestone when one contributor claims completion without a review trail.

Review the board with a project manager at the end of each sprint. Merge unnecessary subitems, add missing owner fields, and rewrite check-in prompts that consistently yield vague answers. Measure time spent chasing updates, revision cycles and unanswered dependencies, not the number of board rows created. Once the structure is stable, decide how often to call using our guide to choosing an agency follow-up cadence.

Automate your Project Follow-ups!

Frequently asked questions

When should an agency use subitems instead of separate parent tasks?

Use subitems when activities contribute to one deliverable but need their own owner, deadline, evidence or follow-up. Use separate parent items when the outputs have different stakeholder outcomes or independent approval paths.

Can subitems have their own status columns in monday.com?

Yes. monday.com documents subitems with their own column structure. Check the integration’s field support and permissions before assuming an AI caller can write to every chosen subitem column.

Should creative approval and task completion share one status?

Generally no. Someone can finish producing an asset while approval is still pending. Separate reported production progress from the authorised reviewer decision to avoid misleading launch-readiness indicators.

What should an AI call ask a freelance designer?

Ask only about assigned work: current version, remaining steps, blocker, expected handoff and evidence location. Avoid confidential client details the freelancer does not need and never use the call to grant client approval.

How can an agency reduce repeated follow-up calls?

Start with clear ownership and usable board data. Send routine reminders asynchronously, schedule calls for important missing information, and stop calling once a reliable update is recorded or the task is formally closed.

Create a board your team can trust

Reliable agency follow-up starts before any AI call: structure the work, name the decision-maker and make each dependency visible. If your agency already manages campaigns in monday.com, see how Autoza collects scheduled task updates or discuss an agency workflow mapping session.

How to Structure Agency Tasks and Subitems for Reliable Follow-Up