CPD spreadsheet or app: should you build your own?

Building can be rewarding in its own right. If you enjoy experimenting and want a particular way of working, a personal app may be a good project. If your priority is recording learning and developing reflections, HandyCPD gives you an existing set of tools to use and assess.

This guide is written by HandyCPD. It explains the reasons to consider our app alongside the flexibility of a spreadsheet or a tool you build yourself. The right choice depends on the capabilities you need and the work you want to take on.

Keep a spreadsheet

Choose your own columns, keep an activity list and link to supporting files. This can work well if you maintain it consistently and are comfortable organising reflections and evidence yourself. You control the structure and the filing habits around it.

Build your own app

Design the fields, screens and prompts you want. You can start small and add capabilities as you need them. You also take responsibility for checking how it handles records, files, access and recovery, and for maintaining it as the software changes.

Use HandyCPD

Start with connected CPD logging, an evidence library, AI enrichment and guided reflection. You learn the workflow and review your records; HandyCPD provides and maintains the application. Check the current plans for features and capacity that suit your use.

Yes. With AI coding tools such as Codex, you can describe what you want, work through changes and get help writing and checking code. Vibe coding makes it more approachable to turn an idea into a prototype, even if you would not choose to write every part yourself.

A sensible first version might let you enter an activity, add a date and learning note, list saved entries and export a readable copy. You could tailor it to a particular role or a way of reflecting that you already use. Start with invented records so you can experiment without relying on the prototype for important information.

You do not have to recreate every feature of HandyCPD. The comparison changes when you want attached evidence, reliable access across devices, AI enrichment, guided reflection and an organised portfolio to work together. Those capabilities bring design decisions, testing and ongoing maintenance alongside the code.

Keeping records and evidence reliable

An entry needs to survive editing, reopening and software updates. Attachments need to remain linked to the correct activity. Exports need to preserve the wording and details you reviewed. You also need a way to recover records if a device, file or service fails. Check those journeys with sample data, including a backup you can actually restore.

Protecting the information you keep

A local app and an online service need different arrangements. Consider access to the device, who can open records and files, what leaves the app for AI processing, and what happens when access is removed. For an online app, a sign-in screen is only part of the work: requests for individual records and attachments also need appropriate access checks.

These are responsibilities you can address in a DIY app. They remain part of maintaining it as features and dependencies change. Keep confidential case material and unnecessary identifying information out of CPD notes whichever tool you choose.

Making AI useful throughout the workflow

Generating text is one part of an AI-assisted CPD tool. You also need to decide what source material it can read, show when reading is incomplete, preserve the user's corrections and keep suggested learning separate from facts about an activity. Guided reflection adds stages, choices and a route back to earlier thinking.

AI coding tools can help with this work, but you still need to define the behaviour you want and assess the results. Include time for checking failures and fixing regressions, as well as the cost of any hosting, storage and AI services your design uses.

HandyCPD's value is the connected workflow: capture an activity, develop the learning, keep its evidence available and review a record you can use later. You can start using those capabilities without first building and maintaining the application around them.

The Reflection Engine: develop your thinking in stages

The Reflection Engine guides you through approaches such as Rolfe and Gibbs. It uses your activity, notes and available evidence to suggest ideas for you to consider. You select what fits, reject what does not and develop the reflection in your own words.

With Rolfe, you explore what happened, why it matters and what follows. Selected insights from earlier stages help shape the next stage, and you can review and edit the resulting draft before approving it. Recreating that experience means designing how the stages, saved choices, context and final draft work together.

A brief activity does not always need a fuller reflection. Use the depth that helps you understand the learning and meets the requirements that apply to you.

AI enrichment: turn rough material into a draft you can review

In Plant a Seed, your notes and readable supporting material can help shape activity details and a draft learning summary. Suggested topics and standards links can help you organise the record and consider its relevance to supported professional frameworks.

That enrichment gives you material to work with. Check the details, correct suggestions and keep only wording that represents your learning. Reading-status information helps you see whether attached material was read or only partly processed; a stored file is not necessarily a file the AI could read. The file-reading guide explains those limits.

Evidence, review and exports in the same system

The Evidence Library keeps supporting files connected to records. Activity views help you find entries, CPD Analytics helps you explore patterns, and PDF exports provide copies to review and retain. Practice-hours and feedback workflows are also available for professionals who need them.

HandyCPD uses authenticated access and ownership checks for records and stored files. Draft review and editing steps keep you involved in AI-assisted content. Those protections and workflows are part of the application we maintain; you remain responsible for choosing appropriate material and checking your records.

Imagine a professional who discussed presenting complex information with a colleague. Their note says: “I tend to explain every detail before stating the main point. Next time, I want to start with the decision the audience needs to make.” They also have a slide deck they are permitted to store. This is a fictional example, with a planned change rather than an outcome already achieved.

In a spreadsheet

Add a row with the date, activity, learning point, evidence location and next action. Keep the slide deck in a named folder and link to it. If you want a fuller reflection, write it in a linked document or a suitable field and keep the references consistent.

In your own app

You might build those fields into a form, then add an attachment and reflection prompts. Decide how you will save the draft, return to it and export it. If you add AI, check that it preserves the planned change instead of claiming that the presentation has already improved.

In HandyCPD

Start with your note in Plant a Seed and attach the permitted material. Review the proposed activity details and learning summary. If you want to explore the experience further, use the Reflection Engine to consider why you lead with detail and what a different opening could achieve. Select ideas that fit your experience, then review the draft and keep the next presentation clearly marked as a plan.

Each approach can hold a useful record. HandyCPD brings the capture, enrichment, reflection and evidence steps together so you can try that process without developing those features yourself.

If you reliably maintain a spreadsheet and can find your evidence and learning notes, there may be little reason to replace it. Start with fields you actually use: date, activity, learning point, relevance, evidence location and next action. Add duration or other details where useful or required.

Notes and folders can support that system

You may prefer free-form writing to a structured reflection tool. Keep a date and a clear title on each note, with a reference to its source or supporting evidence. Our digital organisation guide shows a routine you can use with folders, a spreadsheet or an app.

For HCPC registrants, the official recording guidance allows flexibility in personal record format. Follow your profession's instructions for any formal submission; choosing an app does not replace those requirements.

Bring one recent activity to HandyCPD before committing to a larger build. Use material suitable for the service, review the AI enrichment and explore the Reflection Engine if deeper reflection would help. Then find the evidence again and check the record you would retain.

Ask what you would want to build differently and which existing capabilities you would otherwise need to recreate. Include your setup and maintenance time in the comparison, alongside subscription or running costs. You do not need every feature to benefit from having the parts you use already connected.

Explore HandyCPD for free and check current plan options for the features and capacity you need. If you move records, start with a small set and keep the originals until you have checked the new copies. Use the CPD records checklist for a final content review.