Biohazard Cleanup Software

Biohazard cleanup software for work where the record matters as much as the clean.

The call comes at any hour, the price depends on what the crew finds, and every job leaves a paper trail that has to be right. We turn that into software that prices each scene by severity, sends only certified crew, and keeps the exposure record, the waste manifest, and the family's private details on one controlled job record.

See our work

Bring one stuck workflow. Leave with a build, buy, repair, or wait recommendation.

Trusted by

Perceptional logoMusgrave GroupUrShipper logoBrux Dental SolutionsBella Skin Institute LogoEnergia RewardsDraftly logoTuneClub LogoSekou LMS logoLogo of food order management app gulaSnelwegDealsGrubly logoPSi logoInstantor Rewards logologo of Mobile app for events, membership clubs, and communitiesAldiFest retail campaign logoVidmattic logoEMS Connect logoWorx Squad logologo of Online Web App For Making Intrologo of Referral and Viral Marketing PlatformConcurrences logoGE logoTicketstop logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

The call comes at night, and the details end up in a voicemail, a notebook, and one person's memory.

02

A scene priced as a flat cleaning job loses money once crew hours, protective gear, and disposal weight are counted.

03

A technician whose bloodborne pathogen training has lapsed can still be sent, because nobody checked before dispatch.

Plain answer

RaftLabs builds biohazard cleanup software for trauma and crime scene cleanup companies where every job is urgent, regulated, and private. One record holds the call, the severity tier and price, the certified crew sent, the exposure record, the waste manifest, and the invoice, with access limited to the people who need it.

What to remember

  • Use this when the job record, not the calendar, is where the risk sits: pricing, certification, exposure records, and manifests.
  • The first release should complete one useful path, from the first call to a closed job with its paperwork signed and filed.
  • The code, cloud accounts, data, and operating notes should stay usable by another capable team.
  • Quote the team's own screens as their own scope: dispatch checks, exposure records, manifest tracking, certificate alerts, and access history are a second product, not a single admin-panel line.
  • Hire freelancers for one small, well-defined task; use one accountable agency party when the work needs coordination across screens, rules, data, and connections.

The first decision is not what to build.

It is whether software is the right answer at all. We use four possible recommendations before discussing a development scope.

  • 01

    Buy

    Choose a maintained product when it handles your severity pricing, your certificate checks, and your exposure and manifest records, and the remaining gaps can be solved with configuration, a connector, or a small process change. Paying for software you do not have to maintain is often the better trade.

    Run the build-vs-buy numbers

  • 02

    Repair

    Keep the existing system when crews and office staff still get value from it and the code can be understood safely. Start with evidence: where the code lives, how the data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live.

  • 03

    Build

    Own the system when your pricing tiers, your dispatch rules, or the record each job must leave behind shapes margin, safety, or the trust callers place in you. Start with one complete path, usually the job record from first call to closed file, and the system connections that path cannot work without.

  • 04

    Wait

    Do not turn unsettled procedures into permanent software. Settle your pricing tiers, your decontamination steps, and who may see a full job record, name the workflow owner, and measure the cost of the current paperwork before paying for a product.

Not sure which path is yours? Bring it to a 30-minute call. Leave with the answer in writing.

Fit

Custom cleanup software should earn its maintenance burden.

A feature request is not enough. The case is real when the same constraint shows up in time, errors, margin, or customer experience.

A fit

Jobs are priced, crewed, and documented in separate places, and the gaps surface when an insurer or inspector asks questions.

A general tool runs your calendar but cannot check a certificate, price a severity tier, or keep a private record private.

The organisation can name a workflow owner and what 'done' looks like for the first release.

Not a fit

A maintained product fits your pricing tiers and record rules with reasonable configuration.

The team wants software to settle procedures nobody has agreed yet.

The brief is a feature list with no user, transaction, or business result attached.

Not sure which side you are on? Use the first call to make that decision. A useful answer may be to buy, connect, repair, or wait.

Start with the operation, not the software.

