One configuration looks like this: The applicant enters the essentials (the subject, whether the decision is to be taken by written resolution or at a board meeting, the sponsoring director, the applicant, the entity concerned) and the document is generated from a template Legal has already approved. The resolution itself stays short: it records the subject and the formalities. The decision text and any supporting material, whether PDFs, presentations or contracts, travel with it as annexes, which is what lets a single approved template cover every subject.
From there the resolution follows the path set for it. The mandatory stages are already in place; the applicant only adds which functions need to see it — Legal, Finance, Tax, HR, or whoever else your delegation of authority names. Each approver receives the resolution with all its annexes and has three ways to respond: approve; approve with conditions, written in free text and carried forward with the resolution; or reject, with a reason. A rejection goes straight back to the applicant, who decides what happens next: proceed and let the next stage weigh the objection, or start a new draft that reopens the resolution and returns it to every reviewing function. Every version, decision and condition is kept. Those three options are the difference between a process that absorbs disagreement and one that stalls at it: a condition that would once have been an email to one person now travels with the resolution to everyone who decides after that point.
Once the reviewing functions have approved, the resolution goes for final legal review — usually the General Counsel or the Company Secretary — and, where configured, to the board itself before signature. For a written resolution, that last approval starts the signing step: the resolution and its annexes go to your e-signature tool, are routed to the required signatories and come back signed. Where the decision is to be taken at a meeting, the same process delivers a fully approved resolution to the next board meeting for adoption, and the minutes are drafted from it rather than written up from scratch, then adopted at the following meeting and signed by the chair. Either way the papers are filed under one consistent name and number and appear in the minute book with their own history: drafts, decisions, conditions, signatures. Directors' minutes have to be kept for at least ten years under section 248 of the Companies Act 2006, and this is where they are kept by default rather than on a shared drive that has to be searched. A dashboard shows every open item, the stage it has reached and who it is sitting with, and reminders and escalation handle approvers who do not respond.
Not every resolution needs the full board, and the workflow allows for that. Signing rules are held by resolution type, authority limit or subject matter — the director responsible for the area plus the HR lead for personnel matters below a set limit, for example — and the right signatories are applied automatically, so nobody has to work out who is authorised in this particular case and nobody signs who is not authorised to. The same goes for the two questions that decide whether a decision stands: whether the meeting was quorate, and whether an interested director declared and stayed out of the vote. Both are captured with the resolution rather than recalled afterwards. Rules like these tend to be well drafted and poorly applied, because they were never turned into a process. That is what changes here.
The process above is adapted to meet your specific requirements. Some organisations need only the short path, where authorised applicants submit and the directors approve or reject. Others run the full chain across several entities, with different signatory rules company by company. Which stages are mandatory, what the applicant may choose or how long someone has before a reminder goes out is all tailored to your requirements — set to your articles, your schedule of matters reserved and your delegation of authority.
