How Do I Move from Paper and Scattered Spreadsheets to a Web App?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

Adrian's GitHub · Adrian's LinkedIn.

Published: · Last technical review:

To move from paper log sheets and scattered spreadsheets to a web application step by step, we first identify what daily records you handle, then define who views or modifies each data point via roles and permissions, what alerts and PDF reports you need, and finally agree in writing on deliverables and prior data analysis.

Criteria: identify the record before designing the screen

Start with a document you actually use, but prepare a version without sensitive data to explain its function. I propose pointing out what it contains, who completes it, and why it is consulted later. You do not need to turn that document into an application mockup.

As preparation, separate the information from the medium. A spreadsheet may gather data belonging to different tasks, or use abbreviations known to only one person. I am not claiming that happens in your business: I propose checking it before transferring the format literally to development.

A preparation inventory

Item What is worth describing
Record Name and activity it represents
Information Data you need to use
Query Who needs to see it and for what purpose
Modification Who can enter or change it
Output Document or query you expect to obtain
Open question What you cannot yet define

The inventory is neither a database model nor a migration specification. Its purpose is to prepare the conversation so we can distinguish an information organisation problem from a request to copy documents without reviewing their usage.

My own proof: which offering responds to this need

My published service includes custom web applications to digitise daily workflows and technical records in hotels and SMEs. It describes an installable PWA on mobile and desktop with multi-site management, roles and permissions, push notifications, and PDF export. That is the substantiated offering, not an already defined migration for your records.

I can discuss those published deliverables without attributing results to your business. I do not maintain that switching to digital format eliminates errors or guarantees coordination. For your case, I need to know what you want to organise and agree in writing on what will be developed; visual similarity between a spreadsheet and a screen is not enough.

I propose that you describe a specific need and the outcome you expect to review before making a decision. A visual reference does not replace that analysis, nor does it substantiate compatibility, coverage, or results in your project.

What I propose you organise before the transition

Separate the current record from the work you want to be able to do later. As preparation, you can write down a query you need to resolve and check what information makes it possible. If you do not know why a piece of data is used, leave it as an open question rather than deciding that it should disappear or be transferred automatically.

Then distinguish user profiles: who needs to consult the records and who must enter or modify them via roles and permissions. This separation corresponds to the access item in the self-assessment.

If you operate across multiple sites, note which records belong to each centre and who must supervise them. That way you prepare the sites item of the self-assessment without anticipating access rules.

Migration and integration: needs to analyse

The base offering of a web application or PWA does not assume automatic migrations of historical data or integrations with existing spreadsheets: before including them in the scope, I need to review how your current data is structured.

Historical data import is quoted separately because I do not know its volume beforehand. Formats, data cleaning, and validation are specified for each project.

If you need to keep previous records for consultation, state this so that I can assess in writing what data is worth transferring and what could be retained as an external reference.

You can prepare the conversation by explaining what documents exist and what the purpose of keeping them in the tool would be. You do not need to attach them all to the first message. The goal is to identify what would need to be reviewed, not to transfer private information through a public channel or turn the consultation into a data delivery.

When you should NOT copy paper as is

I would not start by reproducing every single box if you do not yet know what query or action it should enable. It is best to review the workflow first. Development should not become a way of freezing decisions you still need to clarify.

Nor should you assume that a new tool is the only option. You can compare your current setup, an off-the-shelf tool, and custom development based on your requirements. This article does not prove which fits your case, nor does it declare a universal superiority of digitisation.

If you already have a PHP application running, explain it before describing the request as a new PWA. My offering includes maintenance and evolution of existing PHP. It could be a different conversation or an alternative for the same tool, not an additional service you must contract automatically.

How I propose closing the preparation

I propose drafting an end-to-end example: someone logs information, another person consults it, and you need a specific outcome. Add what part of that sequence already happens and what part you want to change.

Then use the agreements question in the self-assessment to note down what concrete deliverables, what ownership or licensing terms, and what hosting and domain management you want to set out in writing before starting development.

How to review your inventory

I propose reading the inventory with someone who actually uses those records to check whether you both understand the same thing. When a discrepancy appears, write it down as a pending decision rather than resolving it by intuition. You do not need to arrive with everything finalised: sound preparation enables you to ask specific questions. The key is not to present a habit or internal abbreviation as though it were already a defined technical requirement.

How we move from your current sheets to the written scope

Send me a description of the record you want to digitise via the form or WhatsApp, and I will reply within 24-48 business hours with an initial written diagnosis. Before programming, we agree in writing on the deliverables, timeframe, and budget (from €3,500 + VAT* for a custom web application or PWA), showing you functional progress in your browser and mobile phone.

From a log sheet to its subsequent consultation

To prepare your case, I propose that you describe the workflow you need and who is involved in it. Distinguish information that is consulted from actions that require authorisation, and point out what document or outcome you expect to review. This is a requirements proposal, not a feature attributed to an existing project or a commitment to implement.

To prepare your inventory, separate a record from a related incident: who logs the data and who must attend to the problem can be different profiles. Then explain what each person needs to consult and what part must appear in a document. I do not turn that preparation into an approved migration; it enables me to spot what content deserves review before transferring it and what decisions remain open.

Frequently asked questions

What records should I identify?

The records you want to digitise should be identified by their use: what process each log sheet represents, what fields it gathers, who enters them, and who consults or exports them to PDF. You can prepare examples without sensitive data. Before transferring historical data, I review its structure and agree on the scope of that migration separately.

How do I define the workflow?

The workflow you want to bring to a web application is defined by how it begins, the people involved, and the expected outcome. I review with you who views or modifies each data point, what site it corresponds to, and what alerts or reports you need. Then I agree on deliverables in writing, without automatically copying the current document.

Web applications and PWAs

Web applications and PWAs

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.