Examples

13. Examples

X-Sheets ships with five ready-made public examples — complete, realistic databases you can open and explore before building your own. Each one is available in English and French, and each was designed to showcase a different set of X-Sheets features, from a minimal two-sheet tracker to a full field-service CRM.

Beyond their features, the examples show what X-Sheets is in practice (see When to choose X-Sheets):

Offline. Each example is stored on your device: browse and edit it without a network connection; your changes are synchronized when you are back online.
A hybrid spreadsheet. Each example is both a spreadsheet — a grid for fast bulk editing — and a small database — sheets linked by references, browsed through lists and forms.
Customizable. A copy of an example is yours to adapt: rename or add columns, change their types, adjust the views, filters, forms, expressions and actions until it fits your own activity.

How to open them. On the main screen, while no spreadsheet is open, tap the search icon and select the Public filter (see Getting Started). Public examples open in read-only mode — make a copy to edit the data or the configuration and use it as a starting point for your own spreadsheet.

The examples below are ordered from the simplest to the most advanced.

13.1 Home Delivery

A personal tracker for home deliveries: the shops you order from, and each order with its delivery details. The smallest example — two sheets and one reference — and the best place to start.

Delivery  →  Shop

What it illustrates:

Reference column — each delivery belongs to a shop, picked from a dropdown.
Done marker — the Delivery time date column doubles as the ✓ marker: one tap records that the order was delivered.
Quick actions — call or text the shop, and open the delivery address in the maps app.
Aggregate formulas — per shop: number of deliveries (COUNT), total spent (SUM), last order date (MAX).
Picture column — a proof-of-delivery photo on each order.

13.2 Gym Teacher — Class Register

A PE teacher managing classrooms of pupils, the physical tests they take, and each pupil’s result — with a scanned score sheet attached to every result.

Student              →  Classroom
Test                 →  Classroom
Result               →  Student, Test
Evaluation document  →  Result

What it illustrates:

Junction sheet — a Result links a student to a test, carrying its own data (score, comment).
Reference constraints — a result’s Student and Test pickers filter each other: pick a student and only that classroom’s tests are offered.
Composite unique constraint — at most one result per student per test; duplicates are rejected.
Computed averages — average score per student and per test, guarded with IF(COUNT(...) > 0, ...).
Picture columns — a photo (illustrated avatar) per student, and a score-sheet image per evaluation document.
Mandatory fields — a result cannot be saved without its score.
Quick actions — call, text, or email a pupil’s guardian.

13.3 Home Nursing

A solo home-care nurse managing patients, their prescriptions, visits, and payment schedules — a working example of a small business run entirely from a phone.

Prescription  →  Patient
Visit         →  Patient, Payment
Payment       →  Patient

What it illustrates:

Date arithmetic — a visit’s end time is computed: Visit date + Duration / 1440.
Filtered views — Next visits (End >= NOW()) and Payments due (paid date empty) keep today’s work on top.
Conditional aggregation — a patient’s outstanding balance sums only the visits whose payment is still unpaid, reaching two levels down (SUM(#Visit.Amount, ...)).
Done marker — the payment’s Paid date doubles as the ✓ marker for settled payments.
Quick actions — call or text a patient, and open their home address in the maps app for the route.
Picture column — the patient’s insurance card, photographed once and always at hand.

13.4 Real Estate — Property Sales

A real-estate agency selling properties: the portfolio with its photo galleries, the clients, and every visit and offer that follows.

Photo  →  Property
Visit  →  Property, Client
Offer  →  Property, Client (buyer), Client (co-buyer)

What it illustrates:

Dropdown lists via lookup sheets — categorical fields (property type and status, visit status, offer status) are small referenced sheets, so the picker is a validated dropdown and an in-use value cannot be deleted.
Photo gallery — each property has a child Photo sheet; every picture is synchronized for offline use in the field.
Composite unique constraint — one offer per client per property.
Two references to the same sheet — an offer has both a buyer and an optional co-buyer, both pointing at Client.
Filtered views — Next visits (Date >= NOW()).
Aggregate formulas — per property: photos, visits, offers, and the best offer (MAX).
Quick actions — call, text, or email a client; open a property’s address in the maps app.

13.5 CRM — Field Service

A field-service CRM: customers and their contacts, a product catalog, the installed base (units installed at customer sites), and the history of services performed on each unit. The most complete example.

Contact            →  Customer
Installed product  →  Customer, Product, Contact
Prestation         →  Installed product, Technician

What it illustrates:

Deep parent hierarchy — services belong to installed units, which belong to customers; the customer of a service is derived, never re-entered.
Multi-level aggregation — a customer’s service count, revenue, and last-service date are computed two relation hops away: SUM(#Installed#Prestation.Amount).
Reference constraints — on an installed unit, the Contact picker only offers the selected customer’s contacts.
Linkable references — on a contact’s form, existing installed units can be linked and detached instead of created and deleted.
Filtered views — Under warranty (Warranty end >= NOW()).
Document column — each product carries its notice as a PDF.
Lookup sheets — product category, unit status, and prestation type are validated dropdowns.
Quick actions — call, text, or email a contact; open a customer’s address in the maps app.

13.6 Which example should I look at?

If you want to see…	Open
The basics: references, done marker, actions, first formulas	Home delivery
Junction sheets, unique constraints, pictures and attachments	Gym teacher — Class register
Dates, filtered views, conditional totals — running a small business	Home nursing
Dropdown lookup sheets, photo galleries, offline media	Real estate — Property sales
Deep hierarchies, multi-level formulas, linkable references	CRM — Field service

← Back to User Manual Index