Layout types

A collection's data can be viewed several ways. There are three layers to know: per-collection layouts, single-record views, and cross-collection dashboards.

Per-collection layouts

A collection can have one of each of these four layouts at a time — switch between them from the collection's layout tabs.

Overview

A KPI-and-recent-activity summary scoped to this one collection: a set of stat widgets plus a recent activity feed. Every collection has an Overview layout and it can't be deleted — it's the collection's landing page.

Grid

The spreadsheet view — every field as a column, every record as a row. Configure which columns are visible, sort, filter, and row density (compact or comfortable). A footer shows N records and a total under each column (sum, average, count and more, chosen per column and saved with the view). Add a record from the row under the last one or with the floating +. A Grid can also show an optional charts strip and timeline strip above the table (see Charts below).

Example: a Deals collection's Grid with the Amount, Stage, and Contact columns visible, sorted by Amount descending, filtered to Stage ≠ Lost.

Kanban

Cards grouped into columns by a select or relation field. Configure the group-by field, which field is the card's title and cover image, column order, and per-column overrides (color, a card limit, hide the column — both are saved with the view). Optionally split each column into swimlanes by a second field, and choose whether an "Uncategorized" column shows records with no value in the group-by field.

Add card sits under the last card, an empty "Uncategorized" column appears only while you drag, and a card opens from the keyboard. Cards show only the fields that have a value — an empty field or an unticked checkbox is left off, so each card reads as what's actually known.

Example: a sales pipeline Kanban grouped by Stage, with a card limit of 10 on "Proposal" and swimlanes by Owner.

List

A denser, non-tabular view: one row per record showing a title and cover field, with up to two levels of grouping (e.g. group by Owner, then by Priority within each owner), plus sort and filter. A row opens the record; list views don't edit cells in the row, so make changes in the record.

Example: a task list grouped by Owner, then by Priority, filtered to incomplete tasks.

Calendar

Calendar isn't one of the four default layouts — create one from the view switcher once the collection has at least one Date field, choosing a start date field (and optionally an end date field) up front. Like Kanban and List, it's a view kind you can create, save, and name (see Saved views below).

• Month, week, and day views, with a "Go to date" jump and a Today shortcut.
• Drag to reschedule a record by dragging its chip to a new day; drag an edge to resize a date range. Week and day views add a 24-hour time grid so timed records can be dragged and resized to the quarter-hour.
• Block height from a Duration field — when a record has a start time but no end date, point the calendar at a Duration field and each block is drawn at its true length, so a 90-minute session and a 15-minute check-in no longer look identical.
• Multiple date fields per record — plot up to 20 date fields as separate series (e.g. a "Start" and a "Review" date on the same record), each with its own color and legend label.
• Color-coding from a select field, or a fixed color per series when no color field is set.
• An Unscheduled panel lists records with no date set. Drag one onto a day to schedule it, or drag a scheduled record back into the panel to clear its date — it supports the same multi-select and right-click actions as records on the calendar.
• All-day vs. timed — drag a record onto the all-day row (or back into the time grid) to convert it, or use Convert to all-day / Add a time from its right-click menu.
• A calendar with no dates says so. If no record has a date yet, it offers to set dates in the grid or change the date field. On a date-only field, a time you drop an event on is left out, and you're told, with Include time if you can change the field.
• An empty range points you somewhere. A month, week, or day with no records says so and offers the nearest months that have some — "← Dec 2025" — so you don't have to page around looking.

Example: a content calendar with a Due date series colored by Status and a separate Published date series, plus an Unscheduled panel showing drafts that don't have a due date yet.

Size blocks from a Duration field

Plenty of collections record when something starts and how long it lasts, without a separate end date. Open the Calendar view's settings and set Duration to a Duration field, and week and day views draw each block at its real length.

• An end date field wins whenever it has a value. The duration only fills in for records where the end is empty, so you can use both on one calendar.
• It applies to records with a time, not all-day ones.
• Resizing writes back to the duration. Drag the bottom edge and the duration changes; drag the top edge and the start moves while the end stays where it is.
• A block that would run past midnight is drawn to the end of its day — it stays a single-day event rather than spilling into tomorrow.
• Records with no duration keep the default 30-minute block.

This also reaches anyone subscribed to the calendar feed: events that used to publish with no length now carry a real end time, so they appear as proper blocks in Google Calendar, Apple Calendar, or Outlook instead of bare timestamps.

Example: a coaching practice's Sessions calendar with a Duration field — 30-, 45-, 60- and 90-minute appointments each drawn to scale, and the subscribed phone calendar showing the same shape.

Share a calendar as a subscription feed

Open a Calendar view's settings and turn on Share as calendar feed. Cheqq generates a read-only link that any calendar app — Google Calendar, Apple Calendar, Outlook — can subscribe to. Subscribers see the underlying records update on that app's own refresh schedule, with no Cheqq account required.

Record views

Opening a record — rather than switching the collection's whole layout — surfaces two more views:

• Detail — the full record, in the page, a side pane or (on a phone) a sheet. All three are the same card, laid out like a form: each field's name above a box you can type in, with a hint when it's empty. There is no Edit mode — change a field where it sits. A picked option saves at once, and an unsaved edit is kept when you close the record. Fields that fill themselves read as plain text marked Auto.
• Form — an auto-generated form for creating a new record, built from the collection's field list.

