Yopla | Discover, build and deliver

Executive summary

Larkspur relies on people to bridge the gaps between its processes and systems. Requests are copied between records, handovers lack a clear end-to-end owner, and knowledge sits with a few helpful colleagues. The organisation lacks a joined-up way to define, prioritise and deliver technology change that serves its strategy.

New software alone would not resolve this. Uneven practical fluency, limited learning time and patchy cover mean that processes, habits and support must change together. People need time to practise, different ways to learn and room to raise concerns.

We recommend starting with one request-to-schedule handover: appoint an accountable owner and sponsor, agree the job pack and exception route, protect practice time, then test a shared queue using existing tools. Resolve the approaching renewal decisions alongside it. This mobilisation provides the diagnosis and recommended plan; the pilot and wider rollout are a separate delivery stage to agree.

17 / 42

sampled requests entered twice

E4 · request review

31 / 74

help nominations point to three bridge roles

E2 · staff survey

28 / 72

anonymous respondents have time to learn

E9 · readiness

Separate fictional evidence streams. Read together, they make ownership, support and protected time part of the technology decision.

01 / Executive diagnosis

Larkspur Works
mobilisation report

The people are keeping the work moving. The organisation is making that harder than it needs to be.

Fictional organisation. Illustrative data. No client information. Larkspur is an invented repair, training and facilities enterprise: 124 people, three sites and 31 tools. This is an illustrative example, not a client case study.

Larkspur needs the capability to carry change through

It lacks a joined-up way to define, prioritise and deliver strategically useful technology change. No end-to-end request owner, 13 unowned tools and uneven protected time point to an organisational gap. This is a judgement about how change is led and supported, not a verdict on individual technical talent. [E4–E5, E8–E10]

An email becomes a planning-sheet row. Missing details trigger a call; a helpful colleague gets the job moving. Finance later reconstructs a separate record. This invented scene illustrates the handover pattern. The spreadsheet itself is not the diagnosis. [E4, E8]

What the evidence says	The hard truth and the decision
17/42 requests re-entered; 11/42 returned for clarity. [E4]	The people are doing the integration. Define one request, a complete handover and an accountable owner before automating the route.
31/74 help nominations point to three bridge roles; only 4/12 workflows have rehearsed cover. [E2, E11]	A helpful person is not a durable process. Protect their time, capture the exception decisions and test a deputy. Nominations alone do not prove overload.
28/72 anonymous respondents say they have time to learn; 9/12 champions have protected time. [E8–E9]	A plan without capacity is a wish. Agree the work that stops or moves before asking people to change how they work.

Our recommendation

Do not start with an estate-wide replacement. Give request-to-schedule one owner, agree the job pack and exception route, then test a shared queue using the existing tools. Resolve six approaching renewal decisions alongside that work, before notice dates lock in the options. [E4–E6]

The decision now: appoint the service owner and finance sponsor; consider the separately agreed delivery stage on section 16. Mobilisation diagnoses the problem and recommends the plan; it does not include that delivery automatically.

Read the report	Sections	Read the report	Sections
Evidence & maturity	2–3	People & capability	5–9
Connected diagnosis	4	Work & technology	10–14
Economics & next stage	15–16	Evidence & review	17–18

Powered by yopla.app. The £37,440 modelled resource cost and cash limitations remain on section 15. All figures and reconstructed scenes are invented; no client quotation or screenshot is reproduced.

02 / Evidence and coverage

What the evidence can support

The example combines broad participation with a smaller set of deeper checks. Coverage is visible so that absence of evidence is not mistaken for absence of a problem.

Evidence stream	Illustrative coverage	What it contributes
People and structure [E1]	124 people / 6 functions / 3 sites	Scope, reporting lines and denominator for participation.
Staff survey [E2]	98 of 124 people (79%)	Reported friction, help networks, tools and learning preferences.
Task assessment [E3]	86 of 124 people (69%)	Performance on five practical scenarios; not a general ability score.
Request review [E4]	42 requests; timing recorded for 24	Handover gaps and a provisional service baseline.
Technology and contracts [E5–E6]	31 tools; 24 paid agreements	Ownership, spend, terms and renewal exposure.
Workflow and interviews [E7–E8]	12 workflows; 12 interviews	How tasks connect and which explanations need testing.

Participation is uneven

