serafex

Overview · Work organization

Work organization in your business: the complete guide

To organize a team’s work, start by linking each request to a file, an owner and a next action. Seraf can help you find the context and prepare that action in the tools available to your account. Decisions, access and approvals must stay explicit. Here is a method to move from scattered conversations to follow-up that everyone can understand.

Two guides go deeper into this topic. See the series

Open planner, notebook and a tray of documents on a midnight blue desk
OverviewWork organization

Pinpoint a concrete problem before changing tools

“We’re just not organized” describes a feeling. To act, look instead for a specific moment where the work gets lost: an invoice is waiting for information, nobody knows which presentation to send, an appointment arrives without its documents, or a website correction stays buried in a conversation. This observation lets you choose a first process to clarify.

Take a recent request and retrace its path. Where did it arrive? Who read it? Which document was prepared? Who was supposed to approve it? What action is still waiting? The point is not to find someone to blame. You are looking for the place where information, a responsibility or a decision is missing. Also keep the steps that already work.

The Serafex Workspace platform brings together tools and an assistant around the context your account can access. It can support this organization, but choosing a tool does not define your team’s responsibilities for you. Before moving files or changing habits, write down the problem you want to solve and the result you expect.

A first objective can be very simple: find the right version of a document and know who is waiting for an answer. Avoid turning this first project into a reorganization of the whole business. A narrow scope lets you test your way of working and fix the rules that cause confusion.

Give each request an entry point and a next action

A request can arrive by email, during a meeting or in a conversation. The channel it comes through should not decide whether it gets followed up. Choose one place where the file can be found and note what was asked, with enough context. A title like “Presentation for the meeting” is better than an entry called “To do”. In a fictional six-person sign shop, which serves as the example throughout this guide, the entry becomes “Quote, outdoor sign for a bakery, request received by email on October 6”.

The next action must be observable. “Take care of the client” does not say what to prepare. “Confirm the billing address with the client” names a task and the information needed. For the sign shop, the first next action reads: “Get the storefront dimensions and a straight-on photo from the client”. If someone has to answer before the work can continue, name that wait. A blocked request does not become urgent just because it stays visible for a long time.

The daily organization and communications features can help you find the calendar, conversations and documents you have access to. What can be done with an email inbox depends on its connection and on the permissions granted. Check what is available before asking the assistant to act in a particular tool.

Keep the original message when it contains useful details, then write a short summary for follow-up. The summary should make the request understandable without replacing the proof of an amount, a deadline or an instruction. When information changes, make the change visible in the file concerned.

A document becomes hard to find when its name says nothing about its use, or when several versions circulate with no way to tell them apart. Set a simple convention: the file it belongs to, the type of document and its status. A presentation to review must be distinguishable from the version chosen for a meeting, even if the two documents look alike. In the fictional sign shop, “Bakery_Sign-quote_v3” names the file, the document type and the version; the tracking then shows whether this v3 is “Awaiting approval” or “Sent October 9”.

Your filing should match the questions your team actually asks. If the work always starts with a client’s name, use that as the entry point. If one project involves several contacts, specify where the shared file lives. There is no ideal folder structure for every business; a structure the people working in it understand is better than categories that are hard to maintain.

The guide to organizing your business documents goes further into filing, naming and taking over existing files. Start with the documents used in your priority process. Moving every archive at once often makes it harder to check what must stay accessible.

Before archiving or deleting invoices and supporting documents, also check how long they must be kept. Revenu Québec requires you to keep the records and supporting documents related to the GST and QST (new tab) for six years after the end of the last year they relate to, and longer in the event of an objection or appeal. Your accountant can confirm the other retention periods that apply to your business.

Finally, separate the document from the decision about it. A document sitting in the file is not necessarily approved. Note which version was reviewed, by whom and for what use. If a correction comes in afterward, the new version must go back through the approval the project requires instead of automatically inheriting the previous status.

One filed sheet remains loose; another is attached to its approval card, while a correction waits separately.
A filed document is not necessarily approved. Link the decision to the reviewed version, its approver and its purpose; a correction needs approval again.

Clarify responsibilities and work statuses

For each request, distinguish the person who prepares, the person who decides and the person who must receive the result. One person can play several roles, but expectations must stay clear. “The team is handling it” leaves a grey area when an answer or an approval is needed.

When files contain personal information, this division of roles also has legal weight. The Commission d’accès à l’information (new tab) (in French) reminds businesses that they must establish governance policies and practices that provide, among other things, for the roles and responsibilities of staff throughout the life cycle of that information, as well as rules for its retention and destruction. The complete guide to Law 25 for businesses details the person in charge, incidents and providers.

