HubSpot Data Management
Optimization
Standardizing TSI's File Architecture
Implement a standardized, scalable file management system that reduces
search time, eliminates version confusion, and protects client-facing materials.
The Social Institute | Data Operations
THE PROBLEM
The Current Landscape
20,000+
Individual Files in HubSpot
Many untitled, duplicated, or dormant
Wasted Search Time
Team members spend unnecessary minutes hunting for the right file among thousands of unorganized assets.
Version Confusion
Outdated drafts and duplicates create risk of distributing incorrect content to partners.
Scaling Challenges
Ad hoc storage habits that worked for a small team cannot sustain organizational growth.
"The last thing anyone needs is to spend ten minutes hunting for the right pitch deck or accidentally pulling a draft from three years ago."
THE SOLUTION
A Governed Asset Management System
Numbered Folder
Hierarchy
A 00-99 tree system that forces strategic visual ordering and departmental autonomy.
Standardized Naming
Conventions
A consistent formula ensures every file is identifiable, sortable, and traceable.
Draft vs. Client-Ready
Protection
Spatial separation of work-in-progress files from finalized, distributable assets.
This SOP is a structural intervention designed to protect brand integrity, URL stability, and SEO.
FOLDER STRUCTURE
The 00-99 Folder Hierarchy
00
ADMIN & BRAND
Brand assets, SOPs, templates
01
CURRICULUM
WinAtSocial, toolkits, educator guides
02
SALES & PARTNERSHIPS
Pitch decks, deliverables, case studies
03
MARKETING & WEB
Website assets, video library, social media
04
CLIENT SUCCESS
Onboarding, webinars, renewal assets
99
ARCHIVE
Legacy data, inactive files
Why This Works
Forced Visual Order
Numerical prefixes override alphabetical sorting. Admin stays at top, Archive at bottom.
Departmental Autonomy
Sales stays in 02, Curriculum in 01. Teams rarely cross paths, reducing accidental edits.
Intuitive Navigation
Clicking through is logical and effortless. Consistent positioning builds muscle memory.
QUALITY CONTROL
Protecting Client Materials
CLIENT-READY
Main Departmental Folders
Finalized, approved content only
Safe for external distribution
Designated "safe harbors"
_DRAFTS
Sub-Folder Within Each Department
Work-in-progress files only
Never distribute externally
Clearly separated from live assets
Spatial separation prevents accidental distribution of incomplete materials to partners.
NAMING CONVENTIONS
Standardized File Naming
[Department] _ [ProjectName] _ [Type] _ [Date] _ [Version]
Example: OPS_TimeZones_ExportedSegment_2026-02-16_v02
Department Code
Three-letter, capitalized prefix
(MKT, SLS, OPS, CUR, CS_)
Automatically groups related assets in any alphabetical list
Project Name
1-2 words, CamelCase
(DistrictNotes, Onboarding)
Answers "What is this for?" at a glance
Date (ISO 8601)
Always YYYY-MM-DD format
(2026-02-16, not 02-16-26)
Newest files always sort to the top
Version
Strict syntax: v01, v02, v03
Never "Final" or "Official"
Highest number = most current version
NON-NEGOTIABLES
Technical Specifications
Use Underscores, Not Spaces
Spaces convert to "%20" in web URLs, creating messy links that can break in emails.
File%20Name%20Final.pdf
Messy, can break links
File_Name_Final.pdf
Clean and readable
Use CamelCase for multi-word segments to maintain readability.
No Special Characters
Servers and browsers may not read these properly, leading to "File Not Found" errors for partners.
&
!
@
#
*
AVOID THESE
Allowed Characters
Letters | Numbers | Underscores | Hyphens
NEXT STEPS
Implementation & Roles
Shifting from individual storage habits to collective stewardship.
Department Heads
Data Operations
All Staff