Service delivery: 34 / 44
Workshops: 24 / 32
Customer support: 16 / 18
Finance: 9 / 10
People: 7 / 8
Leadership and support: 8 / 12

Customer support and finance are well represented. Leadership and support have the lowest response rate. Non-respondents may have different experiences; the 98 responses are not treated as a random sample or reweighted to imply one. Site and shift-level checks remain necessary before organisation-wide conclusions. [E1–E2]

Three different kinds of statement

Recorded means a count or observation in this fictional evidence pack. Modelled means an estimate calculated from stated assumptions. Proposed means a target, decision or future action. None represents a real measurement of a real organisation.

Not covered: penetration testing, accessibility certification, payroll validation, a representative time-and-motion study, supplier due diligence, or a psychological assessment. The document is a mobilisation example, not independent assurance.

The example also includes leadership and anonymous readiness instruments, maturity interpretation, cover and document checks, adoption reconciliation and enquiry outcomes. Their separate denominators and limitations are listed on section 18.

03 / Maturity & evidence

A shared direction, uneven foundations

Digital maturity is how well an organisation can choose, use and improve technology to support its purpose. It depends on the people, decisions and everyday work around the tools, as well as the tools themselves.

How Yopla makes the picture clearer

Our maturity framework brings the evidence together across six dimensions: Strategy & Leadership; People & Change; Operations & Delivery; Technology, Data & AI; Growth, Marketing & Revenue; and Sustainability & Environment. This keeps the diagnosis wider than a software problem and shows which foundations need to improve together.

We compare self-assessment, anonymous responses and Yopla’s evidence-based interpretation. Differences prompt questions, not verdicts on people. For Larkspur, the priorities connect: agree direction and decision rights, give the handover an owner, and protect time to learn before introducing more automation. Sustainability remains unassessed because the evidence is missing.

Self assessed: six sponsor/leadership respondents. Anonymous: 72 respondents, with 72 valid ratings on each of the five assessed dimensions. Yopla: explicit auditor interpretation of the fictional source pack. These are different perspectives and cohorts, not paired measurements. [E9–E10]

Dimension	Yopla score / attained band	Decision implied
Strategy & Leadership	1.8 / Emerging	Sponsor agrees outcomes and decision rights.
People & Change	1.6 / Emerging	Protect practice time and make challenge safe.
Operations & Delivery	1.4 / Emerging	Own the end-to-end handover before automating.
Technology, Data & AI	1.7 / Emerging	Assign owners and evidence access and adoption.
Growth, Marketing & Revenue	1.3 / Emerging	Close the enquiry-to-outcome feedback gap.
Sustainability & Environment	Unassessed	Commission a baseline before choosing targets.

Scale: 0 Initial · 1 Emerging · 2 Defined · 3 Managed · 4 Optimising. Attained bands use the floor of the score: 1.8 is Emerging, not Defined. No whole-organisation average is calculated. Missing evidence is not zero.

The client-facing report has three tracks. Yopla uses an auditor score where supplied, otherwise an observed score; it never blends them. This example supplies auditor judgements for five dimensions, leaving sustainability unassessed. [E10]

04 / Connected diagnosis

Buying a tool will not assign an owner.

The evidence points to a system of work that depends on people repairing its gaps. Fix the connections, not just the screen.

Unclear handoverWho decides the next step?
Personal workaroundsAsk the person who knows
Repeated handlingCopy, clarify and chase

Repeated entry, clarification, help nominations and cover gaps are recorded in the fictional sources. The chain above is an explanation to test through observation and an exception rehearsal, not a proven causal result. The cohorts overlap and must not be added together. [E2, E4, E7–E11]

Dimension	Connection to the decision
Strategy & Leadership	Two planning documents name no end-to-end request owner. The sponsor must resolve that boundary; another project plan alone will not. [E9–E10]
People & Change	Only 28/72 anonymous respondents report time to learn. Protect practice time and a route for challenge before expecting adoption. [E9]
Operations & Delivery	17/42 requests are re-entered and 11/42 returned. Agree acceptance and exception rules across teams, not separate local fixes. [E4]
Technology, Data & AI	13/31 tools lack a business owner; six agreements renew within 90 days. Establish record ownership and service needs before committing to a replacement. [E5–E6]
Growth, Marketing & Revenue	A separate 30-enquiry sample shows 12 booked, 7 declined and 11 unknown outcomes. Commercial lead reconciles the unknowns; do not attribute them to the handover without evidence. [E14]
Sustainability & Environment	Energy, travel and waste records were not supplied. Remains unassessed. Finance and operations agree the baseline; no emissions or maturity claim is justified. [E10]

