You can usually feel a PCN access model drifting before anyone admits it. One practice is running a strict triage gateway, the neighbour still takes walk-ins at the front desk, a third has a digital form nobody trusts, and every meeting ends with someone saying the same thing, the problem is not policy, it's agreement.
That's the job in building PCN-wide consensus on patient access. It isn't to win the argument for a favourite model, it's to get multiple practices, with different histories and different pain points, to sign up to one workable standard and keep to it.
The Access Problem No Single Practice Can Solve Alone
A single practice can change its own front door. A PCN has to deal with the consequences across several front doors at once. That's why access becomes political at network level, because one site's decision changes demand, workload, and patient expectation everywhere else.
The policy baseline already points in that direction. NHS England's primary-care recovery plan required every Primary Care Network to provide extended network appointments from 1 October 2022, with coverage set at 6.30pm to 8pm Monday to Friday and 9am to 5pm on Saturdays. The same plan says general practice in England comprises around 6,500 individual practices and delivers more than 330 million appointments a year. That scale makes it obvious why a practice-by-practice approach can't hold for long, and why PCN-level consensus matters operationally. NHS England primary-care recovery plan guide
Why consensus has to be built, not declared
PCN leaders often try to solve access in one meeting. That rarely works. What works is a short programme with a clear end point, because people need time to see the data, test the trade-offs, and decide what they can live with.
Consensus should be treated as a twelve-week build, not a sentiment. The first step is to name the tension plainly. Patients registered at different practices in the same network can get very different responses to the same problem, and that will eventually be visible to the ICB, local Healthwatch, and the practices themselves.
Practical rule: if the access model can't be explained in one sentence by every partner in the room, it isn't agreed yet.
The right framing is simple. This is not about making every practice identical. It's about agreeing a shared minimum so patients are not gambling on which surgery they belong to.
What the PCN is actually agreeing
The network is not just agreeing opening times. It's agreeing how demand enters the system, who reviews it, how urgent problems move, and what counts as unacceptable variation. Once you put that on the table, the disagreement gets more honest, which is usually the point where progress starts.
That's the roadmap this topic needs, because the hard part isn't knowing that access is broken. The hard part is getting competing practices to land on one model without pretending the differences don't exist.
Mapping the People You Need Around the Table
Start with veto holders, not just enthusiasts. In most networks, the clinical director and PCN manager convene the work, but each practice's GP partner and practice manager are the people who can block it in practice, even if they nod politely in the room.
The other obvious mistake is treating this as a digital project. It isn't. The PCN operations manager, the digital and transformation lead, the clinical pharmacist, the paramedic leads, and the ICB primary care lead all affect how the model works on the ground. So does the patient participation group chair, because a patient voice that understands the trade-offs can legitimise the plan, while a poor patient conversation can sink it.
Sort people by influence and enthusiasm
Use a simple two-by-two, high influence versus low influence, high enthusiasm versus low enthusiasm. The high-influence, low-enthusiasm people need one-to-one conversations before any open meeting. The high-influence, high-enthusiasm people can help carry the room later. Low-influence but vocal people are useful for spotting patient-facing friction, but they should not be allowed to set the architecture.
The first one-to-one should not ask, “What do you think about access?” That question gets you a polite answer. Ask instead, “What will your practice not give up?” That usually reveals the blocker, whether it's continuity, same-day autonomy, or fear of losing control of the diary.
Useful test: if someone's main worry is hidden in the second half of the conversation, you haven't asked the right first question.
Sequence matters. Talk to the sceptics first, before they harden into a public position. Then bring the enthusiasts together around what can be standardised, not around what should be idealised.
Decide who speaks for the network
A PCN without a named chair of the access workstream drifts into informal power. That's bad governance, and it's avoidable. The chair should be someone who can hold the room, keep the meeting on task, and report back without rewriting what was said.
Bring every key player into the design phase, but don't pretend they all carry equal weight. The people who sign off the model are the ones who must live with it when demand rises or a service slips. That's why the mapping exercise has to be brutally practical, not ceremonial.
Building the Evidence Base Before the First Meeting
Consensus built on anecdotes falls apart fast. One partner says the phone lines are the issue, another says online requests are the issue, and a third says patients just want continuity. The only way through that is to walk into the room with shared evidence that everyone can see, question, and improve.
The most useful pack is short and uncomfortable. Pull PCN and practice-level appointment data, GP Patient Survey access questions, Friends and Family Test themes, telephony telemetry, and online consultation patterns. If you can show when demand peaks, where requests fall off, and which channels are failing patients, the conversation gets more precise. The dashboard structure in NHS data also matters here, because it lets leaders compare totals and trends rather than rely on memory alone. NHS England PCN appointments dataset information
Present variation without turning it into a blame sheet
Use the PCN average as the reference point, then show each practice's range around it. Don't lead with league tables. You want curiosity in the first meeting, not defensiveness.
A draft evidence pack should be shared with named practice leads before the meeting, because people accept difficult numbers more readily when they've helped check them. That's where a guide to evidence based product design is useful, not as marketing copy, but as a reminder that decisions stick better when the evidence is visible and shared. guide to evidence based product design
Minimum PCN access evidence pack
| Dataset | Source | Practice-level? | Used to surface |
|---|---|---|---|
| Appointment categories | NHS data | Yes | Where demand is landing |
| GP Patient Survey access questions | Survey dashboard | Yes | Patient experience by site |
| Friends and Family Test themes | Practice feedback | Sometimes | Friction that numbers miss |
| Telephony telemetry | Practice phone system | Yes | Peaks, queueing, abandonment |
| Online consultation telemetry | Digital request system | Yes | Volume, timing, drop-off |
A practical pack does not need to be huge. It needs to be trusted. If a chart can't help the room decide what standard to set, leave it off.
Agreed Access Standards Every Practice Signs Up To
This is the point where many PCNs get vague. They say they want “consistency” and “better access”, then avoid writing down the actual rules. That's a mistake. If the standard is not written, it will be interpreted differently by every practice manager in the network.
The standards should read like a copy-and-adapt template. Set the minimum shared expectations for opening coverage, response windows, urgent routing, routine routing, and administrative queries. Keep local flexibility around appointment lengths and internal clinic templates, because forcing identical diary structures across different workforce models is a fast way to create resistance.
What should be non-negotiable
Safeguarding, duty doctor cover, and complaints handling should never be optional. Same-day escalation for clinically urgent patients also needs a clear rule, because vague wording is how patients get stuck between channels.
The working principle is straightforward. Patients should know what route to use, staff should know what happens next, and the practice should be able to show why the decision was safe. NHS England's digitally enabled triage guidance is clear that there is no contractual requirement for a total triage system, and contractual rules do not extend to using the tools when triaging patients. That matters because the model is a local governance choice, not a national mandate. NHS England digitally enabled triage guidance
Minimum PCN access standards template
| Access standard | Minimum requirement | Why practices must sign up |
|---|---|---|
| Core access | Agreed shared opening coverage | Patients should get the same basic offer |
| Urgent requests | Same-day routing and escalation | Safety depends on fast handling |
| Routine requests | Clear response window | Prevents drift and hidden delay |
| Admin queries | Named route and turnaround rule | Stops admin getting dumped into clinical queues |
| Non-digital route | Published alternative with guaranteed response | Protects patients who can't use digital channels |
| Exception handling | Logged and reviewed monthly | Keeps variation visible |
| Flexibility | Local diary template choice | Lets practices staff the standard differently |
For a six-practice PCN covering around 42,000 patients, the point is not to impose the same internal timetable everywhere. It's to make sure every site offers the same external promise to patients, even if the internal mechanics differ. That's how you reconcile stronger and weaker practices without breaking the network.
The wording the ICB usually wants is simple. The PCN agrees a shared access policy, member practices adopt it through local operating procedures, and exceptions are recorded, time-limited, and reviewed. If that sounds dry, good. Dry is what survives contract scrutiny.
Governance, Ownership and Escalation Pathways
Once the standards are agreed, ownership has to be explicit. A standard without a named owner becomes folklore, and folklore is how networks drift back into old habits.
Appoint a PCN Access Lead, ideally a practice manager or operations director with protected time, reporting to the clinical director and accountable to the PCN board. That person should hold the exception log, review pattern drift, and bring problem practices back into line before the issue becomes a patient complaint or a funding problem.
What good escalation looks like
A decent pathway is boring and fast. A practice files a short exception log each month with the reason, duration, and mitigation. The PCN Access Lead reviews it, speaks to the practice if the issue is minor, and escalates to the clinical director if the issue repeats or looks unsafe.
If the breach continues, the board has to decide whether the network is dealing with a temporary capacity problem or a refusal to work to the agreed model. The answer changes the response. Support first, then formal escalation if needed, because a standard that nobody enforces eventually stops being a standard.
Who sees what
The PCN board should receive the access summary, the exception log, and any pattern of repeated slippage. The ICB should see the agreed metrics that sit under DES and wider primary care reporting, not a mess of narrative excuses. Keep discretion at PCN level where the issue is operational. Defer to the ICB where the issue becomes contractual or system-wide.
If the board can't tell the difference between a one-off operational miss and repeated non-compliance, it isn't governing, it's watching.
The realistic goal is not perfection. It's fast visibility, fast correction, and enough escalation muscle that practices take the standard seriously the first time, not after the third reminder.
Keep the follow-up tight
Within two weeks, send two comms packs. One goes to practice teams and explains what changes, why it changes, and who owns questions. The other is patient-facing, for websites and waiting rooms, and should say the access route plainly without bureaucratic language.
At four weeks, review adoption against a small set of KPIs. Track DNA rate, time to third next available appointment, online triage completion rate, and patient survey satisfaction. Use thresholds as a trigger for review, not as a public reprimand, because the point is to correct behaviour early, not to shame teams into hiding problems.
Common PCN access pitfalls and mitigations
| Pitfall | Early warning signal | Mitigation |
|---|---|---|
| Silent workarounds | Old triage scripts reappear | Audit a sample of triage outcomes monthly and feed issues back within 48 hours |
| Demand shifting | Neighbouring practices see sudden booking pressure | Monitor cross-practice fill rates weekly and rebalance capacity through the PCN |
| Digital exclusion | Patients struggle to find a usable route | Keep a published non-digital route with a guaranteed response window |
| Dominant partner capture | Minority views disappear after the meeting | Rotate chairing, cap speaking time, and record dissent in writing |
The first month should feel controlled, not perfect. If you can see where the model is bending, you can still fix it. If you only discover the problem at quarter-end, the room has already moved on to blame.
GP Triage gives PCNs an autonomous AI triage and booking option that fits this kind of shared access model, with reporting for practice, PCN, and ICB oversight. If you're trying to move from debate to a single operating standard, visit GP Triage and ask for a demo built around your network's access workflow.