Time response specifications
Time-domain design specifications define how a control system should behave after a change in input. They give you concrete, measurable targets for things like how fast the system responds, how much it oscillates, and how accurately it tracks a reference. Without these specs, controller design is just guesswork.
The core specifications are rise time, settling time, overshoot, and steady-state error. Each one captures a different aspect of performance, and they often trade off against each other. Making a system faster (shorter rise time) tends to increase overshoot, for example. The design challenge is finding controller parameters that satisfy all specs simultaneously.
Transient response of second-order systems
The transient response is the system's behavior during the initial period after an input change, before it reaches steady state. Second-order systems are the workhorse of control theory because many real physical systems (motors, spring-mass-dampers, RLC circuits) behave approximately as second-order, and the math is tractable enough to derive closed-form expressions for every design spec.
Standard second-order transfer function
The standard form is:
Two parameters control everything:
- (natural frequency): Sets the speed of the response. Higher means a faster system.
- (damping ratio): Controls how oscillatory the response is. It's dimensionless and determines whether the system rings, settles smoothly, or sluggishly creeps to its final value.
Damping ratio and natural frequency
The damping ratio describes how much energy the system dissipates relative to how much it stores. The natural frequency is the frequency at which the system would oscillate if there were zero damping (). Together, they fully determine the locations of the closed-loop poles:
The real part () governs how quickly oscillations decay. The imaginary part () governs the frequency of oscillation.
Effect of damping ratio on system response
The value of places the system into one of three regimes:
- Underdamped (): The response oscillates before settling. This is the most common case in control design because it offers the best balance of speed and accuracy.
- Critically damped (): The fastest response with no oscillation at all. The two poles are real and equal.
- Overdamped (): No oscillation, but the response is slower than the critically damped case. The two poles are real and distinct.
Most control design targets an underdamped response with somewhere between 0.4 and 0.8, depending on how much overshoot is acceptable.
Overshoot vs damping ratio
Percent overshoot () measures how far the response exceeds its final value at the peak. For an underdamped second-order system with a step input:
As increases, overshoot decreases. A damping ratio of gives about 16.3% overshoot, while gives about 4.3%. If you're given a maximum overshoot spec, you can invert this formula to find the minimum required .
Settling time vs damping ratio
Settling time () is the time for the response to stay within a tolerance band around the final value. For a 2% tolerance band:
For a 5% band, use instead. Notice that settling time depends on the product , which is just the magnitude of the real part of the poles. To reduce settling time, you need the poles further left in the s-plane.
Rise time vs damping ratio
Rise time () is the time for the response to go from 10% to 90% of its final value. A common approximation for underdamped systems:
Rise time depends primarily on , not . Higher natural frequency means faster rise time. However, increasing to get a faster rise time also affects settling time and overshoot, so you can't tune it in isolation.
Peak time vs damping ratio
Peak time () is the time at which the response hits its first (and largest) peak:
The denominator is the damped frequency . As increases toward 1, the damped frequency decreases and peak time increases. As decreases toward 0, the peak comes sooner but the overshoot gets worse.
Steady-state error
Steady-state error () is the difference between the desired output and the actual output as . It tells you how accurately the system tracks a reference signal in the long run. A system might have great transient behavior but still fail to reach the correct final value.
The steady-state error depends on two things: the system type (number of integrators in the open-loop transfer function) and the type of input (step, ramp, or parabolic).
Position error constant
The position error constant applies to step inputs:
If (which happens when there's at least one integrator in ), the steady-state error for a step input is zero.
Velocity error constant
The velocity error constant applies to ramp inputs:
A Type 0 system has , meaning infinite steady-state error for a ramp. You need at least a Type 1 system (one integrator) to get a finite ramp error.

Acceleration error constant
The acceleration error constant applies to parabolic inputs:
You need at least a Type 2 system (two integrators) to track a parabolic input with finite error.
System type and steady-state error
The system type equals the number of pure integrators (poles at ) in the open-loop transfer function . Here's how type relates to tracking ability:
- Type 0: Finite . Tracks step inputs with a constant (nonzero) error. Infinite error for ramp and parabolic inputs.
- Type 1: , finite . Zero error for step inputs, constant error for ramp inputs, infinite error for parabolic inputs.
- Type 2: , , finite . Zero error for step and ramp inputs, constant error for parabolic inputs.
A common mistake is thinking you can just add integrators to eliminate all error. Each added integrator makes the system harder to stabilize.
Dominant poles and time-domain specifications
Real systems often have more than two poles, but the transient response is usually shaped most strongly by the poles closest to the imaginary axis. These are the dominant poles, and they let you use second-order approximations even for higher-order systems.
Dominant vs non-dominant poles
- Dominant poles are the closed-loop poles closest to the imaginary axis. Their transient modes decay the slowest, so they dominate the visible response.
- Non-dominant poles are further left in the s-plane. Their associated transient modes decay much faster and contribute little to the overall response.
A common rule of thumb: if a non-dominant pole is at least 5 to 10 times further from the imaginary axis than the dominant poles, its effect can be neglected.
Second-order approximation
When a higher-order system has a pair of complex conjugate dominant poles and all other poles are far to the left, you can approximate the system as second-order using only the dominant poles. This lets you apply all the standard second-order formulas (, , , ) directly.
The approximation works well when non-dominant poles are much further from the imaginary axis and when there are no zeros near the dominant poles. Zeros near the dominant poles can significantly alter the transient response and invalidate the approximation.
Dominant poles and transient response
The location of the dominant poles in the s-plane maps directly to transient specs:
- The real part () controls the exponential decay rate, which determines settling time: .
- The imaginary part () controls the oscillation frequency, which determines peak time: .
- The angle from the negative real axis corresponds to , which determines overshoot.
By specifying desired values for overshoot and settling time, you can compute the required pole locations and then design a controller to place the closed-loop poles there.
Time-domain design using root locus
The root locus is a graphical tool that shows how closed-loop pole locations move as a parameter (typically the loop gain ) varies from 0 to . It connects open-loop characteristics to closed-loop performance and is one of the most practical design methods in classical control.
Root locus review
- The locus starts at the open-loop poles (when ) and ends at the open-loop zeros or at infinity (as ).
- Branches on the real axis exist to the left of an odd number of real-axis open-loop poles and zeros.
- The root locus tells you at a glance which gain values produce stable, underdamped, overdamped, or unstable closed-loop behavior.
Selecting closed-loop pole locations
Given your time-domain specs, convert them into a target region in the s-plane:
- From the overshoot spec, compute the minimum . This defines a pair of radial lines from the origin.
- From the settling time spec, compute the minimum . This defines a vertical line in the left half-plane.
- From the rise time or peak time spec, compute the minimum . This defines a circle centered at the origin.
The intersection of these regions is where the desired dominant poles should be placed. You then look for a gain that puts the root locus branches through (or near) that target region.
Designing controllers for time-domain specs
If simple gain adjustment can't place the poles where you need them (the root locus doesn't pass through the target region), you'll need to reshape the locus with a compensator:
- Lead compensator: Adds a zero-pole pair that pulls the locus toward the left half-plane, increasing phase margin and improving transient response.
- Lag compensator: Adds a zero-pole pair near the origin that boosts low-frequency gain, reducing steady-state error without significantly affecting transient behavior.
- Lead-lag compensator: Combines both effects when you need to improve both transient response and steady-state accuracy.
The required gain at the desired pole location is found using the magnitude condition of the root locus.
Time-domain design using frequency response
Frequency response methods (Bode plots, Nyquist plots) offer an alternative path to meeting time-domain specs. They're especially useful when you have experimental frequency response data or when you need to assess robustness to model uncertainty.