New software changes habits, responsibilities and culture

A shared queue only works if people trust it, managers use it and the next team accepts its records. Agree the process, practise exceptions, give staff time and make concerns safe to raise. Otherwise the old spreadsheet and informal workarounds may continue beside the new tool.

What would change our mind?

Test the explanation. If clearer ownership does not reduce returns, investigate workload and scheduling. If a deputy cannot resolve an exception, revise the guide or decision rights. Build only where existing tools cannot safely carry the agreed work.

Owners: service owner tests the handover; sponsor resolves decision rights and time. Commercial and environmental evidence tasks remain separate.

05 / Organisation and ownership

Change follows the real network, not only the chart.

The shadow hierarchy is the route people actually use for help and decisions. Understand it before changing how work moves.

Recorded in the fictional survey: 31 of 74 cross-team help nominations (42%) point to three bridge roles: service coordinator, planning lead and finance analyst. Nominations are mentions, not unique people helped, hours of work or proof of overload. The diagram summarises role connections; line weight does not represent a measured workload. [E2]

The informal network will shape adoption

Three bridge roles attract 31 of 74 help nominations. People may be relying on them to cross unclear boundaries. Involve these trusted contacts in design, test cover and capture their exception knowledge. A manager announcing a new process will not automatically replace the route people trust. The nominations alone do not prove overload or resistance. [E2, E11]

Handover	Accountable owner proposed	Practical change
Customer request → planning	Head of service	Own the end-to-end request queue, acceptance rules and exception review.
Planning → workshop	Operations lead	Define a complete job pack and a deputy for scheduling decisions.
Completed work → finance	Finance lead	Agree completion evidence and one route for unresolved differences.

Support the people who make the system work

Involve the bridge roles in the pilot with protected time. Pair each with a deputy and capture decisions in the shared workflow. Do not simply route more work to the most nominated person. Invite staff to correct the map before it is used to change responsibilities.

Privacy and interpretation: a public example uses role-level, fictional data. A real report should use an agreed access model and avoid identifiable small-group reporting. Network position is not a performance rating.

06 / Knowledge, security & cover

A helpful colleague is not a resilience plan

Look at who people turn to, what knowledge is accessible and whether another person can carry the work when the usual contact is absent.

Three bridge roles31 / 74 help nominations
Usable instructions6 / 12 workflows
Rehearsed deputy4 / 12 workflows

The help network on section 5 is a nomination pattern. The cover check below uses a different source: a structured review of the 12 key workflows. A nomination does not establish dependency, workload or essentiality. [E2, E7, E11]

Workflow cover status	Count of 12	What follows
Named deputy; rehearsal evidenced	4	Keep instructions current and repeat after material change.
Named deputy; no rehearsal evidence	5	Run an exception scenario without the usual contact.
No deputy recorded	3	Agree cover before widening the service change.

Follow knowledge, not just reporting lines

In this fictional review, three cross-team workflows require decisions from more than one function. Two have no shared exception log. Capture the reason for each exception and its resolution so the next person does not have to rediscover the route. Operations owns this work. [E11]

Make the safe route easy to find

Of the 98 named survey respondents, 62 could identify the agreed security contact; 36 could not in that instrument. This is a recognition check, not proof that an incident would be reported safely. The technology lead should publish one route, rehearse a scenario and confirm out-of-hours cover. [E2 extension]

Decision	Accountable role	Evidence to close
Protect bridge roles from extra routing	Operations lead	Agreed cover, time allowance and exception ownership.
Make knowledge usable	Service owner	A deputy completes an unfamiliar case using the guide.
Check security escalation	Technology lead	Contact, deputy and response route tested without a real incident.

All roles, connections and counts are invented. Public examples stay at role or workflow level. A real engagement requires agreed access and protection against identifying small groups.

07 / Readiness & working preferences

People need room to change, not another instruction.

Most respondents understand the reason for change. Far fewer have time to learn it. A new system could feel like extra work unless managers change those conditions.

Understand the reason for change: 54 / 72
Can raise concerns safely: 39 / 72
Have time to learn new tasks: 28 / 72

