Microsoft cloud, security, and AI implementation for regulated and mid-market organizations. Learn More →
GOVERNED WORKFLOWS | ARCHITECTURE AND CONSTRUCTION
These fictional Contoso Builders workflows show what AI drafts, what a person approves, and which permissions each step needs on the Harbor Point Tower B project.
CONTOSO BUILDERS | HARBOR POINT TOWER B
All names and examples on this page are fictional. The Microsoft Marketplace listing is pending; its action currently leads to Solutions.
What can AI reach?
Which actions need approval?
Can outside content redirect it?
Can your team stop it?
The problem: Field observations reach the safety lead too late.
AI drafts: A cited hazard record from the supervisor's voice note.
A person approves: The safety lead confirms severity and assignment.
At Harbor Point Tower B, a fictional railing observation is routed to the safety lead before any crew instruction.
The problem: A classification mismatch is found after payroll closes.
AI drafts: An exception list with the source row and wage rule.
A person approves: Payroll staff accept each correction.
Contoso Builders sees a fictional classification mismatch before its weekly approval deadline.
The problem: A blocked decision disappears in a crowded RFI queue.
AI drafts: A cited priority digest of open items.
A person approves: The project manager chooses what to send and when.
On Harbor Point Tower B, a fictional submittal delay is surfaced before a subcontractor return visit.
The problem: The owner report takes days to reconcile across systems.
AI drafts: A report with cited schedule, cost and issue changes.
A person approves: The project lead signs off on the exact report.
Contoso Builders reviews a fictional Tower B cost delta before sending the owner report.
OTHER INDUSTRIES
THE WOUND
The superintendent finds out on site and you find out from the owner, which is why the brief here is drafted by AI and approved by a person before anyone reads it.
Four fictional workflows on Harbor Point Tower B show the pattern: a safety observation, a certified payroll exception, an RFI and an owner report. Each one names what AI drafts, who approves, and the permission row behind the step.
THE MICROSOFT INSIGHT
Copilot Cowork runs the multi-step task across Microsoft 365 and pauses for approval before a sensitive action such as sending the brief or posting it in Teams.
Copilot Cowork carries out multi-step tasks across Microsoft 365 and pauses for the user's approval before sensitive actions such as sending an email or posting in Teams. (Microsoft Learn, checked Oct 31, 2026)
With the pause, the owner reads what you approved. Without it, the owner reads what the model guessed.
THE ROW
The project executive approves the brief and the owner report, payroll staff approve the certified payroll correction, and the safety lead approves the observation record, each named in the row.
THE DATA
No. The workflow reads from it under the signed-in person's access and writes nothing back without the approval the row requires.
Your PMs keep their tools. What changes is that a draft arrives waiting for a decision instead of a blank page waiting for an hour.
Read in place and the platform of record stays the platform of record. Copy out and you own a second copy nobody governs.
THE FIRST RUNG
With the free Copilot readiness check, then a scoping call that picks one workflow and one project, then the switch-on engagement for the pack on SimpleOS Delivery and Simple Time.
The pack is a Simple Intelligence Group product with its own Microsoft Marketplace listing, which is pending. Simplicity IT does the governance and the switch-on as a service, quoted after the call.
AFTER TWO WEEKS
HONEST ABOUT LIMITS
It does not keep an agent working when nobody is there to approve. Copilot Cowork carries out multi-step tasks across Microsoft 365 and pauses for the user's approval before sensitive actions such as sending an email or posting in Teams. (Microsoft Learn, checked Oct 31, 2026) The row names a deputy for the superintendent who is offline, and anything without an approver waits.
It does not run on a live project until the approver trusts the draft and you decide in writing.
It does not promise a saving: the measures beside each workflow are what to inspect, not a result.
THE ONE THING TO REMEMBER
Said another way: one project, one workflow, one approver, then widen.
Said a third way: the platform of record stays where it is.
SHOW YOUR WORK
The fictional bank records the exact action and approver.
Coming
See every demonstrationDIRECT ANSWERS
The deputy named in the permission row. Anything without an approver waits, and nothing that changes a record or sends a message runs on its own.
No. The workflow reads what the signed-in person may already open and writes nothing back without approval. The platform of record stays the platform of record.
No. Drafts arrive where your people already work in Microsoft 365, waiting for a decision.
No. Contoso Builders, Harbor Point Tower B and Corliss Bay Construction are fictional and used in every example so no client is named and no result is implied.
Quoted after a scoping call. The pack is a Simple Intelligence Group product on the Microsoft Marketplace; the switch-on is a Simplicity IT service with its own scope.
NEXT STEP
Choose a focused check, or speak with the team about the workflow you need to improve.