One governed front door for every request.
Capture capital, tenant, stakeholder, service, and inspection requests; classify and prioritize them; and route them to approval and action — with configurable request types that put the work in motion.
Requests don’t belong in a shared inbox and three spreadsheets.
Capital asks, tenant projects, access requests, service tickets, and inspection needs arrive from every direction. Without a governed front door, they’re lost, duplicated, or approved by whoever shouts loudest. Request Management gives every request one intake, one owner, and one path.
Ad hoc intake
- Requests arrive by email, call, and hallway conversation.
- No consistent priority, owner, or SLA.
- Duplicates and dropped requests are normal.
- Approvals take weeks, and no one can see the queue.
Governed request management
- One front door captures every request as structured intake.
- Request types set the form, routing, and approvals automatically.
- Prioritized against clear criteria, with a visible queue.
- Approved — and put into action — in days, not weeks.
Capture → Classify → Prioritize → Approve → Act → Close.
A governed path that takes a request from “someone asked” to “done, on the record” — and, where it makes sense, straight into field work.
Every kind of request, in one place.
From a multi‑million‑dollar capital ask to a badge for a contractor — the same governed intake, tailored to each kind of request.
Capital investment requests
Publish selection criteria, capture proposals and follow‑on opportunities, and prioritize the pipeline.
Tenant & stakeholder requests
Expedite tenant fit‑outs and stakeholder projects, and coordinate the interfaces between them.
Service, maintenance & access
Capture service, maintenance, and access requests — routed, de‑duplicated, and tracked to resolution.
Configure the request type once — it does the work every time.
- R‑01Define the type, not a one‑off formEach request type carries its own intake form, required fields, routing, and approval path.
- R‑02Generate the work automaticallyA request type can spin up an Activity List or field inspection the moment it’s approved — no re‑keying.
- R‑03Close the loop back to the requestFindings and completion flow back to the originating request, so intake and execution stay in sync.
The bridge to field execution
Request Management is the front door; Inspections & Field Execution is where an approved request becomes a checklist on someone’s device — connected end to end.
See the queue. Approve with confidence. Move in days.
- P‑01Prioritize against criteriaRank requests by published investment and selection criteria — a defensible pipeline, not a squeaky‑wheel list.
- P‑02Monitor approval queuesSee what’s waiting on whom, clear bottlenecks, and process reviews and approvals in days.
- P‑03Coordinate the interfacesMap where requests touch each other — locations, tenants, and teams — so approvals account for the whole picture.
A queue leadership can actually see
Give owners and approvers a live view of intake, priority, and status — so decisions are fast and the backlog is visible.
Governed intake — not project management.
Request Management governs how requests get in, get prioritized, and get routed to action. It’s the owner’s front door, not a PMIS — it doesn’t run the delivery schedule or replace your project controls.
It hands off to the right system — and integrates with the ones you have.
An approved request becomes an Activity List, a work item, or a project in your PMIS or project‑controls tool. CitiriOS governs the intake and routing and connects to those systems; it doesn’t try to be them.
Powered by CitiriOS. The front door to the work.
Request Management captures and routes the work — then hands off to field execution, stakeholders, and the evidence chain.
Give every request one governed path.
Book a demo built around your capital, tenant, stakeholder, service, and inspection requests — from intake to approval to action.
Queue figures shown are illustrative, not a customer result. Request Management governs intake and routing; it is not a PMIS and integrates with — does not replace — your project‑controls, PMIS, and service systems. Opti suggests and cites; people prioritize and approve.