Tasks and SOPs tied to the work

Client projects, recurring tasks, deadlines, owners and checklists, linked to the ads, creatives and signals they are about.

Get early access All featuresHow it works
app.roasfinity.com/operate/tasks-sops
Tasks and SOPs screen in the ROASfinity app, with test data

Floating cards and figures are examples on sample data, not a customer account.

1The proof

Every number comes with its receipt.

Sample data, fictional brand. This is how Tasks and SOPs shows a figure: the value, where it came from, the formula behind it and when it was last updated.

Tasks and SOPsSample data, fictional brand
Test the question hook on TikTokDue FridaySource and formulaOwner: designerUpdatedsee source
Monthly reviewRepeats every monthSource and formulaSOP checklist, 8 stepsUpdatedsee source
Fix rejected adIn progressSource and formulaFrom a signalUpdatedsee source

Rule: every number shows its source, formula and update time. A missing source reads "not measured", never 0.

2Part of Operate

Tasks and SOPs: what it does.

One of four areas of the product, sharing the same client record, roles and log.

01

Recurring work stays recurring

Monthly reviews and weekly checks come back on their own with their checklist.

Tasks and SOPs in the app, with test data
02

Evidence attached

A task opened from an insight or a signal carries the numbers that caused it.

03

Everything under one client

Tasks, files and ads sit under the same client record and respect the same roles.

Works with

1 platform, read-only first

Connections start read-only. Writing is switched on per account, only after you grant the rights.

At a glance

Stated up front

things it does
3
steps start to finish
4
platform connections
1
limits stated
2
3The data path

How the data moves. Source to screen.

Lines draw as you scroll. Platforms on the left are read-only first, Tasks and SOPs sits on the one client record, and each output keeps its receipt.

Google WorkspaceRead-only first
ROASfinityTasks and SOPs
Recurring work stays recurring
Evidence attached
Everything under one client

Sources are read first, the numbers are stored once per client, and every output shows its source, formula and update time.

How the work moves in Operate

The same four moves apply to every module in this area.

  1. 1 CaptureFrom the work itselfTasks start from comments, results, approvals and requests.
  2. 2 AssignRoles and ownersOne owner per task, and clients only see what they should.
  3. 3 TrackStatus in one recordDue dates, SOP steps and approvals sit with the client record.
  4. 4 LogNothing is lostEvery change is written to a log that cannot be edited afterwards.
4The routine

How it works, step by step.

From first connection to the number a client sees.

  1. 1

    Create or recur

    Add a task or a recurring routine for a client.

    Tasks and SOPs app screen with test data
    Step 1Create or recurexample
  2. 2

    Assign

    Set an owner, a deadline and a checklist.

    Step 2Assignexample
  3. 3

    Work with context

    Open the linked ad, asset or signal from the task.

    Tasks and SOPs app screen with test data
    Step 3Work with contextexample
  4. 4

    Close with a note

    Record the outcome next to the evidence.

    Step 4Close with a noteexample
5In use

Built for businesses like these. Example scenes.

Photos are stock images that show the kind of business this is built for. They are examples, not customers.

Examplea small team
Examplea cafe or local shop
Examplea small team
Examplea creator studio

Stock photos and example labels, not customers.

6In practice

Common mistakes, and a short checklist.

General practice for this kind of work, not a claim about any one tool.

Mistake

Tasks with no owner or due date

A task that belongs to everyone belongs to no one. Give each task one owner and a date, and review open items in a fixed meeting.

Mistake

SOPs written once and never updated

A procedure that no longer matches the work misleads the next person. Review each SOP after every error and on a fixed schedule.

Mistake

Knowledge that lives in one person

When the only person who knows the steps is away, the work stops. Write the steps down and test them with someone who has never done the task.

A short checklist

Your ticks stay in this browser only.

7Honest limits

What it will not claim, and what it works with.

What it will not claim

  • It is built for agency delivery work, not as a general project management suite.
  • Reminders and integrations with other task tools are added as they are needed.

Works with

Connections are read-only first and go live only after the platform access is approved.

Google Workspace

Built: the connector exists in the product and goes live per account once access is granted. Planned: not built yet.

Used instead of

No single tool replaces this module; it connects work that is usually split across several.

9FAQ

Questions about tasks and sops.

Can I use my own SOPs?

Yes. A checklist is a template you write and attach to a recurring task.

Do clients see tasks?

Only what their role allows. Client approvers see their own brand and approval items.

Does it replace Asana or ClickUp?

It covers delivery tasks that need ad and creative context. You can keep a general tool for everything else.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Get early access How we plan to price it