What is required under Article 28 of the Road Act? Three obligations that managers must keep in mind

Many practitioners who search for Article 28 of the Road Act have practical concerns such as, "I understand that a road ledger must be created, but as the administrator, what exactly and to what extent must I prepare?" and "When someone requests to inspect it, in what condition must it be for me to be able to explain it?" Article 28 of the Road Act requires road administrators to prepare and keep a road ledger for the roads they manage. It also states that the items to be recorded in the road ledger and the requirements regarding its preparation and safekeeping shall be prescribed by a ministerial ordinance of the Ministry of Land, Infrastructure, Transport and Tourism, and that a road administrator may not refuse a request to inspect the road ledger. ([e-Gov Laws][1])

This article explains how Article 28 of the Road Act should be understood in the field of road management by dividing it into three obligations that managers must grasp. The road ledger is linked to a wide range of information related to road management, such as route, road area, length, width, structure, major occupied objects, road appurtenances, and update history. However, the road ledger alone does not uniformly determine parcel boundaries, ownership, road classification under the Building Standards Act, or whether an occupancy permit can be granted. In responding to Article 28 of the Road Act, it is important to grasp the legal obligations and to be prepared to explain them while cross-checking with the site and related documents.

Table of Contents

• Article 28 of the Road Act forms the basis for road register management

• Obligation 1 Prepare the road register

• Obligation 2 Keep and maintain the road register so it can be managed

• Obligation 3 Maintain the road register in a state that allows responding to requests to view it

• Information that operational staff should check in the road register

• Understand the causes of discrepancies between the road register and the actual site

• Common mistakes likely to occur when complying with Article 28 of the Road Act

• Operational framework that managers should establish

• Summary Article 28 of the Road Act is the entry point to road management

Article 28 of the Road Act forms the basis for road ledger management

The core of Article 28 of the Road Act is that road administrators must prepare and maintain a road ledger and make it available when inspection is requested. The provision itself is concise, but in the practical work of road management the road ledger serves as the starting point for organizing and explaining basic information about roads. If the road ledger is not properly maintained, it becomes difficult to explain to stakeholders the road boundaries, routes, widths, lengths, structures, road appurtenances, and major items occupying the road.

The road ledger is not merely a drawing that shows the location of a road. Under the Enforcement Regulations of the Road Act, the road ledger is to be composed of records and drawings, and those records and drawings are to be prepared for each route. ([e-Gov Law Search][2]) In other words, the road ledger should be treated as a management document that combines records organized as text and numbers with drawings that indicate the road’s extent and positional relationships.

What is important in practice is not to let Article 28 of the Road Act be reduced to the mere formal claim that "it's sufficient to have a road register." Even if a register exists, if routes are not organized properly, if records are difficult to match with drawings, or if changes to designated areas or post-construction information have not been reflected, it becomes hard to use as an authoritative basis for road management. Road registers are required in a wide range of situations, including road occupation, boundary verification, road works, roadside development, maintenance and management, disaster recovery, and inquiries from residents.

On the other hand, the road register is not a document that alone determines all rights relationships or administrative decisions. Even if the road register organizes information on road areas and widths, that information by itself does not automatically determine land ownership, parcel boundaries, public-private boundaries, whether a road is treated as a road under the Building Standards Act, or whether an occupancy permit can be granted. In practice, professionals use the road register as a starting point and make judgments by cross-checking it with the cadastral map, land survey diagrams, boundary confirmation materials, certified route documents, area designation materials, past construction drawings, occupancy permit records, and on-site survey results.

Therefore, when reading Article 28 of the Road Act, it is important to distinguish between the statutory obligations and the practical management standards. Statutorily, the focus is on the compilation, storage, and responding to requests for inspection of the road ledger. What is required on the ground, however, is that the road ledger be searchable, explainable, usable for on-site verification, and in a state that allows tracing the history of changes. For road administrators, Article 28 of the Road Act is easier to understand if considered the basic rule for continuously maintaining road information.

Obligation 1: Prepare the Road Register

The first duty under Article 28 of the Road Act is to prepare a road register. Preparation does not simply mean producing paper drawings; it means organizing the necessary information about the roads under management and arranging it into a form that can be used as a road register. Under the Enforcement Regulations of the Road Act, the road register is composed of written records and drawings, so it is fundamental to have both the written records, which organize information in text and numerical form, and the drawings that indicate the road area and positional relationships. ([e-Gov Law Search][2])

