Daniel did not meet the required CORI threshold this cycle and moved one step back.
Early positive signals. Reliability is forming, but it has not yet been demonstrated consistently across cycles.
Next strong assessment moves to Consistent. Next weak assessment moves to Inconsistent.
Competence (9/9) and Initiative (7/9) are current strengths, but Ownership (2/9) and Relationships (2/9) are in the Needs Work range. Because Ownership and Relationships are currently what most limits reliability, the read below follows from this specific pattern of ratings — not a general judgment about Daniel.
Capability is real, but neither accountability nor collaboration support it. This combination is operationally dangerous — strong output without ownership produces unpredictable delivery; strong output without collaboration produces a team-tax. The talent is present; the reliability foundation isn't.
The current pattern doesn't yet support taking on more reliance or responsibility. The immediate priority is improvement before expansion.
Show visible improvement before additional responsibility is considered.
Competence is where you are most consistent this cycle at 9/9. This is what the next ninety days builds on — the growth opportunity below is something to add to it, not a correction of it.
This is the most serious constraint because ownership is the foundation of reliability.
Each pillar score is the sum of three behavioural items. Every rating is anchored to something your manager actually observed, so nothing in this report is an impression you cannot trace.
Capability is currently a strength. You appear able to understand the work, improve, and deliver at acceptable quality.
“Ships production-grade work; his pull requests clear review with minimal rework and rarely reopen after merge.”
Supports being relied on at your current scope.
Needs little oversight.
“Reframes vague tickets around the real business outcome before writing a line of code — he solves the problem, not the literal request.”
Supports being relied on at your current scope.
Needs little oversight.
“Absorbs technical feedback fast; the same review note almost never has to be made twice.”
Supports being relied on at your current scope.
Needs little oversight.
Ownership is the most serious risk signal. Without ownership, competence and relationships cannot fully convert into reliability.
“When the Q2 launch slipped he opened with external blockers and team dependencies before acknowledging his own missed handoff.”
Reduces confidence in handing work over.
Creates extra work for other people.
“Commitments routinely need a reminder; two of the last three deadlines moved without a proactive heads-up.”
Reduces confidence in handing work over.
Creates extra work for other people.
“Flagged a minor API risk early but sat on the larger data-migration risk until it forced a weekend rollback.”
Reliable in parts; not yet consistent.
Still needs periodic checking.
Working with you currently creates friction or resistance. This carries further than it may appear, and strong individual output does not offset it. The cost is usually indirect — people hesitate to raise things with you, or route around you — which is why it can persist for a long time without anyone saying so.
“Peers have started routing design reviews around him to avoid the friction his comments create in the room.”
Reduces confidence in handing work over.
Creates extra work for other people.
“Feedback lands intellectually but behaviour change is inconsistent — improves for a sprint, then reverts.”
Reliable in parts; not yet consistent.
Still needs periodic checking.
“In architecture debates he defends his position well past the point the decision has already been settled.”
Reduces confidence in handing work over.
Creates extra work for other people.
Initiative is currently a strength. You show signs of creating movement without always needing pressure or instruction.
“Moves confidently on well-scoped gaps but stalls and waits for direction the moment requirements turn ambiguous.”
Reliable in parts; not yet consistent.
Still needs periodic checking.
“Rebuilt the CI pipeline unprompted and cut build times by half — a clear, unsolicited systems improvement.”
Supports being relied on at your current scope.
Needs little oversight.
“Output stays sharp under deadline pressure but visibly dips during quieter, unmonitored stretches.”
Reliable in parts; not yet consistent.
Still needs periodic checking.
Readiness for more responsibility requires more than contribution. It requires consistent reliability without repeated chasing. The current pattern shows one or more CORI pillars not yet strong enough to indicate readiness for increased autonomy.
You are not being written off, but the current pattern needs to change. The next stage is not about proving intention. It is about proving consistency. For the next 90 days, the focus should be on creating visible evidence that reliability can increase.
These are not a test and nobody scores them. They are the questions this pattern usually makes worth asking. Answer them honestly to yourself before the next cycle.
When something slips, what is your first instinct — to explain it or to name it?
Which of your commitments this month would someone have had to chase you for?
What is the last risk you raised before it became a problem?
These are the success indicators for this cycle. They are yours to track — tick them off as they become true, and bring them to your next assessment.
CORI Score = the sum of all four pillar scores (0–36). Each pillar = three behavioural items rated Mostly True (3), Sometimes True (2), or Rarely True (0). An assessment meets the CORI standard when the score is at least 28 / 36 with no pillar in the “needs work” range — meeting it moves the person up one reliability band, missing it moves them down one. Reliability is earned over repeated cycles, not declared from a single assessment. Scoring is deterministic — the same answers always produce the same report. CORI measures business reliability and readiness for responsibility; it is not a personality test, a psychological diagnosis, or an AI prediction.