What Happens to a Request After Someone Hits "Submit"?

Picture a single request inside your institution. A citizen applies for a permit. An employee files an internal approval. A vendor sends in a document that needs a formal reply. From the outside, it looks simple: someone fills in a form, and eventually something comes back.

Inside the building, it is rarely that clean.

The request lands somewhere. A person picks it up, or doesn't. It gets forwarded by email, or printed and walked to another desk. Somewhere along the way it turns into official correspondence that has to be signed, logged, replied to on a deadline, and filed. And when an auditor later asks "who approved this, when did the reply go out, and where is it stored," the honest answer at a lot of organizations is a shrug and a search through inboxes.

This is the gap most institutions live with. Not a technology gap exactly. A handoff gap. The point where a structured request becomes official communication is where things slow down, go missing, and stop being traceable.

Two IT-Blocks platforms were built to close that gap from both ends, and they were built to work together. WFM captures and routes the request. CMS governs the correspondence it turns into and keeps the record. Here is how one request moves through both.

Step one: the request comes in, and it comes in clean

Most delays don't start in the approval stage. They start at data entry, when a form arrives half-filled, with the wrong attachment, or with a date typed in a format nobody downstream can use.

WFM, the IT-Blocks forms builder, stops that at the door. It replaces paper forms with digital ones that a non-technical administrator can build without writing code. The forms mirror the layout of the paper versions your staff and applicants already know, so there is nothing new to learn. More importantly, the data gets checked as it is entered.

The validation is specific, not generic. You can require an email field to actually look like an email. You can enforce a Gregorian or Hijri date. You can restrict a field to Arabic letters only, English only, numbers only, or numbers with decimals. You can set minimum and maximum character lengths, mark fields as required, and hide fields that don't apply. If someone starts a long application and gets interrupted, the save-and-resume function lets them come back and finish rather than starting over or submitting something incomplete. The result is a request that arrives ready to be processed, not one that bounces back three times before anyone can act on it. Everything happens in the browser. Nobody installs anything.

Step two: the request finds the right people, on its own

A clean form is only useful if it reaches the right desk. WFM routes each submission through the organization's internal workflow using rules the administrator sets, then tracks it every step of the way.

The person who submitted it can watch it move. They see whether their request is under review, accepted, pending information, or sent back for data correction, and they can search their own history by request number, type, status, or submission date. No phone calls to ask "where is my application." The status is just there.

On your side, requests are organized into a two-level structure of sections and the specific services under them. Each service carries its own form, its own required attachments, and even its own availability schedule, so a service can be open for submission only on the days and hours you choose. Access is governed by a role-based model: administrators build and restructure forms, define attachments, and approve incoming requests, while end users submit and track their own. Permissions are assigned by group, so people see and do exactly what their role allows and nothing more. At this point the request has been captured, checked, and routed. But plenty of requests don't end inside a workflow. They become something official.

Step three: the request becomes correspondence, and it gets a number that never lets go

Here is the handoff that usually breaks. A validated request often has to produce an official response: a formal approval, a signed decision, a reply that leaves the institution under its name. The moment that happens, you are no longer managing a workflow. You are managing correspondence, and correspondence has stricter rules.

CMS, the IT-Blocks Correspondence Management System, is built for exactly that moment. It shares the same organizational and user-role model as WFM, which is why the two fit together rather than sitting side by side. Managements, groups, and users are defined once, with a system administrator over the data lists and permissions, and system users working the day-to-day.

The first thing CMS does is give every piece of correspondence a single unified number the moment it is registered. That number can be printed as a barcode, so anyone with a reader can pull up the full correspondence, its attachments, and its entire path through the institution in one scan. From that point on, the reply your workflow produced is not a loose document. It is a tracked, numbered record. CMS handles both directions: incoming correspondence is registered with its classification, subject, sender details, how it arrived, and a reply-by date that puts it on the clock; outgoing correspondence is registered the same way. Either way, the item now carries a deadline the system watches for you.

