Custom GPT: A Company Policy and Vendor Assistant for Office Managers

What This Builds

A custom version of ChatGPT that already knows your employee handbook, your preferred vendor list, and your standard procedures before you type a single word. Instead of re-explaining the remote work policy or the PTO carryover rule every time you draft a staff email, you ask your assistant directly and it answers from the documents you gave it. Every reply comes out consistent with what's actually written down, not whatever the office manager remembers off the top of their head that day.

Prerequisites

• Plus subscription ($20/month). Building a Custom GPT requires a paid plan, though anyone you share the finished GPT's link with can use it on a free account
• Digital copies of the documents you want it to know: employee handbook, vendor list, standard operating procedures, or any policy documents you reference often
• 1-2 hours of uninterrupted time to build, configure, and test it
• Total ongoing cost: $20/month/month for your own account. Free for staff who only use the shared link

The Concept

Think of a Custom GPT as an assistant you only have to train once. A new employee would need weeks to learn your vendor contacts, your PTO policy, and how you phrase a reminder email. A Custom GPT reads all of it the day you upload it and never forgets. You're not teaching it to think differently. You're handing it the reference material every regular ChatGPT conversation is missing, so it stops guessing and starts citing your actual policy.

Build It Step by Step

Part 1: Gather your source documents

Pull together the documents you reference most often when drafting staff communication or checking a policy detail:

• Employee handbook or policy manual (PTO, remote work, dress code, whatever you have written down)
• Preferred vendor list with contact names, contract terms, and reorder thresholds
• Any standard operating procedures you've already written (onboarding checklist, emergency procedures, expense approval steps)

Save each as a PDF or Word document. If a policy only exists as an old email thread or someone's memory, write it down first. A Custom GPT can only answer from what you give it.

Before you upload anything: vendor lists often include negotiated pricing or contract terms you wouldn't want outside the company, and a handbook can reference salary bands or other sensitive terms depending on how yours is written. Skim each document before uploading and strip anything tied to an individual employee's pay, performance, or personal details. If you're unsure whether a document is fine to upload, check with whoever owns your data or confidentiality policy first.

Part 2: Start building the Custom GPT

ChatGPT's Custom GPT builder lives under the "Explore" or "GPTs" area of the app, with a "Create" option that opens a configuration screen. Menu names and exact placement shift between ChatGPT updates, so look for wording like "My GPTs" or "Create a GPT" in the sidebar or account menu rather than a fixed click path. Open the Configure tab once you're in the builder. You'll see fields for a name, a description, instructions, and a place to upload files.

Part 3: Write the configuration

Name: Something staff will recognize, like "[Your Company Name] Office Assistant"

Description: "Answers questions about our employee handbook, vendor list, and office procedures. Drafts policy reminders and vendor emails in our standard tone."

Instructions (copy and customize with your own company name and tone):

You are an office assistant for [Company Name], a [size]-person [industry] business. You have been loaded with our employee handbook, vendor list, and standard operating procedures.

When answering a policy question:
1. Answer from the uploaded documents first. Quote or closely paraphrase the relevant section.
2. If the documents don't cover the question, say so plainly instead of guessing. Suggest the office manager confirm with leadership or HR.
3. When drafting a staff email or announcement, match a [friendly and direct / formal and concise] tone.
4. When asked about a vendor, pull their contact details and any contract terms from the vendor list before answering.

Do not invent policy details, contract terms, or dollar figures that aren't in the uploaded documents.

Adjust the bracketed tone description to match how your company actually writes to staff.

Part 4: Upload your documents

Look for the Knowledge or file upload section of the same configuration screen and add your handbook, vendor list, and procedure documents there. Wait for each file to finish processing before moving to the next one. Uploaded documents work best as text-based PDFs or Word files rather than scanned images, since a scanned page can't be searched or quoted accurately.

Part 5: Test it before relying on it

Switch to the preview or chat pane next to the builder and ask it real questions you'd actually need answered:

• "What's our policy on PTO carryover into the new year?"
• "Who's our contact at [a vendor from your list], and what's the reorder threshold?"
• "Draft a reminder email to staff about the updated remote work policy."

Check every answer against the source document. If it gives a confident answer that isn't actually in your handbook, that's a sign the file didn't upload cleanly. Remove it and upload it again.

Part 6: Decide who else needs it

If only you will use it, you're done after testing. If you want your admin team to use it too, most builders include a share option limited to people with the link, so you're not publishing it for anyone to find. People you share it with can use a free ChatGPT account to open a shared Custom GPT. They don't need their own paid plan.

Real Example: A Policy Question at 4:45 PM on a Friday

Setup: You built the assistant with your employee handbook, a vendor list of 12 suppliers, and your onboarding checklist template.

Input: A staff member emails asking whether they can carry over unused PTO into next year, and how much. You don't remember the exact number off the top of your head, and HR isn't a department here, you're it.

You ask the assistant: "What's our PTO carryover policy? Draft a short reply to a staff member asking about it."

Output: The assistant quotes the exact carryover cap from your handbook, then drafts a two-sentence reply confirming the policy and reminding them of the deadline to request it.

Time saved: What used to mean digging through a shared drive folder for the handbook PDF and searching for the right section, several minutes lost each time this comes up, now happens in a single question with the reply already drafted.

What to Do When It Breaks

• It gives an answer that isn't in your documents → Ask it directly to quote the source line it's using. If it can't, the document likely didn't process correctly. Remove and re-upload it, and confirm it's a text-based file rather than a scanned image.
• It answers with outdated information after a policy change → The old document is still sitting in its knowledge base. Delete the outdated file and upload the new version, then retest with a question that touches the changed policy.
• Staff can't find the shared link → Save it somewhere permanent, like a pinned message in your team chat or a bookmark on the shared office computer, rather than a one-time email that gets buried.
• It starts giving generic advice instead of your company's specific policy → This usually means the instructions field is too vague. Go back and add a line telling it explicitly to answer only from the uploaded documents and to say when something isn't covered.

Variations

• Simpler version: Skip building anything and just upload your handbook and vendor list to a regular ChatGPT conversation each time you need them. No setup time, but you re-upload every session and lose the saved instructions.
• Extended version: Build a second Custom GPT scoped to hiring, loaded with your job description templates, interview question sets, and reference-check questions, so hiring and general office policy don't compete for the same knowledge base.

What to Do Next

• This week: Build it with just your handbook and vendor list, and test it on the next real policy question that comes up.
• This month: Add your onboarding checklist and any SOPs you've written, and update the knowledge base any time a policy changes.
• Advanced: Once it's reliable, share it with your admin team so policy answers stay consistent no matter who's covering the front desk that day.

Advanced guide for office manager professionals. Requires a paid ChatGPT plan to build; staff can use the shared link on a free account. Interfaces for AI tools change often, so menu names and exact click paths may shift after this guide was written.