I’m trying to build an evaluation tool for shift workers, starting with nurses. To evaluate whether picking up an extra shift (OT) is worth the costs (burnout, childcare, transportation, etc). I have a spreadsheet with equations and labels; however, when I load it into Glide, I don’t understand what to do or where to start. Many of the Glide videos deal with products vs. evaluation.
Hi there, welcome to Glide’s community forum 
A few ideas to help you get started:
-
Could you share a little bit more information about what your app is supposed to do: types of users and their permissions, core features of the app, main screens, workflows and user journeys (what happens when a user does xyz), perhaps a few usage numbers (expected number of users, entries, etc.)
-
You could explore Glide University, Glide Docs, Glide’s templates.
-
Have you tried creating an app from scratch and using the AI assistant to help you get started? See point 1. above to help you define your app in a little more detail.
-
Trying to make it so users can enter numerical variables (hours, wage, fatigue%) to evaluate if it’s worth working any additional hours or shifts. Also using varibles as burnout, recovery time, direct costs to find the true value of the shift not just the related pay.
-
I am currently watching videos
-
I’m so use to the formulas in Excel and being able to apply the directly to one cell vs applying them to a column or row. Also alot of the video’s are geared toward inventory, items type applications. I trying to translate that into a evaluation type apllication.
I just ran your app feature requests in an LLM. The output is below. I didn’t review it, you could use this as a starting point if you feel like it reflects your actual needs.
1. App Summary
A mobile-friendly decision-support tool designed for shift workers (initially nurses) that helps them evaluate whether picking up an overtime (OT) shift is truly worth it — beyond just the pay. The user enters numerical variables such as hours, wage, fatigue percentage, recovery time, and direct costs (e.g., childcare, transportation). The app runs calculations to produce a “true value” of the shift, accounting for both financial and personal costs, so the user can make a fast, informed decision.
2. User Roles
- Shift Worker (Nurse) — Primary User: Enters numerical variables for a potential shift, views the calculated true value output, and decides whether to accept or decline.
- App Administrator (unconfirmed): Manages the app and updates calculation logic or variable labels if needed. (Still requires clarification — see below.)
3. Core Features
- Shift Input Form — User enters core shift variables: hours, hourly wage, and OT pay rate.
- Personal Cost Variable Inputs — User enters numerical values for personal cost factors: fatigue percentage, recovery time, and any other wellbeing-related variables from the prospect’s spreadsheet.
- Direct Cost Inputs — User enters out-of-pocket costs associated with the shift (e.g., childcare, transportation, meals) as numerical values.
- True Value Calculation Engine — App applies the prospect’s existing spreadsheet equations to all entered variables and computes the true net value of the shift — not just gross pay.
- Evaluation Result / Summary Screen — Displays a clear, easy-to-read output showing the calculated true value of the shift so the user can make a decision.
- Saved Evaluations History — User can view past shift evaluations they have run.
- User Authentication — Secure login so each user sees only their own data and history.
4. Data entities
- Users — Shift worker profile (name, login credentials, role)
- Shift Variables — Hours, wage, OT pay rate, per evaluation
- Personal Cost Variables — Fatigue percentage, recovery time, and other wellbeing inputs per evaluation
- Direct Cost Entries — Line-item out-of-pocket costs per evaluation (childcare, transportation, meals, other)
- Evaluation Records — The complete set of inputs plus the calculated true value output, stored per user
5. Integrations & External Tools
- Existing Spreadsheet (owned): Contains the core equations and variable labels that drive the true value calculation — must be reviewed and mapped into the app before build can begin.
- Glide (no-code platform): The intended build platform.
6. Clarifications Needed
Data & User Role Questions
- Spreadsheet access: Can you share the spreadsheet so we can review all the equations, variable names, and labels? This is the single most important step before we can build the calculation engine accurately.
- Single user or multi-user: Will this app be used by one person, or do you expect multiple shift workers to each have their own private accounts and data?
- Saved baseline data: Should the app remember a user’s personal defaults (e.g., their usual wage, typical commute cost) so they don’t have to re-enter them every time — or does every evaluation start fresh?
- Administrator role: Does anyone need a back-end admin view to manage users or adjust variables and calculation logic, or is that handled entirely by you as the builder?
Feature Questions
- Full variable list: Beyond hours, wage, fatigue%, recovery time, and direct costs — are there any other numerical variables in your spreadsheet that feed into the true value calculation?
- Output format: What should the result screen display? For example: a net dollar amount, a “worth it / not worth it” verdict, a score or index, or a combination?
- Direct cost categories — fixed or flexible? Are the direct cost categories (childcare, transportation, etc.) a fixed list every user sees, or should users be able to add their own custom cost types?
- Evaluation history: Should users be able to review, edit, or delete past evaluations, or is the history log read-only?
Nice-to-Have Questions
- Expansion plans: You mentioned starting with nurses — do you plan to expand to other shift worker types where the variables or calculation logic might differ by profession?
@nathanaelb Greate Job!!!