Favourable means agree or strongly agree on each item. Each item has 72 valid responses from 72 anonymous respondents; 52 of the 124 people in scope did not respond. Responses may overlap between items. No team-level breakdown or individual linkage is used. [E9]

Readiness is weaker than understanding

Understanding is favourable for 54/72 respondents; learning time for only 28/72, and safe challenge for 39/72. This suggests a risk of hesitant or surface-level adoption, not proof that the whole culture is change-averse. Managers must protect time, hear concerns and remove competing work. Only nine of 12 champions have time agreed. [E8–E9]

First working preference	Count / 98 named respondents	Design response
A clear plan before starting	37	Show the purpose, boundary and next action.
Try a concrete example first	34	Offer a low-risk rehearsal with immediate feedback.
Discuss with others first	27	Allow a short peer walkthrough and questions.

These three single-choice responses are an illustrative working-style summary, not a validated personality typology. They are separate from the learning-format question on section 8 (39 guided practice, 31 written guide, 28 peer demonstration). No cross-tabulation is implied. [E2 extension]

Preferences change how we introduce the work

Personality and operating-style profiles help anticipate who wants a clear plan, a practical trial or time to discuss uncertainty. Learn this before choosing the rollout and support. Offer those routes; check with each person what helps. A preference is not competence or a fixed identity. Anonymous culture answers must never be linked back to individuals.

Owner and check: People lead agrees protected time before the pilot; sponsor reviews concerns in aggregate. Repeat the same anonymous items after the first phase, reporting coverage and any change in who responded.

08 / People and capability

Teach the changed task, not just the new software.

Only 48 of 86 participants passed a complete workflow record unaided. A new interface will not remove that support need. Design the process, practice and instructions together.

Find the correct shared file: 71 / 86
Validate a data record: 55 / 86
Handle a suspicious message: 68 / 86
Use an AI tool safely: 29 / 86
Pass a complete workflow record: 48 / 86

Recorded illustrative results: the same 86 participants attempted five independent scenarios. Each bar counts people completing that task without assistance; a participant may appear in several bars. The scenarios are not a validated ability test and should not be used to rank staff. [E3]

Prioritise the tasks the change will require

The pilot depends on finding the correct shared record, checking data quality and handing work to the next owner. Start with those tasks. The lower safe-AI result suggests a separate support need; it does not justify making AI a dependency of the service pilot.

Support need	Practical response	Check learning
Shared records and data quality	Use real-shaped, fictional job packs in guided practice.	Observe an unfamiliar example; check accuracy and safe handling.
Workflow and exception handling	Rehearse a missing field, an urgent request and an unavailable owner.	Ask staff to locate the next owner and record the exception.
Safe use of AI tools	Explain approved uses, information boundaries and human checking.	Use a new scenario, not recall of the training example.

Preferences shape delivery, not judgements

Of 98 survey respondents, 39 selected guided practice, 31 a short written guide and 28 peer demonstration as their preferred first format. Offer all three, with accessible alternatives and time to practise. Preferences can change with the task and circumstances. [E2]

Operating style is not competence. Personality or preference data must not be used to infer ability, motivation, suitability for a role or performance. Confirm an individual’s needs with them. In this example, 12 people volunteer as champions; only nine have protected time agreed, so the plan assumes nine until the remaining capacity is confirmed. [E8]

09 / Confidence & practical fluency

Design for the practical effort the work requires.

Confidence can hide a support need; hesitation can hide capability. Check real tasks before deciding how much input, training and support the change will demand.

80 matched participants	Task completed unaided	Task needed help / incomplete	Total
High confidence before the task	27	21	48
Lower confidence before the task	15	17	32
Total	42	38	80

One fictional shared-record handover task, with a pre-task confidence question. High confidence means 4 or 5 on a five-point scale. The 80 matched participants are a subset of the 86 practical participants; six additional people completed the task but lack a matched confidence answer. Thus 42 + 6 = the 48 of 86 completions on section 8. [E3 extension]

High confidence: unaided completion: 27 / 48
Lower confidence: unaided completion: 15 / 32

Typing matters when the job depends on repeated entry

Illustrative practical measure	Result	Coverage / limit
Typing speed	Median 38 words per minute	74 of 86 opted into the same short transcription task.
Typing accuracy	Median 96% character accuracy	Same 74 participants; medians are separate, not one typical person.