Choose statuses that describe the reality of the work. “To clarify” means a piece of information is missing. “In preparation” means someone is working on the result. “Awaiting approval” means a specific version is waiting for a decision. “Done” should match a defined end, for example a document delivered or a correction verified.

For invoices, contracts and client follow-up, information that commits the business needs particular attention. An amount suggested in a conversation must be confirmed before it is treated as an approved condition. Preparing a document does not replace checking its recipient, its content and the applicable terms. The guide to tracking your projects and invoicing separates the statuses of an invoice, from draft to payment received, and suggests a weekly review of projects and documents.

Avoid multiplying statuses if no one knows when to use them. A short rule is often enough: a file moves to “Awaiting approval” only when the version to review is accessible and the approver is named. When a file goes back to preparation, state the correction expected. The person who picks up the work must understand why the status changed.

Ask Seraf for help that fits the available context

A useful request to Seraf says what you want to prepare, from which information and within what limits. “Prepare the points to discuss at our meeting from this file” gives more direction than “Organize everything”. You can also specify the audience, the expected format and the questions still open.

Then check the answer against the documents in the file. The assistant can help you summarize, find a piece of information or prepare a proposal. Missing information does not become confirmed because it appears in a well-written sentence. Ask for a correction when a passage does not match your situation, and provide the missing fact when you know it.

The platform also gives you direct access to the available features, including the calendar. You don’t have to go through a conversation every time you want to look something up. Choose the path that suits your task: open a document, check an appointment or ask for a summary of several items you have access to.

Permissions and approvals frame what can be done. Preparing an email, reviewing it and sending it are separate steps. Likewise, a content proposal is not a publication. When an action commits you, make sure you understand what is ready, what still needs to be confirmed and the result actually obtained.

Move content forward without losing approvals

A presentation, an image and website copy can reuse the same information about your business. Keep a clear base for the facts: the services offered, the description of an offer and the approved brand elements. When several pieces are being prepared in parallel, this base helps you spot a contradiction before anything goes out.

The visual design and content creation area covers different formats depending on the agreed need. Specify the final format, its use and the person who reviews it. Content meant for a web page is not approved exactly like a meeting document: the reading context and the next expected action can differ.

The social media process calls for one more distinction. The platform’s Social space is currently in development, and social media plans are not available at this time. Preparing topics or gathering your visuals does not mean that scheduling or publishing is possible for your account.

For each piece, note the version, the feedback requested and the next step. “The text looks good to me” can still leave open the question of the visual or the publication date. A useful approval names what is accepted and what still needs to be checked. Connected tools and permissions then determine which actions are possible.

Loose proofs remain separate from the selected version clipped inside the tray.
An approval identifies the format, the version and what is accepted. Approved copy does not automatically approve its image or publication date.

Treat the website and SEO as specific files

A visibility need also deserves a clear file. “Redo the website” bundles very different decisions: explaining an offer, improving a page, fixing a link, changing a form or rethinking the whole structure. Start with the situation you observed and the pages involved before choosing the scale of the project.

The website, publishing and hosting services are defined according to that scope. Building the website and hosting it are separate offers. The guide to preparing a website redesign helps you inventory the content, the addresses to keep and the approvals needed before construction.

For SEO and online presence, separate the problem you observed from its assumed explanation. A page with few visits may call for a check of its content, of how it can be reached or of the data available. A serious diagnosis keeps the uncertainties visible instead of automatically blaming a single cause.

The guide to preparing an SEO audit helps you gather the useful pages and questions. SEO add-on plans are currently on hold. This commercial availability is separate from the tracking features and from the services an existing account has already chosen; the offer you accepted remains the reference for what has been committed.

Use a tracking table simple enough to keep up to date

The table below is a suggested working aid, not a copy of a Seraf screen. You can use it in whatever format suits your team. Its role is to make visible the information needed to pick up a file. Add a column only if it helps a real decision or action.

Field Question it answers Illustrative example
Request What do we want to obtain? Quote for a bakery’s outdoor sign
File and source Where can the facts be found? Client file, October 6 email, last year’s quote
Owner Who prepares the next step? Quotes lead
Next action What task moves it forward? Have the shop price the LED lighting
Status What is happening now? To clarify
Approval Who decides, on which version? Management, version 2
Deadline When is the result needed? Answer promised to the client by October 10
Result What record shows it is finished? Approved version, sent and filed with its date

Fill in a row with a real file. If you don’t know the approver or the deadline, keep that as a question to resolve. Don’t replace an uncertainty with a date picked just to fill the box. The table should help you see the gaps, not hide them.