In the records, information necessary to identify and manage a route is important, such as the type of road, the route name, the date of designation or approval of the route, the route’s start and end points, major intermediate localities, the sections and dates when they began service, the length, site area, minimum carriageway width, and an outline of major occupied properties. The enforcement regulations also prescribe the minimum items that must be recorded in the records. ([Aspic Japan][3]) When there are routes with similar names within the same area or when documents using an old route name remain, it is important to verify not only the route name but also the reference number, start and end points, length, area map, and related approval documents.

In drawings, it is required that positional information related to road management can be confirmed, such as road right-of-way, the shape of the roadbed, intersections, side ditches/gutters, slopes, sidewalks, bridges, drainage facilities, and road appurtenances. However, the accuracy and methods of representation in drawings may vary depending on the time of creation, scale, surveying methods, and the preparer’s standards. Older road ledger maps may not perfectly match current survey results or digital maps. When preparing drawings, it is necessary to understand what the drawing indicates, at what point in time the information applies, and which sources were used to create it.

What needs particular attention when preparing road registers is the mechanism for reflecting changes to the road. A road is not finished once it has been constructed. Widening, sidewalk construction, intersection improvements, side ditch repairs, bridge repairs, slope stabilization measures, disaster recovery, and adjustments of road limits accompanying roadside development are examples of changes in condition over time. Under the Enforcement Regulations of the Road Act, when there are changes to the matters recorded in the registers and drawings, they must be corrected promptly. ([e-Gov Law Search][2]) Even if as-built drawings and completion documents exist, if they are not reflected in the road register there is a risk that outdated information will be presented when responding to information requests or making occupancy decisions.

Also, when preparing the road register, it is important not to separate field inspection from document review. If the width shown on the drawings does not match features observable on site—such as the pavement edge, gutter, curb, boundary markers, retaining walls, or the toe of the slope—making a judgment based on only one source can lead to errors. It is necessary to sort out whether the site has changed, the drawings are outdated, the designated road area differs from the apparent paved area, or structures on private land are affecting the road. The road register is a document that explains the site, but it is not a universal resource for making judgments without actually seeing the field.

In practical preparatory work, it is also important to standardize the granularity of materials. If one route has detailed drawings, another route only has old drawings, and yet another route has unorganized construction histories, differences in judgment will arise even within the road management authority. It may be difficult to bring all routes to a complete state at once, but it is practical to prioritize organizing routes that are frequently viewed or subject to inquiries, sections with many occupancies or developments, locations prone to boundary negotiations, and sections where road improvements were carried out in the past.

When preparing a road register in response to Article 28 of the Road Act, the ultimate objective is not simply the fact that documents were produced, but to make those documents usable for road management. It is the basic stance expected of administrators that records and drawings correspond for each route, that the relevant section can be located when necessary, and that the relationship with the actual site can be explained.

Obligation 2 Ensure the road ledger is kept in a condition that allows it to be stored and managed

The second obligation under Article 28 of the Road Act is to keep the road ledger. If you look only at the word "keep," it may seem to mean merely storing the created road ledger so it will not be lost. However, in practice mere storage is not sufficient. Because the road ledger is reference material used for viewing, inquiries, design, inspection, consultations, and internal confirmations, it must be kept in a condition that allows it to be retrieved when needed, its contents to be checked, and its update status to be explained.

If paper road ledgers are being stored, problems such as deterioration of the originals, damage to drawings, unclear replacement histories, and storage locations known only to the responsible person tend to arise. Especially for roads that have been managed for many years, past revised drawings, road area change documents, as-built drawings, certified route documents, and boundary confirmation documents may be dispersed across multiple locations. In this situation, even if the road ledger itself remains, it becomes difficult to determine which materials are the most up-to-date and which drawings are being used for current management.

What is important in storage is to distinguish originals, copies, updated materials, and reference materials. If materials that are formally managed as the road ledger are mixed with reference drawings used in construction design, notes from field surveys, old area maps, and unfinalized consultation documents, there is a risk of responding based on incorrect materials. Road administrators need to separately manage materials made available for viewing, materials for internal verification, materials undergoing update work, and materials used to confirm past history, and clearly define the status of each.