Typing helps reveal the effort of a keyboard-heavy task. Use it to question repeated entry, prefill known data and plan support. Device, accessibility and task context affect results; 12 people did not take the exercise. It is not intelligence, a universal speed target or a basis for individual productivity claims. [E3 extension]

Design support around the work

Offer guided practice to the 38 matched participants needing help, including 21 who felt confident. Give the 15 lower-confidence completers unfamiliar cases without labelling them incapable. People lead checks accurate handover and safe exceptions, not attendance or speed alone.

10 / Service diagnosis

Fix the handover before automating it

The request-to-schedule journey is the first pilot because it combines visible service friction, repeated entry and a manageable boundary.

RequestCustomer team
TriageService team
Job packPlanning
ScheduleWorkshop
CompleteFinance check

Clarification: incomplete information returns to the sender. Ownership gap: no visible next action when an exception occurs.

17 / 42requests re-entered

11 / 42returned for clarity

9 / 42without a clear next owner

These counts come from the same 42-request fictional sample and may overlap. They must not be added to claim 37 separate failures. The timing subset contains 24 complete requests: median elapsed time is 3.8 working days; median hands-on administration is 38 minutes. These are different measures and cannot be subtracted to infer idle time. [E4]

What the sample suggests

Information is collected before the next team’s acceptance criteria are clear. Staff then repair the job record through email or personal contact. Adding automation now could move incomplete work faster without resolving why it comes back. The first design task is a common definition of a request that is ready to schedule.

Change to test	Evidence of success	Stop or revise if
One request ID and shared status	A request can be traced through all five stages.	Teams keep a second queue because the shared one misses essential work.
Minimum job pack at acceptance	Required fields and attachments are complete at handover.	Extra fields increase collection effort without preventing rework.
Visible owner and exception route	Every live request has an owner and a next action.	Exceptions wait longer or staff bypass the route.

Pilot design

Use one site and one request type for four weeks. Include routine work and a defined set of exceptions. Retain a fallback queue, reconcile it daily, and record every bypass. Compare like-for-like requests before deciding whether the change should spread.

Proposed outcome: fewer returned handovers and shorter elapsed time, with no deterioration in safety checks, customer communication or staff effort. The target and release criteria are on section 16.

11 / Process portfolio & document health

One pilot, a wider improvement backlog

The request handover is the worked example. Mobilisation also exposes the quieter processes and missing evidence that shape delivery risk.

Opportunity / evidence	Consequence	Next decision and owner
Request → schedule: 17/42 re-entered. [E4]	Avoidable handling; unclear next owner.	Pilot first. Service owner agrees acceptance rules.
Joiner access: 4/10 sampled cases lack an approval record. [E11]	Approval cannot be evidenced; unauthorised access is not established.	Technology lead checks actual authorisation and the record trail.
Renewals: 6 agreements within 90 days. [E6]	Notice deadlines can pre-empt a useful choice.	Finance lead records decisions before notice dates.
Customer enquiry: 11/30 outcomes unknown. [E14]	Commercial learning is incomplete.	Commercial lead reconciles outcomes before setting a growth target.

Can somebody else use the documents?

Current workflow instructions: 6 / 12
Named workflow owner: 9 / 12
Rehearsed workflow cover: 4 / 12

Instructions: six current, three outdated, two confirmed absent and one not received. Those categories sum to 12. Owner and cover counts overlap with instructions; they are not additional workflows. “Not received” is an evidence gap, not proof a document does not exist. [E7, E11]

A separate request list contains 16 policies or control documents: nine current, four overdue for review and three not received. This is a document-status check, not assurance that the controls work. Technology and People leads agree an owner and review date for each gap. [E12]

Prioritise by consequence and readiness

Keep the first pilot narrow. Work on access evidence and time-sensitive renewals in parallel. Put the remaining opportunities into an owned ledger with evidence, dependencies and a decision date. Do not add their modelled benefits together until overlap has been checked.

12 / Technology estate

Make the estate governable

An inventory is only useful when it shows what each tool supports, who owns the decision and what happens when it changes or fails.

31tools recorded

18 / 31named business owners

£286,400annualised paid spend

Work coordination: 8 / 31
Service operations: 7 / 31
Corporate systems: 6 / 31
Analytics: 4 / 31
Specialist tools: 6 / 31

Ownership: 18 tools have a named business owner; 13 remain to resolve.