Frequency response review
The frequency response describes how a system amplifies or attenuates sinusoidal inputs at each frequency, and how much phase shift it introduces. Bode plots show magnitude (in dB) and phase (in degrees) versus frequency on a log scale. Nyquist plots show the same information as a polar curve in the complex plane.
Bandwidth and rise time
Bandwidth () is the frequency at which the closed-loop magnitude drops to dB below its DC value. It's inversely related to rise time:
A wider bandwidth means a faster system. If your rise time spec requires a certain speed, you can translate that into a minimum bandwidth requirement and then shape the frequency response accordingly.
Resonant peak and overshoot
The resonant peak () is the maximum of the closed-loop frequency response magnitude. A larger resonant peak corresponds to more overshoot in the step response. For a second-order system:
This only exists when . Keeping below a target value is equivalent to enforcing an overshoot limit.
Phase margin and stability
Phase margin () is measured at the gain crossover frequency (where the open-loop magnitude equals 0 dB). It equals the phase plus 180°:
A rough relationship between phase margin and damping ratio for second-order systems:
(for in degrees, valid roughly for )
Typical designs aim for a phase margin of 30° to 60°. More phase margin means less overshoot and more robustness to modeling errors.
Gain margin and stability
Gain margin () is measured at the phase crossover frequency (where the open-loop phase equals ). It's the reciprocal of the open-loop magnitude at that frequency:
Expressed in dB, a positive gain margin means the system is stable. Typical designs aim for at least 6 dB of gain margin, meaning the gain could increase by a factor of 2 before the system goes unstable.
Designing controllers for time-domain specs
Frequency-domain controller design involves reshaping the open-loop Bode plot to hit your targets:
- Lead compensator: Adds phase near the crossover frequency, increasing phase margin. This reduces overshoot and improves transient response.
- Lag compensator: Boosts gain at low frequencies without affecting the crossover region much, reducing steady-state error.
- Notch filter: Targets a specific resonant frequency to suppress the resonant peak and limit overshoot.
The key idea is that time-domain specs translate into frequency-domain requirements (bandwidth, phase margin, gain margin, resonant peak), and you shape the Bode plot to meet those requirements.
Time-domain design using state-space methods
State-space methods handle the same design problem from a different angle. Instead of working with transfer functions and frequency plots, you work directly with the system's differential equations. This approach scales naturally to multi-input, multi-output (MIMO) systems and gives you direct control over all closed-loop pole locations.
State-space representation review
The state-space form consists of:
- State equation:
- Output equation:
Here is the state vector, is the input, is the output, and , , , are matrices that define the system. The eigenvalues of are the open-loop poles. The state-space form is equivalent to the transfer function but more general, since it can represent systems that aren't easily described by a single transfer function.
Controllability and observability
Before designing a state-feedback controller, you need to verify two properties:
- Controllability: Can you drive the state from any initial condition to any final condition using the input? Check by computing the controllability matrix and verifying it has full rank.
- Observability: Can you determine the system's state from the output measurements? Check by computing the observability matrix and verifying it has full rank.
If the system isn't controllable, you can't place all poles arbitrarily. If it isn't observable, you can't build a full-state observer.
Pole placement using state feedback
With full-state feedback, the control law is:
This changes the closed-loop system matrix from to . The eigenvalues of are the closed-loop poles. If the system is controllable, you can choose to place these poles anywhere you want.
The design process:
- Convert your time-domain specs (overshoot, settling time, etc.) into desired pole locations.
- Compute the gain matrix such that matches those desired locations. Methods include Ackermann's formula or direct coefficient matching.
Observer design for state estimation
In practice, you rarely have access to all state variables. An observer (or Luenberger observer) estimates the states from the measured output:
The matrix is the observer gain. The estimation error dynamics are governed by , and if the system is observable, you can place the observer poles wherever you want by choosing .
A standard guideline is to make the observer poles 3 to 5 times faster than the controller poles, so the state estimates converge quickly and don't degrade the closed-loop performance.
Designing controllers for time-domain specs
The full state-space design procedure:
- Translate time-domain specs into desired closed-loop pole locations.
- Verify controllability and observability of the plant.
- Design the state feedback gain via pole placement to achieve the desired poles.
- If full state measurement isn't available, design an observer with gain to estimate the states (with observer poles faster than the controller poles).
- Combine the controller and observer. The separation principle guarantees that the controller and observer can be designed independently: the closed-loop poles are the union of the controller poles and the observer poles.
This approach is systematic and extends naturally to MIMO systems, which is a major advantage over classical transfer-function methods.