Also plan how a file can be picked up during an absence. The person helping out temporarily must be able to read the request, find the document and identify the decision expected without guessing their colleague’s intentions. Tracking then becomes a way to pass on context, not just a personal task list. This handover must respect the access rights set for the file: making information easy to find does not justify making it accessible to the whole team. The Commission d’accès à l’information (new tab) (in French) makes this point for personal information: under the Act respecting the protection of personal information in the private sector, only authorized people for whom the information is necessary to perform their duties may have access to it.

You can test the table with two different situations, for example a presentation and a website correction. If a column changes meaning between the two, clarify its label or add suitable instructions. Still, keep the same distinction between request, preparation, approval and result. The vocabulary should help people pick up the work without forcing a false uniformity on different activities.

During a team check-in, look first at blocked requests and those waiting for a decision. Update the next action at the moment you change the status. If an entry is done, check that its result is easy to find. This check prevents a ticked box from being the only record of the work done.

Follow an example request, from message to result

Here is the fictional sign shop’s situation, designed to explain the method: it describes no Serafex client and no result. On October 6, a bakery asks by email for a quote for its outdoor sign. The base prices appear in a quote from last year, but the client also wants LED lighting that the shop has never priced for this model.

The quotes lead creates a tracking entry, links the email and the old quote to it, then writes the next action: have the shop price the lighting. As long as that price is missing, the file stays “To clarify”. Seraf can help spot the lines to update in the old quote, but it must not invent a price or a production time.

On October 8, the price is confirmed and version 2 moves to “Awaiting approval”. Management reviews the dimensions, prices, taxes and payment terms, then asks for the installation time to be corrected. Version 3 is approved the next day and sent to the client.

The end of the work corresponds to a record anyone can find: version 3, filed with its sending date. The tracking does not claim that the bakery will accept the quote. It shows which version went out, when, and what follow-up to plan if the answer is slow to come. Sending is not selling yet: this difference between work done and business result deserves to stay visible.

Four stages connect a request, missing information, an approved version and a send with a retained copy.
In the fictional example: request received, missing price confirmed, version corrected and approved, then sent with a record kept. A sent quote is not yet a sale.

Check access, plan and connections before expanding use

Once the method works on a first process, you can extend it to other needs. Before that, check the features available to the account and the services chosen. The list of what Serafex can do describes a scope of support; it does not prove that every service is included in every subscription.

The Serafex plans page presents the base offer, website creation quoted for your project and hosting offered as a separate service. Your current plan and its services can be viewed in the app’s Settings, in the wallet and subscription section. The account’s contracts and invoices complete this information when you need to check a commitment.

Connections can also limit an action. An email inbox, a data source or a publishing tool must be accessible with the necessary permissions. Seraf Browser and the Social space remain in development. Their restricted preview does not make them generally available to clients.

Your team’s access deserves the same rigour. For small and medium organizations, the Canadian Centre for Cyber Security (new tab) recommends giving each user a unique account rather than shared accounts, granting only the permissions their tasks require and managing the life cycle of accounts, since employees come and go. Before opening a new space to someone, note the role they should have there and who will remove their access when they leave.

Human support can help clarify how things work and how to set them up. Its scope is defined with your business. If a need goes beyond the current features or services, describe it so it can be assessed. Don’t build your new organization around an automation whose availability has not been confirmed.

Choose a first process and check what changed

Finish your preparation by choosing a request your team actually handles. It must be specific enough to be followed from start to finish: preparing a document, organizing a meeting, reworking a page or answering an administrative request. Don’t add every other topic to this first trial right away.

Before you start, check this short list:

  • The expected result is described in one sentence.
  • The useful sources are accessible to the people involved.
  • The owner and the approver are named.
  • The next action is concrete and its status is easy to understand.
  • The necessary access and the available features have been checked.
  • The end of the work corresponds to a record the team can find.

After the process, go back over the same questions. Can you find the right version? Do people know who is waiting for an answer? Was the promised result prepared and checked? These observations are more useful than a general impression of speed. They let you adjust a filing rule or a responsibility without changing the whole system.

You can then choose the next process to improve. Keep the habits that really help the team and remove the fields or steps that serve no decision. To clarify how it works and which services fit your situation, tell Serafex what you need.

Series · Work organization

Two guides to go further.

Each guide goes deeper into a project mentioned in this article. Pick the one that matches your next step.

  1. You’re reading · OverviewWork organization in your business: the complete guide16 min
  2. DocumentsOrganize your business documents as a team9 min
  3. Projects and invoicesTrack your projects and invoicing without mixing up the steps9 min
The whole series