A biohazard cleanup problem usually starts as a record problem. The call is taken on a phone at night. The price is worked out on site. The crew is chosen by whoever answers. The manifest is a paper form in the van. Each piece looks manageable on its own. The trouble starts when they have to agree with each other, weeks later, in front of an adjuster, an inspector, or a family asking what was done and how the waste was handled.

The work itself makes a plain job sheet fail. One scene is a single room, contained, with two technicians for half a day. Another runs across several rooms, with more crew, days of equipment time, and hundreds of pounds of regulated waste. A flat price treats those as the same job. So does a dispatch board that cannot tell a certified technician from one whose training lapsed last month.

A second product hides inside the first. The family sees a quiet, discreet service; your team lives in another: checking certificates before anyone is sent, signing off each decontamination step, closing the exposure record, chasing the signed manifest, and controlling who can open the file. Quotes that squeeze all of that into an "admin panel" line item are where budgets most often break, so we quote your team's screens as their own job, with their own users, from the start.

This is regulated decontamination work, not property mitigation. Drying a structure and removing affected material is a different trade, covered by our water damage restoration and mold remediation pages. Custom software makes sense here when one owned record can hold the call, the tier, the crew, the exposure record, and the manifest together better than a product, connector, or process change. The first release should take the smallest useful path from first call to closed job. It should not replace every tool at once.

We start where it hurts.

The dispatch board is only one part of the job. The real scope includes the pricing tiers, the certificate rules, the records each job must leave, what happens when things fail, who can see and change what, and who runs it after release.

Calls that arrive at any hour

Log every call as a ticket the moment it comes in: scene type, address, access notes, who reported it, who can approve the work, and how it will be paid for. Urgent call-outs are flagged at the top of the board. When a crew is assigned, the ticket becomes the job, with the whole first call still on record.

Scenes priced as flat cleaning jobs

Price from severity tiers your company sets. Crew hours, protective suits and chemicals used up, waste by weight, and equipment time are the lines that move the price, and they are counted on the job as it runs. When a scene turns out worse than the first call described, the tier change is recorded with a reason, so the invoice explains itself.

Crew sent without a certificate check

Hold every technician's training and certificates, with expiry dates, on their record. Dispatch checks that record before anyone is assigned: a lapsed or missing bloodborne pathogen certificate blocks the assignment, and an alert lands while there is still time to book the refresher. A double-booking check stops the same crew being promised to two scenes at once.

Exposure records and manifests in a folder

Keep the regulated paperwork on the job record itself. The decontamination checklist is worked through and signed on site, photos sit with the steps they prove, the exposure record closes with the job, and the waste manifest is tracked from sealed container to the disposal facility's signature.

Private details on a shared spreadsheet

Give each job record role-based access. Crew see the job in front of them, the office sees billing, and the full file, with the family's details and circumstances, opens only for the people you name. Every opening is logged, so discretion is something you can show, not just promise.

Which one is yours?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

Verticals

Custom software for specialised operations.

Some workflows only exist in one kind of company. The same rules apply: configure first, build only the part the maintained products cannot cover, and start with one complete path.

Trauma and crime scene work

The scene cannot be touched until it is released, and the record starts before the crew arrives. Intake holds who reported the scene, who can approve the work, and the release state, then the job carries photos, the signed checklist, and the manifest through to a file an adjuster can read without calling you.

Unattended death call-outs

These jobs are often found days later, priced on what the crew finds, and handled for a family who may be in another state. The record keeps the remote family contact, the property access notes, and the scope changes in one place, so updates to the family come from the file, not from a technician's memory.

Hoarding and heavily affected homes

A home that needs days of sorting and decontamination is priced and staffed differently from a single scene. Tiered pricing holds the multi-day crew plan, the waste volume as it grows, and the line between what is removed, what is cleaned, and what is kept, agreed with the family or the housing provider paying for the work.

Commercial incidents

A workplace, hotel, or shop needs the area decontaminated, documented, and reopened, often outside trading hours. The job record holds the out-of-hours crew plan, the clearance paperwork the business needs for its own insurer and its staff, and an invoice that separates the emergency call-out from the decontamination work.