This is the exact handoff most institutions struggle with. See how WFM and CMS close it together.

Explore WFM

Step four: nothing sits in the dark

Once correspondence is in CMS, it lands in an inbox structure designed so nothing gets lost between people. There is a General Inbox for a department that receives correspondence centrally, where a manager or assigned staff distribute items to the right person. There is a Personal Inbox for correspondence assigned to an individual. And there is a Task box that holds items an employee has not yet acted on, so unfinished work is always visible.

CMS then does something a shared email account can never do: it makes the state of every item obvious at a glance. Correspondence is colour-coded and flagged by case. Unread items are marked. Items that must be answered before their deadline are shown in distinctive colours, with a second colour to warn when the deadline is close. Rejected items, items under follow-up, and items deleted from a personal inbox each carry their own sign. Unread counts sit next to every box in the menu. An employee opening CMS in the morning can see, without searching, what is new, what is overdue, and what still needs a decision.

When someone acts, the options are the real actions correspondence requires, not a generic "forward." An employee can direct an item to one department or many at once, send a copy for information, and specify the exact action required from each recipient: study and give an opinion, prepare a memorandum, prepare a resolution, take necessary action, and so on. They can reply directly to the sender. They can reject an item, with a required reason, so it cannot simply vanish without explanation. They can set a follow-up on an item they have sent, so they are reminded to check what happened to it.

Step five: the record holds up when someone asks

This is where the whole point comes together.

For any piece of correspondence, CMS can print the full path: who sent it, who received it, what action each person took, how long it sat with each recipient, and the reply dates along the way. That printed path is meant to be handed to officials. It is, in plain terms, an audit trail that produces itself.

Underneath it, the documents are handled properly. CMS attaches and indexes files, scanned or electronic, using a built-in scanner tool that supports duplex scanning, automatic document feeding, and saving to standard formats like PDF and TIFF. It indexes each document by type, number, and page count so it can be retrieved in seconds. It links related correspondence together, so a reply is always connected to what it answers. And for permanent storage, departments create archive files that record not just the digital classification but the physical location too: room, cupboard, shelf. Security sits across all of it. Access to correspondence and its attachments is limited to the people involved. Download and print rights can be withheld from specific users. For integration, CMS connects with the content management systems institutions already run, including IBM FileNet, Microsoft SharePoint, and Oracle ECM.

And leadership is not left guessing. CMS includes an analytics dashboard that reports on the movement of correspondence, performance rates, and the ratio of completed to delayed tasks per user, filterable by month, week, department, or individual. A director can see where work is flowing and where it is stuck.

Why this pairing matters more here than almost anywhere

Put the two systems together and the full path is covered with no seam in the middle. WFM owns the intake and the internal journey. CMS owns the official communication, the deadline tracking, and the permanent record. The request never falls into the gap between them, because they were designed around the same structure and the same roles.

Across Egypt and Saudi Arabia, the pressure on institutions is not just to move faster. It is to be able to show their work. Vision 2030 and the wider push toward paperless government have made traceability a baseline expectation, not a nice-to-have. Regulators, auditors, and leadership all want the same thing: a clear, provable line from the moment a request arrived to the moment it was resolved and filed.

Manual processes cannot produce that line. An email chain is not an audit trail. A filing cabinet is not a search function. A shared inbox is not governance. A connected WFM and CMS deployment gives you the line, end to end, built by a team that has spent twenty-five years inside banks, ministries, and authorities in this exact region.

The honest test

Take one real request that matters to your institution. Follow it from the form to the final signed reply, and then to wherever that reply is stored today. Count the handoffs. Count how many of them leave a record you could print and hand to an auditor without flinching.

If the answer makes you uncomfortable, that discomfort is the business case.

We are happy to walk a real process from your organization through WFM and CMS and show you exactly where the gaps close. It is a short conversation, and it tends to be a clarifying one.

Frequently Asked Questions

The solution behind thisWFM — Workflow ManagementNo-code digital forms and routing that hand a clean, tracked request straight to CMS.