Everlight: the system Scanlan’s runs on.
A management platform Scanlan’s owns outright — from the first call through the arrangement, the service, the billing, and the years of care that follow. Built to retire Tribute Management Software one stage at a time, without a single risky cutover.
What changes, and why now
The first blueprint replaced one thing: the third-party “Build & Price” tool. It stopped at the edge of Tribute Management Software, and it said so plainly — regulated information stayed in TMS, where we believed it had to stay.
You have since asked whether Scanlan’s could own the whole system. We went and checked. The answer is yes, and the reason is in what we found.
Everlight is that system. It is one platform covering the full arc of a case:
- The family’s side — planning, estimates, obituaries, events, and the years of contact that come before and after a death.
- The director’s side — first call, removal, arrangement conference, vital statistics, services, disposition, and the paperwork each stage produces.
- The back office — price lists, adjustments with oversight, invoicing, cash advances, and the accounting handoff.
Everything in the first blueprint remains, unchanged and still first in line. Everlight is not a different project — it is the rest of the same one.
TMS is not holding what we thought it was holding
The original blueprint assumed death certificates were the one thing locked inside TMS — regulated, state-controlled, and out of reach. That assumption was worth checking before anyone spent money on it, so we checked it against the State of New Jersey’s own documentation.
New Jersey’s death registration system does not connect to funeral home software at all. NJ-EDRS is a state-run website. Every licensed funeral director is issued their own user ID and password, and types the record in directly. The state’s official training manual for funeral directors is, from beginning to end, instructions for typing into a web form:
We searched the full manual for every term that would indicate a software connection — import, interface, API, vendor, upload, batch, export, integration. The only data exchange described anywhere is between EDRS and the Social Security Administration. Government to government. There is no provision for funeral home software to submit anything.
The clearest confirmation is an instruction the state gives funeral homes directly:
New Jersey assumes your office keeps its own separate records and bridges the two by hand. That instruction exists precisely because nothing is connected.
What this means
When a death certificate is filed in New Jersey, your director is typing it into the state’s website using their own license credentials. TMS is not filing anything. It never was. Whatever management software Scanlan’s runs, that work happens the same way.
So there is no function inside TMS that Scanlan’s is prevented from owning. The question was never whether it is permitted — it is simply a question of what gets built, and in what order.
It also points to the single largest daily time saving available to you, which nobody has yet proposed: gather the death certificate information once, during the arrangement conference, and have it fill the state’s form for the director to review and submit. That is Stage 3.
One record, from the first call to the last anniversary
Scanlan’s currently runs on two systems that do not speak. A family’s estimate is built in FuneralTech’s tool. The case is managed in TMS. Between them sits a person retyping the same information. That gap is not a minor annoyance — it is the defect the whole platform is designed around.
Everlight treats them as what they actually are: an estimate and a case are the same record at different stages of its life. A family pricing a cremation at midnight and a director finalising that same funeral three days later are looking at one record, not two.
Why this matters more than any single feature
Because one record carries the whole arc, information is entered once and used everywhere. The name a family types into the planning portal at midnight is the same name on the Statement, on the death certificate form, on the obituary, on the prayer cards, and on the thank-you note four months later. Nobody retypes it, and nobody mistypes it on the fourth attempt.
What each person actually does
Families
- They arrive with no account required. Burial, cremation, or green burial — your Green Burial Council certification given the prominence it deserves. Everything saves as they go. Requiring a sign-up first is how the current tool loses people.
- They save or send. Saving means an email and a sign-in link — no password to invent or forget. Sending means it reaches your staff with their name, phone, and best time to call.
- They are cared for afterwards. Obituaries, service details, event invitations, and grief support all come from the same place, addressed to the same person, without anyone rebuilding a mailing list.
Directors, at the funeral home
- A dashboard of what needs attention — new submissions, today’s conferences, cases waiting on a certificate or a signature.
- The arrangement conference on screen. The family can watch the estimate update on a second screen in real time as choices are made. No whiteboard arithmetic, no surprises at the end.
- Every adjustment is accountable. A discount or price change requires a written reason and is recorded with the director’s name — a clean oversight trail, automatically.
- Vital statistics gathered once. The information the death certificate needs is collected during the conference, while the family is present and can answer. It is then ready for the state’s form rather than being chased down two days later.
- Finalising produces the paperwork. The Statement of Funeral Goods & Services, matching your current form, plus the invoice and any cash advances recorded against the case.
Directors, in the field
- First call from anywhere. A removal can be logged from a phone at a hospital, a nursing home, or a family’s kitchen.
- Chain of custody with signatures. Each transfer is recorded with who released, who received, and when — the record you want to have and never expect to need.
- Vehicles and staff assigned against the service schedule, so two funerals never quietly claim the same hearse.
The technology, in plain terms
The foundation from the first blueprint carries over unchanged. What is added is what a system of record needs and a planning portal does not.
The cloud service that hosts and runs the application.
WhyFast, reliable, scales automatically with traffic.
The framework the application is built with.
WhyIndustry standard; one codebase covers the family portal, staff tools, and field use on a phone.
The secure database holding every case, contact, price list, and record.
WhyEncrypted, backed up, with access rules enforced at the data itself rather than trusted to the application. A director cannot see what they are not permitted to see, even by accident.
Runs the work that happens on its own schedule rather than when someone clicks.
WhyFollow-up emails, accounting sync, event archiving, retention deletion. It retries on failure instead of silently giving up — which matters when the task is a family’s follow-up.
Produces the Statement of Funeral Goods & Services, contracts, invoices, and stationery as finished PDFs.
WhyBuilt to match your existing forms exactly. Because the data is already in the case, the same engine covers prayer cards and service folders without a separate vendor.
Fills New Jersey’s death registration form from the case file for the director to review and submit.
WhyThe information is already gathered. This removes the retyping, not the director — every entry is reviewed and submitted by a licensed person, as the state requires.
Sends the system’s own emails.
WhySign-in links, estimate PDFs, confirmations, follow-ups.
Your marketing and event emails, written by your team.
WhyEverlight holds the contacts and sends them across; Constant Contact remains where campaigns are composed. Keeping one source for who is who is what prevents a family receiving a newsletter three days after a funeral.
Invoices and payments flow into the accounting system your bookkeeper already uses.
WhyBuilding accounting from scratch would be a project of its own, and yours already works. Everlight feeds it rather than replacing it.
Watches the system continuously and raises an alarm when something breaks.
WhyYour work does not keep office hours. We would rather know at 3am from a monitor than at 7am from a director.
Shows how families actually use the platform.
WhyThe visibility you lose entirely today the moment somebody clicks “Build & Price”.
Privacy policy, cookie consent, and the accessibility widget already running on your main site.
WhyThe platform stays as accessible and as compliant as scanlanfuneral.com, and consistent for families who rely on the widget there.
For comparison, management software for a funeral home of Scanlan’s size is typically several hundred dollars a month, and that figure does not fall as you add locations or staff. The running cost above is the whole platform, not a per-seat licence.
What changes when the records live here
The first blueprint could make a simple promise: no Social Security numbers, no death certificate data — that information stayed in TMS. Everlight cannot make that promise, because holding those records is the entire point. So the protections have to be stronger, and stated plainly.
How information is protected
- Families never create passwords. They sign in through a link emailed to them.
- Staff sign-in requires a second verification code — the same two-factor protection banks use.
- Draft estimates are private. Staff can only see an estimate once a family chooses to send it. Someone quietly comparing cremation prices at 2am has not asked for a phone call, and knowing that is what makes families comfortable using it at all.
- Sensitive identifiers are encrypted individually, beyond the encryption already applied to the database as a whole.
- Permissions are enforced at the data, not the screen. Roles run from owner through admin, director, and staff; the database itself refuses a request outside a person’s role.
- Every access to family information is recorded — who, what, and when — in a log that can be added to but never quietly edited.
- Abandoned anonymous drafts delete themselves after 90 days.
- Families control their email. Every automated message carries an unsubscribe link, and admins can stop or adjust sends by group or by individual.
- Separate test and live environments, so nothing is ever tried out on real families.
Backups, and getting your data back
Once Everlight holds the only copy of a case, backups stop being a technical detail and become an obligation. The platform runs continuous backups with point-in-time recovery, plus a scheduled independent copy held separately from the hosting account — so a backup survives even the unlikely loss of the provider account itself. New Jersey’s record retention requirements for funeral records are what set how far back that history must reach, and we will size it to them.
Rules we build around
- FTC Funeral Rule — the platform mirrors your General Price List item for item, and every estimate carries the required wording plus clear “this is an estimate, not a contract” language. Your counsel reviews the final templates; the system is built to hold whatever wording they require.
- New Jersey pre-need rules — NJ requires prepaid funeral money to be held in regulated trusts. Everlight records pre-need arrangements; it does not take pre-need payments. That remains true unless and until Stage 7 is scoped with counsel involved from the start.
- Vital records — death certificates are filed by a licensed director, in the state’s system, under their own credentials. Everlight prepares the information and fills the form. It does not file, and it does not pretend to.
- Privacy and accessibility — iubenda maintains the privacy policy and cookie consent; the UserWay widget matches your current site.
What is entering the industry, and what it actually solves
A wave of AI-branded products is arriving in funeral service, and more will be on the floor at the October show. We looked closely at one of them — eterni, by myagentworks llc of West Orange, NJ — because it is the one your manager was introduced to, and because it is a fair representative of the category.
It is a genuinely decent product in a narrow band. It does 24/7 AI call answering in 30-plus languages, a CRM, a case dashboard, and removal fleet dispatch with live tracking and signature capture. Several ideas in it are good enough that we have folded them into this blueprint — faith-aware intake protocols, an overnight call briefing each morning, and signatures captured at each stage of custody.
What it does not do
We checked its product, pricing, security, and FAQ pages. There is no mention anywhere of death certificates, vital statistics, price lists, arrangement conferences, the Statement of Funeral Goods & Services, invoicing, accounting, pre-need, obituaries, or any connection to TMS, CRäKN, SRS, or Passare.
| Capability | eterni | Everlight |
|---|---|---|
| After-hours call answering | Yes, AI-led | Stage 5; ASD continues meanwhile |
| Removal dispatch & chain of custody | Yes | Stage 5 |
| Family-facing planning & estimates | Not offered | Stage 1 |
| Your General Price List & versioning | Not offered | Stage 1 |
| Arrangement conference & Statement PDF | Not offered | Stage 1 |
| Vital statistics & NJ-EDRS assistance | Not offered | Stage 3 |
| Obituaries & your website | Not offered | Stage 4 |
| Invoicing, cash advances, accounting | Not offered | Stage 6 |
| Replaces TMS | No — runs alongside it | Yes, by Stage 7 |
| Cost | $599–1,199/mo + setup, 6-month minimum | $120–200/mo running cost, owned outright |
The decisive point is the last two rows. A funeral home running eterni still needs TMS underneath it. So it is not a replacement for anything Scanlan’s currently pays for — it is an additional $600 to $1,200 every month, on top of the TMS licence, indefinitely. Over three years that is roughly $44,000 spent without owning anything or retiring a single existing cost.
Worth knowing as you evaluate the category: the company was founded in 2025 and its domain registered in August of that year. It names no customers, no team members, and its public pages still carry placeholder contact details. That is not a reason to dismiss it — every company starts somewhere — but routing your first calls through a new vendor’s AI is a decision about the single highest-stakes moment in your business, and it deserves the same scrutiny you would give a new director.
We can now tell you the answer to the first one for every vendor on that floor: your director still types into EDRS. No funeral software files death certificates in New Jersey, because the state does not permit software to file them. Any vendor claiming otherwise is worth a careful follow-up question.
Seven stages, each one useful on its own
Nothing here requires a cutover weekend. TMS keeps running and keeps doing whatever has not yet moved. Each stage is a fixed scope with its own deliverables, an estimate in hours, and a plain test for when it is finished. A working day means 8 focused hours.
-
1
Family portal & director workspace
60–70 hours · about 8–9 daysExactly as scoped in the first blueprint, unchanged. It is first because it delivers on its own regardless of everything that follows.
- Burial, cremation, and green burial paths with the step-by-step builder and running total
- Anonymous autosave, email sign-in links, estimate PDFs, save and submit flows
- Director workspace, roles, live conference mode, adjustments log with reasons and names
- Statement of Funeral Goods & Services matching your current form; staff two-factor sign-in
- Analytics, cookie consent, accessibility widget; the site’s Build & Price buttons repointed
Done when: a family builds and submits a real estimate, and a director runs a real arrangement conference start to finish and finalises it to the Statement PDF.
-
2
The case spine
40–50 hours · about 5–6 daysWhere the platform stops being a tool and becomes a system. The estimate becomes a case, and every way a case can begin arrives in one place.
- At-need, pre-need, and grief care case types, with conversion between them as a family’s situation changes
- One contact record per person — the same individual can be an informant on one case, next of kin on another, and an event attendee, without three separate entries
- Intake queue accepting first calls from your answering service, a web form, or a staff member directly. New calls arrive as provisional records for a human to confirm, never straight into live cases
- Duplicate detection matching on name, date of death, and place — proposing matches for a person to approve, never merging records on its own
- Case timeline: every status change, handoff, and access recorded
Done when: a first call taken after hours becomes a confirmed case in the morning without anyone retyping it, and a duplicate is caught before it reaches the live record.
-
3
Vital statistics & the EDRS assistant
30–40 hours · about 4–5 daysThe largest daily time saving in the entire platform, and the one nobody else is offering.
- Vital statistics gathered during the arrangement conference, in the order the state asks for them, while the family is present to answer
- Browser add-on for Chrome and Edge that fills the NJ-EDRS form from the case — the director reviews every field and submits under their own credentials, exactly as now
- Change detection: if the state alters its screens, the add-on stops and flags the mismatch rather than filling fields incorrectly. Staff type manually until it is updated
- EDRS case ID recorded back against the case automatically, as the state instructs you to do by hand today
- Private installation to your staff’s browsers with an install guide, plus a batch of past cases run side by side to verify accuracy before it is trusted
Done when: a director completes a real death certificate in EDRS without retyping information the family already gave once, and the case ID lands back on the file by itself.
-
4
Website, obituaries & events
40–50 hours · about 5–6 daysThe stage that ends Scanlan’s dependence on Tribute entirely. Your public website currently runs on FuneralTech — a Tribute company — which means the most visible part of your operation sits on the platform you are leaving.
- scanlanfuneral.com rebuilt on Everlight, carrying your existing design and content across
- Obituaries written from the case file and published directly — no separate system, no retyping, no waiting on a vendor
- Events published automatically, with past events archiving themselves. Grief support gatherings, seminars, and services all as one kind of record
- Newspaper and memorial-site syndication where you use it today
- Analytics finally unbroken end to end, because families never leave your own property
Done when: an obituary written during an arrangement appears on your website without anyone opening a second system, and no part of your public presence depends on Tribute.
-
5
Logistics & first call
Scoped after Stage 4Removals, chain of custody with signature capture, vehicle and staff scheduling, facility booking, and the after-hours intake question — whether that stays with ASD, moves to an AI-assisted model, or a blend of both. Deliberately scoped once you have lived on the system and know how your directors actually use it in the field.
-
6
Revenue cycle
Scoped after Stage 4Invoicing, cash advances recorded against the case, accounts receivable, insurance assignment funding, and the QuickBooks handoff. This is where the back office genuinely leaves TMS.
-
7
Pre-need
Scoped after Stage 4, with counselThe most regulated corner, and last on purpose. New Jersey’s trust requirements mean this stage is designed with your attorney involved from the first conversation rather than reviewed at the end. Once it is complete, TMS holds nothing but history.
Estimated hours, all together
Stages 5 to 7 are deliberately not priced here. Quoting them now would mean guessing at how Scanlan’s actually works in the field, what your accountant needs, and what your attorney will require on pre-need. We would rather scope them accurately later than cheaply now.
Keeping it running
This is the part the first blueprint deferred, and it cannot be deferred again. A planning portal running alongside TMS could be maintained casually. A system that files your death certificates and holds your records cannot.
Owning your software means someone maintains it — dependency updates, New Jersey rule changes, a browser update that breaks the EDRS add-on, and a failure at 3am with a family waiting. Part of what a TMS licence buys is a vendor obliged to answer that call. Replacing TMS means replacing that obligation too, and it belongs in the agreement rather than in good intentions.
- A monthly maintenance retainer covering updates, monitoring, and fixes — quoted alongside Stage 1, not after it
- Defined support hours and response times, including out-of-hours, because your work does not stop at five
- A continuity plan — what happens to Scanlan’s if we are unavailable for two weeks
- Handover terms — you own this, so it is written down exactly what you receive, and when, if the relationship ever ends
What we need from you
The build clock starts once these are in hand. Everything below comes from your side. Check items off as you gather them — this page remembers your progress.
Two further items become relevant at Stage 5 and beyond, and are listed here only so nothing arrives as a surprise: your vehicle and staff roster for scheduling, and your bookkeeper’s QuickBooks setup for the accounting handoff.
The blueprint, on one map
Everything in this document in a single view — the platform, what each part of the business does with it, what sits underneath, and the order it arrives in.