Tamispace · Fitzrovia, London
For the people who keep healthcare organised.
We design and build software for the administrative work behind health organisations: rotas, requests, onboarding, rooms and the reporting that ties them together. Quietly, carefully, and with a firm line between administration and care.
Who we work with
- Practice and service managers
- Rota and scheduling coordinators
- Referral and bookings administrators
- HR, onboarding and operations teams
Why we exist
The work nobody sees until it goes wrong
Behind every clinic, practice, charity or community health service is a layer of administration: who is working when, which request is with whom, which documents a new colleague still needs, which room is free on Thursday.
It is skilled work, and it is often supported by tools that were never designed for it: shared spreadsheets, colour-coded calendars, long email chains and the memory of one or two experienced people. That works until someone is on leave, a request is missed, or a rota error lands at the worst moment.
Tamispace exists to make that work calmer. We build focused software that fits the way your administrative teams already think, removes the repetitive copying and chasing, and makes the state of things visible to the people who need it, without asking clinical staff to learn yet another system.
Scope
A clear line, drawn early
What we build
- Rota, scheduling and leave tools
- Request, referral and booking administration queues
- Onboarding and staff-document workflows
- Room and equipment booking
- Operational reporting from administrative data
What we never build
- Clinical records or decision support
- Anything that diagnoses, treats or advises on care
- Software regulated as a medical device
- Patient-facing medical advice
- Emergency or out-of-hours operational systems
When a workflow touches clinical information, we design around it: an administrative tool can record that a referral was received and who owns it, without holding the clinical content itself. If the clinical content is essential, we will tell you plainly that you need a specialist clinical system instead.
Find your starting point
What would help your role first?
Choose the role closest to yours. We will show the kinds of tools that usually help most, and a question worth bringing to a first conversation.
Oversight without chasing
- A single view of open administrative tasks by team and due date
- Approval routes for leave, purchases or room changes with a clear audit trail
- Weekly operational summaries drawn from data your team already enters
A question to bring to us: Which three questions do you answer by asking colleagues every week?
Fewer late-night spreadsheet edits
- Shift and session templates with availability and leave in one place
- Swap requests that respect your rules and notify the right people
- Published rotas staff can view on their phones without editing access
A question to bring to us: What rules does your current spreadsheet enforce only because one person remembers them?
A request never lost between inboxes
- One intake queue for requests arriving by email, form or post
- Status tracking with agreed stages and owners
- Templated acknowledgements and chasers, written in your voice
A question to bring to us: Where does a request wait longest today, and who notices?
New starters ready on day one
- Onboarding checklists with document collection and reminders
- Expiry tracking for registrations and training records you are required to hold
- Clear ownership of each step across HR, managers and IT
A question to bring to us: Which onboarding step most often delays a start date?
Rooms and equipment that are where they should be
- Room and equipment booking with clear rules and conflicts shown
- Maintenance and check logs with reminders
- Simple reports on use and gaps
A question to bring to us: What do people book by word of mouth today that causes clashes?
Approach
How we work with you
- Listen. We spend time with the administrators who do the work, using fictional or anonymised examples rather than real records.
- Describe. A short written outline: the workflow, roles, data needed (and not needed), retention, and what is out of scope. Reviewed with your data protection lead.
- Build gently. Small releases, tested by the people who will use them, alongside existing processes until everyone is confident.
- Hand over and support. Training for administrators, plain documentation and support during UK working hours.

Data care
Careful with information, by design
Health organisations hold some of the most sensitive information there is. Even administrative systems carry names, contact details and sometimes the fact that a person is in contact with a service. We treat that seriously:
- Collect only what each workflow needs, agreed field by field
- Role-based access, with significant actions logged
- Hosting in the UK or EU, in accounts you control
- Retention and deletion agreed with your information governance lead
- No real records used in design or testing
We are not a certification body and do not claim to make you compliant. We work alongside the people in your organisation who are responsible for that.
Data care and boundariesDeliverables
What you receive
- A workflow outline
- Roles, steps, data, retention and exclusions, written for your managers and your DPO.
- Working software in small releases
- Each tested by the administrators who will use it.
- Plain documentation
- Guides for administrators, and a technical handover for whoever looks after the system.
- Ownership
- Code in your repository, hosting in your accounts, nothing held back.
- A support arrangement
- Weekday support with a clear distinction between fixes and changes.
Readiness
Is this workflow ready to be designed?
Eight questions about information handling. None of them asks for any real data. Tick what is already true; each unticked item shows a short note.
If you cannot list it, the first step is a data inventory for this one workflow.
Access rules are easier to agree on paper before software enforces them.
Your DPO or information governance lead should be involved from the start.
Retention is a policy decision; software can only follow it.
We build administrative tools. If clinical content is essential, a specialist clinical system is needed.
Real-looking but fictional examples let us design without seeing real patient or staff data.
Even a list of names helps us assess connections early.
An hour a fortnight from the people doing the work is enough.
0/8
Standards
Quality, in practice
- Accessible. Keyboard use, screen readers, clear contrast and readable type, checked against WCAG 2.2 AA criteria; administrators often work long days on these screens.
- Gentle on attention. Few notifications, clear states and no clutter.
- Tested with real users. The people doing the work test each release before it replaces anything.
- Reversible. We run alongside existing processes until the new one is trusted.
Aftercare
Support, during working hours
Once a tool is live, you can reach us Monday to Friday, 09:00–18:00 UK time. We acknowledge requests within one working day. We do not provide out-of-hours or emergency cover, which is why we only build administrative tools that can safely wait until the next working day; anything that cannot should not depend on us.
Support and requestsQuestions
Questions people ask us
Do you work with NHS organisations?
Will you need access to patient records?
Can you connect to our existing systems?
Are you a medical software company?
How long does a first tool take?
Tell us which part of the week is hardest.
Write a few lines about the workflow that takes the most chasing. Please do not include any patient or staff personal information. We reply within two working days.