Also, managing the change history of the road ledger is important. When there are changes such as modifications to road limits, the opening or closure of use, changes in width or structure, additions of bridges or road appurtenances, or the reorganization of records concerning major occupancy items, it is helpful to be able to trace when, based on which documents, and over what extent corrections were made so that subsequent inquiries can be handled more easily. It is desirable to record not only the update date but also the reason for the update, the supporting documents, the responsible department, the affected route, and the affected section, linking them together.

There are also points to watch when storing digitized road registers. Simply converting data to digital form does not automatically make management easier. If file naming is inconsistent, old and new versions are saved in the same location, or drawing data and record data are managed separately, searchability will not improve. In digitization, it is important to standardize management of route numbers, route names, management classifications, update dates, drawing numbers, applicable sections, and so on, and to create a state in which anyone can find the same document.

In storage arrangements, preparations for handling viewing requests are also indispensable. The road ledger is both an internal management document and a document that may be requested for inspection. When documents are inspected at the counter, it is necessary to clarify which documents will be presented, how far individualized explanations will be provided, how the provision of copies and photography will be handled, and how to respond if old or reference materials are requested. Article 28 of the Road Act provides that requests for inspection cannot be refused, but when operating inspection procedures, attention must also be paid to document preservation, personal information, internal office procedures, and the relationship with rules established by each administrator. ([e-Gov Laws][1])

Storage is not mere preservation but maintaining road information in a continuously usable state. Safely keeping the road register, clearly identifying the latest version, enabling tracking of historical records, and ensuring that, even when personnel change, comparable judgments can be made—these are important practical measures for road managers.

Obligation 3: Ensure readiness to respond to access requests

The third obligation under Article 28 of the Road Act is to respond to requests to inspect the road ledger. The provision states that a road administrator may not refuse when asked to allow inspection of the road ledger. ([e-Gov Laws][1]) Roads are highly public facilities, and information about road areas and structures relates to roadside land use, construction, development, occupation, boundary confirmation, sales and purchases, and design. Therefore, it is important that the road ledger not only be kept internally but also be made available for external inspection.

When handling viewing requests, the first requirement is to enable the viewer to identify the location they wish to check. Because road registers are prepared by route, we search for the target route during inquiries using clues such as the address, lot number, landmarks, route name, intersection name, position from the start or end points, and vicinity maps. Since many viewers do not know the route name, the service counter needs a process to narrow down the target road based on location maps or guide maps.

When responding to requests to view the records, it is also important to be able to explain the contents and limitations of the road register. The width recorded in the road register may indicate the width as the road area or may serve as a clue for confirming the structural width. It can differ in meaning from the paved width visible on site, the passable width, the road frontage width that is an issue in building permit reviews, and the parcel boundary dealt with in boundary verifications. If a viewer looks only at the figures in the road register and uses them for a different purpose, there is a risk that differences in understanding will arise later.

Notably, people who consult the road ledger are not always specialists in road management. Their purposes vary: landowners, construction professionals, developers, surveyors, businesses preparing occupancy applications, nearby residents, and others. Therefore, road managers should take care to communicate clearly and appropriately that the road ledger is a fundamental resource for road management; that verification against on-site conditions and other statutory documents may be required; and that boundaries and rights relationships may need to be confirmed separately.

To facilitate smooth viewing procedures, how the road register is presented is also important. If it is unclear which line on the drawing indicates the road area, which symbols indicate road appurtenances or structures, or which items in the records indicate a route’s start and end points or its length, viewers will have difficulty extracting the information they need. If front-desk staff have to explain things individually each time, their burden increases. Organizing in advance explanations of terminology, viewing precautions, how to read the materials, and the information you want requesters to prepare will stabilize the quality of service.

On the other hand, agreeing to an inspection and guaranteeing the conclusion the requester wants on the spot are different. For example, even if someone looks at a road ledger and asks, “Can you build with this width?”, “Is this location the boundary between public and private land?”, or “Can this item be installed within the road?”, it may not be possible to determine the answer from the road ledger alone. Building, development, boundary determination, occupation (use), and construction execution may each require separate checks and procedures. Road administrators need to separate and explain what can be learned from the road ledger and what requires additional confirmation.

Responses to requests to view records are one of the parts of Article 28 of the Road Act that involve the greatest external contact. Even if the ledger is well organized, if explanations at the counter are unclear, misunderstandings and follow-up inquiries will increase. Conversely, even if the ledger contains outdated entries or changes that have not been reflected, if you can carefully explain the update status and the points to note, users will find it easier to understand which documents or procedures they should check next. In handling inspection requests, it is important not only to avoid hiding information but also to convey the meaning of the information correctly.

