What is the difference between a contact log and a session record?

A session record describes a structured support session in detail, including the work done, goals addressed, and progress observed. A contact log is shorter and covers every contact, including quick phone calls, texts, missed visits, and drop-ins that do not amount to a full session.

How often should a contact log be updated?

In real time. Ideally within minutes of the contact. Logs written hours or days later drift in detail, lose accuracy, and become a chore. Good platforms let a worker log a contact from a phone in under a minute.

Can a contact log replace session records?

No. The two serve different purposes. The session record is for structured support activity. The contact log is for everything in between. Services that drop session records in favour of contact logs produce documentation that looks active but lacks depth.

What about missed visits and failed contacts?

Missed visits and failed contacts should always be logged. They are evidence of attempted engagement and of the service's response. An inspector who sees three missed visits followed by an adjusted support plan is looking at a responsive service. Three missed visits with no follow-up is a different story.

Is a contact log required by CQC?

The Care Quality Commission does not list contact logs as a specific requirement. It does require providers to keep accurate and contemporaneous records of care and support delivered. In practice, a contact log is the easiest way to demonstrate contact patterns, so providers adopt it by default.

Does the resident need to see the contact log?

Residents have the right to access their records under UK GDPR. In most supported housing services the contact log is available to the resident on request rather than shared automatically. Be aware that entries should be written as if the resident might read them, because they might.

What is a Contact Log and Why Do Inspectors Check It First?

Q: Why do inspectors check the contact log first?

Because it shows at a glance whether the service is in real contact with the resident. An empty contact log is a red flag even if every other document is polished. A rich contact log tells an inspector the worker and resident are genuinely engaged.

Q: What should each contact log entry include?

Date and time, the form of contact such as phone call or visit, who initiated it, a brief description of what was discussed, any outcome or follow-up, and the signed-in worker's name. Keep the language factual and short.

The contact log is the humblest document in supported housing. Three lines per entry, no subheadings, no signatures per row, no review schedule of its own. And yet it is often the first document an inspector reads, because it answers the single most important question about the service: is anyone actually in touch with the resident?

This short guide explains what a contact log is, why it matters more than its length suggests, and how to keep one that helps the service without becoming a second pile of admin.

What is a contact log in supported housing?

A contact log is a chronological record of every interaction between a support worker and a resident. Phone calls, text messages, visits, missed appointments, drop-ins, emails, and anything else that counts as contact go in the log. Each entry is short and factual: when it happened, what was said, what the outcome was, who the worker was.

It is not a session record, which describes a structured support session in depth. It is not a support plan, which sets out goals and tasks. It is the thread between them, and the evidence that the relationship between worker and resident is alive.

Why do inspectors check the contact log first?

Because it is the fastest way to tell whether the service is actually engaging with the resident. A sparse contact log with a long gap signals either a service that has lost touch with someone, or a documentation practice that does not capture what is actually happening. Either way, the rest of the inspection tends to follow that initial read.

The Care Quality Commission does not name the contact log as a required record, but inspectors know how useful it is as a lens on the service. Even where the inspector does not ask for it by name, the question of how often workers are in contact with residents comes up quickly.

What should each contact log entry include?

Keep entries short and factual. A useful minimum:

Date and time of the contact
Form of contact such as phone, text, visit, email, missed visit
Who initiated the contact
A one or two sentence summary of what was discussed or attempted
Outcome and any follow-up required
Worker name, populated automatically from the signed-in account

Good example:

15 April 2026, 14:20. Visit. Worker attended, resident not in. Note left. Follow-up phone call at 17:00, resident answered, confirmed work kept him late, rescheduled for 16 April at 16:00. JM.

Less useful example:

15/04 Quick chat with resident. Fine. JM.

The second entry may reflect a real interaction, but it tells a later reader nothing. The first entry tells a story and captures the worker's response to a missed visit, which is the content inspectors value.

How is the contact log different from a session record?

The two documents answer different questions. The session record answers what happened in a structured support session. The contact log answers how much contact the service is having with the resident, broadly.

| Feature | Contact log | Session record |

|---|---|---|

| Entries per resident per month | Often 10 to 30 | Usually 2 to 6 |

| Length per entry | One to three sentences | Several paragraphs |

| Structured fields | Minimal | Many |

| Worker signature per entry | Implicit through the system | Explicit signature required |

| Purpose | Show continuity of contact | Record substantive support work |

Services that treat the two as interchangeable tend to lose substance. The contact log is the river; the session record is the landing points along it.

How do you keep a contact log properly?

Real-time entry is the only reliable approach. A worker who tries to write up the day's contacts in the evening will miss most of them, get times wrong, and compress different contacts into single entries. Specific habits that work:

Log during or immediately after the contact. Most platforms let you do this from a phone in under a minute.
Use voice input where available. Speaking a twenty-second note produces a better log entry than a typed fragment at the end of the shift.
Log failed contacts explicitly. Missed visits, unanswered calls, and residents who decline to engage are all entries. The pattern matters.
Keep it factual. Save interpretations and reflections for the session record.
Name actions. If the contact produced a follow-up, say what and by when.

A useful rule of thumb

If a worker had a contact but it does not end up in the log, ask whether the worker could describe it accurately in three days. Usually the answer is no. The cost of a one-minute entry at the time is much smaller than the cost of losing the detail entirely.

What does a good contact log look like across a month?

A resident in active support should generate between ten and thirty contact log entries per month, depending on the intensity of the service. A handful of contacts in a month from a supposedly high-support service is a pattern worth examining. A hundred entries that are all one-word confirmations is also a pattern worth examining, because it suggests the log is being used as a presence counter rather than a record.

The shape inspectors are looking for is roughly:

A mix of planned contacts and responsive ones
Evidence that missed or failed contacts were followed up
Some variation in length and detail, reflecting real differences in what happened
A consistent worker voice across entries
No gaps longer than the service's agreed contact cadence

Data protection and the contact log

Contact log entries are personal data under UK GDPR. They are often sensitive because they describe a resident's engagement with a support service, which can indicate health status, vulnerability, or other protected characteristics. Practical rules:

Apply the same access control, encryption, and retention policies as for other resident records
Avoid naming third parties unnecessarily, especially children or other residents
Be prepared for subject access requests, under which the resident has the right to see the log
Retain entries for the documented retention period, usually aligned with the wider resident record

The Information Commissioner's Office UK GDPR guidance sets the framework.

The contact log is boring to write and rewarding to read. A service that keeps a good one rarely has to explain itself at inspection. A service that does not often spends the inspection explaining why not.

How does a platform change contact log practice?

A good documentation platform removes most of the friction that makes paper contact logs painful.

Voice entry in the browser or app turns a twenty-second note into a structured entry.
Auto-timestamping removes the temptation to round times.
Auto-attribution means the logged-in worker is always the author.
Search and filter let a manager see all contacts for a resident, all contacts by a worker, or all missed contacts in a week.
Links to the support plan and session records put each contact in the context of what the service is trying to do.
Export produces a tidy PDF of contact history when needed for audit or inspection.

A paper contact log is better than nothing. A structured digital one is a different category of tool.

Sources and further reading

A contact log that writes itself between visits

Residoc turns a quick voice note after a visit into a structured contact log entry. Ten seconds of speech, a professional record, no evening admin.

Book a demo