Stop wondering if your fieldwork spreadsheet will survive review.
FieldworkLedger turns weekly ABA fieldwork rows, category decisions, supervisor approvals, and missing forms into an audit-ready ledger before certification submission anxiety hits.
Fieldwork ledger
May hours · review packet
7
gaps found
Narrow customer
BCBA candidates, RBTs, and small ABA supervisors still using spreadsheets.
Best fit: people accruing hours while working full-time, or supervisors responsible for multiple candidates without a training-ops system.
Paid problem
One silent tracking mistake can turn into months of rework or submission panic.
The cost is supervisor admin time, candidate anxiety, possible certification delay, repeated approvals, and paid review help after the spreadsheet is already messy.
Landing-page validation
One redacted weekly log in. One audit-readiness mockup out.
The waitlist tests whether candidates or supervisors will share a non-client sample and ask for a human-reviewed ledger before automation exists.
Day-in-the-life pain
You did the work. Now you have to prove the work was counted correctly.
A candidate finishes a week of sessions, indirect activities, supervision meetings, notes, and study work. The spreadsheet has rows, but the hard questions remain: is this restricted or unrestricted, did the monthly supervision requirement hold, did the supervisor approve it, and will the final packet make sense later?
Input
Weekly activities, dates, settings, supervisor, restricted/unrestricted category, supervision format, signatures, and notes from the spreadsheet or tracker you already use.
Checks
FieldworkLedger flags ratio risk, missing approvals, concentrated-hour assumptions, month boundaries, duplicate rows, stale supervisor review, and documentation gaps.
Output
A clean / risky / missing fieldwork ledger plus a supervisor review queue and a final verification packet before the candidate submits.
Why the workaround breaks
The spreadsheet knows what you typed. It does not know what is risky.
FieldworkLedger starts as a narrow review layer around the tools candidates already use. It does not replace official guidance, supervisors, universities, or clinics. It makes the fieldwork trail visible enough to ask better questions earlier.
Restricted vs unrestricted guardrails
Translate messy weekly rows into a visible category mix so candidates stop discovering ratio problems after months of work.
Supervisor approval queue
Show exactly which weeks, forms, or activities need review instead of chasing signatures through email, texts, and shared drives.
Monthly compliance snapshot
Give the candidate and supervisor a month-by-month view of hours, supervision touchpoints, concentrated assumptions, and missing proof.
Submission packet preflight
Export a human-readable packet with source rows, notes, approvals, and risk flags before the final certification application moment.
Clinic cohort dashboard
For small ABA clinics, see every supervisee as safe, watch, blocked, or review-needed without forcing a full HR/training system migration.
Evidence, not proof
Public ABA and BCBA threads repeatedly describe spreadsheets, lost forms, category confusion, and supervision-hour anxiety.
Reddit / r/ABA · fieldwork tracking
A BCBA-path user describes fieldwork logging as a full-time job on top of the actual job: messy spreadsheets, restricted vs. unrestricted calculations, supervisor approval chasing, and proof stress.
Open source →
Reddit / r/bcba · concentrated hours help
A full-time school-system candidate asks how to track concentrated fieldwork accurately, especially supervision requirements and restricted/unrestricted breakdowns.
Open source →
Reddit / r/ABA · supervisor-side chaos
A BCBA/former clinical director frames the workflow as painful on both sides: overwhelmed trainees, supervisors supporting multiple people, spreadsheets, lost forms, unclear goals, and compliance second guessing.
Open source →
Reddit / r/bcba · tracker alternatives
An RBT describes building tracker alternatives for friends because candidates were not receiving enough support when trying to track and document supervision hours.
Open source →
Objections
This is not another generic timer.
The validation offer is concrete: a redacted fieldwork-log sample becomes a risk-marked ledger mockup with missing approvals, ratio flags, and review questions.
Why not keep using a spreadsheet?
A spreadsheet can store rows. The pain in the evidence is confidence: category math, approvals, lost forms, and knowing whether the log is ready for review.
Is this a certification guarantee?
No. FieldworkLedger is a readiness and documentation layer. It helps candidates and supervisors catch gaps; certification decisions and official rules remain with the relevant board.
Is this for big ABA providers?
Not first. The first wedge is candidates, RBTs, supervisors, and small clinics that already rely on spreadsheets but need a safer weekly ledger.
Will this collect client PHI?
The validation version asks for redacted fieldwork-log structure, not client details. Early workflow samples should remove client identifiers before sharing.
Early waitlist
Send one redacted week. Get the ledger your spreadsheet should have shown.
Early users get a human-reviewed ledger mockup, a 20-minute fieldwork workflow review, and a say in whether FieldworkLedger should begin as a concierge packet, spreadsheet companion, or lightweight micro-SaaS.