Information Field Staff Should Verify in the Road Ledger

When handling a road ledger under Article 28 of the Road Act in practice, first confirm which route the subject road corresponds to. The types of roads under the Road Act are expressways, national highways, prefectural roads, and municipal roads. ([e-Gov 法令検索][1]) If you misidentify which road fronts the subject site, the managing authority, the contact for confirmation, and the required documents will change. The first step is to check the route name, route number, start point, end point, and main intermediate locations, and identify which management records include the relevant section.

Next to check is the road area. The road area is important when considering the scope that falls under road management. The area paved on site does not necessarily coincide with the legally designated road area. Ditches, slopes, sidewalks, planting strips, retaining walls, drainage facilities, and so on may be included in the road area. Conversely, places that look and are used like roads may not be organized as road areas under the Road Act. When reviewing the road register, you need to carefully read the area indications on the register, not rely solely on the site appearance.

Confirming the width is also important. The widths recorded in the road register may be referenced when making decisions about road management, design, occupancy, and roadside use. However, width can have different meanings depending on context, such as the width of the road area, carriageway width, sidewalk width, effective width, and current width. Rather than using the figures in the register for other purposes as-is, it is important to confirm which width they indicate.

Checking lengths and sections is also essential. Because the road ledger is created for each route, you need to determine which section the target location falls into. If road improvements or zone changes have been carried out in only some sections, the width and structure can vary even within the same route. If you assume conditions are uniform from the starting point to the end point, you risk referring to information for a different section than the target location.

Information about road structures is also important in practical work. Carriageways, sidewalks, side ditches, drainage facilities, bridges, slopes, retaining walls, intersections, and road appurtenances are involved in maintenance, construction planning, and occupancy decisions. Even if the locations of structures can be confirmed on road ledger maps, they may have been renovated, removed, or newly installed on site. It is prudent to grasp the general outline of structures from the ledger and, as needed, perform on-site verification and review related construction documents.

Attention is also required for information on major occupancies and underground buried utilities. Within the roadway, various facilities may be involved, such as water and sewer, gas, power, communications, signs, lighting, signboards, driveways, drainage pipes, and so on. Even if the road ledger organizes an overview of the major occupancies, it does not necessarily allow you to grasp the detailed positions, depths, pipe diameters, managers, or the latest relocation status required for construction. When considering excavation or occupancy, in addition to checking the ledger, it is necessary to make inquiries to the occupiers, conduct on-site surveys, and review related documents.

When practitioners consult the road ledger, it is important not to extract a single figure but to review together the route, area, width, length, structure, timing of renewal, and on-site conditions. The road ledger is a record that links the basic information used in road management. For individual applications and consultations, it is appropriate to use it as an entry point for proceeding to any necessary additional checks.

Understanding the Causes of Discrepancies Between Road Registers and On-site Conditions

A common problem in practical work involving road ledgers is discrepancies between the ledger and on-site conditions. When someone consults a road ledger and visits the site, they may find that the lines on the plan do not align with the actual locations of structures, the recorded width differs from the width measured in the field, private-property structures exist where the area was thought to be road right-of-way, or there are gutters or pavements not shown in the ledger; these do not necessarily mean that the ledger itself is simply incorrect.

One cause of discrepancies is the difference in timing when road improvements or renovations are reflected. Even if construction is complete on site, its reflection in the road ledger may occur at a later date. If the ledger is updated only after as-built drawings, inspection documents, district change documents, and documents related to the commencement of use have been organized, a time lag arises between the field and the ledger. Conversely, there are also cases where planned changes are organized in the ledger while construction on site is still in progress.

Differences in old survey results and drawing accuracy can also be a cause. Road ledger maps created in the past are not necessarily produced with the same level of accuracy as current surveying instruments or digital maps. During the process of reproducing, rescaling, scanning, and digitizing paper drawings, line thickness and distortions of the drawings can occur. Therefore, when road ledger maps are overlaid on field survey results, positional discrepancies may arise.

The difference between the designated road area and actual on-site use is another point that is easy to overlook. The road area is an administrative management boundary and does not necessarily coincide with the parts that are paved or passable by vehicles on site. The road area may include unpaved sections, slopes, side ditches, and planting strips. Also, in some areas, due to long-standing patterns of use, parts that appear to be used as roads may not coincide with the management area defined under the Road Law.

