A project manager calls to check on the status of an intervention. The technician sent photos via text, hours are on a paper sheet, the quote is in an email, and a part was noted in a truck logbook. The work might be done, but the file is not. Organizing documents by mandate allows you to put every piece of information in its place: with the client, the location, the tasks performed, and the costs to be invoiced.
For an SME managing field operations, this is not a matter of aesthetic filing. It is a way to avoid incomplete handovers, respond quickly to the client, and invoice what was actually executed. The mandate becomes the meeting point between the office, field teams, and administration.
Why organize documents by mandate rather than by type
Classifying all files into folders like "Photos," "Contracts," "Invoices," or "Reports" seems logical at first. The problem arises as soon as someone looks for the complete history of a client or an intervention. They have to open multiple folders, search through emails, and ask the team for clarification.
A classification by mandate reverses the logic. Instead of filing a document according to its nature, it is attached to the work to which it belongs. A mandate can be a work order, a project, a service ticket, an installation, a preventive maintenance task, or a client request. Regardless of the term used in your company, the important thing is that the entire team recognizes this work document.
Take an equipment maintenance company. For a client visit, the same mandate can bring together the initial request, site contact details, the list of equipment, tasks to be performed, before-and-after photos, technician hours, parts used, client signature, and notes necessary for the invoice. When the mandate is complete, no one has to reconstruct the story after the fact.
This model does not mean that all mandates must be identical. An excavation contractor does not have the same evidence to keep as a production agency or a property manager. The structure must follow your work method, not force your teams to adopt useless fields.
Defining what must live in each mandate
Before moving your files, start with a simple question: what information must be visible to execute, validate, and invoice a mandate without unnecessary follow-ups?
Basic elements are often the client, contact, address or work site, request description, person in charge, scheduled dates, and status. This information already provides a clear view of the activity. Then come the data specific to your trade: plans, permits, photos, readings, checklists, safety procedures, inspection reports, expenses, materials, or approvals.
It is better to limit mandatory fields at the start. If a technician has to fill out twenty boxes before starting, they will bypass the process. Ask only for what helps in making a decision, proving the work, or preparing the invoice. More detailed information can be added according to the type of mandate.
Making status a coordination tool
A good status is worth more than a folder whose name starts with "To be processed." It indicates what needs to happen next and who needs to act. For example, a mandate can move from "To be planned" to "In progress," then to "Waiting for parts," "Ready to validate," and "Ready to invoice."
These statuses must reflect your actual handovers. If the office waits for a signature before invoicing, this point must be visible. If a mandate blocked by site access requires client follow-up, it should not remain mixed with completed work. The status creates a readable work queue for each team.
Building a file that follows real work
The mandate should not become an archive updated at the end of the day. It must accompany the work while it is being done. That is where the difference is seen in the field.
When planning, the coordinator creates the mandate from a client request or an accepted quote. They assign people, set the deadline, and add useful instructions. The team thus arrives with the right context, without searching for the latest version of a document in an email chain.
During the intervention, employees add their hours, check off tasks, attach photos, and report unforeseen events in the same file. A photo of a problem discovered on-site is no longer isolated on an employee's phone: it is linked to the mandate, the location, and the client. If an approval is necessary, it is requested at the right time, with supporting documents in sight.
After the work, the manager validates what was done. They can check discrepancies between planned and actual work, confirm expenses, and return the file for correction if information is missing. The office then receives a mandate ready to be turned into an invoice, rather than a pile of notes to interpret.
Naming, searching, and finding without guessing
Even with a centralized platform, a naming convention remains useful for external documents. Vague names like "final report," "photo 1," or "new invoice" waste time as soon as they leave the context of the mandate.
Use a stable mandate identifier, followed by an explicit name. For example: "MT-2487 - Roof inspection report - 2026-08-16." The number protects against duplicates, the label explains the content, and the date helps when multiple versions exist. For photos, a short title like "MT-2487 - North wall crack before repair" is much more useful than a file generated by a phone.
Searching must also be thought out according to the questions your teams actually ask. Are they looking for a work order number, a client name, an address, equipment, a technician, or a status? If the information is entered only once in the mandate and used everywhere, it becomes findable without creating copies.
Avoiding the two most expensive traps
The first trap is centralizing files without centralizing action. A shared folder can contain all the PDFs in the world, but it won't tell you who needs to do what, what is blocking, or which hours are billable. Documents are necessary, but they must live with the tasks, exchanges, and validations.
The second trap is wanting to digitize the old mess as is. Reproducing a tree of fifty subfolders in a new tool does not solve the problem. Start with active documents and current mandates. Define a clear template, test it with a team, then adjust what slows down the work.
You must also decide what is worth keeping. Some documents are essential for compliance, warranty, or a claim. Others are only useful during execution. Your retention policy must take into account your obligations, contracts, and the real value of the information. Keeping everything indefinitely can complicate searching just as much as deleting too quickly.
Linking the mandate to invoicing without re-entry
It is often at the moment of invoicing that organizational flaws become visible. Are the hours complete? Have the materials been entered? Did the client approve the addition? Is the intervention description clear enough to justify the invoice? If this information is scattered, each invoice requires an investigation.
When a mandate brings together the executed work, the transition is much more direct: quote, work document, validation, invoice. Approved hours, authorized expenses, and parts used can feed the invoicing document without being retyped. This reduces omissions, accelerates sending, and gives the client an invoice that corresponds to what happened in the field.
This is the approach Sequentia applies by starting from the business document of each company. The work order or mandate becomes the central file, configurable according to your procedures, rather than a generic form imposed on your teams.
Starting small, then enforcing the single file
Change works when everyone understands the concrete gain. For the technician, fewer calls to find a photo or confirm an hour. For the coordinator, a real view of current mandates. For the administration, more complete files and fewer delayed invoices.
Choose a frequent mandate type, such as service calls or scheduled maintenance. Create a simple template, define the statuses, and test the complete path with a few users: creation, assignment, execution, validation, and invoicing. The irritants identified during this test are valuable. They show where your method needs to be clarified or where the tool needs to be adapted.
The right goal is not to have a perfect tree structure. It is to ensure that when a client calls or an invoice needs to go out, the person answering already has the complete file in front of them. When the mandate becomes your single source of truth, work advances less by searching for information and more by taking action.