There are 24 paid agreements and seven tools with no direct subscription charge. Spend is the annualised committed amount in the fictional contract register, excluding VAT and internal support time. It is not total cost of ownership. The category bars count tools, not contracts or users. [E5–E6]

Three findings to resolve

Finding in the example	Meaning	Mobilisation action
13 tools lack a named business owner	Technical support alone does not decide whether a tool is still useful.	Assign business and technical ownership separately; record a deputy.
8 tools have no documented access route	Joining, moving and leaving controls cannot be evidenced from the register.	Verify the actual access process and test it on a controlled sample.
6 of 12 key workflows have current instructions	Documented cover is incomplete even where the tool itself is supported.	Write short task instructions and test them with someone other than the author.

Keep the useful capability

Map the shared queue, records, reporting and finance checks to what is already licensed. Test configuration and integration options before adding another product. Retention is conditional on support, usable access controls, exportability and an affordable way to maintain the connection.

Evidence limits: user-reported adoption is not login telemetry. A tool reported by several teams may still have low use or duplicated records. This example does not claim that every asset, integration, licence or security control has been independently verified. [E2, E5, E7]

13 / Adoption, shadow tools & decisions

Reported use is a starting point

Connect the contract register to how work happens. A licence, a survey mention and an observed task are three different kinds of evidence.

Fictional evidence layer	Coverage	What it does and does not show
Register	31 tools; 24 paid agreements	Scope and annualised commitments, not active use.
Reported current use	27 of 31 registered tools mentioned by at least one of 98 respondents	Four unmentioned tools remain unknown; do not call them unused.
Controlled task check	8 registered tools selected; 6 checked in a task, 2 not checked	All six checked tools were used in the selected task. This is not organisation-wide adoption telemetry.
Unreconciled names	4 additional tool names mentioned	May be aliases, trials or unregistered tools. Not four confirmed extra systems or contracts.

31 toolsDefined estate
27 mentionedSurvey evidence
6 observedSelected task checks

Reconcile before consolidating

The technology lead should resolve the four extra names with the reporting teams, identify the work they support and check information boundaries. Finance then confirms whether any paid commitment exists. No shadow-spend amount is added to the £286,400 register without evidence. [E2, E5–E6, E13]

Decision	Evidence required before acting
Retain or change a tool	Business owner, service need, observed task, access route and support plan.
Remove a licence	Named users or seats, contract terms, actual need and an agreed alternative.
Connect systems	Defined record ownership, failure handling, reconciliation and a tested fallback.

Accountability: Technology lead owns reconciliation; finance owns commitment evidence; service owners accept any change to their work. Popularity does not establish criticality, and a missing mention does not establish non-use.

All adoption and tool-name counts are invented. The six observed tools are a selected subset of the eight checked-in-scope tools and the 31-tool register. There is no usage telemetry or security certification in this example. [E13]

14 / Renewals and supplier choices

Use the renewal window to make decisions

Six fictional agreements represent £74,200 of annualised spend and renew within 90 days. Decide against service needs and notice dates, rather than treating renewal as an automatic purchase.

Fictional supplier and use	Annual spend	Notice by	Renewal	Decision to prepare
Deskbeam / work coordination	£18,400	Day 07	Day 17	Retain core; verify seats
Caseweave / service records	£15,600	Day 14	Day 29	Retain during pilot
Pathlog / project tracking	£12,200	Day 12	Day 42	Test overlap and export
Noteharbour / team knowledge	£10,800	Day 33	Day 63	Test coverage before change
Pulsegrid / forms	£9,400	Day 47	Day 77	Check shared queue needs
Trackmere / reporting	£7,800	Day 58	Day 88	Verify reports and owners

Day 0 is the decision baseline at the end of this illustrative mobilisation. Delivery requires a separate agreement; supplier deadlines still apply. Dates and terms are invented. Spend in this window is 25.9% of the £286,400 register; the other 18 agreements total £212,200. Notice dates precede renewal dates and must be confirmed against the signed terms in real work. [E6]

No exit without a service test

For any consolidation, confirm which work and records rely on the supplier, validate a usable export, test the replacement with the people doing the work, and cost migration and ongoing support. Do not count an avoided renewal while a necessary overlapping contract remains.

Finance lead

Check committed terms, payment schedule, price changes, notice method and approval authority. Model cash timing separately from annual run-rate savings.

Service owner

Confirm support continuity, records retention, access needs and a rollback route. A cheaper tool is not a saving if service failures or manual work replace it.

