Skip to content
toandata_
PortfolioSystem overview ↓Sequence workflows ↓
Internal Systems / Technical Case Study

Event Agency
Mini-ERP.

One connected operational platform serving five core agency departments.

An internal operations platform built with Google AppSheet, Apps Script, and Google Sheets — connecting customer projects, event delivery, workforce processes, purchasing, and budget controls.

Google AppSheetGoogle Apps ScriptGoogle SheetsREST Webhooks5 Modules
System architecture ↓UML sequence workflows ↓
5
Operating modules
Sales, Ops, HRM, Proc, Fin
6
UML workflows
Sequence diagram explorer
GPS / IP
Attendance tracking
Geofenced check-in rules
Daily
Team utilization
All agency staff active
01 / System overview

How the modules connect.

A single project record connects commercial work to execution, purchasing, and financial control. HRM supplies workforce context.
Figure 01 · Five-module system architectureConceptual data & process relationships
Sales→Operation→Procurement↔FinHRM · shared staff and assignments
02 / Real application

The app behind the architecture.

The actual AppSheet home screen. Its five operational areas match the architecture and module diagrams shown on this page.
Event Agency Mini-ERP / AppSheet Home
REAL APPLICATION
Figure 02 · Actual internal AppSheet home screenOriginal application capture · No synthetic mockup
03 / Module breakdown

Inside each module.

Explore one data model at a time. Each diagram shows the module’s application views, key entities, workflow, and cross-module dependencies.
Commercial operations

From account to project.

Customer records, booking requests, project ownership, and a shared CRM interaction history.

Customer 360°Booking workflowBulk account handover
Explore another module
MODULE WORKFLOWS / UML SEQUENCE DIAGRAMS

How each module works.

Explore how business users, AppSheet, Apps Script and Google Sheets interact across the Mini-ERP.

5 modules + 1 cross-module flow
SALES & CRM / PROCESS WALKTHROUGH

Customer relationship → project → booking → structured handover

Conceptual sequence Illustrative workflow; implementation not independently audited

PARTICIPANTSSales / AMAppSheetGoogle SheetsApps ScriptNew Account Owner1Create or updatecustomer2Save customer &contacts3Create project andbooking4Persist linked records5Start bulk ownerhandover6Apply reassignment7Send groupednotificationSequence steps are based on project documentation; diagram is not a live execution trace.
↔ Scroll horizontally to inspect the complete diagram on smaller screens · Click a numbered arrow for the matching step

Sequence walkthrough

7 interactions
Data touchpoints KHACH_HANG · DANH_BA_KH · DU_AN · BOOKING · NHAT_KY_CRM
Action Notification / response

These diagrams communicate documented workflows and intended integrations. They do not assert that in-development functionality is live or that the arrows represent measured runtime execution.