A record opens on what's filled in. Empty optional fields fold away behind Show N more fields; required fields and Field Agent fields always show. A new record opens with every field you can fill in, and only fields that fill themselves — computed and attribution fields — are folded.

If you can only view the record, its values are shown the way the rest of the Wapp shows them: select options and people as chips, checkboxes as Yes or No, links you can follow, and formatted text and dates. Linked records appear as cards that can't be changed.

With a record open, Ask about this record starts a conversation about it in the Wapp's chat.

Dashboards

A dashboard is a separate, composable canvas that isn't scoped to one collection — it can combine tiles pulling from multiple collections at once. Each tile is positioned on a grid and is one of: a chart, a table, or a timeline. This is distinct from a single collection's Overview layout, which is scoped to that one collection only.

A dashboard rearranges to fit the room it has. On a wide screen you see the layout exactly as it was arranged. In a narrower window — beside the chat, say — tiles go two to a row in reading order, and on a phone they stack. Tiles can be rearranged only when the dashboard has its full width, so a narrow window never saves over your layout.

Number tiles

A number tile shows one figure, large, the way its field writes it: an amount in the field's currency, a percentage, the field's decimals, a duration. It shows the whole figure when it fits and a short one, such as "£1.3M", when it doesn't, with the exact figure on hover or focus. The (i) beside a tile's title says what the figure counts, such as Total of Value across 4 records in Leads.

Choose a date field under Trend by and the tile also compares this period so far with the same days of the last, so October 1–14 against September 1–14, as ▲ 12% vs last month, over a line of the trend behind it. Bucket by sets the period: a day, a week, a month, a quarter or a year.

Table tiles

A table tile shows every column at its natural width and scrolls sideways, with the first column pinned so you always know which row you're on. Headers are never cut short, numbers line up on the right, and linked records show their names.

Select a row to open that record over the dashboard; timeline rows open theirs too. The tile's header opens the collection or saved view it reads from, and a tile with more rows than it lists offers See all. On a phone, a table tile lists its records the way the rest of the phone layout does.

Timeline tiles

A timeline tile lists records by a date, soonest or latest first: all of them, or only what's coming up, counted from today where you are. Its title says how many it holds. When there are more than it shows, its foot reads Showing the next 50 of 312 with Show more. If the records can't be read, the tile says so and offers to try again, rather than looking empty.

Charts

Charts appear both as a Grid's charts strip and as dashboard chart tiles, and use the same options in both places:

• Chart types: number (a single stat), bar, line, donut.
• Aggregation: count, sum, average, min, or max, applied to a chosen field.
• Date bucketing (for time-series charts): day, week, month, quarter, or year.

Every chart counts every record it covers: a dashboard tile, every record its source matches; a Grid's charts strip, everything the view's filter and search match. A chart catches up within a few seconds of a change. Records group by day in your own time zone, and weeks start on Monday.

Charts read the way their fields do:

• Figures take the field's format. Axes, tooltips and a donut's centre show an amount in its currency and a percentage as one. From 10,000 up, axes and legends read short ("£120K", "1.3M"), and a tooltip has the exact figure.
• Colours follow meaning. An option wears the colour its chips have everywhere else, and options keep the field's own order. Other and Not set are grey, and the colours stay apart for colour-blind readers, in light and dark.
• A long tail folds into Other: past 6 slices on a donut, or 8 bars.
• Time reads as time. Every period shows, including ones with nothing in them, labelled the way you'd say it: Sep, 13 Oct, Mon 13, Q3.
• Totals where they help. Bars carry their values and stacked bars their totals. A donut of counts or totals shows the whole at its centre, and each slice's share in its legend.

The phone app shows the same figures as the web.

Saved views

A Grid, Kanban, List, or Calendar configuration — filters, sort, grouping or date-field series, visible columns and their widths, row height — can be saved and named, so you can switch between different slices of the same collection (e.g. "My open deals" vs. "All deals by stage") without rebuilding the configuration each time.

A collection reopens on the view you last used there. See Views for switching and arranging them.

Your changes and the shared view

A saved view has two layers.

The shared view is what your whole workspace sees. It only changes when someone deliberately saves it for everyone.

Your changes sit on top of it. The moment you adjust a filter, sort, column, or row height, that adjustment belongs to you alone — it follows you between devices and it is still there tomorrow, and nobody else's screen moves. Filtering a shared view to find one record is not an edit to that view; it's just you looking.

You'll know you're seeing your own version because the view's tab shows a small ring, and Only you see this appears beside the tabs. From there you can put your changes back for everyone, or reset yourself to the shared view.

Locked views

An admin can lock a view to fix its definition — its name, its layout, and the shared configuration everyone starts from. Locking is useful when a view is part of how a Wapp is meant to be read, and shouldn't drift because somebody rearranged it.

A lock never stops people working. Anyone can still filter, sort, and re-arrange a locked view for themselves; they just can't change it for everyone, rename it, delete it, or switch its layout. Only an admin can lock or unlock.

Continue with Relations to link collections together, or Computed fields for fields that calculate their value automatically.