Phase 1 Β· Getting Started

Tech Spec Sheet Explained

Not a tech person? No problem. This page walks you through exactly what the Tech Spec Sheet is, what we're asking for, and who can help you find the answers.

πŸ”§ Part of your Pre-Intake homework πŸ‘₯ May involve your IT team ⏱ Needed before build begins
What is it?

A document that gathers all credentials and technical details about your library's current technology β€” so our developers have everything they need to set up your new site and connect your existing tools.

What do you do?

Fill it out to the best of your ability. You won't have every answer β€” and that's expected. Loop in your IT team or previous web vendor for the technical parts, and lean on us for anything unclear.

What's in the form?

The Tech Spec Sheet covers five key areas. Here's a plain-English explanation of each.

🌐

Domain & Hosting

Ask your IT team

Your domain name (e.g., newtonlibrary.org), where it's registered, and where your website is currently hosted. Think of this like your library's address and landlord on the internet.

πŸ–₯️

Current Website Platform

You likely know this

The CMS (content management system) your current site runs on β€” for example, WordPress, Drupal, or a custom platform. This helps us understand how to migrate your existing content.

πŸ”—

Third-Party Integrations

You likely know most

Any outside services connected to your website β€” your catalog, event calendar, newsletter, chat widget, and more. If a third-party company manages a tool on your site, we need to know about it.

Catalog / ILS Event Calendar E-Newsletter Chat Widget Analytics
β™Ώ

Accessibility & Privacy

Decision required

Whether your site currently uses an accessibility widget (like UserWay), and the status of your privacy policy. Your new site will meet ADA and WCAG standards β€” this section helps us match your existing commitments.

πŸ”‘

Access & Credentials

Ask your IT team

Login access to your domain registrar, hosting account, and key third-party platforms β€” so our team can configure everything correctly. Can't share credentials directly? We can coordinate with your vendor or IT contact instead.

Who should fill this out?

πŸ‘©β€πŸ’Ό
You (the Library Director or Project Lead)

Start the form and fill in what you know β€” your domain name, current website, and the tools your team uses day-to-day.

πŸ’»
Your IT Team or Consortium

For hosting credentials, domain registrar access, and anything technical. If your library uses a shared IT department or consortium, they're your best resource here.

🀝
Your Previous Web Vendor (if applicable)

Your current website vendor may hold credentials or configuration details that aren't immediately visible to you. A quick email asking for a handoff document can save a lot of time.

Frequently Asked Questions

How can I find this information if I don't know where it lives? +
We recommend starting with your IT team or your previous web vendor β€” they'll typically have all of it. If neither is available, your domain registrar (where you pay to renew your domain name) often has the rest. And if you're still stuck, reach out to our support team β€” we'll help you track it down.
What if we can't share access to some of this information? +
That's okay β€” we've worked with consortium partners and shared IT departments many times before. As long as you can introduce us to the right person at your IT department or vendor, we can coordinate directly with them. The key is telling us early so we can plan ahead and avoid any surprises close to your launch date.
When do you need this form filled out? +
Ideally at the very start of the project β€” the sooner we have it, the more lead time we have to track down anything that needs chasing. That said, we require it at least one week before your launch date to ensure we can stick to your schedule. Don't let it become a last-minute scramble!
What exactly is a "third-party service"? +
Any outside product or company whose tool appears on your website β€” even if you just have a little widget or embed. Common examples include your library catalog, event management software (like LibCal), your e-newsletter service (like Mailchimp), a live chat tool, social media feeds, or a donation platform. If a company sends you a monthly bill for something on your site, it probably counts.
We're not very technical. Is there someone we can talk to? +
Absolutely. Our support team is always your first point of contact and can walk you through any section of the form. We work with non-technical library teams all the time β€” you don't need to understand the technology, just help us connect with the people who do. Email us any time at support@stirlingbrandworks.com.
βœ…

Once your Tech Spec Sheet is submitted…

Our technical team reviews everything and flags any gaps. If we need a follow-up, our support team will reach out directly.

⚠️

Handle this document with care

The Tech Spec Sheet contains sensitive credentials like login information and account details. Please send your completed form only to support@stirlingbrandworks.com β€” double-check the address before hitting send. Do not email it to personal addresses or share it publicly.

How to submit your Tech Spec Sheet

1
Download the document

Click the button below to open the Tech Spec Sheet in Google Docs. Use File β†’ Download β†’ Microsoft Word (.docx) to save a copy to your computer.

2
Fill it out

Complete as much as you can, then loop in your IT team or previous vendor for anything technical. Leave a note in any field you're unsure about β€” we can help.

3
Email it to our support team

Send your completed document to support@stirlingbrandworks.com. Please verify the address carefully before sending β€” this document contains sensitive information.

Ready to get started?

Download the sheet, fill in what you know, and send it our way.