Decision posture: preserve continuity now, challenge duplication with evidence, and avoid a long commitment that pre-empts the pilot. Supplier names are invented and are not recommendations.

15 / Benefits and investment

Separate potential from money in the bank

The model makes a modest case for testing the change. It does not yet establish a positive first-year cash return or a reason to reduce staffing.

Model component	Assumption and calculation	Illustrative range
Gross recurring administration	15 people × 2 h/week + 25 other people × 0.8 h/week; 46 working weeks	2,300 h/year
Potentially recovered capacity	40–65% of gross hours after adoption and residual checks	920–1,495 h/year
Equivalent capacity value	Recovered hours × assumed £28 fully loaded hourly cost	£25,760–£41,860/year
Potential licence reduction	70–105 removable seat equivalents × assumed £120/year	£8,400–£12,600/year
First-year licence cash effect	40–70% of annual licence reduction, depending on timing	£3,360–£8,820

The two staff cohorts are disjoint. The 50 hours per week is a scenario assumption informed by fictional interviews, not a measured total from the 42-request sample. Licence candidates exclude the labour estimate. All ranges are scenarios, not confidence intervals or guaranteed savings. [E6, E8, M1]

A bounded investment case

£24,000external delivery allowance

480 hinternal time allowance

£37,440combined modelled cost

The external allowance is a fictional planning assumption, not a Yopla quotation. Internal time is valued at 480 × £28 = £13,440. The resulting £37,440 is a resource-cost estimate; it is not all additional cash spending. Recurring support, price changes and any implementation tax treatment require separate confirmation.

What finance can bank

Count only a signed reduction or terminated charge, net of replacement and exit costs, when it takes effect. The modelled first-year licence cash effect does not cover the £24,000 external allowance.

What operations can use

Use released hours to reduce backlog, improve quality or create resilience. Count capacity only when the time is demonstrably available and redirected. Do not describe it as a payroll saving.

Proposed first release: cap discovery and pilot preparation at £6,000 external spend plus 120 internal hours, within the total allowances above. Seek explicit approval for later phases after the first gate. These are example governance thresholds, not an instruction or commitment.

16 / Recommended next-stage delivery

Do the hard work before the build.

Mobilisation supplies the diagnosis and recommended priorities. A separately agreed delivery stage should earn each release through evidence, not activity.

Phase	Work and accountable role	Evidence needed to proceed
Days 1–14 Establish	Service owner: agree job pack, record owner and exception decisions. Sponsor: protect staff time. Technology lead: confirm access. Finance: meet the Day 7 notice deadline.	Named owner and deputy; accepted sample cases; role/access matrix; time booked; fallback and support route. Do not start the connection while these remain undecided.
Days 15–42 Test	Pilot lead: trial the shared queue, job pack and exception route at one site. People lead: run task-based support.	Four weeks of logs, including missing information, duplicate entry and unavailable-owner cases. Reconcile records and rehearse rollback; collect staff feedback.
Days 43–70 Extend carefully	Service owner: resolve pilot defects and extend only to comparable work. Technology lead: document access, export and support.	Comparable routine and exception cases pass; staff can use the changed route; no material service deterioration. Sponsor approves capacity and next-phase cost.
Days 71–90 Hand over	Operations lead: establish support and cover. Finance lead: verify benefits. Sponsor: approve the next quarter or stop.	Operational owner accepts support, access, deputy cover and instructions. Finance verifies benefits; sponsor funds maintenance or stops the extension.

A small scorecard that people can challenge

Measure and owner	Starting point in example	Proposed day 90 test
Handover quality / service owner	11 of 42 returned for clarification	≤15% returned in ≥30 comparable requests; report counts and exclusions.
Elapsed time / pilot lead	Median 3.8 working days; n=24	Median ≤3.0 working days in ≥30 completed comparable requests.
Business ownership / technology lead	18 of 31 tools have owners	31 of 31 have an owner, deputy and review date.
Renewal decisions / finance lead	6 agreements in 90-day window	6 decisions recorded before their notice deadlines.
Task readiness / people lead	Baseline tasks on section 8	≥80% of assessed pilot users complete changed tasks unaided on new scenarios.

Weekly review: inspect exceptions, workload, accessibility feedback and data quality alongside the scorecard. Escalate a missed renewal deadline immediately. Do not expand if safety, service continuity or information handling deteriorates, even when headline speed improves.

