Back to Blog Home

RAG status for a small firm: set red, amber and green from overdue tasks and stale updates

A person writing on a wall covered in sticky notes during project planning

For a small firm, RAG status should be computed from facts the task tool already holds: green when nothing is overdue and the last status update is recent, amber when a task is slipping or the update is stale, red when a task is more than a week late. Most guides define the colors as schedule bands, for example green within 5 percent of planned schedule and red more than 15 percent behind, which needs a baseline that a firm without a project office may not have.

The failure is a color that is the project manager's mood on Monday morning. A late project can stay green until it is suddenly red, a manager who reports red expects questions, and the owner can end up hearing the real state from the client. Writing the rule down gives each color its evidence, settles what amber means, and lets a weekly Slack check propose the colors from task data.

What does RAG status mean, and why does it drift?

RAG status is a three color summary of project health: green is on track, amber is at risk and red needs a decision or help now. The meaning only holds when it is agreed in writing before the first report, as Asana's own status report template advises. Without that, every manager fills the gap with judgment.

Two drifts are named repeatedly. The first is the watermelon project, one whose reported status is green while its actual health is red. RoadmapOne, a vendor, names the tell: a sequence like green, green, amber, amber, amber, red, where status slides through amber and then snaps to red. The second is permanent amber, where managers are so wary of red that every project sits in the middle and the color carries no information.

Pressure on the person reporting can produce both. One engineer on Hacker News describes a workplace where two layers of management disliked seeing red on status reports and wanted to redefine what finished meant. That is a single author's account, not a measured rate, but it matches what an owner sees: when red is punished, red stops being reported.

What do RAG guides leave out for a small firm?

The guides define colors with schedule and budget percentages and leave the person to supply the number. None turns an overdue task or the age of the last update into a color, none addresses a firm without a project office, and none says who may push a color better.

GuideWhat it gives youWhat a 15 to 60 person firm still lacks
Onplana (vendor)Green within about 5 percent schedule and budget variance with no unmitigated high risk, amber from about 6 to 15 percent, red above thatA source for the variance, and no rule on task data or update age
Institute of Project ManagementThe same 5 and 15 percent schedule bands, with the project manager assigning the color and a sponsor reviewing itA color for firms with no baseline, and no rule for moving it better
Mastt (vendor)Delay and cost thresholds, and the advice to automate thresholds from live dataWhich live data, and who may override the result
RoadmapOne (vendor)A diagnosis of watermelon and permanent amber projectsA rule that stops them

Onplana suggests a status and lets the project manager override it with a note. The Institute of Project Management gives the assignment to the project manager. Both put the override in the hands of the person whose project is being rated, which is the weak point for a firm trying to stop a late project reading green. The rule below is our own recommendation, built on the facts a task tool holds, and the thresholds are starting values to tune, not an industry standard.

Which facts can a task tool turn into a color?

Three facts are enough to compute a color: how many open tasks are past due and for how long, whether any task due in the next seven days has no owner, and the date of the project's latest status update. Due dates and owners live in the task tool, the agent reads an Asana project's status updates, and none of the three needs a baseline, a budget or a time sheet.

Here is a one page rule you can paste into a Google Doc. The worst applicable color wins.

ColorFacts that set itWho may move itWhat moving it needs
RedAny task overdue by more than 7 days, or 4 or more tasks overdue, or no status update for 22 days or moreAnyone, to a worse colorNothing, say so in the thread
Amber1 to 3 tasks overdue and none older than 7 days, or a task due within 7 days with no owner, or the last update 15 to 21 days oldAnyone, to a worse colorNothing, say so in the thread
GreenNo task overdue, every task due within 7 days has an owner, last update 14 days old or lessMoving up from amber or redA written reason in the thread and the owner's approval
No colorNo open tasks, or any one of the three facts could not be readA person adds a noteA human note stating why

The numbers are judgment calls, not findings. Seven days is one working week of slip, and 14 days without an update is two missed weekly cycles. Change them if your delivery rhythm is different, but change them in the Doc with a date, not on the Monday you dislike a result. The Institute of Project Management calls moving thresholds mid-project to avoid an uncomfortable red a governance failure unless it goes through change control, and the same reasoning applies to a three line Doc.

Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.

What can this color not see?

A color computed from overdue tasks and the age of the last status update measures schedule hygiene only, so the rule must say that it cannot see budget, hours or dependencies.

The Kipwise agent's Asana connection, for instance, does not manage goals, portfolios, dependencies or time tracking, so it cannot tell you that a project is 30 percent over its hours or that the one late task blocks everything behind it. Put that line at the top of the Doc. A project can be green on this rule and still be losing money, and a project can be red because a manager forgot to close finished tasks. Red means the owner and the manager look at the project together this week.

That framing also protects the people reporting. The UK government's major projects report says a red rating does not mean failure and signals that significant issues need urgent attention. Tell your managers that red triggers help, not blame, and say it before the first red appears.

Who may change a color?

Anyone may push a color worse at once, and a color moves better only with a written reason and a second person.

The reasoning is the asymmetry of risk. A false red costs a short conversation. A false green can cost the client relationship, because the owner stops looking. Leaving the override with the project manager lets a late project stay green, because the person being rated is also the person who decides whether the rating sticks. So the person who sees trouble, whether a manager, a designer or a coordinator, can move a project to amber or red in one message with no approval. Moving it up needs the manager to write why in the thread (the late tasks were closed, the missing update was posted, the client agreed a new date) and the owner to approve. The decision stays with people, and the written reason is what a future you reads when asking why a project was green the week it went wrong.

