devYAN
Copy to my workspace

Oakridge maintenance triage pilot report

Oakridge maintenance triage pilot report

An operations director reading a pilot report

Pilot report Oakridge Property Management Fernway Automation

Owner: Sam Okoro. Updated Oct 12, 2026.

Where the 1,032 requests went

Oakridge maintenance triage pilot Pilot closed Oct 11, 2026 After-hours criterion has no evidence

What the Oakridge maintenance triage pilot actually ran, set against the success criteria agreed at kickoff: how many requests it handled, what needed a person, what it could not do and what is still open. Prepared by Sam Okoro, lead consultant at Fernway Automation, for Diane Foster, operations director at Oakridge Property Management. Every figure comes from six weeks of run records, exceptions and approvals that Diane can open and inspect herself. Issued Monday, October 12, 2026, one day after the pilot closed.

Requests handled1032Aug 31 to Oct 11
Completed within the rules81%836 requests
Needed a person14%144 requests
Out of scope5%52 requests

Oakridge manages 2,400 units. Between August 31 and October 11 every request that reached the maintenance request inbox was run against the same triage rules for six request types, agreed at kickoff on August 10. The six-week totals were counted after the pilot closed on October 11. They come from the run record and are rounded to the percentages above.

PartValue
Completed within the rules836
Needed a person144
Out of scope52

What needed a person is not one problem. The run record was logged in batches, and the exception log names the patterns behind them. The last row is the balance of the six-week totals.

PeriodRequestsNeeded a personWhat the exception log shows
Weeks 1 and 2 (Aug 31 to Sep 13)21443Runs stopped at a draft where after-hours dispatch was outside the approved scope
Week 3 (Sep 14 to 20)2313619 unmatched unit numbers: photos but no unit number, so no property match
Week 4 (Sep 21 to 27)24831Business hours; the 31 are spread across steps
Week 4 after hours (Sep 21 to 27)42537 routed to the on-call coordinator, 5 held as possible emergencies
Weeks 5 and 6 (Sep 28 to Oct 11)29729Balance of the six-week totals, counted after close

In the first fortnight 171 of the 214 requests completed within the rules. Vendor dispatch for after-hours requests was outside the approved scope, so those runs stopped at a draft until Diane approved after-hours routing to the on-call coordinator on September 16 and kept vendor dispatch as a step that waits for her approval.

Success criteria agreed at kickoff

Five criteria were agreed on August 10. The status column reports the evidence, not a verdict on the pilot: three are met, one is partly met and one has no evidence yet.

#CriterionTargetResult from the run recordStatus
1Triage completed within the agreed rulesAt least 75 percent of requests81 percent (836 of 1,032)Met
2Faster first triage in business hoursMedian at least 50 percent faster than baselineMedian 18 minutes against a 3 hour 40 minute baseline taken from June and July inbox timestampsMet
3Every run recorded against a permission100 percent of runs1,032 of 1,032 recorded with identity, scope, time and resultMet
4Requests matched to the right property and unit without a personAt least 95 percent19 runs in week three stopped at matching. The tenant form has required a unit number since Sep 28; the two-week count was taken on Oct 12 and is not yet reviewedPartly met
5Faster first triage after hoursMedian at least 50 percent faster than the after-hours baselineAfter-hours routing is running, but no after-hours baseline exists, so no comparison can be madeNo evidence yet

How far each criterion has moved toward its target:

    1. Completed within the rules: 81 percent against a floor of 75
    1. Business-hours first triage: 92 percent faster than baseline, target 50
    1. Runs recorded against a permission: 1,032 of 1,032
    1. Days on the new tenant form: 14 of 14, counted Oct 12, result not yet reviewed
    1. After-hours baselines agreed: 0 of 1

What the pilot could not do

After-hours response time. The report cannot state a change in after-hours response, because the baseline only covered business hours. Sam Okoro reported business-hours response only and listed after-hours response as an open question. Consequence: criterion 5 stays without evidence, and a second phase cannot be scoped on after-hours claims.After-hours vendor dispatch. Dispatch outside business hours was outside the approved scope, so those runs stop at a draft and wait for Diane Foster's approval. Nothing is dispatched to a vendor without it.Requests with photos but no unit number. Nineteen runs in week three (Sep 14 to 20) failed at the same step because the tenant form does not require a unit number. Fixing them by hand would have hidden that. Sam logged the pattern as a design exception, and Diane agreed to make the unit number required on the tenant form. The change went live on Sep 28. The two-week count was taken on Oct 12 and has not yet been reviewed with Diane, so this report does not state whether unmatched requests have dropped.

Details
Executions recorded1,032 of 1,032, each against a permission with identity, scope, time and result
Permissions approvedInbox read Aug 26, coordinator ticket creation Aug 28, vendor list read Sep 2, after-hours routing Sep 16
First summaryRejected by the Oakridge security reviewer: it listed a shared service account as an approver
ReplacementTwo named approvers, proposed by Sam Okoro and still waiting for Diane Foster to confirm them
Next stepSend the revised permission summary to the security reviewer for sign-off

Recommendation, not a finding

Fernway recommends that no second phase is scoped until an after-hours baseline is agreed and Diane has reviewed the two-week count on the new tenant form. This report does not declare the pilot a success or a failure. The criteria table is the record, and what to do with it is Diane's decision.

Open questions

Open questions with an owner and a date
Agree how after-hours first triage will be measured and set the baseline. Owners: Diane Foster and Sam Okoro, by Oct 20
Confirm the two named approvers. Owner: Diane Foster, at the Oct 13 review
Send the revised permission summary to the security reviewer. Owner: Sam Okoro, by Oct 16
Review the two-week count of unmatched requests with Diane. Owner: Sam Okoro, Tuesday Oct 13
✓Take the two-week count of unmatched requests on the new tenant form. Owner: Ines Moreau, Oct 12
Review the vendor dispatch steps that are waiting for approval at the weekly check-in. Owner: Sam Okoro, every Tuesday
✓Issue the report inside a week of pilot close
Checklist
Decide whether the managed-service proposal goes ahead, after the checklist review on Oct 13. Owner: Diane Foster with Sam Okoro.
✓Log the unit number pattern as a design exception instead of fixing the 19 runs by hand. Owner: Sam Okoro, done.

I can take this into a budget conversation because I can open the same record Sam used. The after-hours gap is the thing I most want closed before anyone talks about a second phase.

Diane FosterOperations director, Oakridge Property Management

What happens next

✓Kickoff, Aug 10
✓Pilot run, Aug 31 to Oct 11
✓Report issued and two-week count taken, Oct 12
Checklist review, Oct 13
Proposal decision, after Oct 13

Prepared and reviewed by

SOSam OkoroLead consultant, Fernway Automation, prepared this report
IMInes MoreauAutomation engineer, Fernway Automation, checked the run record
DFDiane FosterOperations director, Oakridge Property Management, client sponsor

Demo deal room. Fernway Automation, Oakridge Property Management, the people and every figure are fictional sample data. Built on FuseBase.