Think of local first as a workflow choice
A local-first approach begins with the idea that receipt documents and their initial organization stay on your device by default. That can make capture feel more direct because you are working with a photo or imported file in the same place where you review it. The choice is about keeping control of the routine close to the person doing the work.
It does not remove the need for judgment. A document can be stored locally and still contain an unclear date, merchant, or total. The benefit is that you can return to the source material during review without treating every receipt as something that must travel through a remote workflow before you can decide what it means.
Capture documents in the form that arrives
Receipt records often begin as a camera image, but they may also arrive as a PDF, downloaded statement, or file shared from another app. A local-first workflow should make room for the document forms you actually receive. The important thing is to bring them into one review process rather than leave them scattered across several personal locations.
Capture speed matters because it protects context. If you can save a receipt while the purchase is fresh, you are more likely to remember the project or client connection later. The review can happen at a calmer time. Separating capture from detailed decisions keeps the process practical during a busy day.
Use review states instead of pretending everything is final
Local storage does not make OCR output or a manual label automatically complete. A clear workflow uses states such as ready, needs review, or awaiting context so you can return to the right items. These states turn a collection of documents into a manageable queue, especially when some receipts need more attention than others.
The review state should be easy to understand without a manual. If you cannot explain why a receipt is waiting, add a short note. A local-first habit works well when it leaves a visible trail of your decisions, not when it hides uncertainty inside an apparently organized folder.
Export only the records you intend to share
An export is a separate step from local capture. Before you create a CSV or Excel file, decide which receipts are ready, which period is included, and what context the recipient needs. This lets you keep the broader document collection under your own control while sharing a selected record set for a defined purpose.
A smaller intentional export is often more useful than copying every image into a shared destination. It gives the receiver a clear table while you retain the source documents and unresolved questions in your local review process. The handoff becomes a choice you make after review rather than an automatic consequence of capture.
Keep local workflow limits clear and useful
Local first does not mean isolated from every service or immune to ordinary device limitations. You still need to protect access to your device, maintain the habits that keep documents findable, and review what you plan to share. The useful promise is modest: your receipt workflow can begin with your own documents and your own review choices.
RecordSlip describes a local-first receipt process with on-device recognition by default, reviewable fields, organization, and export tools. It does not promise flawless extraction or replace professional advice. It is designed to help independent workers keep documents close while turning chosen receipts into records they can inspect and hand off deliberately.