If your project managers spend the back half of every week turning Azure DevOps into a status slide, the report you need is already sitting in the data. The work is moving the numbers out automatically, with a human still approving what goes to the client.
Why does status reporting take so long when the data already exists?
Most delivery data already lives in Azure DevOps: work items, states, completed hours, and iteration dates. The slowdown is not capture - it is re-keying. Someone copies that data into a deck, adds a RAG colour, and writes a paragraph of narrative, every week, per project.
Because the re-keying is manual, two things go wrong. The report is always slightly out of date by the time it is read, and the numbers quietly drift from what the system actually says.
What can be automated, and what should stay manual?
The mechanical parts are safe to automate: pulling current states, computing velocity and burn-down, deriving a RAG status from variance thresholds, and rolling items up by project or portfolio. These are deterministic - the same inputs always give the same output.
Judgement should stay with a person. A drafted narrative or a flagged risk is a suggestion, not a decision. The reliable pattern is draft-and-review: the system assembles the report, a PM edits and approves it, and only then does it go out.
Where do cost and margin come from if they are not in Azure DevOps?
They are not in Azure DevOps, and that is the common trap. Rates are commercial data, not delivery data. The durable approach is to keep work items and hours in Azure DevOps and hold rate cards, SOW values, and billing type in your delivery-intelligence layer, then compute cost and margin by joining the two - hours from the work, rates from the rate card.
Frequently asked questions
Can you generate status reports automatically from Azure DevOps?
Yes. Work item states, completed hours, velocity, and burn-down already exist in Azure DevOps and can be rolled up into a report automatically. Narrative and risk flags should be drafted for a human to review and approve before the report is shared.
Does Azure DevOps store billing rates?
No. Azure DevOps stores work items and hours, not commercial rates. Cost and bill rates are configured in a separate delivery-intelligence or PSA layer and joined to the hours to compute cost and margin.