The relationship with boundary documents is also complex. The road register is a document for road management, but it is not a document for directly determining parcel boundaries or ownership. When confirming public–private boundaries, not only the road register but also land survey maps, cadastral maps, boundary confirmation documents, past on-site meeting records, land acquisition documents, and on-site boundary markers are often checked comprehensively. Treating the lines in the road register as the land boundary as-is can lead to problems later.

Furthermore, on-site road conditions change daily. Pavement repairs, drainage-ditch cleaning, curb-lowering works, external works on adjacent private property, damage from disasters, temporary restorations, and road-occupying construction can alter the appearance of a road. It is also necessary to distinguish between changes that require corrections to the road register and minor changes related to maintenance. Because not all field changes are immediately reflected in the road register, it is important to assess the nature of any change when cross-checking the register against the actual site.

Assuming discrepancies between the register and the field makes operating the road register safer. The road register should not be viewed merely as right or wrong; it is a document to be used after organizing when the information dates from, what it is based on, and which aspects agree with or differ from conditions on site. It is important for road managers to have a system in place to verify the cause when discrepancies are found and, as necessary, to carry out corrections, add annotations, and organize related materials.

Common mistakes when complying with Article 28 of the Road Act

One common mistake when complying with Article 28 of the Road Act is assuming that there is no problem simply because a road ledger has been created. Even if a ledger exists, it becomes difficult to use in practice if it has not been updated and relies on outdated materials, the correspondence between records and drawings is unclear, route names remain under their old names, or field inspection results have not been reflected. A road ledger is not something you create once and finish with; it is a document that must be corrected and continuously managed in response to changes in the recorded items. ([e-Gov Law Search][2])

Another common mistake is being overly definitive when responding to viewing inquiries. When an inquirer asks, "Is this road width acceptable?", "Is this line the boundary?", or "Can a facility be placed here?", answering definitively based solely on the road ledger can later create inconsistencies with other laws or documents. It is safer to explain what can be confirmed in the road ledger while, as necessary, referring them to the responsible procedures for building, development, occupancy, or boundary confirmation.

Conversely, one should avoid being unduly reluctant when a request to inspect is made. Under Article 28 of the Road Act, a road administrator cannot refuse a request to inspect the road ledger. Of course, there are practical precautions such as the method of inspection, preservation of materials, personal information, provision of copies, and handling of unorganized materials. However, it is not appropriate to operate in a way that unduly restricts the road ledger inspection system itself. It is important to organize the scope of inspection, procedures, and precautions so that responses can be handled consistently. ([e-Gov Laws][1])

Insufficient version control of documents can also lead to major failures. If the drawing presented at the reception, the drawing reviewed internally, and the drawing referenced by the designer are different versions, explanations among stakeholders will conflict. Especially after digitization, old files can be duplicated and it may become unclear which one is the latest. You need to clearly define management of the latest version, the storage location of old versions, the update history, and the separation of view-only data.

There are also mistakes that confuse the role of the road register with other documents. The road register is a fundamental document for road management, but its role may differ from that of road area maps, designated route maps, boundary confirmation documents, as-built drawings, occupancy permit registers, bridge registers, pavement management records, and so on. Trying to explain everything using only the road register can result in missing information or decisions that are outside the intended purpose. It is important to link the necessary documents and separate references according to their intended use.

Not leaving a record of on-site verification is also problematic. Even if the person in charge is aware of discrepancies between the register and the site, if that awareness is not recorded, the next person in charge will repeat the same checks. Keeping concise records of on-site photos, measurement locations, verification date, verifier, affected routes, details of any doubts or issues, provisional judgments, and planned follow-up actions makes continuous management easier.

Compliance with Article 28 of the Road Act requires more than merely knowing the law. The basic obligations—to prepare registers, to store them, and to make them available for inspection—must be implemented in daily records management, on-site verification, handling inquiries, and correction work. Many failures stem less from the absence of documents than from not knowing how documents are classified or whether they are up to date.

Operational framework that administrators want to establish

To stabilize compliance with Article 28 of the Road Act, it is important for the managing authority to establish an internal operational framework for the road register. The first thing needed is to clarify the scope of responsibility for the road register. Departments related to roads—road management, construction, maintenance and repair, occupancy, boundaries, urban planning, building consultation, etc.—may be divided among multiple units. If it is not decided which department manages the original road register, which department provides update materials, and which department handles viewing requests, information will become dispersed.