Institutional repeat work

Property managers, housing providers, funeral directors, and insurers call again and again, each with several sites. Every site keeps its own record, access notes, and contact, and institutional accounts get the invoicing and reporting their own systems expect, without mixing one address's history into another's.

Proof

The fifth attempt became a product customers could keep using.

UrShipper had already worked with four development vendors. Its founder describes the communication and decisions during the recovery.

The case study documents a 14-week recovery, five carrier connections, a Shopify fulfilment workflow, and client-reported results. It is one comparable project, not a promise that every inherited codebase can follow the same plan.

Read the UrShipper case study

Which part of the job record is costing you the most right now?

Bring it to a 30-minute call. Leave with a build, buy, repair, or wait recommendation in writing. Free, whether or not we ever work together.

How it works

Close one expensive risk before opening the next.

Each stage answers a buyer question and leaves behind a decision you can inspect. The next stage only opens when the expensive uncertainty in the current one is small enough to accept.

  1. 01
    Understand

    Trace the real workflow

    Where is the cost or failure actually coming from?

    Follow one job from start to finish: a night call becoming a ticket, a tier being priced, a certified crew being sent, a manifest coming back signed. Include the workarounds, the paper forms, the duplicate records, and the gaps that a tidy process diagram usually misses.

    Decision produced

    A map of the workflow, exceptions, owners, systems, and the baseline cost or delay worth changing.

    Risk closed

    Paying to automate the visible symptom while the expensive constraint remains.
  2. 02
    Shape

    Choose the first useful release

    What needs to exist together for one useful result to work?

    Choose the shape from the way the work happens, not from a preferred technology. Name the pricing tiers, the certificates each job type needs, who can access what on a record, the exceptions, and the result the first release must complete.

    Decision produced

    The right mix of web, mobile, desktop, browser extension, connected device, or behind-the-scenes connection work, with the first-release boundary and a clear definition of done.

    Risk closed

    A small-looking feature list that quietly depends on several interfaces, systems, and owners.
  3. 03
    Prove

    Review working software

    Will it hold up outside a controlled demo?

    Review the product against the agreed workflow, not a tour of finished screens. Try to assign a technician whose certificate has lapsed, change a tier mid-job, and close a job with a manifest still unsigned, and see what the system does each time.

    Decision produced

    Working checkpoints tested with realistic data, real user types, system connections, recovery plans, and the people who will use or run the system.

    Risk closed

    Discovering the important gaps during migration or after customers depend on the release.
  4. 04
    Transfer

    Release, measure, and hand over

    Did the new workflow improve the original constraint, and can another capable team operate it?

    Move a controlled set of users or records first. Compare jobs closed with complete paperwork, pricing disputes, or office hours per job with the starting point before adding the next workflow.

    Decision produced

    A controlled release, comparison with the baseline, operating notes, account ownership map, and a recommendation for what should happen next.

    Risk closed

    Measuring development activity instead of the business result, or depending on the original vendor to keep the system running.

What stays out of the black box

These are operating conditions to put in the engagement, not claims to take on faith.

The scope names one complete workflow

The user, the trigger, the decisions, the data, the exceptions, and what 'done' looks like. A screen list is not enough.

Progress is visible in working software

Reviews against the product at agreed checkpoints, while there is still time to act.

A scope change has a price before it has code

A new workflow or system connection shows its effect on cost and timing before anyone approves it.

Ownership exists throughout, not only at handover

Code, cloud, data, and provider access stay visible and under your control from day one.

The work is checkable without being technical

Checkpoints are working software you use yourself, reported in plain language.

Custom software by industry.

Start from your domain. Each area below is a working practice with shipped products behind it.

What it costs

Every project starts at $10K.

The first phase turns the costliest patched workflow into a scoped build with written acceptance criteria.

Starting investment

Starts at $10K

Workflow complexity, systems to connect, data migration, and user roles set the scope. After a 30-minute call, you get a written build, buy, repair, or wait recommendation plus first-phase direction. Free, whether or not you build with us.

