Inspections and certificates run to a calendar.
Service contracts, statutory inspections and certificates each have their own dates, owners and evidence.
Building operations
Keep every building commitment
moving, shift to shift.
Inspections, contractor follow-up and handovers, tracked and drafted. A person approves every message.
Exploring · Not in development
For facilities managers
“Which inspections and certificates are due before the next statement?”
Compliance calendarExploring
For building managers
“Which jobs are still open after the contractor attended?”
Contractor follow-throughExploring
For operations teams
“What does the next shift need to know?”
Shift handoverExploring
01 / The problem
The building never stops.
The follow-up often does.
Contractor work drifts after the visit.
The job shows as attended, the handover says it’s still happening, and the return visit isn’t booked.
Context gets lost between shifts.
The next person needs what happened, what was promised and who follows up, not a pile of emails.
Exploring. Not in development. These are candidate workflows we are testing in discovery calls, and nothing here has been built.
02 / Use case
Compliance calendar
ExploringFor facilities managers
“Which inspections and certificates are due before the next statement?”
Upcoming inspections and certificates flagged for review from your contracts and records, each with its source and due date.
What it could do
- Due dates counted in code from the schedules you load.
- The evidence on file linked against each item.
- A reminder or request drafted for you to approve.
Exploring. Not in development. Tell us whether this is worth building for your team.
03 / Use case
Contractor follow-through
ExploringFor building managers
“Which jobs are still open after the contractor attended?”
Open work matched across work orders, emails and handover notes, with a follow-up drafted for your review.
What it could do
- The last contractor response and what’s still outstanding.
- Sources cited for every open item.
- Follow-up drafts in your wording, sent only after approval.
Exploring. Not in development. Tell us whether this is worth building for your team.
04 / Use case
Shift handover
ExploringFor operations teams
“What does the next shift need to know?”
A cited handover of what happened, what was promised and who follows up next, prepared for the outgoing team to check.
What it could do
- Changes since the last shift, with sources.
- Commitments made and who owns them.
- Checked and approved by the outgoing team before it’s shared.
Exploring. Not in development. Tell us whether this is worth building for your team.
05 / Same brain, same rules
A new industry.
Not a new platform.
Every workflow runs on the governed loop being built for construction first. See how it’s built.
- 1
Sources arrive
Correspondence and records reach the agent through a dedicated mailbox or upload. Documents are treated as data, never as instructions.
- 2
The agent flags and drafts
Each output points to the exact excerpt and the rule it applied. Dates are calculated in code. Drafts use your templates.
- 3
You decide
Approve, edit, dismiss with a reason, or snooze. Nothing leaves without a person’s approval.
- 4
The brain keeps it
Decisions become memory and evaluation cases. Change models later and keep everything your team has taught it.
06 / Boundaries
Clear about what it would do.
Clearer about what it wouldn’t.
Tracking, not certifying.
It would flag what’s due and what evidence is on file. It does not certify compliance or assess safety.
Your systems stay the record.
No connection to maintenance or building systems is offered. We’re asking in discovery which systems matter.
People stay in charge.
Nothing is sent to a contractor, owner or resident without a person approving it.
Start with how you work today
One conversation.
No project data needed.
Tell us where dates, commitments and approvals slip through your team. We’ll tell you honestly whether ARK360 could help.
Book a discovery call30 minutes. No system access needed.
Prefer email? Write to James.
- 01
Walk us through your process.
How dates, commitments and approvals are tracked today, and who carries them.
- 02
Show us where it’s fragile.
A close call, a busy week, a handover. A description is enough; keep project data where it is.
- 03
Decide if there’s a fit.
If there is, we talk about a design partnership under a written agreement. If not, you leave with a clearer picture.
We’re looking for a design partner to run ARK360 on a closed or live project. That starts with a written agreement, and no real project data is used before it’s signed.
Can building teams use ARK360 today?
No. Building operations workflows are being explored in discovery calls and nothing has been built. The first workflow in development is contract notices for construction.
Does it connect to our maintenance or building systems?
No connection is offered. If a workflow goes ahead, the first inputs would be documents and exports you choose to load. Tell us which systems matter in a discovery call.
Would it replace our compliance or safety processes?
No. It would help track dates and evidence for your team. It does not certify compliance, assess safety or replace your procedures and advisers.