How to Name Tables, Fields and Apps Consistently

Good naming conventions for internal systems are invisible when they work and expensive when they do not. Names are read far more often than they are written.

What inconsistent naming costs

It is a small tax paid constantly by everyone except the person who chose the names.

Two tables with similar names holding different things
Fields named after the form rather than the data
Apps named for the project that created them
Search returning results nobody can distinguish

Conventions worth adopting

Tables are plural nouns — clients, payments, suppliers
Fields describe the data, not where it came from
Apps describe the job, not the department that requested them
Statuses are states, not instructions
Connected fields are named after the entity they point to

How to apply them in Jestor

Name tables in Jestor for the entity they hold, in the plural.
Name connected fields after the related entity — supplier, cost centre, client.
Set the label field on every related table so selection shows names rather than IDs.
Group related tables and apps into a folder per process.
Use the action bar to check whether a similar name already exists before creating.

Why choose Jestor for a navigable workspace?

Jestor shows an app's underlying tables in its editing view, which means a well-named structure is self-documenting for whoever inherits it.

Folders, the side menu hierarchy, and favourites all depend on names being distinguishable — conventions are what make navigation scale past a handful of apps.

Frequently Asked Questions

Should tables be singular or plural?

Plural, since they hold many records. See jestor.com.

What should a connected field be called?

The entity it points to, such as supplier or cost centre.

How do I check for a duplicate name?

Search the action bar before creating.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,