> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/start-here/what-schedulink-is.md). # What Schedulink is Studio management software for high-volume photography. What it does, and who it's for. Schedulink runs your whole volume photography operation in one place. The schools and leagues you work with, the jobs you shoot for them, your staff, your tasks and the emails that go out all live on the event they belong to, so everything about a shoot sits in one record. {% embed url="" %} A five-minute tour of Schedulink {% endembed %} ## Who it's for Studios shooting high volume: schools and districts, sports leagues and clubs, colleges, universities, dance studios, graduations. One job means hundreds of subjects, dozens of tasks, several photographers and a roster that needs chasing. Everyone at your studio works in it. Owners, coordinators, photographers, editors and front desk staff, each seeing the part of the job that belongs to them. The organisations you photograph for hear from you through the emails and forms Schedulink sends on your behalf, automatically, on the schedule you set. ## How the pieces fit together Six things, and they nest. **Accounts** are the organisations you photograph for: a school, a district, a league, a college. If you have forty schools on your books, you have forty accounts. **Contacts** are the people at them, like the office manager or the athletic director you deal with. **Events** are jobs. A picture day, a graduation, a team shoot. Every event belongs to an account. **Tasks** are the work a job needs, before and after the shoot. Culling, ID cards, roster chasing. Tasks usually belong to an event. **Employees** are your own team. You assign them to events on the Scheduling page. **Emails and forms** go out to your contacts automatically, triggered by the event and its date. **Templates** define the shape of all of it. Build an event template once, with its tasks and emails attached, and every job of that type generates the same way. That last one is the piece that makes the rest work, and it's worth getting right early. ## What to do next If you're new, read the Glossary so the words in the rest of these guides mean something, then work through Set up your studio. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://schedulink.io/help-center/start-here/what-schedulink-is.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.