This is our recommendation, not a sourced practice. If it feels heavy, test it on the two or three projects that stayed green too long last quarter.

How do you handle a project the rule cannot rate?

Leave it uncolored and say why. A project with no open tasks or an unreadable fact gets no color at all, because an empty project would otherwise compute to green.

A new project before the plan is entered has no overdue task, no unowned task and, often, no status update to be stale, so a naive rule marks it green on the day it is least understood. Three cases stay blank on the rule above:

  • A new project with no open tasks yet.
  • A project the person running the check cannot see, because the check runs with that person's own login.
  • A fact the tool could not return, such as a status update date it could not read.

Anything the rule does not cover, a client freeze or a deliberately paused project, stays a plain human note beside the project. Do not invent a fourth color for it.

How do you run the weekly check in Slack?

Write the rule once, then ask the Kipwise agent in a #projects thread to apply it every Monday and post one line per project. You need Asana connected under your own login, because the agent reads an Asana project's status updates, and the rule saved as a Google Doc in Drive, which the agent can read with your own Drive access.

Ask in plain language, once:

> Every Monday at 8 am, for the projects Northwind website, Harbor onboarding, Fieldstone retainer, Pine and Co audit and Brightpath rollout in Asana: list the open tasks that are past due with how many days, list tasks due in the next seven days with no owner, and read the date of the latest project status update. Apply the rule in the Google Doc "RAG rule" and post one line per project with a proposed color, the overdue tasks and the oldest due date, the last update date and the rule line you applied. If you could not read a fact, say not read and leave the color empty.

Creating a scheduled request needs one Approve card, and later runs do not ask again. The agent runs with your permissions, so it sees only what you can see. It is told not to guess, which is what lets the blank color work: a project it cannot read comes back as not read, not as a color it made up. Here is a made-up Monday post for an imaginary 30 person agency, to show the shape:

ProjectProposed colorFacts it readRule line applied
Northwind websiteRed2 tasks overdue, oldest due Nov 3 (15 days late); last update Nov 6Any task overdue by more than 7 days
Harbor onboardingGreenNo overdue task; every task due this week has an owner; last update Nov 14No overdue, owners set, update within 14 days
Fieldstone retainerAmber1 task overdue (4 days); one task due Nov 21 has no owner; last update Nov 131 to 3 overdue, none past 7 days, plus an unowned task
Pine and Co auditNoneNo open tasksNot read: nothing to compute from
Brightpath rolloutNoneProject not visible to this loginNot read: no access

The manager replies in the same thread. Moving Harbor to red because the client emailed a complaint takes one line and no approval. Moving Northwind back to amber takes a written reason, such as "both late tasks closed Tuesday, new date agreed with the client", and the owner's approval in the thread. If you want a status update posted in Asana, ask for it, and the agent shows an Approve card before it posts. Nothing goes to a client.

What goes wrong, and how do you check it worked?

Four failures are likely, and each has a check.

  • Everything is permanent amber. Count the colors over eight weeks. If most projects sit in amber and none moved, your thresholds are too tight for your delivery rhythm, or managers close tasks late. Widen the overdue window or fix the closing habit before adjusting the rule.
  • Green projects blow up anyway. Pull the last three problem projects and look at what the rule showed the week before. If it showed green because the problem was budget or hours, the rule is working as designed and you need a separate cost check. If it showed green while tasks were overdue, the facts were not being read, so check access and plan limits.
  • Managers game the facts. A manager can close or re-date a late task before Monday. Look for tasks whose due date moved more than twice, and make a moved date on a task already late part of the thread note.
  • A free Asana plan. It has no full search and no custom fields, so the agent finds tasks by name, person or inside a project and says which search it ran. Read that line before trusting a count.

To verify the setup, run the check once by hand for one project you know well and compare the proposed color with what you would say. If they disagree, find out whether the rule or your instinct is missing a fact. Then run the schedule for four Mondays and compare the first color each late project received against the date the client noticed. A rule that goes red before the client notices is doing its job.

For more on the neighboring jobs, see how the agent can chase overdue tasks across a project, how to collect a status from each person, and how to keep a risk register with an owner and review date for the problems a task tool cannot see.

What does it cost, and what is the trade-off?

The agent is $10 per user per month with a three user minimum, and each user gets $5 of personal credit for their own asks and scheduled requests each month. The trade-off is that you are paying for a weekly read of facts a project lead could read alone. The saving is real only if your firm runs enough projects that the round takes real time, and we do not have a measured figure for how much time small firms save, so test it on your own board.

The agent reads tasks and updates, applies a rule you wrote and proposes a color. People decide what the color means for the client.

What to do next

Open a Google Doc this week and paste the rule table, then change the thresholds to match how your firm delivers. Name the Asana projects that carry client work, add the Kipwise agent to Slack, and ask it to run the check once on Monday. Compare the proposed colors with the ones your managers would have reported and decide, on that first Monday, who may move a color better.

Topics

Related posts

Put an AI teammate in your Slack

Free trial on install: $2 of AI credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or for existing Kipwise customers.