Day 90 decision: continue, revise or stop based on observed outcomes and total cost. There is no assumed organisation-wide software rollout in this plan.

17 / Evidence register and next decision

Trace each finding to evidence

A real mobilisation report should let its reader trace each material finding to evidence, understand the limits and see what decision comes next.

Ref	Fictional record and scope	Used for
E1	People register: 124 staff, six functions, three sites; Day 0 snapshot	Scope, hierarchy, participation denominators
E2	Survey: 98 responses; single-choice learning format; 74 cross-team help mentions	Participation, help network and preferences
E3	Practical task log: 86 participants, five independent scenarios	Task completion, training priorities
E4	Request sample: 42 records; 24 complete timing logs over six weeks	Re-entry, clarification, ownership and timing
E5	Estate register: 31 tools; owners and access process evidence	Tool counts, categories and governance gaps
E6	Contract register: 24 paid agreements; £286,400 annualised excluding VAT	Spend, renewal window and licence model inputs
E7	Workflow register: 12 key workflows; six with current task instructions	Handover design and documentation coverage
E8	Twelve structured interviews and champion availability check	Explanatory hypotheses and capacity assumptions
M1	Benefit model shown on section 15; separate time and cash calculations	Scenario ranges, investment gates and limits

Definitions that prevent misleading conclusions

Coverage is the share of the defined scope represented in a source, not proof that its answers are correct. Current instructions means reviewed against the task and usable by a second person. Annualised spend converts recorded commitments to a yearly rate; payment dates can differ. Recovered capacity is time made usable for other work, not a cash saving.

What would be needed in a live engagement

Replace every synthetic source with permissioned evidence, verify its date and scope, reconcile contradictions with staff, confirm supplier terms, and agree who may see person-level data. Have owners review the findings and record unresolved challenges. Keep a versioned decision log in yopla.app as work proceeds.

The decision requested in this example

Consider a separately agreed, bounded first delivery phase; appoint the service owner and finance sponsor and agree the Day 14 gate. Decide later phases from pilot evidence. This demonstrates the output of mobilisation: a clear starting point, transparent reasoning and a practical way to deliver and verify change.

Illustrative mobilisation example. Powered by yopla.app. All organisation and supplier data is fictional. No client findings, quotations or screenshots are reproduced.

18 / Extended evidence

The source behind each conclusion

The diagnosis is built from a defined set of fictional records. Keep the source, its coverage and its limits attached to the finding.

Ref	Synthetic source / coverage	Used for
E9	6 of 8 invited leaders; 72/124 anonymous responses. Five maturity items and three readiness items each have 72 valid anonymous answers.	Leadership, maturity perspectives and aggregate readiness.
E10	Auditor review of E1–E9 plus two planning documents; five maturity dimensions supported, environmental evidence absent.	Five explicit Yopla judgements; one unassessed dimension.
E11	12 workflow cover checks; 10 joiner cases; 3 cross-team exception routes.	Deputies, rehearsals, access evidence and shared decision logs.
E12	16 requested policies/control documents: 9 current, 4 overdue, 3 not received.	Document gaps and ownership, not control effectiveness.
E13	31-tool reconciliation; 27 mentioned; 8 selected task checks, 6 completed; 4 unreconciled extra names.	Reported use versus observed use and unknowns.
E14	30 enquiry records over six weeks: 12 booked, 7 declined, 11 unknown.	Commercial evidence gap; not a conversion forecast.

Extensions to existing synthetic sources

E2: the same 98 named respondents supply working-preference choices (37/34/27) and security-contact recognition (62/36). These are distinct questions. E3: 80 matched confidence answers within the 86 practical participants; 74 optional typing exercises. E7: the same 12 workflows now show current/stale/absent/not-received status. Existing source counts and economic assumptions remain unchanged. E4/E8: the opening email, planning-sheet and finance-record scene is an invented reconstruction of the handover pattern, not a quotation or an additional measured case.

About this example

Larkspur Works and every person, supplier, figure and connection in this report are invented. The separate Northfield programme illustrates a different fictional organisation. These examples show the approach; they do not describe a client or promise the same results.

Mobilisation output: a diagnosis, audit trail, priorities and recommended next-stage plan. Pilot delivery, integration, training and operational handover require a separately agreed next stage. Powered by yopla.app.