# Company Secretarial Software for Multi-Entity Groups: Build a Board Pack That Preserves Context **Category:** COMPANY-SECRETARIAL **Author:** AI Assistant **Published:** 2026-11-03 **Read Time:** 10 min read ## Summary Board information must be decision-ready without erasing which legal entity, risk, contract or deal produced it. A practical group board-pack framework connects company secretarial work to GRC, contracts and M&A. ## Full Content Company secretarial software for a multi-entity group should help produce board information that is concise without stripping away context. A board pack must make clear which legal entity a matter concerns, where the information came from, what decision is requested and what remains uncertain. Entity-management tools focus on structures and statutory records; board-reporting tools focus on papers and decisions; filing directories describe submission functions. The open gap is a traceable line from the entity record to GRC exposure, contract dependency and M&A change, without pretending those are the same record. ![Distinct legal entities feeding attributed information into a board pack](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793696491548/images/c929226ecd5df810bb452f20adb53a4c2fc1c700c3687e88acda0503a2b2ceb5.jpeg) ## What the market scan covers, and what it misses For the query “company secretarial software for multi-entity groups”, the scan reviewed the Companies House software directory, Board Intelligence's entity-management and board-reporting material, Computershare's GEMS and BoardWorks pages and market comparison pages. The coverage falls into clear product categories. Companies House lists software that can file specified company information. Entity-management providers describe group records, structures, officers, deadlines and corporate events. Board portals and reporting vendors describe meeting materials, dashboards, collaboration and decision papers. Those categories matter, but the material often compares functions within one category. It is less explicit about preserving entity-level source and decision context when a board pack combines group risk, contract performance, governance events and acquisition integration. A consolidated dashboard can make a group easier to read. It can also make it harder to see which subsidiary owns the exposure, what source supports the claim and which board or committee has authority to decide. The official [Companies House software directory for company changes](https://www.gov.uk/software-company-changes) identifies filing functions such as incorporation, company changes and charges. A directory entry is useful evidence about a filing route, not an endorsement of a product as a complete board-governance or group decision platform. Vendor pages describe their own products and should be tested against the buying requirement. Do not compare a filing tool, an entity register and a board portal as if each is a substitute for the others. ## The board pack is an information chain, not a document bundle A useful pack lets directors understand the decision and trace its basis. That does not mean every source document belongs in the paper. It means the author must know the source, the relevant entity, the period covered, the owner and the limits of the information. The company secretary or governance team can coordinate how information is assembled, circulated and recorded. The accountable executive or subject-matter owner remains responsible for the accuracy and interpretation of their report. A board paper should not imply that a risk is controlled simply because a dashboard marks it green. Nor should it turn an overdue task into a legal conclusion without an assessment of the relevant facts and rules. - **Entity context:** name the company or companies affected and link the entity record. Do not let a parent-level summary hide the relevant subsidiary. - **Decision requested:** state what directors or a committee are being asked to decide and link the authority, agenda item and decision record. - **Source and period:** show where the data came from and the period it covers. A current status must not rest on stale information. - **Risk and control:** show the exposure, owner, response and uncertainty, linked to the GRC risk, control, action and evidence. - **Contract position:** identify the contracting entity, relevant provision and commercial status, linked to the agreement version and owner. - **Transaction impact:** identify the target, diligence finding, condition and integration status, linked to the deal record. - **Follow-up:** assign an owner and evidence expectation. Minutes without an operating owner do not deliver the action. ## A seven-step method for a decision-ready group pack ### 1. Start with the decision, not the slide template State the decision, assurance or challenge required. If the item is for information only, say so and explain why directors need it now. A pack should help a reader distinguish an approval request, a risk escalation, an update and a matter that needs further work. Do not bury the request in an appendix or make the reader infer it from a dashboard. ### 2. Identify the entity before summarising the group Name the legal entity or entities affected. If a risk applies across the group, identify the entities and explain the common control or dependency. If evidence comes from a subsidiary, do not silently present it as if it were verified across the whole group. Keep the origin, scope and coverage visible. ### 3. Record source, owner and reporting period Every material chart or statement should have an accountable owner and a clear period. Link to the source record or explain the method used to produce the summary. Record whether information is confirmed, estimated, incomplete or awaiting review. A polished graph is not a substitute for provenance. ### 4. Separate fact, judgement and proposal Mark what has been observed, what has been assessed and what management proposes. For example, a supplier missed a reported milestone is a fact to verify; the likelihood of service interruption is an assessment; a proposed change to the contract is an action requiring approval. Keeping those layers distinct makes challenge more productive and reduces accidental overstatement. ### 5. Show the decision path and authority Identify the relevant board or committee, the approval required and any dependency on another decision. Where a matter concerns a subsidiary, distinguish the subsidiary's own record from a parent-level oversight view. Do not infer authority from a title or from the fact that a director sits on more than one board. Check the organisation's current approved arrangements. ### 6. Connect actions to owners and evidence An action in minutes should identify who will do what, by when and what evidence will show completion. Where the action is an operational control, assign it to the appropriate business owner. The governance record should retain the decision and follow-up without becoming a substitute for the team's working control record. ### 7. Close the loop in the next reporting cycle At the next relevant meeting, report what changed, what remains open and whether the original assumption still holds. Carry forward open decisions with their current owner and evidence. If the issue has materially changed, present the change rather than copying the previous status with a new date. ![A board secretary links distinct records to a clear decision and follow-up](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793696491548/images/58e6617fa2b4d60f2fc35a6460025b1b688db871580b26422ce17938e45fd934.jpeg) ![Distinct entity records converging into a board decision view](https://static.prod-images.emergentagent.com/jobs/sched-simplifi-daily-content-engine-1793696491548/images/1298c2996636953a8eb221db6ae39674ea6b8608afd7889f2ff6f52e35434943.jpeg) ## Consolidation without flattening the source A group view can be useful when it exposes common themes and dependencies. It becomes risky when it removes the record that explains who owns the matter. Preserve the underlying entity, source, period, owner and approval route even when the board sees a single summary. This principle is particularly important when companies share a supplier, system or service. The group may have a common operational exposure, but agreements can be held by different entities and controls can be owned by different teams. Show both the consolidated position and the material differences. If a risk rating is rolled up, explain the method and any missing entity data. Do not imply that a group average is the rating for each company. The same discipline applies to acquisition reporting. A target's documents and management representations are not automatically equivalent to verified group records. Mark diligence evidence, post-completion decisions and integration actions separately. The board should be able to see which facts are confirmed, which are provisional and what decision is being requested. ## Make the platform connection explicit ### Company secretarial: maintain the entity and decision context The company secretarial record anchors the legal entity, relevant officers, board meeting, paper, decision and follow-up. It should help a reader see where an event belongs and which record supports the decision. The company secretary coordinates governance process; subject owners remain accountable for their operational information. ### GRC: give the board a risk view with evidence and limitations Link the board paper to the risk, control, owner, evidence and remediation record. State the assessment period and any gaps. A GRC dashboard can support oversight, but the board still needs a clear explanation of uncertainty and the action requested. ### Contracts: show the agreement and entity behind commercial exposure A material supplier issue should point to the agreement, its contracting entity, the contract owner and the relevant operational evidence. Keep an internal risk assessment distinct from contractual interpretation. Where a decision might change the agreement, identify the required review and approval route. ### M&A: distinguish diligence from integration status A transaction paper should connect the target entity, finding, source material, condition and integration workstream. Keep the deal record and operating-company record linked but distinguish them. A planned task is not a completed action; a diligence observation is not automatically a verified post-close fact. ## Where Simplif-i fits Simplif-i's [company secretarial solution](https://simplif-i.com/solutions/company-secretary) describes entity records, group structures, registers, filing deadline tracking, board packs, resolutions, votes, conflict declarations and follow-up actions. The page says board packs can draw on information already held in the platform, including risks, compliance status and project updates. It also states that Simplif-i reads Companies House data and tracks deadlines but does not submit filings or perform identity verification. Those limits should be included in any product comparison. The linked [GRC](https://simplif-i.com/solutions/grc), [contracts](https://simplif-i.com/solutions/contracts) and [M&A](https://simplif-i.com/solutions/ma) workspaces provide the cross-module context discussed above. ## Frequently asked questions ### Is a board portal the same as company secretarial software? No. A board portal may focus on meeting papers and director access. Company secretarial software may focus on entity records, governance events, registers, deadlines and filings. Products can overlap, but buyers should verify the functions, jurisdictional coverage and limits of the package being considered. ### What should a multi-entity board pack identify? At minimum, identify the entity concerned, decision requested, source, reporting period, owner, relevant risk or contract, uncertainty and follow-up. If the item covers several entities, say how the group summary was produced and where material differences remain. ### Does Companies House software directory listing mean a product is endorsed? The directory is a list of software routes for specified filing tasks. It does not establish that a product is endorsed as a complete governance platform. Check the official page and assess the supplier's wider scope separately. ### Should every subsidiary have a separate board pack? The right format depends on the group's governance model and what decisions are required. A consolidated pack can be efficient, but it should preserve the entity-specific source and decision context. Do not use a group summary to obscure which company's board needs to act. ### Can software decide whether information is board-ready? Software can organise records, generate views and support workflow. It cannot replace the accountable author's judgement, director challenge or legal and governance advice. Set clear review and approval steps. ### How do acquisition findings enter the board pack? Link each material finding to the target entity, evidence, uncertainty, decision or condition and proposed owner. Show whether it is still diligence, has been validated or has moved into an approved integration action. ## Sources - [Companies House, Software to register or file changes to a company](https://www.gov.uk/software-company-changes) - [Board Intelligence, Entity management software guide](https://www.boardintelligence.com/blog/what-is-entity-management-software-and-how-does-it-work) - [Board Intelligence, Board reporting software](https://www.boardintelligence.com/board-reporting-software) - [Computershare, Global Entity Management System](https://www.computershare.com/uk/business/entity-solutions/global-entity-management-system) - [Computershare, BoardWorks board management software](https://www.computershare.com/uk/business/entity-solutions/boardworks) - [Simplif-i, Company secretarial solution](https://simplif-i.com/solutions/company-secretary) - [Simplif-i, GRC solution](https://simplif-i.com/solutions/grc) - [Simplif-i, Contracts solution](https://simplif-i.com/solutions/contracts) - [Simplif-i, M&A solution](https://simplif-i.com/solutions/ma) --- Source: https://simplif-i.com/api/blog/readable/company-secretarial/company-secretarial-board-pack-entity-context-20261103 Web Version: https://simplif-i.com/blog/company-secretarial/company-secretarial-board-pack-entity-context-20261103 © Simplif-i - Unified Business Management Platform