Build or buy

Buy an existing productBuild custom software
Best fitHandles your severity pricing, certificate checks, and record rules with reasonable setup, and its pricing makes senseThe way your company works is itself the advantage
Manual workConfiguration and process changes can remove the constraintRepeated manual paperwork on every job has a measurable cost
ConnectionsExisting connections work with reasonable setupA critical connection to your other systems cannot be done cleanly any other way
Regulated recordA general product treats the exposure record and the waste manifest as notes and attachmentsOwn custom software when the exposure record, the manifest, and the access log must be part of the job itself

Work with us

Bring one stuck workflow. Leave with a decision.

In a 30-minute call, we will help you decide whether to buy, connect, repair, build, or wait. If custom software is not the sensible next move, that is still a useful answer.

  • One named workflow owner and one complete path for the first phase.
  • Scope, price, what 'done' looks like, and exclusions agreed before paid work starts.
  • Code, cloud, data, and provider access remain under your control.
  • Post-launch warranty cover for defects in the agreed scope.

Frequently asked questions

Straight answers to what buyers ask before they scope. Still stuck? .

It is software that runs a biohazard, trauma, or crime scene cleanup company from the first call to the closed job. One record holds the call details, the severity tier and price, the certified crew sent, the decontamination checklist, the exposure record, the waste manifest, and the invoice. General field service tools handle the calendar and the invoice well; they do not handle the regulated record this work leaves behind.

By severity, not as a flat cleaning call. A small contained scene and a property affected across several rooms are different jobs: different crew size, more hours, more protective suits and chemicals used up, more waste by weight, and equipment running for longer. The software prices from tiers your company sets, with the cost lines that actually move the price: crew hours, protective gear and chemicals, disposal weight, and equipment time. When the crew finds more than the first call described, the tier change is recorded on the job with a reason, so the final invoice can be explained line by line.

Each technician carries a record of their training and certificates, including bloodborne pathogen training, with the dates they expire. When you assign a job, the system checks that record first. A technician whose required training has lapsed, or who never held it, cannot be assigned to a job that needs it. You also get a warning before a certificate runs out, while there is still time to book the refresher. This matters because a lapsed certificate on this work is not a paperwork slip. It is a health risk to the technician and a liability for the company.

Under the OSHA bloodborne pathogens standard, your company works to a written exposure control plan, and each job should show who was on site, what protective equipment they used, which steps of the decontamination method were completed and signed, and any exposure incident that happened, recorded while the details are fresh. The software keeps that record on the job itself, next to the photos and the checklist, instead of in a folder nobody can find when an insurer, an inspector, or a former employee asks for it months later.

Regulated waste leaves the site in sealed, labelled containers, and the paperwork has to follow it. The job record carries the manifest from the start: what was bagged, the container count and weight, who transported it, and the disposal facility that received it, with signatures captured at each handover. The signed copy stays attached to the job, so when a family, a landlord, or an adjuster asks how the waste was disposed of, the answer is one search away instead of a call to the hauler.

A job record in this trade holds names, addresses, and the circumstances of the worst day of someone's life. That cannot sit on a shared spreadsheet that anyone in the company can open, copy, or take home. Access is set by role: the crew see what they need for the job in front of them, the office sees billing, and the full record is limited to the people you name. The system also keeps a record of who opened each file, so access can be checked, not just promised.

The call is logged as a ticket the moment it arrives, with the details this trade cannot afford to lose: the scene type, the address and access notes, who reported it, who has the authority to approve the work, how it will be paid for, and whether the scene has been released for work to start. Urgent call-outs are flagged so they sit at the top of the board, not under tomorrow's routine work. When a crew is assigned, the ticket becomes the job, and nothing from that first call has to be typed out again.

Adjusters ask for the same set on most claims: photos before, during, and after the work, a line-by-line scope of what was affected and what was done, the crew hours and materials, and proof that regulated waste was disposed of correctly. When all of that already lives on one job record, the claim file is assembled from the record instead of rebuilt from phones, notebooks, and memory while the family waits.