You also need to clarify the procedures for corrections and updates. Decide who will check which documents and when updates will be reflected in the road register in cases such as completion of road construction, changes to the area, when a road is opened to traffic or decommissioned, when it becomes necessary to arrange major occupancy items, or when on-site verification reveals inconsistencies with the register. If the update entry point is not clearly defined, the site may change while only the register remains outdated.

Standardizing procedures for handling viewing requests is essential. Organizing the information to be collected at the counter, the materials to be presented, points to emphasize in explanations, cases in which responses should be put on hold, and cases that should be referred to other departments will reduce variation in how staff respond. For viewers, asking them to provide materials that show the location of the site, the lot number, a vicinity map, and the purpose of their inquiry makes it easier to identify the relevant route. It is important to structure the flow of explanation so that it is understandable even to those unfamiliar with how to read the road ledger.

From the perspective of data management, it is important to link information at the route level. Even if inspection records, drawings, construction histories, site photographs, update histories, and inquiry records exist separately, they become difficult to use in practice if they cannot be searched by the relevant route or section. It is desirable to standardize basic items such as route name, route number, drawing number, update year‑month, and management classification so that required materials can be found quickly.

It is also worth reviewing how on-site inspections are conducted. For updates to and access of the road ledger, it is effective to record the on-site conditions with photographs and location information. Recording the target points, road edges, gutters, boundary markers, structures, pavement edges, encroachments, and damage locations makes it easier to later compare them with drawings and reports. If records of on-site inspections remain only as individual notes, they are unlikely to support road management at the organizational level.

Also, when advancing the digitization of road registers, it is important not simply to convert paper into images but to consider searchability, updating, viewing, and integration with on-site inspections. Practical benefits come not only from being able to view drawings, but from being able to locate the relevant routes, link on-site photos and inspection records, track update histories, and extract materials for viewing. From the perspective of the purpose of Article 28 of the Road Act, it is also important to keep road registers in a condition that allows them to be used for management.

Finally, training personnel is also indispensable. Sharing the meaning of the road ledger, the difference between road areas and the actual roadway, how to read width measurements, points to note when responding to viewing requests, the relationship with boundaries and occupancy, and the documents to check during updates will make it easier to maintain response quality even when transfers or personnel changes occur. The road ledger is a highly specialized document, but because staff often handle it at service counters and in the field, it is important that responsible personnel understand the basic concepts.

Summary Article 28 of the Road Act serves as the entry point to road management

Under Article 28 of the Road Act, the obligations that administrators must meet are threefold: preparing the road ledger, keeping it, and responding when requests for inspection are made. The statutory text is concise, but in practice it leads to many tasks, such as preparing records and drawings, managing by route, reconciling with on-site conditions, preserving change histories, and standardizing responses to inspection requests. The road ledger is a fundamental document for road management and an important resource that also serves as the entry point for roadside use, occupation, boundary confirmation, construction planning, and maintenance management.

To operate the road register safely, it is also necessary to adopt an approach of not treating the register as an all-purpose document. The road register organizes basic information for road management, but it does not, on its own, determine land ownership, parcel boundaries, building-related decisions, or whether occupancy permits should be granted. It is important to conduct on-site inspections and cross-check related documents as needed, and to distinguish what can be determined from the road register from what requires separate verification.

For administrators, what matters is transforming the road register from "documents kept in storage" into "usable management information." If routes, areas, widths, structures, change histories, site photographs, and inquiry records are organized, the burden of responding to access requests is reduced and explanations to stakeholders become more consistent. Conversely, when documents are scattered, update histories are unclear, and the relationship to the actual site cannot be explained, formal compliance with Article 28 of the Road Act may be achieved, but practical operational risks remain.

In road management practice, records that link the ledger and the field are becoming increasingly important. By preserving the roadside, side ditches, structures, damage, encroachments, and conditions near boundaries confirmed on site together with location information, and making them cross-referenceable with the road ledger and related materials, it becomes easier to improve the accuracy of update work and responses to viewing requests. If Article 28 of the Road Act prompts a review of the preparation, storage, and access handling of the road ledger, it is effective to establish operations that can organize on-site records, document management, and update histories in an integrated manner.