Much of this work comes from the same callers: property managers, housing providers, funeral directors, insurers, and public bodies. Each one is held as an account with several sites, and each site keeps its own record, its own access notes, and its own contact. A manager with forty properties does not get one tangled file; each address stands on its own, and the history at that address stays with it.

Suits, gloves, respirators, and chemicals are used up on every scene, and on a severe scene they are a real cost line, not overhead. The software takes what the crew used off your stock as the job runs and charges it to that job, so the price you quoted and the cost you carried can be compared when the job closes. Low stock on the items a crew cannot work without is flagged before the next call-out, not discovered at the van.

No, and the difference matters. Water damage and mold work is property mitigation: drying, removing affected material, and stopping further damage. Biohazard work is regulated decontamination: certified crew only, exposure records, and waste that must be manifested to an approved facility. The two trades share vans, pumps, and some callers, but a system shaped for mitigation jobs will not check a certificate before dispatch or keep an exposure record. This page covers the decon work only.

Buy an existing product when it handles your severity pricing, your certification checks, and your manifest and exposure records, and its pricing makes sense. Build custom when the way your company runs is itself the advantage, when repeated manual paperwork has a measurable cost, or when a critical connection to your other systems cannot be done cleanly any other way. If your pricing tiers and procedures are still changing every month, wait and settle them first.

For a small, well-defined task with someone technical managing it, freelancers are often cheaper. The pattern that goes wrong is a non-technical buyer coordinating several freelancers becoming the project manager, the tester, and the person who discovers the pieces do not fit. An agency earns its fee when the work needs coordination across screens, rules, data, and connections: one accountable party, one phase price, and checkpoints against the whole workflow. If your need is one screen or one fix, hire the freelancer.

The first paid phase may cover a bounded audit, a proof of concept, a recovery plan, or a small first release. The final price depends on how deep the job record goes, how many kinds of users it serves, how your pricing tiers and certification rules are structured, what it needs to connect to, whether job history needs moving over, and the condition of any existing system. The agreed phase is priced in writing before it starts.

Timing depends on scope: a bounded audit or proof of concept is a smaller engagement, while a system covering intake, dispatch checks, job records, manifests, and invoicing takes longer. The schedule is set once the first workflow and what 'done' looks like are clear.

Yes. Takeover is a common first engagement, and it always starts with an audit: where the code lives, how your data is organized, what is tested, which outside services it depends on, who can access what, and how updates go live. Code that is understandable and fit for the next release stays; only the parts blocking reliability get replaced. And if you already paid another vendor and have nothing working, the audit tells you which story you have before you spend more: the most expensive version is the product that looks finished, clean screens and clicking buttons, while underneath nothing is tested and the important checks run in the browser, where anyone can tamper with them, instead of on the server where they hold.

Security starts with the data, the people, who can see and change what, the systems it connects to, and where it runs. A cleanup company's records hold private family details, exposure records, and signed manifests, so the scope can include role-based access, a record of who opened each file, separate testing and live environments, protected passwords and keys, activity logs, backups, and recovery plans. We write down which protections are included and which evidence your team must provide. We do not call a product compliant until the technical, operational, and legal requirements are all verified.

We need one person who owns the workflow, access to the relevant users and systems, timely answers on business rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.

Ask for the quote to name everyone who will use the system, including your own team. Every platform has two products: what customers see, and what your people use all day: checking certificates before dispatch, closing exposure records, chasing a manifest signature, adjusting a tier, and a record of who did what. When that second product is quoted as an 'admin panel' on a single line, it becomes the overrun. Our quotes treat your team's screens as their own scope, with their own users. Then the phase names the workflow, what 'done' looks like, the price, and the exclusions, all before paid work starts.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start: log a night call and watch it flag as urgent, try to assign a technician with a lapsed certificate and watch the system refuse, close a job and find the manifest and exposure record attached. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

Every launch includes post-launch warranty cover for defects in the agreed scope, release support, and small screen corrections. After that, work can continue as another fixed phase or an ongoing product engagement. The code and accounts stay under your control either way.